Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 16-May-2006 08:03
User is offline View Users Profile Print this message


Martin Dunn

Posts: 3
Joined: 21-Nov-2005

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.

thanks

Report this to a Moderator Report this to a Moderator
 16-May-2006 14:40
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.