![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Suspect Links in v7 Topic Summary: Created On: 22-Apr-2004 00:17 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Am I missing something here?
In the marketing blurb for what's new in DOORS version 7, it's stated that Suspect Links no longer need to be initialised - an annoying redundant step required in v5 and v6. Anyway, much to my surprise - the Initialise function is still in the Module menu ie: Analysis > Suspect Links > Initialise. Even more to my surprise is that you do actually have to still initialise or Suspect Links will not work as expected. I'm aware a pre-condition concerning modules that may have been originally created in older versions of DOORS, but my tests shows that you still need to initialise new modules created in version 7. With respect to an incoming suspect - if you don't initialise, the suspect status is automatically cleared when you modify the object that is displaying an incoming suspect. The suspect status is meant to be frozen until explicitly cleared by a user. Anyone else encountered this? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Paul,
I've seen exactly the same behaviour, I'm clueless why it is stated in the release notes that it is no longer necessary. Regards, Mikael Bendtsen Software Engineer @ St Jude Medical |
|
![]() |
|
![]() |
|
The release notes are easily misinterpreted. What they mean is that suspect links now work "out of the box" without having to set the module up for suspect links by running "Initialise".
(old links didn't contain any suspicion info i.e "Suspicion Cleared Forwards" and "Suspicion Cleared Backwards" attributes. "Initialise" creates these.) >>The suspect status is meant to be frozen until explicitly cleared by a user. not really. Suspicion works against the last point in time that the suspicion was cleared, or if the suspicion has never been cleared, then suspicion is flagged if the target object modification timestamp is more recent than the source object modification timestamp. "Initialise" explicitly clears the suspicion status of each object, so thereafter suspicion will continue to be flagged whether or not the source object is edited. Objects which have not been explicitly cleared will have their suspicion calculated by modification timestamp. If suspicion was automatically cleared on creating a link (i.e suspicion attributes set to the creation date) then you wouldn't have the option of suspicion being displayed on object modification date by default. But then it might be a bit simpler, because its currently not obvious which suspicion links have ever been cleared unless you add a column displaying the clearing date. what might be useful is an object specific "initialise" function. link."Suspicion Cleared Forwards" = dateOf( intOf today) would do the trick. equally, an "unclear" operation might be useful, i.e link."Suspicion Cleared Forwards" = null these are easily enough added to the object dropdowm menu. |
|
![]() |
Telelogic DOORS
» General Discussion
»
Suspect Links in v7
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.