![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Copy and Link in DOORS 6.0 Topic Summary: Created On: 5-Feb-2004 16:20 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Has anybody else had a problem with this....
I have two modules A and B, with a mandatory linkset defined from B to A. The linkset is stored in a user defined link module. When I try to copy and link objects (copy from A to B, link from B to A) I get an error message saying the module does not exist. I can do the copy on its own just fine, and I can manually link once the copy is made, the problem seems to be in doing both operations in one (i.e. copy and link). I find this very strange as this is a fundamental tool for DOORS, and I find it hard to believe that this wouldn't work properly. Does anybody know if this is a recognised limitation of version 6.0, and is there an effective fix? Awaiting your valuable help.... |
|
![]() |
|
![]() |
|
Don't know, but try these:
I have an incomplete nagging memory that the Copy Objects tool incorrectly uses the Source-to-Target link Default Link Module even when you reverse the link direction, and link target-to-source. Try this: define the same Default Link Module A->B as you already have B->A. Another thing to try is to define you link module using the "Links >> Create Links..." menu. - Louie |
|
![]() |
|
![]() |
|
Yes, this seems to work but it leads to the following problems....
1) In terms of a database architecture and only linking upwards (as recommended by Telelogic in their training literature) could this workaround lead to the possibility of other users making "illeagal links"? With these redundant linksets going in the "wrong" direction, could my traceability be compromised? 2) What if I don't have access rights to the higher level module? If I only have limitted access to a module and want to copy objects from it and link back to them using "copy and link" will I be able to set up this A->B linkset as you suggest? Thanks for your help so far |
|
![]() |
|
![]() |
|
Lets not confuse a [1] "Link Set" with a [2] "Default Link Module" aka "Link Set Pairing LSP" aka "Link Module Descriptor LMD". [1] is a physical "object" in a link module [2] is a single piece of information ABOUT a module (actually "housed" in the module's folder).
The "LinkSets" tab in the Module Properties is ambigously labeled since it refers to [2] not [1]. Creating [2] does NOT create [1]; which only gets created when you actually create a link. Creating an LSP from A->B does NOT create a link-set and does NOT "allow" folks to actually create links. If you do NOT define one they can still create A->B links, but they will default probably to "DOORS Links". If you NEED to disallow any links from A->B, you can define a mandatory LSP into a special Link Module and give "Everyone Else" only "R" access to this Link Module (disallowing links to be created). Too bad you cannot deny access to individual LinkSets. - Louie |
|
![]() |
Telelogic DOORS
» Defect/Issue Tracking
»
Copy and Link in DOORS 6.0
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.