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: Suspect Link Traceability from the bottom up ?
Topic Summary:
Created On: 29-Oct-2002 14:32
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.
 29-Oct-2002 14:32
User is offline View Users Profile Print this message


Richard harkness

Posts: 13
Joined: 24-Oct-2002

The scenario I have is this...



What I need to do is ripple the suspect link indication down to the Test Procedure Module, such that if a change occurs in the PRS module then not only would an indicator flag be shown in the Clarification Module but all modules in the chain.

This would help me in deciding if a given test is good and consistent with its top level source requirement.

Any ideas ?
Report this to a Moderator Report this to a Moderator
 29-Oct-2002 16:23
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Don't know about suspect links, but your post aroused some hackles. Consider the following...

[1] Tests that verify the top level requirement should be linked to that top level requirement, not to the detailed requirements down the decomposition chain. If a test (for whatever reason) tests both lower-level AND top-level requirements, then it should be linked to both ..err.. all.

[2] If a top-level requirement change does NOT trigger a changed to a linked lower-level requirement, then the test for that lower-level requirement should remain intact.

[3] Changing a top-level requirement should trigger consideration for changes for the linked mid-level requirements (via suspect links if you want). If a particular mid-level requirement does not change then the chances that its linked lower-level requirements changes is very small. If you suspect that they MAY change, then you can tweak some attribute of the mid-level object in order to trigger your suspect-links strategy to bring your attention to the lower-level requirements.

[4] You'd be better off not making ANY requirement changes until you have followed the links and found ALL the affected requirements at all levels; then approve/disapprove/apply these changes all at once.

- Louie
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.