Overview
In this activity, the software configuration management (SCM) manager defines the software change management process required to ensure that only approved changes are implemented into any baselined software product.
Roles and Responsibilities
The SCM manager defines the software change management process based on the project’s defined SCM needs.
Controls
The Software Configuration Management Volume, which describes the organization’s standard change management process (see activity 2.2. Dispositioning Software Configuration Management Reports and Requests).
Inputs
The completed Software Configuration Management Needs Form (see Appendix C).
The description of the software control boards and forms to be used, as documented in the Configuration Control section of the SCM Plan (SCMP) (see Appendix E).
Procedures
1) The SCM manager carefully reviews the Software Configuration Management Volume to gain a detailed knowledge of the organization’s standard change management process.
2) The SCM manager carefully reviews the software control board descriptions and forms to be used as documented in the Configuration Control section of the project’s SCMP.
3) The SCM manager should tailor (if necessary) the standard change management process (see activity 2.2 Dispositioning Software Configuration Management Reports and Requests).
Example:
If it has been determined that a Software Trouble Report Board (STRB) is needed then the SCM manager should define the actions of that board and how it would interface with the other control boards.
Any major changes to the standard change management process, as defined in the Software Configuration Management Volume, must be approved by the software engineering process group (SEPG). This approval may be obtained by submitting a Request for Deviation/Waiver (see Appendix C) request (see activities 2.2.1 Request Deviation/Waiver and 4.2.4 Maintain Process Standards) to the SEPG.
4) The SCM manager documents the project’s software change management process in the Configuration Control section of the SCMP. If no changes were made to the standard software change management process, this may simply be a reference to activity 2.2. Dispositioning Software Configuration Management Reports and Requests. If changes were made, the new activities should be documented and placed in the Configuration Control section of the SCMP with the changes clearly identified and any approved deviations referenced.
Outputs
The software change management process as documented in the Configuration Control section of the SCMP.