![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Requirement ID Topic Summary: Created On: 15-Sep-2004 23:48 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
In Doors do we have RequirementID? Is it same as Absolute Number?
If not then, is there a unique number - id (non-string)? The function "identifier" returns a string which is a combination of absolute number + module name. Thanks Babu |
|
![]() |
|
![]() |
|
It depends on how you define "RequirementID". In DOORS, every object has an identifier that is unique to the module. That is called the Absolute Number. The identifier is actually a combination of the module Prefix (module level attribute) and the Absolute Number.
In our use of DOORS, we make the module prefix unique within a project (through a naming scheme) which makes the ID unique for the project. We then use the identifier as a "Requirement ID". All objects have the ID though, so merely having a Requirement ID does not make something a requirement (but all requirements have an ID). We also use an object level attribute to identify which objects are actually requirements. Brian Azelborn Rockwell Collins |
|
![]() |
|
![]() |
|
Brian,
Is there an ID (at object level) which is unique across projects? (since, identifier is unique only within a folder) Babu |
|
![]() |
|
![]() |
|
You can combine the object attribute "Absolute Number" with the value returned by "uniqueID" for the module. UniqueID gives an 8 digit string, which is a hexadecimal number and can be converted (if your write the DXL) into a data item of type int. A combination of these two numbers will give you a unique reference to every object in the database, but, in order to ensure no duplication, the number will need to be bigger than an int. If you know how many objects you will have at most in each module, there are two things you can do. First, you can probably limit the database wide unique reference to each object to fit in an int. And second, you can sell your ideas and retire on the proceeds.
![]() Paul. ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|
![]() |
|
![]() |
|
Object ID works fairly well but becomes a nightmare if you copy objects around or worse yet restore modules from archives.
You can impose a new policy using a string attribute "ReqID", but will have to manage these unique IDs yourself. Tiplady's idea of using the Module unique ID will work so long as you never restore module's from archives. Keeping your module names and Prefixes unique within a project is feasable, but doing so across all projects is probably not, unless you simply append the project name to the module's prefix. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Requirement ID
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.