TO
BUY “Software Configuration Management Plan - Template” FROM AMAZON CLICK HERE
Configuration Management Plan Template.
Overview
The
purpose of Configuration Management (CM) is to establish and maintain the
integrity of the products of the projects throughout the system/software life
cycle.
Configuration Management involves identifying the
configuration of the system and comprising components (i.e., selected work
products and their descriptions) at given points in time, systematically
controlling changes to the configuration, and maintaining the integrity and
traceability of the configuration throughout the system/software life
cycle. The work products placed
under configuration management include the software products that are delivered
to the customer (e.g., the software requirements and product specifications and
the code) and the items that are identified with or required to create these
software products (e.g., the compiler).
All projects shall:
1. Prepare a
program CMP in accordance with this template and plan the configuration
management activities;
2. Identify,
control, and make available selected work products;
3. Control
changes to identified work products;
4. Inform
affected groups and individuals of the status and content of baselines;
5. Establish
a board having the authority for managing the project's baselines (i.e., a
software configuration control board - CCB);
6. Appoint a
group responsible for co-ordinating and implementing CM for the project (i.e.,
the CM group);
7. Provide
adequate resources and funding for performing the CM activities;
8. Train members
of the CM group in the objectives, procedures, and methods for performing their
CM activities;
9. Train
members of the software engineering group and other software-related groups to
perform their CM activities;
10.Update the
project Configuration Management plan (CMP) to reflect the current status
according to a documented procedure;
11.Use the
documented and approved project CM plan as the basis for performing the CM
activities;
12.Establish
a configuration management library system as a repository for the software
baselines;
13.Identify
the software work products to be placed under configuration management;
14.Initiate,
record, review, approve, and track change requests and problem reports for all
configuration items/units according to a documented procedure;
15.Control
changes to baselines according to a documented procedure;
16.Create
products from the baseline library and control their release according to a
documented procedure;
17.Record the
status of configuration items/units according to a documented procedure;
18.Develop
standard reports documenting the CM activities and the contents of the software
baseline and make available to affected groups and individuals;
19.Conduct
software baseline audits according to a documented procedure;
20.Make and
use measurements to determine the status of the CM activities;
21.Review the
CM activities with senior management on a periodic basis;
22.Review the
CM activities with the project manager on both a periodic and event-driven
basis;
23.Have the
CM group periodically audit software baselines to verify that they conform to
the documentation that defines them;
24.Conduct
reviews or audits by the software quality assurance group on the activities and
work products for CM and reports the results.
Software Project Managers shall be responsible for implementing
this policy.
The Software Engineering Management Group (SEMG) is
responsible for maintaining this policy.
-----------------------------------------------------------------------------------------------------------------------------------
This
Configuration Management Plan (CMP) template has been prepared to meet the
minimum requirements of MIL-STD-973, ISO 12207/MIL-STD 498 and SEI “Best
Practices” (CMM level 3) for the participating projects. The CMP template shall be applicable to
all system/subsystems, CSCIs, and aggregate software and shall be adopted by
all participating developers and subcontractors.
This document provides Configuration Management
(CM) planning for achieving the "Repeatable" level on the Software
Engineering Institute's (SEI's) Capability Maturity Model (CMM) and meeting the
ISO/IEC 12207, ISO/IEC 15288, MIL-STD-498 and MIL-STD-973 requirements. It describes the identified CM
interfaces, inputs, outputs, and products common to all projects. This document contains information on
the roles and responsibilities of the CM organization, and software-related
groups (including software developers and subcontractors), as well as programme
and project management's role in CM activities. The CM Process definition and CM detailed procedures (CMDP)
have been developed as companion documents to be used by all participants in
the projects. These documents,
when treated as a unit or set, contain all the requirements for a CM
organization to implement project CM as well as to achieve a repeatable level
and meet all the requirements for Configuration Management.
This document was
developed to provide any project developing software with a template for
generating a project specific Software Configuration Management Plan
(CMP). This template shall be used
with project-specific information to produce an CMP that accurately describes
the specific project’s CM organization, role, responsibilities, current
baselines, and change reports. This
document shall supplement the “Software Development Plan Template” document by
providing an CMP template that a project shall use to generate a specific
software project CMP.
The CMP is the document
that allows all personnel including the customer insight into all stages of the
CM process. It identifies the
CSCI, CSA, schedules, and CM capabilities of the software developer's
organization. The plan serves a
basis for managing and tracking the CM activities defined to accomplish the
development of the project’s software.
The CMP documents each group's responsibility for the CM of the
software.
SEMG will maintain this
"CMP Template". Users of
this document may report deficiencies and or corrections using the format
provided by the attached Document Change Request (DCR) form. SEMG shall configuration manage this
data as part of the process improvements to the “CMP Template”.
SEMG will maintain this
"CMP Template". Users of
this document may report deficiencies and or corrections using the format
provided by the attached Document Change Request (DCR) form. SEMG will configuration manage this
data as part of the process improvements to the “CMP Template”.
SEMG
shall be responsible for the Software Management policy and will be responsible
for the preparation of all the required management processes required to
harmonize the development of system components CSCIs and HWCIs across the
program.
The
purpose of the Organizational Program Management Plan/Process” is to satisfy
the SW Management Policy. This
process will be as required by ISO/IEC 15288, ISO/IEC 12207, MIL-STD-498, and
the SEI/CMMI “Best Practices”.
TO
BUY “Software Configuration Management Plan - Template” FROM AMAZON CLICK HERE
Back to Home page MANAGING STANDARDS
Home page
Please send any
beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk