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: Linking and Partitioning
Topic Summary: Do links created in imported partition get lost on rejoin?
Created On: 14-Apr-2005 17:18
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.
 14-Apr-2005 17:18
User is offline View Users Profile Print this message


Brant Stoner

Posts: 30
Joined: 2-Aug-2004

We exported a partition which contained several formal modules as well as the link module containing the links between the formal modules. We imported the partition into a local DOORS database and created several links. When we rejoined the modules with the original DOORS database, our new links were not created....

Did we do something wrong, or is this a (known) issue? We thought this was possible.

Thanks,
Brant
Report this to a Moderator Report this to a Moderator
 14-Apr-2005 23:06
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Any LinkSet Pairings that exist in the Home database are certainly not replicated in the Away database; therefore its likely you created links in the Away database in some other non-partioned link module; probably DOORS Links.
Report this to a Moderator Report this to a Moderator
 15-Apr-2005 14:43
User is offline View Users Profile Print this message


Brant Stoner

Posts: 30
Joined: 2-Aug-2004

I'm confused now. Are you saying that even if we include a Link Module in a partition, the Linksets in that Link Module are not included? For example, let's say we have Formal Module A and Formal Module B in our Home database. Link Module L contains the appropriate linksets to allow us to link from B to A. Then we define a partition to include Modules A, B, and L, and we export the partition. I import that partition into my Away database. Are you saying if I then link from B to A while in my Away database, that link won't get created in Link Module L...so when I return the partition, all my links I made in the Away database are lost? If so, is there a way around this?

We're using DOORS 7.1, by the way, if it matters.

Thanks for your help.
Report this to a Moderator Report this to a Moderator
 15-Apr-2005 21:53
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

LinkSet Pairings are not the linksets themselves, they are the default link modules that you can define in the Properties of the Module. You can decide that links between two modules must (mandatory) or should (overwriteable) go to a particular link module, and therefore a linkset therein.

So if you say that links from A to B must be in link module L, that "must" notion does NOT go to the away database. You'll have to redefine that there.

In DXL you'll deal with "LinkModuleDescriptors" LMDs, that have the same meaning as "LinkSet Pairings" LSPs, and the same meaning as "Default Link Modules" DLMs. As I said, this is different than "LinkSets".

- Louie

For whatever its worth, LMDs are stored in the Folder housing the module, not the module itself. Thus, DXL would be structured like this "get the folder handle for the current module; for LMD in folder do"; Get the Source, Target, and LM of the LMD; If this LMD's source name doesn't match the current module then continue."

Confused? Yup.
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.