Team Collaboration

[Hugo]

OK I have some questions that stem from a desire to use the tool for a team in a (very) large organisation.

1. Can we set it up so that users have to login and users can be assigned a role like Analyst, etc

2. Is there a way to secure a model and/or parts of a model so that only certain roles can edit certain aspects of a model?

3. How can we have version control so that we have an audit trailed way of getting at previous models and seeing whats changed from one to the next?



Thx
Hugh

[thomaskilian]

1. Try Settings/People
2. Not sure. Maybe the Security feature (corporate edition) can handle that?
3. You might read more about baselining

[Hugo]

Well Settings/People certasinly lets me setup "people" but seems to have no "login" support.

I want users to "login" to EA as it were.

H

[Eve]

As Thomas said, look at the Corporate Edition of EA and the Security feature.  By itself it doesn't have roles.  But you could create a set of groups each with appropriate permissions for the roles and assign users into groups.

http://www.sparxsystems.com/EAUserGuide/index.html?usersecurity.htm

[Jan ´Bary´ Glas]

you could create a set of groups each with appropriate permissions for the roles and assign users into groups.
[/url]

That is what we do. We have differents view in repository allowed for different groups of users. We named them Business, Analysts, Designers,... Whatsmore every package has its owner - responsible user that has it locked and that unlocks it for use for asking.

[fowlesp]

I undrstand how EA Security setting can control access to the model, but what about version control.

Has anyone tried using CVS for this? EA seems to have "issues" with CVS, so is there another/better way?

[Eve]

What kind of "issues" are you having with EA and CVS?  I actually use it reguarly and don't have any problems with it.

[fowlesp]

Bearing in mind that we've just started using EA, so all this might be down to in-experience...

The main concern relates to model integrity.

When a model is placed under CVS and import into an EMPTY project by a second user (checking out the XML from CVS) we noticed that any images in the original model are lost (because they are not exported into the XML)

Also any links between model components can be broken (and converted to text entries).

Both issues have be acknowleded by Sparxs, and we have workarounds, but it does raise questions...

Having been through the documentation, and this forum,  I suspsect that the solution is to use a shared database for the model and CVS for the version control; but the immediate implication of this is again model integrity and how good  EA is at keeping the two model versions "in step"?

Obviously this solution is just a guess on my part, so if you have "real world" experience and any hints or tips I'd be interested to hear them...

[CapJo]

I have already made a suggestion for export / import bitmap images to xml.

Diagrams are exported to xml but images are lost in the diagrams.

I think this is not really a consistent behavior.

http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=suggestions;action=display;num=1158847177

[fowlesp]

Thanks for the information.

Looking at the other thread, I agree that this is inconsistent behavior, from a version control viewpoint then ideally the reference data should also be roundtripped in the same way as the model data.

With regards the images (specifically) then supporting external  images (with relative paths) from within the model could be a useful alternative.