Multi-user and DBMS in EA

[netripper]

Hi,

We're attempting to perform some tests with the Enterprise Architect model in a DBMS. We have currently deployed a MySQL server, ran the appropriate script to create the tables and transferred an EA model.

We own a Corporate edition of EA.

I have three questions regarding this situation.

1) The manual specifies the following:

* Registered users can obtain the scripts from the Registered Corporate Edition resources page of the Sparx Systems website at http://www.sparxsystems.com.au/registered/reg_ea_corp_ed.html
* Trial users can obtain the scripts from the Corporate Edition Resources page of the Sparx Systems website at http://www.sparxsystems.com.au/resources/corporate/

Is there a difference between the trial and registered scripts?

2) How is locking provided in diagrams?

Imagine this situation: two designers are working in the same diagram, both edit the diagram, user 1 saves the diagram, user 2 saves the diagram afer that. In my experience the save user 2 performs **silently** overwrites the changes of user 1 (I have tested this). There is not even a warning that the diagram was changed in the meanwhile (like you have when you share a .EAP project).

Ideally, the moment one user makes a change in a diagram, the diagram becomes locked for other users. Is this possible?

3) We want to work with around 5 persons on one model. The model is large, but due to multiple persons working closely together on the same area, package locking (i.e. subversion) is not handy.

Are there any suggestions for working with multiple persons in a single diagram? Documents on the Sparx website I may have missed concerning working with multiple users?

Thanks in advance for your help.

[thomaskilian]

1) Propably no difference (I guess). EAUI
2) Only per package. Locked elements can't be changed
3) Try searching the forum. There are a lot discussions related to this topic (I know, searching is a PITA)

[netripper]

Thanks for your response. We were hoping any locking or other advanced features might be available if the 'registered' scripts were used.

We have used package locking, but that didn't quite work in our situation as we're working together on a pretty fine level; we'd have to make a (versioning) package of each use-case just to provide locking.

I've seen it's possible to lock elements, manually, by using the Security features of a project. However, this isn't really ideal as well and in my opinion it takes more effort to do than just communicating what diagram a user is working on.

Also I have tried searching the forum a bit but didn't find any solutions besides locking by using versioned packages or using the Security feature.

If anyone still knows other ways to use locking in models on diagram level (preferably), please let me know.

[thomaskilian]

Not really an answer, but communicating over the built-in forum might help. That, however, might also be the place where the cat bites its tail :-/

I'm currently facing the task to share my work with multiple users. Up til now we only had forced distribution by me. But now (after several months (they managed to start a CVS server). I'll see how to get that running.

[peter.zrnko]

Ideally, the moment one user makes a change in a diagram, the diagram becomes locked for other users.

This would be a nice feature.


I just want to say, that using the Security feature it's possible to lock a diagram. It will lock all elements at that diagram also.

Look at the option "Require User Lock to Edit". Using this mode together with the diagram locking you will gain full security with not so much work.
Using this mode it's necessary to release locks as soon as possible. It could be managed in "View and Manage Locks" window.

[netripper]

Thanks for your reply. That sounds like a reasonable situation to work with. I'll give it a shot soon when I've got some more spare time.

Hadn't really played around with the Security settings yet as I was given the idea it'd be a hassle to get it working and you still wouldn't be forced to lock before editing (effectively being able to work without locking).