Skip to main content

developerWorks >  Rational  >  Forums  >  Rational DOORS DXL  >  developerWorks

Best way of picking up data two levels up?    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
This question is answered.

Permlink Replies: 4 - Pages: 1 - Last Post: Nov 10, 2009 4:18 AM Last Post By: Mathias Mamsch Threads: [ Previous | Next ]
mtmccor

Posts: 7
Registered: Oct 28, 2009 04:17:42 PM
Best way of picking up data two levels up?
Posted: Nov 05, 2009 08:43:57 AM
 
Click to report abuse...   Click to reply to this thread Reply
I have three levels of specifications - A spec, B spec, C spec. Each spec is in its own module and there are links showing the relationship of the requirements between the A spec and the B spec and then between the B spec and the C spec. I believe this is a fairly standard setup.

I have a DXL attribute in the B spec that gets the A spec requirement IDs that map to the B spec requirements. I also have a similar DXL attribute in the C spec showing the B spec requirement IDs mapping to the C spec requirements. In the C spec, I would like to show the A spec requirement IDs that map to the B spec requirements that map to the C spec requirements. The two ways I see to do this are
1. follow the link from the C spec to the B spec and then follow the link from the B spec to the A spec to get the A spec IDs
2. follow the link from the C spec to the B spec and then use the DXL attribute in the B spec that has the A spec IDs

The second way is easier from a coding standpoint, but I wasn't sure if there were some gotchas with the second option, and I would like input/opinion from those of you that have more DXL and DOORS experience than I.

Thanks,
Marjorie
PDU

Posts: 25
Registered: Oct 01, 2009 11:46:01 AM
Re: Best way of picking up data two levels up?
Posted: Nov 05, 2009 10:48:39 AM   in response to: mtmccor in response to: mtmccor's post
 
Click to report abuse...   Click to reply to this thread Reply
Why you don't use the Wizard from module C, depth of analysis = 2 ? (menu : Analysis -> Wizard...)

If you need see other attributs that those profided :
  • transform layout DXL in Attributs.
  • modify code of Attributs.

Pierre

mtmccor

Posts: 7
Registered: Oct 28, 2009 04:17:42 PM
Re: Best way of picking up data two levels up?
Posted: Nov 05, 2009 03:41:41 PM   in response to: PDU in response to: PDU's post
 
Click to report abuse...   Click to reply to this thread Reply
Your answer tells me how to easily get the dxl code using the DOORS tools, but it does not really answer my question about whether there are gotchas with the second method using the dxl attribute in the B spec.
kbmurphy

Posts: 186
Registered: Nov 03, 2008 09:26:48 AM
Re: Best way of picking up data two levels up?
Posted: Nov 06, 2009 06:49:03 PM   in response to: mtmccor in response to: mtmccor's post
 
Click to report abuse...   Click to reply to this thread Reply
The two options should yield identical results (perhaps in a different format). However, if you don't code it correctly, you risk making a mistake. Further, if the DXL Attribute hasn't been updated because the module was opened read-only, you may get an error.

In other words, why make this so complicated? Use the analysis wizard, or at least the code it generates as your starting point.
Mathias Mamsch

Posts: 45
Registered: Nov 04, 2009 08:22:06 AM
Re: Best way of picking up data two levels up?
Posted: Nov 10, 2009 04:18:26 AM   in response to: kbmurphy in response to: kbmurphy's post
 
Click to report abuse...   Click to reply to this thread Reply
There is no functional difference between both approaches, assuming you use the same DXL code for following the links between the modules. But there are some design decisions you should make:

If a module links to several other modules there might be the need to follow only some special link paths. Example

If you have a link setup like this (A,B,C,D, E = modules):

A - B - D 
 \    / 
  \  / 
   C
  / 
 / 
E


Sometimes you want to follow only a special link path (e.g. D->B->A) which is easy with DXL attributes but sometimes you want to follow all link paths (D-B-A and D-C-A). If you use DXL attributes in this case, you will need to combine the values of DXL attributes in C and B to one value. But C needs now two different DXL attributes, because you may not want links to E to appear. Therefore you need to maintain a lot of DXL attributes.
And what happens if another link path to A will be created later? You will need to modify the DXL attribute in D.

So you should really answer the question about how stable you link setup will be and if you want to follow only one special path from a module to another or maybe ALL paths.

Regards, Mathias
 Tags
Help

Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular type of content or application that you're viewing.

My tags shows your tags for this particular type of content or application that you're viewing.

 

MoreLess 


Point your RSS reader here for a feed of the latest messages in all forums