ARIS 98.7-Defining a simple Change control process
Currently got ARIS 98.7 set up with Designer connect on thin client. Just wanted some recommendations on designing a simple change control process.
So as an example modelers will have rw+c access to models, they submit a proposal. The QA person receives that proposal and either approves or rejects that proposal. The proposal may mean it was either an actual edit to the model or just some comments seeking a response.
If the QA person approves the changes he then runs the semantic/ structural checks, if these are okay..QA person re-versions and we then merge the database with the live db on a weekly basis.
Can anyone provide me with a simple example of how they manage the change control process?
Is there any difference using the ARIS change request process within Design connect (Person responsible attribute) and from within the ARIS architect/ designer thick client install.What does the 'Start governance' functionality do that is difference from within Designer connect.