Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 17-Jun-2005 12:44
User is offline View Users Profile Print this message


michael Barnes

Posts: 85
Joined: 12-Nov-2003

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.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.