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: Multiple linksets
Topic Summary:
Created On: 8-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.
 8-Dec-2005 14:42
User is offline View Users Profile Print this message


Amy Hartwell

Posts: 11
Joined: 1-Jul-2005

We have various Design Documents that we have linked to a Systems Requirements Document in DOORS through a link module called "satisfies requirement".  The format for the design documents was contractually imposed on us and, as such, contains additional information that we would like to connect to the Systems Requirements through a second link module called "supports".  The diagram in the DOORS Help section "Understanding link modules and linksets" suggests that this is possible.  When I try and add the linkset to the Module properties dialog I get an error message "Unable to add linkset pairing: Source/target pairing already exists."

I have made sure that the original "satisfies requirement" linkset is no longer mandatory.

Why can't I use two different link modules to describe relationships between documents?

Any help much appreciated,

Amy

Report this to a Moderator Report this to a Moderator
 8-Dec-2005 22:21
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

When you are in a formal module planning the targets of its links and you use the module properties box, you are defining a "Link Set Pairing" (LSP) or a "Default Link Module" (or "Link Module Descriptor" in DXL), you are not creating a "Link Set". The purpose of LSPs is to tell DOORS what link module to use if you do not specify one.

If such an LSP us "overwritable" then you can create links in some other link module (via Links >CreateLinks menu). When you do, a "Link Set" is created in that link module. If its "mandatory" then you cannot create links anywhere else.

Creating links in another module is tedius and its hard to believe they STILL haven't created an interface to do it gracefully. Thus, many of us create links with DXL, but that's another story.

- Louie

Another option is to create the links in DOORS Links, then use a copy link set tool to move them to your desired link module. Good luck managing that.
Report this to a Moderator Report this to a Moderator
 9-Dec-2005 09:01
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Beware - here be dragons!

I would strongly recommend that you only have a single relationship defined between any two modules and that you make the relationship mandatory and not overridable.
If you do not have mandatory linkset pairings then you are leaving the doors schema open to abuse by users who will be able to create all sorts of links that are either wrong or misplaced.

Your average doors user probably wants to concentrate on engineering the requirements and will (should) not be interested in the internals of how doors creates links.

One solution may be to add an attribute to the link itself so you can distinguish between satisfaction and support.

Link attributes are most easily edited from the links tab on the object properies dialog.

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 9-Dec-2005 11:06
User is offline View Users Profile Print this message


Hazel Woodcock

Posts: 78
Joined: 6-May-2005

It sounds as if you have a mixture of requirement types in your System Requirements module. I would look at the possibility of either:
Using different sections within the module, then the relationship is implied by the section.
OR (for preference)
Splitting this into its two separate parts as separate modules. If you are worried about retaining the absolute numbers with this approach, then copy the module and create the second from a copy of the first.

If you really have to use link attributes then be warned that they are slightly awkward to work with (it messes up the workflow to have to click around with the mouse), I would suggest an object attribute if each requirement has either one type of link or the other.

As Tony said, it should be simple to use.

Hazel
Report this to a Moderator Report this to a Moderator
 12-Jan-2006 09:49
User is offline View Users Profile Print this message


Soft Male

Posts: 3
Joined: 19-Dec-2005

Hi.

My question is about selecting multiple target modules when creating the linkset.
Does any of you know a script that does this?
Report this to a Moderator Report this to a Moderator
 20-Jan-2006 12:32
User is offline View Users Profile Print this message


Anton Drexler

Posts: 25
Joined: 9-Dec-2003

Hi,

per definition a "linkset" stores the links between exactly one source and one target module.

Thus, I don't know what you mean if you like to select mutliple targets when creating a linkset; could you explain what you are going to do?

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