Working with multiple versions of a model

[OpenIT Solutions]

Hi,

I need some best practice advice. We have a large user base of business process modellers. We took the decision to only use a centralised db and built in baselines for our model (as most modellers struggled with the concept of integrated version control and the additional managment steps in entails).

We have a small subset of modellers that need to work on multiple versions of the model. As we use baselines to create versions - this is straight forward. They just baseline their current work and select a previous baseline to work on. The problem is that because we are using a shared db - all users then see the selected baseline. Most users actually want to keep working with the current version.

I did think of setting up version control for the small subset that want to view multiple versions - the problem is that version control flags/data are stored in the shared db - so all users will be asked to configure version control when they connect to the shared model- is there a way around this ?

Any other suggestions / workarounds much appreciated

Thanks,

Jon.

[Geert Bellekens]

Jon,

We have the same situation more or less.
We have a small subset of rootnodes in our central db that are version controlled, and only a handfull users ever need to be able to check-in or -out.

We used to train our users to just click 'No' when EA asked them to complete the version control settings, and I asked Sparx to include an option to "never ask again" when starting up.

Recently (I don't remember which version exactly, something like 8.x I think) they have added that checkbox to the annoying popup at startup.

So that solves the problem of the popup.
But then, if you are absolutely sure you need to work on different branches, you'll have no choice but to use another db (or local .eap files) for your other branches.
Afterwards you'll then have to merge the branches with the main trunk (which is a royal PITA)

Geert

[OpenIT Solutions]

Thanks Geert.