![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Requirement ID Topic Summary: How to customize the requirement id? Created On: 25-May-2005 18:26 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I would like to know if it is possible to customize requirement ids using dxl. Requirements should be the concatenation of two variable string codes and a number increased by five. For example:
SSS-CAP-000
SSS-CAP-005
SSS-CAP-010
...
SSS-CAP-990
SSS-QTY-000
SSS-QTY-005
...
SSS-QTY-990
thanks in advance
|
|
![]() |
|
![]() |
|
You have attribute RequirementID that applies to the module as well as to the objects. The module version has only the desired prefix, perhaps SSS-CAP-; this means all objects have this prefix as their Requirement ID.
You could then have a DXL that examines all the Requirement IDs of all "requirements" objects in the module, including deleted requirements (a requirement perhaps is an object that says "shall" in the Text). The Prefix is stripped from the ReqID leaving an integer. The highest integer found is remembered. You could then find Requirements that have no ID. The highest ID found is rounded up to the next integer of 5, converted to string with leading zeros, appended to the Prefix, and assigned to that requirement. Padding and unpadding is a little tricky but we've got functions for that. If a spec can have different ReqID Prefixes, then instead of the module attribute you can prompt for it. The initial object seach would look only for ReqIDs that match that Prefix. You'll find you run out of ReqIDs if you use only 3 digits (leaves you only 200 before you run out). I'd use 5 digits allowing for 20k ReqIDs. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Requirement ID
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.