Open larsbe opened 6 years ago
To visualize the history of the process evolution, we first have to make sure that we can store data and re-access it in later runs. I think this is out of scope, if we keep running the vPAV as JUnit test. But if someone has an idea how to actually do this inside a JUnit run, please comment :)
I'm not sure if we should run this as part of a unit test. The idea is that we connect to the repository (e.g. GitHub). Then we parse the change history and correlate changes to model elements. You don't necessarily need a data store for this to work, but something like a cache could be helpful, so that you don't have to retrieve the whole history everytime.
One of the outcomes of the Delphi study was that managing change in process automation projects is one of the major concerns of IT architects. In software projects the history of the VCS is a big help in tracking and reconstructing changes in a project. In process automation projects we have the process model that could be used to make the change history more accessible.
If we scan the VCS repository of the project, we could link changes to specific model elements and provide a view on the model to further inspect them, e.g. we could easily show when an element was changed for the last time or where changes occur frequently.
This feature doesn't build on top of validations and consistency checks of vPAV. Therefore, it needs to be discussed whether to integrate it into vPAV or develop a separate solution.