Subversion - hudson - trac

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 to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=BodyText).] [To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field andpress F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]

 Configuration Management Plan

Version: Date:

Revision History
Date Version Description Author

Confidential

©, 2010

Page 2 of 6

 Configuration Management PlanVersion: Date:

Table of Contents
1. Introduction 1.1 1.2 1.3 1.4 1.5 2. Purpose Scope Definitions, Acronyms, and Abbreviations References Overview 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 5 6 6 6

Software Configuration Management 2.1 2.2 Organization, Responsibilities, and Interfaces Tools, Environment, and Infrastructure

3.

The Configuration Management Program 3.1 ConfigurationIdentification 3.1.1 Identification Methods 3.1.2 Project Baselines Configuration and Change Control 3.2.1 Change Request Processing and Approval 3.2.2 Change Control Board (CCB) Configuration Status Accounting 3.3.1 Project Media Storage and Release Process 3.3.2 Reports and Audits

3.2

3.3

4. 5. 6.

Milestones Training and Resources Subcontractor and Vendor Software Control

Confidential

©,2010

Page 3 of 6

 Configuration Management Plan

Version: Date:

Configuration Management Plan
1. Introduction
[The introduction of the Configuration Management Plan provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Configuration Management Plan.] 1.1 Purpose [Specify the purpose ofthis Configuration Management Plan.] 1.2 Scope [A brief description of the scope of this Configuration Management Plan; what model it is associated with and anything else that is affected or influenced by this document.] 1.3 Definitions, Acronyms, and Abbreviations [This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the ConfigurationManagement Plan. This information may be provided by reference to the project’s Glossary.] 1.4 References [This subsection provides a complete list of all documents referenced elsewhere in the Configuration Management Plan. Identify each document by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This informationmay be provided by reference to an appendix or to another document.] 1.5 Overview [This subsection describes what the rest of the Configuration Management Plan contains and explains how the document is organized.]

2.

Software Configuration Management

2.1 Organization, Responsibilities, and Interfaces [Describe who is going to be responsible for performing the various ConfigurationManagement (CM) activities described in the CM Process Discipline.] 2.2 Tools, Environment, and Infrastructure [Describe the computing environment and software tools to be used in fulfilling the CM functions throughout the project or product lifecycle. Describe the tools and procedures required used to version control configuration items generated throughout the project or product lifecycle. Issues...