![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Transfering links Topic Summary: Transfering links from older module to updated module Created On: 8-Dec-2005 21:25 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: The attached shows how this can be done quite simply using skip lists. Hope this helps. | |
![]() |
|
We have two modules that are linked one to another. The upper module that have in-links is updated externally. the modules have requirements and requirement ID as object text and seperate attribute respectively. We want to transfer links from older module to updated one by using the identical and unique Requirement ID attribute. Is there a way to transfer links ?
|
|
![]() |
|
![]() |
|
There was some kind of "capture5.dxl" script that captured information about outgoing links. If so, do this: [1] capture5.dxl all the link information in the source lower module. [2] Delete and purge the target upper module [3] restore the new target upper module, using the exact same name [4] link-by-attribute from the lower older module, using the captured information attributes from [1].
- Louie |
|
![]() |
|
![]() |
|
There's a example DXL script supplied with DOORS which can copy links from one module to another, check for linkcopy.dxl
lib\dxl\example directory ( both for 7.1 and 8.0). Another way of finding this script is to browse the DXL Library, in module menus select Tool / DXL Libary. Start of this script is as follows: // Example to copy incoming or outgoing links from one module to another // Header: /DOORS/lib/dxl/example/linkcopy.dxl // Copyright 2002 Telelogic AB. All rights reserved. // See DOORS manuals for copying conditions. // Copy this file to a different location before modifying it. You may also // need to amend the paths to any #include files for this script to work - // these are contained in a subdirectory called include /* Assumes that modules are versions of one another, so that object identifiers are the same in both modules (with some added, and some deleted). */ ------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
Taner, I am reading between the lines here. When you talk about the unique requirement ID are you referring to the DOORS absolute number, or are you referring to an ordinary attribute that is manually set in the external module?
If you are using the absolute number, then you have no problem using the link by attribute tool to recreate the links. If, howeveer you are using a user-defined attribute then you may need custom DXL to compare attributes. You cannot rely on the object in the external module matching those in the original, so you will need error checking to ensure that all objects are handled correctly. Take a look at the compare modules tool. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Tony, unique requirement ID is ordinary attribute that is set in external module.
Compare module tool is just compares the attribute and indicates the differences, it doesn't transfer links between the compared modules. Thanks for help, Taner ASLAN |
|
![]() |
|
![]() |
|
The attached shows how this can be done quite simply using skip lists.
Hope this helps. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Hi Taner,
have you ever heard about DOORS eXchange? DOORS eXchange is a tool to exchange modules between DOORS databases, and particularly to update an existing copy of a module to its actual status. In doing this, eXchange also marks the changes from the earlier version of your customer's module to the most recent one. And what is more: the links you have drawn from your modules to the copies of your customer's modules are kept, which means you don't have to redraw the same links once more. The prerequisite for the use of eXchange, however, is that you have RMCD access to the copies of your customer's modules, as eXchange, of course, actually performs changes in those modules. Contact your Telelogic representative to learn about DOORS eXchange! Regards Toni |
|
![]() |
|
![]() |
|
Hi Toni,
one method of application is, that you get the away module with RMCD rights and you apply DOORS eXchange. The other method is, that you are only provided by the exchange-file generated by the customer, who of course has the necessary rights to do so. The module remains in this case in his hands... Best Regards Hubertus |
|
![]() |
Telelogic DOORS
» General Discussion
»
Transfering links
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.