![]() |
Telelogic DOORS (steve huntington) | ![]() |
Topic Title: change bars, change date, history settings for attributes - best practice question Topic Summary: Created On: 20-Dec-2007 10:37 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
What is considered best practice for setting the check boxes for:
Change Bars, Change Dates, & History for attributes? I believe that Change dates are used to support Suspect Links analysis. Because of this, it appears desirable to limit Change dates to attributes that are linked. For example in a requirement module Object Text might be the only attribute that should have Change Date set. However if the requirement document was linked to a verification module, it might be appropriate to have other attributes affecting Change Date. The problem then would be that the object would show up as having a Suspect Link when another attribute had been changed I had set up some new modules with most attributes only affecting Change Bars and Change History, but am now wondering if this is the right thing to do. It looks as though Change Date controls the Last Modified On system attribute. History obviously controls the generation of history. There appears to be no way of finding objects that have their change bars set to a particular value using the UI; is there a way using DXL? Filtering on Last Modified On since a particular date is useful, but if Change Date and Affect History are set differently there may be objects that are not included in a filtered se3t but have history associated with them. All advice gratefully received. Jim Backus ------------------------- Jim Backus<BR>Ultra Electronics, Controls |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.