Configuration Management Plan

Size: px

Start display at page:

Download "Configuration Management Plan"

Britton Nelson
10 years ago
Views:

1 Project: Version: Prepared by: :

2 Approvals: Submitted By: Project Team Member Review Approvals By: Document Change Log Version Author Description ii

3 Table of Contents 1.0 Scope Configuration Management Resources Organization Responsibilities Facilities Tools Training Configuration Management Elements Configuration Management Planning Configuration Identification Configuration Items Software Builds Release Management Baseline Identification Configuration and Change Control Configuration Change Requests Change Control Authority Controlling Work Products Vendor Commercial-off-the-Shelf (COTS) Software Control Configuration Status Status Records Status Reports Configuration Management Measurements Software Baseline Audits 4 iii

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 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 projectdeveloped 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 1

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.

5 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 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: Software Builds Identify the code, files, compilers, development tools, and other components that are needed to create an official build: 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: 2

Present the updated version of the CM Plan to the peer review group 6. Approve CM Plan for implementation 7.

6 Describe how software items are released from the QUAL library to the Production library: 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 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: Change Control Authority Change Control Authority Delegated By Responsibilities Primary: Alternate: Describe how unresolved issues are escalated to upper management: 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: 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 Status Records Describe how the status of CM activities is created and maintained: 3

Baseline Contents Requirements Baseline Design Baseline Product Baseline Other: 3.

7 Identify each record needed to track CM activities: Status Reports CM Status Report Prepared For Due 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: 4

3 Configuration Management Measurements CM Measurement Prepared For Due 3.

<Project Name> Configuration Management Plan

<Project Name> Configuration Management Plan Version [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=infoblue) is included