![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Mirroring Objects Topic Summary: Created On: 20-Feb-2007 20:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am trying to mirror objects between modules. I want to have an upper level document that has a system requirement. For example "The system shall operate on less than 90 watts." Then I would like this requirment to be copied down to the lower level requirment documents for each device that makes up the system. Therefore there may be several copies of this requirment in several documents. So for this example in each of the lower modules there would be an object saying, "The system shall operate on less than 90 watts." Yet I would like to have all the lower level objects be able to change if the higher level requirement object was changed. So if the upper level object changed to "The system shall operate on less than 60 watts." All the lower level requirment objects would change automatically to "The system shall operate on less than 60 watts." How can I perform this action? Any help would be appreciated. Thanks
John Hupfer |
|
![]() |
|
![]() |
|
Ahh yes, that one. We're in the process of doing the same thing here. Our "lower level" documents have, in the past, just had blank objects with links to the higher level ones, and we have traceability columns set up that let you see the text in outlinks.
But, we decided to change that and have the actual text in the lower level document. I wrote a script that looks through the lowest level document and finds the links we want in empty objects. Then it grabs the higher-level text and copies it in, and sets a "Source" attribute (that it creates) for the object to tell what level it was inherited from, as well as a "Freeze" attribute. Then, when you run it again, it will look again at anything empty, and at anything that is not "Frozen" (which defaults True). If anything has changed (either the higher- or lower-level doc), it asks you what to do. We've used the script some but I'm waiting to hear if the update features are what we need. Hope that gives you some ideas. Chris |
|
![]() |
|
![]() |
|
Thanks Chris, this problem seems so simple that it should be easy to implement this function easily. Thanks for your thoughts I might give something like that a try. If I come across an easier way I'll let you know.
|
|
![]() |
|
![]() |
|
Use the Tools->Functions->Copy Objects menu item. Check the box to make the links. This gives you a copy of the original and a link back to it. You can edit the copy and if the original changes you can spot it with the suspect links.
|
|
![]() |
|
![]() |
|
We call this Shadowing. A script runs nightly (using a Windows Scheduled Task) that updates all the shadow objects in the project (~300). It involves an attribute called Shadow Source ID to tell the script where to go to get the master object's data. It also involves a "Shadowing?" attribute (Yes/No type) that's used to make any shadow objects appear with gray text in certain views, making the shadow objects more obvious. And we do this without links. I'm sure there are several ways to do this.
|
|
![]() |
Telelogic DOORS
» General Discussion
»
Mirroring Objects
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.