DEFENSE FINANCE AND ACCOUNTING SERVICE

Configuration Management Plan

For

Program Name

Date of Issue and Status: Date plan acknowledged as acceptable (mm/dd/yyyy) and whether plan is draft or approved. Also include version number.

Issuing organization: Identify the organization issuing this plan.

CONFIGURATION MANAGEMENT PLAN

1. Purpose. This plan specifies processes and procedures for the execution of configuration management (CM) to support the entire software change/modification process.

2. Scope. This plan applies to all activities related to the establishment of system/configuration baseline and change and release of application configuration items (CIs). These CIs are identified in appendices to this plan.

3. Software Configuration Management Structure.

3.1. Organizational Components. Identify the organizational units or teams responsible for the system’s CM activities.

3.1.1. Systems Engineering. Identify and describe the systems engineering activities and tasks that will be accomplished and how the results of these efforts will be documented.

3.1.2. Configuration Management. Identify and describe CM tasks that will be performed.

3.1.3. Development Platform Engineering Team (DPET). Identify and describe the integration of release management procedures with informational and technical requirements necessary for release of software for test and production.

3.1.4. Configuration Control Board (CCB). Identify and describe the membership, roles, and responsibilities of the CCB.

3.2. Configuration Management Responsibilities. Describe the responsibilities of the organizational components performing CM activities.

3.2.1. Configuration Item Identification. Identify who is responsible for CI identification.

3.2.2. Configuration Control. Identify who is responsible for configuration control and describe the procedures for accomplishing configuration control (CI identification, establishing baselines, changes, deviations, waivers, configuration change orders (CCOs), CCB requirements).

3.2.3. Configuration Status Accounting. Identify who is responsible for configuration status accounting and describe the procedures for accomplishing configuration status accounting (CIs, baselines, records, databases, etc.) requirements.

3.2.4. Audits and Reviews. Identify the responsibilities involved in audits and reviews and describe what will be accomplished during each audit and review.

4. Software Configuration Management (SCM) Activities.

4.1. Configuration Identification. Describe the procedures for meeting the CI requirements, including a description of activities for identifying CIs and baseline items, formation of releases, and baselining of products.

4.2. Configuration Control. Describe the configuration control activities, including level of authority for approval, change proposal processing, and CCB roles and procedures.

4.3. Configuration Status Accounting. Identify reports required for status accounting, i.e., the status of CIs, SCRs, and releases.

4.4. Audits and Reviews. Describe the formal review/audit procedures to be used for configuration audits and reviews (functional configuration audits and physical configuration audits).

4.5. Scheduling and Tracking of SCM Activities. Describe the scheduling and tracking of CM activities that will be accomplished for each release.

5. Library Management. Describe the procedures to be used for development library environment management, release management library environment management, validation testing library environment management, and release certification.

6. Tools, Techniques, and Methodologies. Identify tools and techniques and describe any unique methodologies used to accomplish effective CM.

7. Records Collection and Retention. Identify CM information to be retained and the locations and methods of retention.

8. Procedures for Updating Plan. Describe the steps required to modify the plan to include version number and methodology.

9. Change Information Sheet. List the changes and additions included in the current version of the plan.

CONFIGURATION MANAGEMENT PLAN

APPENDIX A – ACRONYMS

Describe the acronyms as they are used in the plan.

APPENDIX B – DEFINITIONS

Describe the key terms as they are used in the plan.

APPENDIX C – REFERENCES

Provide a complete list of documents referenced in the text of the plan. Each reference shall contain, as approp