![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to display an attribute from another formal module Topic Summary: Created On: 19-Jul-2006 21:27 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: There are two ways I can think of... The most elegant is via a filtering DXL that follows the link paths through the project but that's a custom which involves a fair level of understanding and DXL proficiency. At least beyond the context of this 'General Discussions' forum. The 'simple' way (meaning you don't need to know any DXL) is use the wizard multiple times as outlined below. First, create a 'Layout DXL' the from Func Spec to Test module using 'specified Link module' and 'Specified file'. This way you will be able to choose any attribute including the 'Test Status' attribute to view. Because thewizardd creates only Layout DXL's, you still need to do some work. The 'Test Status' data now exists as a 'Layout DXL' in your Func Spec module. Using 'Tools>Support Tools>Convert Layout DXL to Attribute DXL' you can convert it to an attribute DXL. Now you have an actual instance of the 'Test Status' information inside the Func Spec module. Repeat this process with the Wizard in the SOW by choosing this new attribute from the Func Spec to display in the SOW (also converting it to a 'Attribute DXL'), then repeat the process once again from the User Requirements and import the new attribute created in the SOW. Your done... Make sure all modules are opened when viewing the attribute so everything is up to date. This method can be used to show attributes' contents from four (or more) levels away. I show our engineers how to do this when I'm in a pinch for time, later will follow up with a custom DXL that imports the information directly via the link module paths. I'd suggest you do the same sometime in the future, however this method is a quick way to get what you are asking for - especially if you are not yet proficient in DXL programming. | |
![]() |
|
I have a custom attribute named Test Status in a formal module named Test. I have links from Test to Func Spec, from Func Spec to SOW, from SOW to User Requirements.
What I want to be able to do is display the Test Status in the User Requirements formal module. I have tried the traceability wizard and I can only display the common attributes and no user defined if I use the open modules. If I choose the Test Status fomal module in the Wizard I get no traceability.
Can anyone help?
thanks,
MikeM
|
|
![]() |
|
![]() |
|
There are two ways I can think of...
The most elegant is via a filtering DXL that follows the link paths through the project but that's a custom which involves a fair level of understanding and DXL proficiency. At least beyond the context of this 'General Discussions' forum. The 'simple' way (meaning you don't need to know any DXL) is use the wizard multiple times as outlined below. First, create a 'Layout DXL' the from Func Spec to Test module using 'specified Link module' and 'Specified file'. This way you will be able to choose any attribute including the 'Test Status' attribute to view. Because thewizardd creates only Layout DXL's, you still need to do some work. The 'Test Status' data now exists as a 'Layout DXL' in your Func Spec module. Using 'Tools>Support Tools>Convert Layout DXL to Attribute DXL' you can convert it to an attribute DXL. Now you have an actual instance of the 'Test Status' information inside the Func Spec module. Repeat this process with the Wizard in the SOW by choosing this new attribute from the Func Spec to display in the SOW (also converting it to a 'Attribute DXL'), then repeat the process once again from the User Requirements and import the new attribute created in the SOW. Your done... Make sure all modules are opened when viewing the attribute so everything is up to date. This method can be used to show attributes' contents from four (or more) levels away. I show our engineers how to do this when I'm in a pinch for time, later will follow up with a custom DXL that imports the information directly via the link module paths. I'd suggest you do the same sometime in the future, however this method is a quick way to get what you are asking for - especially if you are not yet proficient in DXL programming. |
|
![]() |
|
![]() |
|
You could use the analysis wizard and display the Object Text. Having done that, edit the dxl in the traceability column. You are looking to replace "Object Text" with "Test Status". When you have made the change, press the 'check' button and make sure it says 'no errors', then OK your way back to displaying the column.
If you want two custom attributes, then pick two standard ones and do the replacement of both. No need to understand the dxl, just tweak the recognisable bits. Hazel |
|
![]() |
|
![]() |
|
One of the major flaws in DOORS is the staggeringly poor traceability and impact wizard functionality, why these tools haven't been completely revamped and improved over the years is a mystery to me.
The linking ability is essentially why we use DOORS and allowing standard users to download the information through the links in an easy and intuitive manner and see it in there preferred style/ format is to my mind essential. What you need is a tool that allows you to query one module (the target) possibly through intervening modules and display the information in the module you are running the code from in the order and style that you prefer, this is not as hard as you might think, it is in fact the first major task I completed on my current assignment. If you don't do this you will be forever tweaking traceability columns and making layout dxl attribute dxl etc. Believe me when I say that this will get extremely tedious over time! ------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
Thanks Dan that worked.
|
|
![]() |
|
![]() |
|
Hi:
When converting Layout DXL into Attribute DXL, that will make the data static. So, if data ,for example test status, changes, how the SOW knows the newest value of test status ??
Regards,
Jerry
|
|
![]() |
|
![]() |
|
Attribute DXL's are not really 'static'. However, they are refreshed only at module open or if you refresh them manually from the main menu. That is why I mentioned to make sure ALL of the modules in the link chain were open. If they are all opened (starting with the Test module) up the chain you will insure an fully updated view of the Test Status in the User Requirements module every time you open the set of modules.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.