Show Posts
1
Suggestions and Requests / Re: EA 11 wishlist
« on: May 23, 2013, 07:09:25 am »
New feature requested: Record locking to control write access to packages
I have explored the current security control in Sparx EA and would like to propose minor changes that could lead to an increase usage flexibility that could allow large organisation to use Sparx EA with one single central repository without worrying about information being changed by the wrong people.
My proposition is to merge the functionality of both security mode and enhance it slightly in order to:
• Allow package owner to control who can modify the package user group locking and group membership,
• Allow members of that group to lock elements in order safely apply changes,
This would require additional permissions:
• Split “lock elements” into permissions
o For Package owner to set group permission to package,
o For Members to lock elements
It would require people with “Group Locking” permission to the dialog to manager group ownership (associate users to group).
The current security policies are not sufficient for large organisation to use one central repository.
I have explored the current security control in Sparx EA and would like to propose minor changes that could lead to an increase usage flexibility that could allow large organisation to use Sparx EA with one single central repository without worrying about information being changed by the wrong people.
My proposition is to merge the functionality of both security mode and enhance it slightly in order to:
• Allow package owner to control who can modify the package user group locking and group membership,
• Allow members of that group to lock elements in order safely apply changes,
This would require additional permissions:
• Split “lock elements” into permissions
o For Package owner to set group permission to package,
o For Members to lock elements
It would require people with “Group Locking” permission to the dialog to manager group ownership (associate users to group).
The current security policies are not sufficient for large organisation to use one central repository.