![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: What is the best way to implement parallel development? Topic Summary: Created On: 1-Feb-2005 20:41 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
You have a multi-enumerated attribute "Release" with enumerations "Rel-1", "Rel-2", "Rel-3", and "Rel-All". All objects must choose at least one value. Headings typically will choose Rel-All. If an object is different for different releases then make it two objects, the first applies to "Rel-1" and the second applies to "Rel-2" and "Rel-3". When Exporting the module, say for Release 2, be sure to filter for objects that contain Rel-2 or Rel-All.
I'd be tempted to insist that all headings are Rel-All. If the heading really doesn't apply to a particular release then add an object "Not Applicable" that applies to that Release. If you have only slight changes between releases, you can realistically insert something like this in the Object Text: "... shall respond in less than [Rel1: 120ms; Rel2orHigher: 110ms] ...". Be sure to have a standard format for such insertions since you WILL eventually want to find them with DXL and/or filter for them. - Louie |
|
![]() |
|
![]() |
|
When I first joined this company, we were using this process to control variants. It was a nightmare because creating new objects destroyed links. You would spend half a day updating a module then the next day sorting out the links. We have just started work on the next build standard of our equipment and I have elected to create a new project within the project containing copies all the required modules. This has worked so far.
My original intention was to use the new DOORS baseline sets feature to baseline the previous build standard but it didn't work. (Be aware the link wizard at V7.1 puts in extra code to cope with sets and you can't change legacy Attribute DXL once it is baselined.) In the event, seperate projects has worked because we have done more work on the previous build standard. Edited: 4-Feb-2005 at 10:54 by Peter Seager |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.