![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Managing trace to common components Topic Summary: A problem on DOORS configuration to meet a need Created On: 17-Jun-2005 12:44 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
The problem
I am developing applications that are used as components of systems that are then delivered on to customers. Each application has its own set of requirements that are designed to meet the needs of multiple customers. These requirements can be changed independent of end-customer requirements, subject to certain business restrictions. We need to provide trace information from each system requirement to the application requirements that partly or wholly meet the system requirement. No great problems so far, but now come the constraints: 1. Systems will use a specific version of each application, and therefore need to trace to the requirements for that version. Ongoing application development must not affect the trace. 2. Baselines for each application must be based on the development of that application and not on the development of any system that uses the application. This makes it impossible to use baseline sets that include both system requirements and application requirements. 3. In general, the work of application requirements teams should be independent of the systems that use the application; maintaining trace information is the responsibility of the using system's team. Thus we cannot provide links from the application requirements to the system requirements. 4. When systems move to later versions of applications, the trace will need to be moved on to the appropriate baseline requirement set. My initial thoughts A. Each system provides a "trace module" that links to a) the system requirement being satisfied, and b) the application requirements that satisfy it. (not strictly in accordance with DOORS philosophy, but it allows two non-modifiable modules to be linked) B. Links are maintained to the "current" module for application requirements (this will give some indication that application requirements have been modified but will not cover all cases). C. Links are copied to the specific baseline required (the topic in this forum at Link to Baselines indicates an approach to this) D. Baseline set for system includes requirements module and trace module. E. When systems move to a later application version, the links to exiting baseline are deleted and links to new baseline created (based on links to current). HELP!!! As a DOORS novice, I would apprciate any help that anyone can give on this problem. * The above seems possible to me, but may not make effective use of DOORS facilities; all guidance welcome. * If anyone has experience of this problem and has solved it, or can point out pitfalls I have not foreseen, then I would be grateful for any help you can give. |
|
![]() |
Telelogic DOORS
» General Discussion
»
Managing trace to common components
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.