State Transitions In Hierarchical Change Requests

Early Working Draft This is used to describe state transitions in hierarchical Change Requests with a couple of scenarios. In being under development, it is NOT recommended

This scenario will focus on creating a number of Change Requests from a requirement document in which a Test Case has been assigned to each of the Change Requests for verification.

Scenario

Pre-conditions

• A requirement management (RM) repository exists
  • The RM repository has one or more requirements.
  • The requirements change management capability in the RM repository is enabled.
• A change management (CM) repository exists.
  • A change request type exists.
• A quality management (QM) repository exists.
• Cross-server communication is established between the RM, CM, and QM repositories

Post-conditions

• One Change Request is created for each Requirement.
• One Test Case is created for each Change Request.
• A state transition of a Test Case may trigger a roll-up state transition to its Change Request.
• A state transition of a Change Request may trigger a roll-up state transition to its parent Requirement.

Steps

*(Step 1) Product Manager: Submit a Requirement

1. In the requirements management repository, create multiple requirements based on customer's scenario.

*(Step 2) Requirement Engineer: Submit Change Requests

1. Open the Requirement(s)
2. Submit a Change Request for each selected requirement

*(Step 3) Change Request Engineer: Start working then Resolve one of the Change Requests

1. Open and identify the work required for the Change Request
2. Set the Change Request to In Progress
3. Check in changes associated with the Change Request to an SCM system
4. Set the Change Request to Resolved, which will set the Requirement to Completed

*(Step 4) Quality Engineer: Create a Test Case for each Change Request

1. Open the resolved Change Request then create a Test Case for it
2. Execute the test against the Change Request's fix
3. Set the Test Case to Failed as the fix does not satisfy the Change Request. This action will reopen the Change Request since it is the only child of the Change Request. The Change Request's state transition in turn will reopen the Requirement.