![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: suspected link Topic Summary: Created On: 25-Jul-2007 12:15 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi all |
|
![]() |
|
![]() |
|
Jon,
You can't do this with suspect links. You can, however, use the analysis wizard from module D, display "Last Modified On", recurse two hops, and then set up a filter on the second column...maybe. I'm not in front of a database where I can test this out. You may have to use Attribute DXL to hold the Column B "Last Modified On" attribute for Module B so you can filter it. Then you can just write a script that accepts a date to show requirements where Module B changed after a certain date. Admittedly, that's not straightforward. Another thing to consider is just use the suspect links in Module C, and then set up a view in Module C to show suspect outgoing links (Filter> under the Suspect Links menu), and use the analysis wizard to get the IDs of the incoming links you need to check in Module D. There you go--two answers to your question. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
suspected link
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.