![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Create 'Selective' DOORS Baseline Topic Summary: Created On: 10-Oct-2006 12:55 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Has anyone tried something similar to this ?
I would like to find a way to create a DOORS baseline where only objects with a certain boolean attribute get baselined? My plan is as follows, changes that have been 'Approved' go into the baseline, but 'Pending' changes do not go into the baseline. That way I can write a Layout DXL column that displays changes since last baseline with underline and strikethrough markup, but the "Pending' changes will still display with reference to the baseline thay were written against rather than the latest one. Unchanged objects have nothing in this column, to aid spotting the changed ones. The basic problem is that we will have multiple changes occuring simultaneously, each change having its own independent lifecycle. Common enough peoblem I'm expecting? I would be happy enough to hack the standard baseline creation script except it is encrypted, grrrrrr. I'm guessing there is more than one way to crack this particular nut, havent given it too much thought yet, just fishing for ideas. ------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Andrew,
I don't believe there is a way to do what you're asking. Three suggestions: 1. Create a view with a filter based on your criteria. When you create the baseline, in the comments of the baseline explain that the baseline is based on the viewname. 2. Use the copy objects feature and copy those objects into an empty module. Archive the module. You can import it back at any time. 3. Create your filter, delete anything not in the filter. Baseline, then undelete. Not a perfect solution (you need to tag items deleted just for the baseline versus those not)... ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
OK, here are my latest thoughts on this one:
If I create a 'Status' attribute,and lets keep it simple as 'Approved' and Pending', I can baseline the modules as soon as a Change Request (object linked to all the changed objects) becomes Approved. I can then modify my publishing tool so that Approved objects go into the published document as they are, but for the Pending ones, I will have to traverse back in baseline time to pull out the 'last approved' version of the object, rather than printing the current text for that one. I'm expecting that this will increase my publishing time ( currently 30 mins for 15 modules of around 1000 objects each via word), so my next question is what is the most time efficient way to look back through the baselines ? Wait untill I find a Pending object, load the previous baseline, get the last changed, continue? Load all previous baselines and create skip lists, process the objects, delete the skip lists when i move on to the next module? .....any other ideas ? Thanks again. Andrew ------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Create 'Selective' DOORS Baseline
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.