Hi all!

I’ve read many interesting discussions on the ‘versioning usage’ topic (best practice for AS IS and TO BE models, release management, etc.) but I found few information about “methological aspect” on ARIS documentation. Where can I find ARIS docs on this?

In my company, we are modeling our processes and we want to share and publish only the processes approved. So we have created two DBs: one available only to modelers (‘DB WIP’) and one published in ARIS Connect (‘DB Public’) available to viewers. Both DBs have the same structure and according to ARIS methology, they contain: a folder with objects library and a folder with the company map with sub-folders and sub-models (with two or three levels of dept).

When a model is approved, we want to “freeze” it and its sub-models approved in ‘DB WIP’ and to copy them in the ‘DB Public’. Our idea is to use versioning, so every time that a process is approved we must: (1) version the model approved in DB WIP; (2) Copy this model in DB Public (with merge, because import seems more complex for the previous versions); (3) and version the DB Public.

The disadvantage is that maintain two DBs and its versioning can be more complex. In fact, our doubt is that after two-three times there is an high probability to disallign the versioning between two DBs (for example, the DB WIB is to the 5° change list and the DB Public to the 3°).

According to yours ARIS experience, what do you think abut this method? Do you have any suggestion?

Sorry for longer post and thank you in advance!!

S.

Tags: ARIS ARIS Architect ARIS Connect