![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Poll - Implementation of Rich Traceability Topic Summary: Created On: 28-Apr-2004 12:05 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Does anyone use rich traceability?
If so, I would be interested to know what approach you have taken. Did you implement it yourself or did Telelogic do it for you. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Tony,
To clairify, are you referring to "Rich Traceability" as described by Jemery Dick in the following paper? Rich Traceability ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Yes, Rich Traceability as defined by Jeremy Dick, whereby an intermediate object is used to store link rationale or justification.
------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I've been looking at it, but haven't implemented anything. When I say I've been looking at it, I've actually been looking at the very similar REVEAL process that Praxis Critical Systems propose, which uses separate justification records to document (e.g.) design decisions. More info on REVEAL can be found here.
Praxis implement REVEAL in DOORS, as well as other Requirements Management Tools (yes, they do exist!) ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive Edited: 28-Apr-2004 at 16:42 by Paul Tiplady |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Poll - Implementation of Rich Traceability
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.