![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Conditional Attributes value Topic Summary: Created On: 21-Feb-2006 19:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
IS there a way to have an attribute that shows the parent level object text for child requirements.
Example: Requirement Parent Attribute 1. Make Coffee Parent 1.1 Open coffee Beans Make Coffee 1.2 Grind Coffee Make Coffee 1.3 Add Coffee to Machine Make Coffee 1.4 Add Water Make Coffee 1.5 Press Brew button Make Coffee 2. Clean Coffee Machine Parent 2.1 Unplug Coffee Machine Clean Coffee Machine 2.2 Remove Coffee Grounds Clean Coffee Machine In this example the "Parent Attribute" would be dynamic depending on its specified level parent Thanks |
|
![]() |
|
![]() |
|
Create a new boolean attribute "IsParent" that has property Defaulted to False. Set that attribute to true for each object you decide is a parent. I don't care if you set it false for the children or just let it default to false.
You can now create another DXL attribute "Parent" whose DXL looks something like attached. No, I didn't run it. - Louie |
|
![]() |
|
![]() |
|
An alternative approach would be to create a layout DXL column using something like the attached code. This shows the cummulative object headings for each object, except level 1 headings, based on hierarchy structure, so providing some "context". For example;
1 Make Coffee 1.1 Open Coffee Beans Make Coffee 1.1.1 Remove lid Make Coffee.Open Coffee Beans Scoop out needed amount Make Coffee.Open Coffee Beans.Remove lid Put into grinder Make Coffee.Open Coffee Beans.Remove lid 1.2 Grind Coffee Make Coffee 1.3 Add Coffee to Machine Make Coffee 1.4 Add Water Make Coffee 1.5 Press Brew Button Make Coffee 2 Clean Coffee Machine 2.1 Unplus Coffee Machine Clean Coffee Machine 2.2 Remove Coffee Grounds Clean Coffee Machine Level 1 headings are blank, but you could easily modify to say <Parent> if you want. You can also create as attribtue dxl of type text, change the 2nd to last line to refer to the attribute name rather than display. If using this approach you need to trust you or your users have the hierarchy right, if your not confident then Louie's solution allows manual setting. If using Louie's code I believe the second line needs to read "bool IsParent = obj."IsParent"" but as he said it wasnt run. ------------------------- Paul Ransley<BR><BR>Beaver Computer Consultants Limited Edited: 22-Feb-2006 at 09:28 by Paul Ransley |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Conditional Attributes value
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.