![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to prevent users creating attributes & types Topic Summary: Created On: 31-Oct-2007 15:39 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Jim, You're doing everything right, yet users can still create attributes because of how DOORS is designed. I don't know why they designed DOORS this way, but really, creating and modifying attribute information should be an A function, not a C and M function. Baselines on modules, same thing. If a user has edit rights to a module, they can create a baseline. To me, only the A function should be able to do baselines. But to Telelogic, A only means the ability to assign rights and not do what is considered admin work (create baselines, attributes, etc). The answer to your question: user training. You can also police the database by writing scripts to check for non-standard attributes. | |
![]() |
|
For a user to be able to work in a module creating, editing and deleting objects they need RCMD rights; MD may be enabled using propagate access. But a user with those access rights can create new attributes and types in the module. By changing the access rights to Attribute Defs and Attribute Types, existing attributes can be protected from unnecessary changes, but how can users be prevented from adding new Types and Definitions?
TIA Jim ------------------------- Jim Backus<BR>Ultra Electronics, Controls |
|
![]() |
|
![]() |
|
Jim,
You're doing everything right, yet users can still create attributes because of how DOORS is designed. I don't know why they designed DOORS this way, but really, creating and modifying attribute information should be an A function, not a C and M function. Baselines on modules, same thing. If a user has edit rights to a module, they can create a baseline. To me, only the A function should be able to do baselines. But to Telelogic, A only means the ability to assign rights and not do what is considered admin work (create baselines, attributes, etc). The answer to your question: user training. You can also police the database by writing scripts to check for non-standard attributes. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
You can provide these folks 'R' access to the module. That will prevent them monkeying with module properties and attrbutes and types. You can then provide these folks perhaps RMC access to each level 1 object which will allow them to monkey with the objects.
Having said that, 'R' access to the module will cause the Edit and Shared module open commands to be greyed out; I hate it when that happens. Perhaps you can provide 'RM' to the module but then provide them 'R' to all existing attributes and types. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.