2.0 PERFORM SOFTWARE CONFIGURATION MANAGEMENT

Overview

The purpose of software configuration management (SCM) is to establish and maintain the integrity of the project’s software products. This activity includes: controlling software changes, placing software products under configuration control, and controlling the release of software products to the field. SCM activities occur throughout the software life cycle of the project.

Roles and Responsibilities

The SCM manager is responsible for all SCM activities.

The SCM staff is responsible for SCM activities delegated by the SCM manager.

Controls

The project’s SCM Plan (SCMP) (see Appendix E), written, approved, and available to the SCM manager and SCM staff.

Inputs

Approved software products to be placed under SCM.

Dispositioned Requests for Deviation/Waiver from the software engineering process group (SEPG).

Procedures

Before performing any SCM activities described in this volume, the SCM staff should read and understand the project’s SCMP. The SCM manager oversees the SCM staff throughout the project.

This activity consists of the following subactivities. Note: Subactivities 2.1. Place Software Products Under Software Configuration Management and 2.2. Dispositioning Software Configuration Management Reports or Requests are performed throughout the software life cycle. While performing these subactivities, software metrics are reported to the SEPG.

1) 2.1. Place Software Products Under Software Configuration Management. This subactivity describes the processes of placing an item under SCM control and configuration status accounting, and the handling of versions and revisions.

2) 2.2. Dispositioning Software Configuration Management Reports or Requests. This subactivity describes the change control process, including writing Software Change Requests (SCR), Software Trouble Reports, and Requests for Deviation/Waiver (see Appendix C for forms). This subactivity also includes analyzing these requests, conducting Software Control Board (SCB) meetings, and submitting items to be placed on the Configuration Control Board (CCB) candidate list.

3) 2.3. Prepare Software Products for Delivery. This subactivity describes the development of the Software Version Description (SVD) (see Appendix E), audits performed before releasing any software products (i.e., Physical Configuration Audit (PCA) and Functional Configuration Audit (FCA)), and all SCM activities related to releasing software products into the field.

Outputs

Metrics, which are generated throughout the project’s life cycle, as specified in the SCMP.

The approved SCRs and Requests for Deviation/Waiver, which are stored in the project’s SCM tracking system.

Requests for Deviation/Waiver from the organization’s standard software process, which must be approved by the software engineering process group (SEPG).

Software products, which are placed in the organization’s asset library at the completion of the project.