![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Change Management Topic Summary: Moving Requirements Created On: 16-Jan-2009 19:00 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am the Requirements Manager for my project which basically involves the implementation of the Change Proposal System and Module organization. I am wrestling with an idea about managing my requirements. For all requirement attribute changes (Text, VM, Safety...etc) I require that individuals submit change proposals. DOORS' CPS accommodates that very well, but I am not sure how to manage the moving of a requirement. Should I just move it without going through the CPS? If not, how do I capture requirment moves? CPS only has Modify, Delete and Add. My thought was that since all of my requirements have an increment # (When its Implemented), nothing is really changing about that requirement. Do you think I should be capturing requirement Moves?
for clarification. A requirement move is when I move requirement 123 from Section 1 to section 2. |
|
![]() |
|
![]() |
|
Rashaad,
Here is how I handle that: When someone wants to move a requirement to a different section, I still require them to submit a CP and, in the Reason for Change field, explain what they want. That way the request will still get reviewed. You have to make some attribute change in the CP to be able to submit it so I just have them add a space bar after a paragraph ending in the Object Text or something like that. When the CP is approved, I manually make the modification in the module then in the CP's property sheet in the Proposals module, I change the Status attribute to Applied. I know we're told not to manually edit the Proposals document but it would impose severe limitations not to. Hope that helps, Nancy |
|
![]() |
|
![]() |
|
We put a 'Cp-Instructions' string attribute in all the modules and configured that for CPS. Folks who requied to do non-standard things would insert instructions therein on the CP. Moving isn't the only thing you may want to do, undeleting was another. That was a little clumsy.
Smith's idea is sound so long as the CP Reason clearly states such things as Instructions. I would NOT use Object Text as a target attribute, instead use some benign string attribute to add spaces to. Another option is to edit the CPS module after CP generation, and set false the corresponding Using flag of the attribute you 'modified' on the CP submit form; thus nothing will happen when you 'apply' the CP. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Change Management
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.