Disappearing scenario's...

[Tom G]

Sometimes we lose use case scenario's... At the moment we have no clue when or why they disappear because it does not happen all the time - are we lucky !? The big problem is, you don't notice it immediately.

Our situation is:
- build 818 professional using EAP files
- version control via VSS (and different settings for packages in the same project)
- 2 or 3 people working on the same (version controlled) package of a project

It seems to be linked to the import/export of the xmi files for version control / locking.

Does anyone have similar problems ? Any idea how to prevent such problems ?

Kr,
Tom

[gpc]

Hi Tom,

Are you using the private or shared model of version control?
If you have a number of packages, make sure that you are using a 'local' instance of elements for diagrams within a package - this caught us out a few times (i.e. don't have a diagram in one package using a link to an element in another package).

[Tom G]

Hey
Thanks for your reply.

We are using private models (each user has his own copy). True, you have to watch out when you use links to elements in other packages. We can't prevent it, luckily the influence is only on the diagram itself not on the elements (the links don't actually disappear, the elements are simply removed from the diagram) Personally I think this is a serious problem. Don't know if Sparx is going to do something about it. Anyway it makes sharing models and reusing elements quite hard, but at least you don't lose information.

In this case - the disappearing use case scenario's - we actually lose information. The scenario's are really gone from the repository, so no way of getting them back. If we can't pinpoint when or why this happens it makes EA very untrustworthy.