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: Recommendation for linking objects
Topic Summary: Circular linking
Created On: 29-Dec-2005 14:42
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-Dec-2005 14:42
User is offline View Users Profile Print this message


Brenda Cornell

Posts: 29
Joined: 7-Jul-2005

We have Use Cases (UC) with Basic Flows (BF), subvariations (SV) and extensions (EX). BF steps can often lead to SV flows, and we do create an intradependency link. We also have a UC that extends to another UC and back, where we also create an intradependency link from the first UC to the second.

My question is, if the SV has a step to return back to the BF, or an extended UC has a step to return back to an original UC, is it recommended to do those links back, thus creating a circular linkage??

Has anyone out there tried anything like this and run into any problems with reporting, with regard to this type of linkage??

Thanks.

-------------------------
Brenda Heiss Cornell
Report this to a Moderator Report this to a Moderator
 10-Jan-2006 23:14
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I didn't quite understand your structure. However Circular links of the same type (i.e. in the same link module) is just asking for trouble.

Which Direction?
[1] Link direction could be governed by the principle that the source is dependant on the target: its more likely the target will change forcing a change to the source; than that the source will change and force a change to the target. Thus, System Requirements should be the target of SubSystem Requirements links and the SubSystem requirements "Satisfy" the System Requirements. [2] Another scheme is to insure the source of the links is in the module authored by the person who determines whether the links should exist. If your System Requirements owner does the decomposition and creates the SubSytems requirements, then links could arguably be down the chain; where the System requirements "Drive" the SubSystems.

As far as I can tell, most systems engineering organizations are set up such that one level of requirements is derived, and then the subordinate owners coordinate how to satisfy them. This is the traditional water-fall approach. This favors the link-up-the-chain scheme of [1] above. You can functionally and actually "lock down" the system spec while the subsystem specs are being generated.

Similarly, "Test" links should link from the tests to the requirements; clearly you don't change a requirement because a test changes.

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