![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
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 |
![]() |
![]()
|
![]() |
|
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. |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.