![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Baseline compare not correct Topic Summary: Result of compare specifies objects that do not exist Created On: 16-May-2008 10:19 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Yep - one of those endearing little nuances of DOORS that has been around since the beggining. The Baseline Compare function will only compare against the current filter settings, and that includes the setting for the Show Deletions option which is a type of filter. If deleted objects are visible, you will get a completely differant compare result than when they remain hidden. DOORS really should issue a warning if filters have been set otherwise users may act on incorrect compare data. | |
![]() |
|
I have a module with several baselines. Last baseline is 2.3.
I compare baseline 2.3 with the current module with File > Baseline > Compare... (starting this in the current module). The 'Show baselines' checkbox is NOT checked. The tool finds 104 differences, all related to objects that only exist in baseline 2.3. Having a look in baseline 2.3, these objects do NOT exist at all (also not when showing deleted objects). That's strange. Then I compare version 2.3 with the current again, but now the 'Show baselines' checkbox IS checked. The tool finds NO differences. I'm lost. How is it possible that the baseline compare function gives different results, depending on the 'Show baselines' checkbox? How is it possible that the baseline compare function specifies objects that only exist in the baseline, while these objects do not exist at all? Thank all for your feedback in advance. Sjors |
|
![]() |
|
![]() |
|
It turns out to be that compare baselines does not take table cells into account when they are not shown in the view from which you invoke the compare function.
The same applies for showing / hiding deleted objects. |
|
![]() |
|
![]() |
|
Yep - one of those endearing little nuances of DOORS that has been around since the beggining.
The Baseline Compare function will only compare against the current filter settings, and that includes the setting for the Show Deletions option which is a type of filter. If deleted objects are visible, you will get a completely differant compare result than when they remain hidden. DOORS really should issue a warning if filters have been set otherwise users may act on incorrect compare data. ------------------------- Paul Miller Specification Practices Specialist EuroCyber Melbourne, Australia Mobile: + 61 (0) 418 135 103 http://www.eurocyber.biz |
|
![]() |
Telelogic DOORS
» General Discussion
»
Baseline compare not correct
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.