![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Saving Requirements for later versions Topic Summary: How to mark a requirement for use in a later document baseline Created On: 19-Jan-2005 03:09 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I am after some assistance with the best way to save an already entered requirement for use in a later version of a module/document. I have requirements at a level which will be used at the next layer down delivery to a customer, but wish to retain in the master document, i.e. don't publish this yet! I am loathed to use an attribute as I am looking for a way to functionally allocate requirements to document versions. Thanks in advance Jason |
|
![]() |
|
![]() |
|
I'm assuming that all levels of requirements are entered in a single module.
I don't understand your reluctance to use an attribute, as I'm sure a much neater solution could be obtained through attributes, but a couple of solutions without using an attribute could be: - delete the requirement. When you do need it, undelete it. The problem is that it could accidently be lost if "purge all" is used to get rid of junk in the module. - under your normal document structure, use a sub-heading for each level of requirement. If you don't wish to publish a level, use a filter to remove those sub-headings and their descendants from the display before export. |
|
![]() |
Telelogic DOORS
» General Discussion
»
Saving Requirements for later versions
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.