Activity: Submit Change Request Purpose This activity logs a requested change. Change Requests may include requests for new features, enhancements, corrections, changed requirements, and so on. Any role may submit a change request as part of any activity throughout the project lifecycle. Role:  Any Role  Frequency: Once a configuration item has been baselined and entered into the configuration management system, all requests to changes to it should go through the official change request management process.  Steps Complete Change Request Form Submit the Change Request Resulting Artifacts:  Change Request   Tool Mentors:  Submitting Change Requests Using Rational ClearQuest   Workflow Details:  Configuration & Change Management Manage Change Requests     Complete Change Request Form The Change Request Form isa formally submitted artifact that is used to track all requests (including new features, enhancement requests, defects, changed requirements, etc.) along with related status information throughout the project lifecycle. All change history will be maintained with the CR, including all state changes along with dates and reasons for the change. This information will be available for any repeat reviews and for final closing. An example Change Request Form is provided in Artifact: Change Requests.   Submit the Change Request Once the CR is completed, it should be submitted through the proper channels to assure compliance with the established Change Request Management Process. Any stakeholder on the project can submit a Change Request (CR). The CR is logged into the CR Tracking System (e.g., ClearQuest) and is placed into the CCB Review Queue, by setting the CR state to Submitted. Typical states that a Change Request may pass through are shown in Concepts: Change Request Management) © Copyright IBM Corp. 1987, 2004. All Rights Reserved.

Rational Unified Process