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: How to Create Link bewteen Requirement and Design/Code?
Topic Summary:
Created On: 6-Sep-2008 08:54
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.
 6-Sep-2008 08:54
User is offline View Users Profile Print this message


Shaohua Cheng

Posts: 3
Joined: 5-May-2008

DOORS is very powerful at requirement traceability.
In my project team, we use DOORS to write requirement, use Catia to design the CAD model, use VisualStudio to write C code.
Is there any way to create link directly bewteen requirement text and Catia component design? or create link directly bewteen requirement text and one function wrote in C?
It would be very helpful if DOORS can work in this way.
Report this to a Moderator Report this to a Moderator
 8-Sep-2008 12:01
User is offline View Users Profile Print this message


Roy Bond

Posts: 39
Joined: 25-Mar-2003

You could do this in a number of ways.

First, and most simple, is to record a hyperlink in an attribute of the Requirement which provides a direct link to the source code.

Second, and a little more difficult, is to place the Requirement ID in the Header of the source code, and then use a Parser to 'read' the IDs in all the source. The Parser can then create a Surrogate Module which lists all the Procedures/Functions found and links them back to the Requirements listed in the Header.

The second approach is how we tackled this problem.


Roy Bond
BAE Systems
Report this to a Moderator Report this to a Moderator
 8-Sep-2008 15:21
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

We do something similar with our test cases, where the header of each test case contains the requirements it satisfies. We then have a script the we run that basicaly creates the test case object in the specified DOORS module, then creates the links to the requirements.

We working on a script that will parse the test cases nightly and update the tracing as needed (adding/deleting links as necessary).

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 16-Sep-2008 12:15
User is offline View Users Profile Print this message


Matthew Thomas

Posts: 15
Joined: 14-Feb-2008

If you want a more productive and fully integrated approach, use a code-generative UML modelling tool like Telelogic Rhapsody with its requirements' Gateway add-on. That way, all development artefacts are driven from (and therefore traceable from) requirements. See: http://modeling.telelogic.com/...ody/add-on/gateway.cfm
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.