![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Active Linking two attributes between different formal modules Topic Summary: Created On: 11-Mar-2004 09:50 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I would like to create a link between two attributes "A1" and "B1". A1 can be found in a formal module "A" the other one in formal module "B". A1 consits of the possible values "yes", "no", "n.a.", "todo" and "?". Now I would like that changes done in A1 affect B1 or invers so that the values are identical if one or the other attribute is changed, so called "active relationship" or "active link". Thank's for input ! Best regards Moritz |
|
![]() |
|
![]() |
|
You cannot link attributes, only objects. You cannot really do what you want but you CAN write DXL that will keep two values in Synch, perhaps by querying History of objects that do NOT share the same value to determine which obj.attr was modified most recently. Better would be to adopt a philosophy that the values of objects in module B are subordinate to those in A; so if you change A then B gets updated, but you cannot change B directly.
In any event Objects in A need to be associated with objects in B. Presuming related objects share the same absolute number will never work (obj #5 in B is the same as #5 in A), so you will need to [1] link each B to A [2] have some other attribute defining the relationship: perhaps module B has int attr "SameAsA" that has the AbsNo of A associated with each A object. With [2] it would be pretty easy to write an Attribute DXL for some attribute in B that automatically searches A for the object #SameAsA and sets the value (attrDXLName) if found. Its also possible to write a Trigger (perhaps a post-attribute-save Trigger) that detects when this certain attribute changes and automatically finds the value in the other module and updates its value. Triggers are not for the inexperienced nor faint-of-heart. Unfortunately, DOORS really isn't a "DataBase" in the manner you desire; its really a repository for hierarchical specifications that can be linked. If it WAS a database you could have requirement "It shall be Green" in one place and 'include' it in whichever specifications it needs to be in. But you cannot; each spec needs its own object "shall be green". Good luck. - Louie |
|
![]() |
|
![]() |
|
Moritz,
If you just want visibility to the attribute value from A1 for Objects linked to/from Module B1, that can be accomplished with Layout DXL. Try the Analysis -> Wizard. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Hi Moritz,
I have no solution to your problem but some questions: What is the reason why the two attributes shall (must?) have the same values? What is the relation between the both modules? When clarifying the goals you have, there might be a completely different database structure which fits better what you want without this need of synchronisation. Maybe the both modules could be molded into one where the different roles are implemented by views? Feel free to contact me if the topic is of further interest to you! Toni Drexler Consultant for Quality Management and Requirements Management a.s.drexler@gmx.de Edited: 20-Apr-2004 at 15:38 by Anton Drexler |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.