Hello All,
I am trying to figure out how to use baseline sets for our next project. We are using DOORS 8.1, with the upgrade to 9 coming in the next month or so.
Right now I am just playing around in a practice database, but I am thinking this could be a real problem for us.
Here is the scenario:
We work using an iterative development process where we concentrate on a small set of functionality to develop the requirements, code, and tests.
1) Systems group uses customer requirements to develop the technical product specification.
2) Software group uses output from systems group to develop high level SW requirements
3) Software group uses the high level SW requirements and HW to produce low level SW requirements and design details.
I am envisioning a process where the systems group will work on requirements for a certain portion of the product, create a baseline in DOORS, and then continue working. The SW team would use that baseline as the basis for their work on this certain portion of the product.
I am thinking that we would have minor baseline sets for each specific portion and then a major baseline set for the first major release.
My problem is this: If the systems group has baselined their DOORS module into the minor baseline set, and they need to update it, so that SW team is not developing to "out of date" data, that existing baseline cannot be replaced within the baseline set. I tried both methods of baselining to the set, and neither let me select the systems DOORS module to baseline. It seems like replacing a baselined item in a baseline set would be a valid thing to do. The only way I can see around this is to close the baseline set without and declaring it "unusable".
Any other thoughts or insights?
Thanks in advance.
Robert Allen
Principal Software Engineer
Goodrich Corp - Sensors and Integrated Systems
rallen - Tue Nov 17 11:43:32 EST 2009 |