Configuration Management Plan
Project:
Version:
Prepared by:
Date:
ii
Approvals:
Submitted By:
Project Team Member Signature Date
Review Approvals By:
Signature Date
Signature Date
Signature Date
Signature Date
Document Change Log
Version Date Author Description
Table of Contents
iii
1.0 Scope 1
2.0 Configuration Management Resources 1
2.1 Organization 1
2.2 Responsibilities 1
2.3 Facilities 1
2.4 Tools 1
2.5 Training 1
3.0 Configuration Management Elements 2
3.1 Configuration Management Planning 2
3.2 Configuration Identification 2
3.2.1 Configuration Items 2
3.2.2 Software Builds 2
3.2.3 Release Management 2
3.2.4 Baseline Identification 3
3.3 Configuration and Change Control 3
3.3.1 Configuration Change Requests 3
3.3.2 Change Control Authority 3
3.3.3 Controlling Work Products 3
3.3.4 Vendor Commercial-off-the-Shelf (COTS) Software Control 3
3.4 Configuration Status 3
3.4.1 Status Records 3
3.4.2 Status Reports 4
3.4.3 Configuration Management Measurements 4
3.5 Software Baseline Audits 4
1
1.0 Scope
The scope of this project is:
Describe whether this Configuration Management Plan is a project-level plan (addressing a specific project) or a group-level plan (addressing more than one project):
Identify the system, program, or application to which this plan applies:
2.0 Configuration Management Resources
2.1 Organization
Identify the person(s) responsible for implementing CM activities on this project, and explain their relationship with the group manager and the project team:
2.2 Responsibilities
Identify roles and individual(s) by name and their CM responsibilities.
Role and Name CM Responsibility
Group Manager:
Project Manager:
CM Group:
SQA Group:
Developer(s):
Other:
2.3 Facilities
Describe the location (name and address) where all software development activities will take place and project- developed work products will be stored:
2.4 Tools
Describe the tools used to support software development and CM activities.
Tool Name Version Purpose
2.5 Training
Identify all training requirements needed by the software engineering group to implement project CM activities.
Training Topic Person in Need of Training
2
3.0 Configuration Management Elements
3.1 Configuration Management Planning
Configuration Management Plan Preparation procedure:
1. Assign responsibility for preparing the CM Plan 2. Gather data to be used and include in the CM Plan 3. Conduct a peer review of the CM Plan
4. Incorporate changes noted during the peer review
5. Present the updated version of the CM Plan to the peer review group 6. Approve CM Plan for implementation
7. Release the approved CM Plan
Identify the software development lifecycle model to be used on this project:
Lifecycle Phases, CM Activities, and Work Products:
Lifecycle Phase CM Activity Work Product
Inception Phase
Elaboration Phase
Construction Phase
Transition Phase
Production Phase
3.2 Configuration Identification
3.2.1 Configuration Items
Identify where all configuration items, including software baselines and work products, are stored in the table below.
Configuration Management Library:
Contents Responsible Person(s) Location
Library Backup Procedure:
Configuration Management Log procedure:
Describe the DEV environment:
Describe the TEST environment:
Describe the QUAL environment:
Describe the PROD environment:
3.2.2 Software Builds
Identify the code, files, compilers, development tools, and other components that are needed to create an official build:
3.2.3 Release Management
Describe the project software migration procedure:
Describe how software items are released from the Development library to the Test library:
Describe how software items are released from the Test library to the QUAL library:
3
Describe how software items are released from the QUAL library to the Production library:
3.2.4 Baseline Identification
Describe how baselines are established, managed, controlled, and stored:
Software Baseline Library:
Contents Responsible Person(s) Location
Software Baseline Identification:
Baseline Contents Requirements Baseline
Design Baseline
Product Baseline
Other:
3.3 Configuration and Change Control
3.3.1 Configuration Change Requests
Describe how problems are reported and approved using a Change Request:
Describe how change impact is assessed:
Describe how enhancements are identified, reviewed, and approved:
Describe how emergency production fixes are handled involving modules checked out:
Describe how each change or problem is peer reviewed:
3.3.2 Change Control Authority
Change Control Authority Delegated By Responsibilities
Primary:
Alternate:
Describe how unresolved issues are escalated to upper management:
3.3.3 Controlling Work Products
Describe the Checkout/Check-in procedure:
Describe how project-related software baselines and work products are controlled:
Describe how configuration items are versioned:
Describe labeling, branching, and merging procedures:
3.3.4 Vendor Commercial-off-the-Shelf (COTS) Software Control
Describe how the CM group controls all vendor-provided and supported (COTS) software, how changes are
evaluated for project impact, how the software is approved for use by the customer and project management, and the steps taken by the CM group to maintain a current record of the software:
3.4 Configuration Status
3.4.1 Status Records
Describe how the status of CM activities is created and maintained:
4 Identify each record needed to track CM activities:
3.4.2 Status Reports
CM Status Report Prepared For Due
3.4.3 Configuration Management Measurements
CM Measurement Prepared For Due
3.5 Software Baseline Audits
Describe the software baseline audit process:
Software Baseline Audit Schedule Audit Responsibility
Requirements Baseline
Design Baseline
Product Baseline
Other:
