Overview
This activity describes the process for writing Software Change Requests (SCR). All SCR information is stored in the project’s software configuration management (SCM) tracking system. SCRs are generally written by individuals working on the project prior to qualification testing or as a result of Configuration Change Requests (CCR) or Software Trouble Reports.
Roles and Responsibilities
The requester requesting a change in a software product is responsible for writing a SCR, entering it into the project’s SCM tracking system, and notifying the project software manager and the SCM manager.
The SCM manager is responsible for verifying that the SCR was properly written and correctly entered into the SCM tracking system.
Controls
The SCR form and instructions, (see Appendix C), which are documented in the Configuration Control section of the project’s SCM Plan (SCMP) (see Appendix E).
Inputs
An identified need for change in a software product.
An Software Trouble Report or Request for Deviation/Waiver (see Appendix C).
An approved CCR, which may have been issued at the project level, requiring one or more SCRs to be written (in this case, the requester is the project software manager).
Procedures
Note: Forms may be electronic or hard-copy and are provided by the SCM manager.
1) The requester documents the requested change and its justification on a SCR, and enters it into the SCM tracking system. The requester references any materials or information that may be needed to make the necessary changes. If a CCR, Request for Deviation/Waiver, or Software Trouble Report has led to or has been required by the SCR, the requester also references it on the SCR.
2) The requester notifies the software engineering manager, project software manager, and SCM manager of the new SCR via E-mail. This notification is in addition to any automatic notification that the project’s SCM tracking system may provide.
3) The SCM manager reviews the SCR, and verifies that it was properly written and was correctly entered into the SCM tracking system. If allowed by the SCM tool, the SCM manager may place access restrictions on the SCR, giving write access only to those individuals who require it (normally only the project software manager).
Output
The SCR, which has been entered into the project’s SCM tracking system.