www.CMCommunity.com

Software Configuration Management Plan

Software Configuration Management

Document History

CM Plan Approvals

Table of contents

1     Introduction........................................................................................................................................................................................................... 4

2     Purpose......................................................................................................................................................................................................................... 4

3     Scope.............................................................................................................................................................................................................................. 4

4     Promotion Model/SDLC................................................................................................................................................................................... 4

5     Labels / Tags in Version Control Ssyetm (Visual Source Safe)....................................................................................... 5

5.1      Labels- Common Codeline:............................................................................................................................................................................ 5

5.2      Labels-Project Codeline................................................................................................................................................................................ 5

6     Build Frequecny................................................................................................................................................................................................... 5

7     Configuration Management Items Matrix.................................................................................................................................... 5

8     Reference Documents..................................................................................................................................................................................... 7

8.1      Codeline Policy 1.0........................................................................................................................................................................................... 7

1         Introduction

IEEE Standards 828 (Standard for Software Configuration Management Plans) establishes the minimum required contents of the software configuration management plan. Theses standards are supplemented by IEEE standard 1042 (Guide to Software Configuration Management) that provides approaches to good Software Configuration Management Planning.

The CM plan documents what software configuration management activities are to be done . how they are to be done, who is responsible for doping specific activity, when they are happen, and what resources are required.

The Software Configuration Management Plan documents methods to be used for the identification of software items, control and implementation of change, and recording and reporting change implementation status. The plan describes methods used for:

• Identification of software configuration items
• Control and implementation of change
• Recording and reporting change and problem report implementation status
• Conducting configuration audits
• Review and approval cycles as well as approval authority
• Identification of personnel responsible for configuration management

A CM item can be any one of hardware, software, magnetic or optical media, machine data or documentation, indeed any product, which is a constituent of a larger product.

2         Purpose

To show how the components of a release and the changes to those components are to be managed to achieve project objectives.

3         Scope

The SCMP sets forth and/or incorporates by reference, the CM policies and procedures for software development of . It describes how the CM elements of configuration identification, change control, status accounting, and audits and reviews, shall be applied to establish and maintain the software configuration throughout the development or maintenance effort.

4         Promotion Model/SDLC

<

>

5         Labels / Tags in Version Control System

As defined in Codeline Policy Version 1.0

5.1        Labels- Common Codeline:

5.2        Labels-Project Codeline

6         Build Frequency

>

>

7         Configuration Management Items Matrix

NOTE: Document control is not implemented in this project, therefore, the document paths and naming convention is not enforced.

The documents for this project may be found in path:

8         Reference Documents