![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: script to re-number Topic Summary: DXL script to re-number Created On: 9-Mar-2006 14:30 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi
Any one have a script to introduce ones own numbering for the objects, as opposed to the system assigned unique numbers? Regards, Rad |
|
![]() |
|
![]() |
|
There is considerable discussion on project policies; whether the Absolute Number ..err.. I mean the Object Identifier is also used to identify the requirement housed within it. There are sound theoretical reasons why projects should assign each system requirement a unique project-controlled "Requirement ID" and that THESE should be referenced by everyone else; e.g. The test department insures that requirement "SysReq_1ab4" gets tested. There are sound practical reasons why the Object Identifier should be used; e.g. The test department insure that requirement "Sys_126" gets tested.
The problem with "Req ID" (or "Capability ID") is difficult to manage since you have to control and assign it to each requirement. The problem with Object Identifiers is its hard to move the text of a requirement to a different object; such as may happen if a requirement is deleted and then reinstated. You cannot change the absolute number of an object, but I suppose you could write a DXL that creates a new module, creates specific objects in the right place, and copies corresponding numbers over. You can, however, create and maintain an attribute with whatever numbers you like, perhaps called "Requirement Number". - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
script to re-number
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.