![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Numbering Format Topic Summary: Definition stage for Object identifiers Created On: 16-May-2006 08:03 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Our implementation phase of DOORS has reached the decision point as to how to use unique Identifiers or prefixes. Does anyone have any ideas / pointers towards information as to how to use the identifier field in the most efficient way. Ideally we want to come up with a numbering system now that will work for all future projects. |
|
![]() |
|
![]() |
|
There are good reasons to add a "Requirement ID" or "Capability ID" field to your modules; this ID houses the project-wide unique identifier for each requirement. I think this is a bit unwieldy. Instead, you CAN use the Object Identifier to also mean the Requirement ID as follows.
We adopted Raytheon's superior strategy as follows: Module names will be short accronyms, the description of the module can have all the verbiage. Module names will be unique within the PROJECT. Module Prefixes are the module name with an underscore. Thus, object identifiers are unique within the project. The naming convention for the module acronyms needs to be ironed down; typically the first character of the name determines the level of the module; perhaps "Sxxx" are System level modules. You could add a suffix to module names that describes the kind of module, "RD" for requirements modules, "V" for verificaction module (making modules "Sxxx RD" and "Sxxx V"). You need to be careful to never copy one Requirement text from an object to a new object; since other objects are refering to the old ID. Thus, deleted requirements should be in deleted but not purged objects, just in case you revive that requirement. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Numbering Format
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.