![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Duplicates after recursive traces Topic Summary: In environments where children have multiple parents, recursive traces results in duplicates Created On: 31-Dec-2004 22:42 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: If you want to customise the column dxl created by the Wizard try the following mods; Good luck. | |
![]() |
|
After performing a recursive analysis with a depth of 4 or more, I'm getting duplicate requirements in the 4th+ layers. This is because there are multiple paths to get to the requirements in the 4th+ layer. For example, A -> B -> C -> F and A -> B -> D -> F and A -> E -> C -> F. This should be a common dilemma for applications where children requirements have multiple parents.
Does anyone know how to avoid or automatically delete the duplicates? This is a serious problem for us because we have 8 levels of requirements, and each requirement can have multiple parents. It's okay if the solution involves post-processing in Word or Excel, because I'm exporting the trace matrices anyway. Thank you! Debbie |
|
![]() |
|
![]() |
|
There are several approaches -- however the easiest to explain is:
Build a skip list of each one of your links -- this will filter duplicates -- then display the filtered list. For more info contact ron_lewis@hotmail.com |
|
![]() |
|
![]() |
|
We often get this, and use either a solution similar to Ron's responses, or capture the traces to a text attribute (for various reasons), then run a script to remove the duplicates. As an example see the attached script which assumes the traceability is only showing the Object Identifier or Absolute Number but is easily modified to include other attributes as needed. The script might be useful to experiment with after creating a couple of objects with duplicated values in the attribute. We have also used a variant to modify the script created by the Analyse Wizard, though as I said our preference is to use the traces stored in a text attribute.
------------------------- Paul Ransley<BR><BR>Beaver Computer Consultants Limited Edited: 3-Jan-2005 at 09:50 by Paul Ransley |
|
![]() |
|
![]() |
|
If you want to customise the column dxl created by the Wizard try the following mods;
Good luck.
------------------------- Paul Ransley<BR><BR>Beaver Computer Consultants Limited Edited: 3-Jan-2005 at 10:31 by Paul Ransley |
|
![]() |
|
![]() |
|
Would you be willing to provide code to do recursive analysis? I could use some code that starts with a current module and traces links for several levels. Thanks!
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Duplicates after recursive traces
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.