Deployment of Enterprise Architect

[Srikanth]

This is in reference to the Deployment of Enterprise Architect white paper downloaded from http://www.sparxsystems.com/resources/whitepapers/index.html

As suggested in that document, we would like to implement the Multiple Project – One Repository Model. But we are unable to create such a scenario using Spark EA.

What we have been able to achieve is multiple “Models”: in a single project file (*.EAP) thus making it impossible for us associate user groups to each models which we want to achieve.

My Questions are  

How do achieve the scenario as mentioned in the White Paper. ?

How can we associate a user level rights to a model/element created ?

[peter.zrnko]

How can we associate a user level rights to a model/element created ?

In order to use User Level Rights you need to Enable Security in your project. This is appropriate for models without Version controlled packages.

[Srikanth]

I have enabled User Level Security ...   ...but how do i assosiate user rights to models or elements created ...

for example .... i have a Project with Mutiple Models in it ...i would like to setup user level security for the project at model level ... i would want to allow a set of users complete access to a model ..provide Read only to another and No Aceess to another...

PLease advise how to go about achieving this  

[RoyC]

Perhaps you could read through this section of the online EA User Guide:

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

This should tell you how to assign access rights to individual users and groups of users, and more besides.

You can't assign read-only rights to users - you can rights to perform specific tasks on selected elements or packages, assign no rights at all, or asign rights to do everything possible.

You can use a read-only version of enterprise Architect though, which enables people to review your project without changing anything in it.

[Srikanth]

"You can't assign read-only rights to users - you can rights to perform specific tasks on selected elements or packages, assign no rights at all, or asign rights to do everything possible. "

Thanks a Lot for your input Roy.

But Unfortunately i could not find a Mechanism to assosiate specific rights to selected element or package. Would be helpful if you can help me achieve the same.

[RoyC]

Actually, I don't think that what you want is the same thing as what EA Security does.

Security has two modes - require user lock to edit, and (effectively) unlock item to edit. In the second mode, you can select a package and set a lock that prevents anyone other than the specified user or group from editing the:

• Package and all its contents

• Package, but they can edit diagrams

• Package, but they can edit child packages

• Package, but they can edit elements (not very effective by itself)

So that gives you some control over edit access to specific packages. But it isn't setting the range of access permissions on specific packages and elements.

[rdhupar]

hi guys,

i am trying to achieve the same thing (being able to control packages and elements individually via EA's Security) and based on my understanding this is not possible presently with EA. What I would like to know is that if EA is planning to launch such a feature in the present future? Maybe an EA Administrator will be able to assist.

Regards

[Geert Bellekens]

There is actually a workaround through a VC system:

- Setup EA with an integration to a VC system
- Setup the desired security (which people have the right to edit) in the VC system.
- Enable EA user security
- Set the option "require user lock to edit"

Now if the integration works like it should (which isn't always the case) EA will suggest to lock a package when checking in out. When checking in it will suggest to unlock it. (you still have to click "OK")
That was the way we set it up back then.
If I remember correctly the EA user security with "require user lock to edit" was only necesarry because of a bug in the VC interface (VC side). So If you're lucky you don't even need to setup EA user security, only version control.