Software Configuration Management Knowledge Area

Software Configuration Management (SCM) is the discipline of identifying the configuration of a system at distinct points in time for the purpose of systematically controlling changes to the software configuration and maintaining the integrity and traceability of the configuration throughout the system lifecycle. This knowledge area includes six sub-areas.

The first sub-area is the management of the SCM process. It covers the topics of the organizational context for SCM, constraints and guidance for SCM, planning for SCM, the SCM plan itself, and surveillance of SCM.

The second sub-area is software configuration identification, which identifies items to be controlled, establishes identification schemes for the items and their versions, and establishes the tools and techniques to be used in acquiring and managing controlled items. The topics in this sub-area are the identification of the items to be controlled and the software library.

The third sub-area is the software configuration control, which is the management of changes during the software life cycle. The topics are

The fourth sub-area is software configuration status accounting. Its topics are software configuration status information and status reporting.

The fifth sub-area is software configuration auditing. Consisting of software functional configuration auditing, software physical configuration auditing, and in-process audits of a software baseline.

The last sub-area is software release management and delivery, covering software building, and software release management.

The above summary was adapted from the Introduction to the IEEE Computer Society's SWEBOK Guide. For more information on the Software Requirements Knowledge Area, read Chapter 7 of the SWEBOK Guide.

Standards

Standard:

Title:

Abstract:

IEEE Std 730™-2002

IEEE Standard for Software Quality Assurance Plans

The standard specifies the format and content of software quality assurance plans. It meets the IEEE/EIA 12207.1 requirements for such plans.

IEEE Std 828™-1998

IEEE Standard for Software Configuration Management Plans

The minimum required contents of a Software Configuration Management Plan (SCMP) are established, and the specific activities to be addressed and their requirements for any portion of a software product's life cycle are defined.

IEEE Std 1028™-1997

IEEE Standard for Software Reviews

This standard defines five types of software reviews, together with procedures required for the execution of each review type. This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.

About IEEE standard numbers.