Configuration Management (CM) Category: Support
Notes:
·
The contents of this web page were extracted from
the following document: Capability
Maturity Model® Integration (CMMISM), Version 1.1, Continuous Representation, CMU/SEI-2002-TR-011,
March 2002 (CMMI-SE/SW/IPPD/SS). Copyright 2002 by Carnegie Mellon University.
NO WARRANTY.
·
Ignore the identifiers
in square brackets that appear at the end of paragraphs.
·
The formatting may not
be the same as in the printed CMMI document. The web page is best viewed in
Internet Explorer.
·
In the CMMI, a subset is known as a "Process Area
(PA)" and a requirement is known as a "Practice". The specific practices are
referred to as SPs and the generic practices are referred to as GPs.
·
This web page contains the text for SPs and GPs as
it appears in Chapter 7 of the CMMI document, in the section corresponding to
the process area named in the heading of this page. This web page does not
include the detailed description of the GPs that appears in a separate chapter
of the CMMI document; the detailed description of the GPs
is available in a separate web page. (Note: Using the hyperlink provided here
will open that web page in a separate window.)
Purpose The
purpose of Configuration Management is to establish and maintain the integrity
of work products using configuration identification, configuration control,
configuration status accounting, and configuration audits. [PA159]
Introductory Notes
The
Configuration Management process area involves the following: [PA159.N101]
· Identifying the configuration of selected work products that compose the baselines at given points in time
· Controlling changes to configuration items
· Building or providing specifications to build work products from the configuration management system
· Maintaining the integrity of baselines
· Providing accurate status and current configuration data to developers, end users, and customers
The work
products placed under configuration management include the products that are
delivered to the customer, designated internal work products, acquired products,
tools, and other items that are used in creating and describing these work
products. See the definition of “configuration management” in Appendix C, the
glossary. [PA159.N102]
For Supplier Sourcing
Acquired products may need to be placed under configuration management by both the supplier and the project. Provisions for conducting configuration management should be established in supplier agreements. Methods to ensure that the data is complete and consistent should be established and maintained. [PA159.N102.AMP101]
Examples of work products that may be placed under configuration management
include the following: [PA159.N109]
· Plans
· Process descriptions
· Requirements
· Design data
· Drawings
· Product specifications
· Code
· Compilers
· Product data files
· Product technical publications
Configuration management of work products may be performed at several levels of
granularity. See the definition of “configuration item” in Appendix C, the
glossary. Configuration items can be decomposed into configuration components
and configuration units. Only the term “configuration item” is used in this
process area. Therefore, in these practices, “configuration item” may be
interpreted as “configuration component” or “configuration unit” as appropriate. [PA159.N103]
Baselines
provide a stable basis for continuing evolution of configuration items. See the
definition of “baseline” in Appendix C, the glossary.
[PA159.N104]
An
example of a baseline is an approved description of a product that includes
internally consistent versions of requirements, requirement traceability
matrices, design, discipline-specific items, and end-user documentation. [PA159.N110]
Baselines
are added to the configuration management system as they are developed. Changes
to baselines and the release of work products built from the configuration
management system are systematically controlled and monitored via the
configuration control, change management, and configuration auditing functions
of configuration management. [PA159.N105]
This
process area applies not only to configuration management on projects, but also
to configuration management on organization work products such as standards,
procedures, and reuse libraries. [PA159.N106]
Configuration management is focused on the rigorous control of the managerial
and technical aspects of work products, including the delivered system. [PA159.N107]
This
process area covers the practices for performing the configuration management
function and is applicable to all work products that are placed under
configuration management. [PA159.N108]
Refer
to the Project Planning process area for information on developing plans and
work breakdown structures, which may be useful for determining configuration
items. [PA159.R101]
Refer
to the Causal Analysis and Resolution process area for more information about
both the method to use for analyzing the impact of change requests and the
method to use when evaluating changes. [PA159.R102]
Refer
to the Project Monitoring and Control process area for more information about
performance analyses and corrective actions.
[PA159.R103]
Specific Goals
SG 1
Establish Baselines [PA159.IG101]
Baselines of identified work products are established.
SG 2
Track and Control Changes [PA159.IG102]
Changes to the work products under configuration management are tracked and controlled.
SG 3
Establish Integrity [PA159.IG103]
Integrity of baselines is established and maintained.
Generic Goals
GG 1
Achieve Specific Goals [CL102.GL101]
The process supports and enables achievement of the specific goals of the process area by transforming identifiable input work products to produce identifiable output work products.
GG 2
Institutionalize a Managed Process [CL103.GL101]
The process is institutionalized as a managed process.
GG 3
Institutionalize a Defined Process [CL104.GL101]
The process is institutionalized as a defined process.
GG 4
Institutionalize a Quantitatively Managed Process
[CL105.GL101]
The process is institutionalized as a quantitatively managed process.
GG 5
Institutionalize an Optimizing Process [CL106.GL101]
The process is institutionalized as an optimizing process.
Practice-to-Goal Relationship Table
SG 1 Establish Baselines
[PA159.IG101]
SP 1.1-1 Identify Configuration Items
SP 1.2-1 Establish a Configuration Management System
SP 1.3-1 Create or Release Baselines
SG 2 Track and Control Changes
[PA159.IG102]
SP 2.1-1 Track Change Requests
SP 2.2-1 Control Configuration Items
SG 3 Establish Integrity
[PA159.IG103]
SP 3.1-1 Establish Configuration Management Records
SP 3.2-1 Perform Configuration Audits
GG 1 Achieve Specific Goals [CL102.GL101]
GP 1.1 Perform Base Practices
GG 2 Institutionalize a Managed Process [CL103.GL101]
GP 2.1 Establish an Organizational Policy
GP 2.2 Plan the Process
GP 2.3 Provide Resources
GP 2.4 Assign Responsibility
GP 2.5 Train People
GP 2.6 Manage Configurations
GP 2.7 Identify and Involve Relevant Stakeholders
GP 2.8 Monitor and Control the Process
GP 2.9 Objectively Evaluate Adherence
GP 2.10 Review Status with Higher Level Management
GG 3 Institutionalize a Defined Process [CL104.GL101]
GP 3.1 Establish a Defined Process
GP 3.2 Collect Improvement Information
GG 4 Institutionalize a Quantitatively Managed Process [CL105.GL101]
GP 4.1 Establish Quantitative Objectives for the Process
GP 4.2 Stabilize Subprocess Performance
GG 5 Institutionalize an Optimizing Process [CL106.GL101]
GP 5.1 Ensure Continuous Process Improvement
GP 5.2 Correct Root Causes of Problems
Specific Practices by Goal
SG 1 Establish Baselines
Baselines of identified work products are established. [PA159.IG101]
Specific
practices to establish baselines are covered by this specific goal. The specific
practices under the Track and Control Changes specific goal serve to maintain
the baselines. The specific practices of the Establish Integrity specific goal
document and audit the integrity of the baselines. [PA159.IG101.N101]
SP 1.1-1 Identify Configuration Items
Identify the configuration items, components, and related work products that
will be placed under configuration management.
[PA159.IG101.SP101]
Configuration identification is the selection, creation, and specification of
the following: [PA159.IG101.SP101.N101]
· Products that are delivered to the customer
· Designated internal work products
· Acquired products
· Tools
· Other items that are used in creating and describing these work products
Items
under configuration management will include specifications and interface
documents that define the requirements for the product. Other documents, such as
test results, may also be included, depending on their criticality to defining
the product. [PA159.IG101.SP101.N104]
A
“configuration item” is an entity designated for configuration management, which
may consist of multiple related work products that form a baseline. This logical
grouping provides ease of identification and controlled access. The selection of
work products for configuration management should be based on criteria
established during planning. [PA159.IG101.SP101.N102]
For Systems Engineering
In a system that includes both hardware and software, where software represents a small part of the system, all of the software may be designated as a single configuration item. In other cases, the software may be decomposed into multiple configuration items. [PA159.IG101.SP101.N102.AMP101]
Configuration items can be decomposed into configuration components and
configuration units. Only the term “configuration item” is used in this process
area. In these practices, “configuration item” may be interpreted as
“configuration component” or “configuration unit” as appropriate. For example,
configuration items in the area of requirements management could vary from each
individual requirement to a set of requirements. [PA159.IG101.SP101.N103]
Typical Work Products
1. Identified
configuration items [PA159.IG101.SP101.W101]
Subpractices
1. Select the configuration items
and the work products that compose them based on documented criteria.
[PA159.IG101.SP101.SubP101]
Example criteria for selecting configuration items at the appropriate work
product level include the following:
[PA159.IG101.SP101.SubP101.N102]
· Work products that may be used by two or more groups
· Work products that are expected to change over time either because of errors or change of requirements
· Work products that are dependent on each other in that a change in one mandates a change in the others
· Work products that are critical for the project
Examples of work products that may be part of a configuration item include the
following: [PA159.IG101.SP101.SubP101.N101]
· Process descriptions
· Requirements
· Design
· Test plans and procedures
· Test results
· Interface descriptions
For Software Engineering
Examples of software work products that may be part of a configuration item include the following: [PA159.IG101.SP101.SubP101.N101.AMP101]
A. Code/module
B. Tools (e.g., compilers)
2. Assign unique identifiers to
configuration items. [PA159.IG101.SP101.SubP102]
3. Specify the important
characteristics of each configuration item. [PA159.IG101.SP101.SubP103]
Example characteristics of configuration items include author, document or file
type, and programming language for software code files.
[PA159.IG101.SP101.SubP103.N101]
4. Specify when each
configuration item is placed under configuration management.
[PA159.IG101.SP101.SubP104]
Example criteria for determining when to place work products under configuration
management include the following:
[PA159.IG101.SP101.SubP104.N101]
· Stage of the project life cycle
· When the work product is ready for test
· Degree of control desired on the work product
· Cost and schedule limitations
· Customer requirements
5. Identify the owner responsible
for each configuration item. [PA159.IG101.SP101.SubP105]
SP 1.2-1 Establish a Configuration Management System
Establish and maintain a configuration management and change management system
for controlling work products.
[PA159.IG101.SP102]
A
configuration management system includes the storage media, the procedures, and
the tools for accessing the configuration system.
[PA159.IG101.SP102.N101]
A change
management system includes the storage media, the procedures, and tools for
recording and accessing change requests.
[PA159.IG101.SP102.N102]
Typical Work Products
1. Configuration
management system with controlled work products [PA159.IG101.SP102.W101]
2. Configuration
management system access control procedures [PA159.IG101.SP102.W102]
3. Change
request database [PA159.IG101.SP102.W103]
Subpractices
1. Establish a mechanism to
manage multiple control levels of configuration management.
[PA159.IG101.SP102.SubP101]
Examples of situations leading to multiple levels of control include the
following: [PA159.IG101.SP102.SubP101.N101]
· Differences in the levels of control needed at different times in the project life cycle (e.g., tighter control as product matures)
· Differences in the levels of control needed for different types of systems (e.g., software-only systems versus systems that include hardware and software)
· Differences in the levels of control needed to satisfy privacy and security requirements for the configuration items
2. Store and retrieve
configuration items in the configuration management system.
[PA159.IG101.SP102.SubP102]
Examples of configuration management systems include the following: [PA159.IG101.SP102.SubP102.N101]
· Dynamic (or developer’s) systems contain components currently being created or revised. They are in the developer's workspace and are controlled by the developer. Configuration items in a dynamic system are under version control.
· Master (or controlled) systems contain current baselines and changes to them. Configuration items in a master system are under full configuration management as described in this process area.
· Static systems contain archives of various baselines released for use. Static systems are under full configuration management as described in this process area.
3. Share and transfer
configuration items between control levels within the configuration management
system. [PA159.IG101.SP102.SubP103]
4. Store and recover archived
versions of configuration items. [PA159.IG101.SP102.SubP104]
5. Store, update, and retrieve
configuration management records. [PA159.IG101.SP102.SubP105]
6. Create configuration
management reports from the configuration management system.
[PA159.IG101.SP102.SubP106]
7. Preserve the contents of the
configuration management system. [PA159.IG101.SP102.SubP107]
Examples of preservation functions of the configuration management system
include the following: [PA159.IG101.SP102.SubP107.N101]
· Backups and restoration of configuration management files
· Archiving of configuration management files
· Recovery from configuration management errors
8. Revise the configuration
management structure as necessary. [PA159.IG101.SP102.SubP108]
SP 1.3-1 Create or Release Baselines
Create or release baselines for internal use and for delivery to the customer. [PA159.IG101.SP103]
A baseline
is a set of specifications or work products that has been formally reviewed and
agreed upon, that thereafter serves as the basis for further development, and
that can be changed only through change control procedures. A baseline
represents the assignment of an identifier to a configuration item and its
associated entities. [PA159.IG101.SP103.N101]
For Systems Engineering
Release of a baseline involves approving a set of configuration data for the agreed-upon set of configuration items from the configuration management system and releasing the baseline for further development. Multiple baselines may be used to define an evolving product during its development cycle. One common set includes the system-level requirements, system-element-level design requirements, and the product definition at the end of development/beginning of production. These are referred to as the “functional baseline,” “allocated baseline,” and “product baseline.” [PA159.IG101.SP103.N101.AMP101]
For Software Engineering
A set of requirements, design, source code files and the associated executable code, build files, and user documentation (associated entities) that have been assigned a unique identifier can be considered to be a baseline. Release of a baseline constitutes retrieval of source code files (configuration items) from the configuration management system and generating the executable files. A baseline that is delivered to a customer is typically called a “release” whereas a baseline for an internal use is typically called a “build.” [PA159.IG101.SP103.N101.AMP102]
Typical Work Products
1. Baselines [PA159.IG101.SP103.W101]
2. Description
of baselines [PA159.IG101.SP103.W102]
Subpractices
1. Obtain authorization from the
configuration control board (CCB) before creating or releasing baselines of
configuration items. [PA159.IG101.SP103.SubP101]
2. Create or release baselines
only from configuration items in the configuration management system. [PA159.IG101.SP103.SubP102]
For Systems Engineering
Ensure that the configuration items are built to the correct drawing. [PA159.IG101.SP103.SubP102.AMP101]
3. Document the set of
configuration items that are contained in a baseline.
[PA159.IG101.SP103.SubP103]
4. Make the current set of
baselines readily available. [PA159.IG101.SP103.SubP104]
SG 2 Track and Control Changes
Changes to the work products under configuration management are tracked and
controlled.
[PA159.IG102]
The
specific practices under this specific goal serve to maintain the baselines
after they are established by the specific practices under the Establish
Baselines specific goal. [PA159.IG102.N101]
SP 2.1-1 Track Change Requests
Track change requests for the configuration items.
[PA159.IG102.SP101]
Change
requests address not only new or changed requirements, but also failures and
defects in the work products. [PA159.IG102.SP101.N101]
Change
requests are analyzed to determine the impact that the change will have on the
work product, related work products, and schedule and cost. [PA159.IG102.SP101.N102]
Typical Work Products
1. Change
requests [PA159.IG102.SP101.W101]
Subpractices
1. Initiate and record change
requests in the change request database. [PA159.IG102.SP101.SubP101]
2. Analyze the impact of changes
and fixes proposed in the change requests.
[PA159.IG102.SP101.SubP102]
Changes are evaluated through activities that ensure that they are consistent
with all technical and project requirements.
[PA159.IG102.SP101.SubP102.N101]
Changes are evaluated for their impact beyond immediate project or contract
requirements. Changes to an item used in multiple products can resolve an
immediate issue while causing a problem in other applications. [PA159.IG102.SP101.SubP102.N102]
3. Review change requests that
will be addressed in the next baseline with those who will be affected by the
changes and get their agreement. [PA159.IG102.SP101.SubP103]
Conduct the change request review with appropriate participants. Record the
disposition of each change request and the rationale for the decision, including
success criteria, a brief action plan if appropriate, and needs met or unmet by
the change. Perform the actions required in the disposition, and report the
results to relevant stakeholders. [PA159.IG102.SP101.SubP103.N101]
4. Track the status of change
requests to closure. [PA159.IG102.SP101.SubP104]
Change requests brought into the system need to be handled in a proficient and
timely manner. Once a change request has been processed, it is critical to close
the request with the appropriate approved action as soon as it is practical.
Actions left open result in larger than necessary status lists, which in turn
result in added costs and confusion. [PA159.IG102.SP101.SubP104.N101]
SP 2.2-1 Control Configuration Items
Control changes to the configuration items.
[PA159.IG102.SP102]
Control is
maintained over the configuration of the work product baseline. This control
includes tracking the configuration of each of the configuration items,
approving a new configuration if necessary, and updating the baseline. [PA159.IG102.SP102.N101]
Typical Work Products
1. Revision
history of configuration items [PA159.IG102.SP102.W101]
2. Archives of
the baselines [PA159.IG102.SP102.W102]
Subpractices
1. Control changes to
configuration items throughout the life of the product.
[PA159.IG102.SP102.SubP101]
2. Obtain appropriate
authorization before changed configuration items are entered into the
configuration management system. [PA159.IG102.SP102.SubP102]
For example, authorization may come from the CCB, the project manager, or the
customer. [PA159.IG102.SP102.SubP102.N101]
3. Check in and check out
configuration items from the configuration management system for incorporation
of changes in a manner that maintains the correctness and integrity of the
configuration items. [PA159.IG102.SP102.SubP103]
Examples of check-in and check-out steps include the following:
[PA159.IG102.SP102.SubP103.N101]
· Confirming that the revisions are authorized
· Updating the configuration items
· Archiving the replaced baseline and retrieving the new baseline
4. Perform reviews to ensure that
changes have not caused unintended effects on the baselines (e.g., ensure that
the changes have not compromised the safety and/or security of the system). [PA159.IG102.SP102.SubP104]
5. Record changes to
configuration items and the reasons for the changes as appropriate.
[PA159.IG102.SP102.SubP105]
If a
proposed change to the work product is accepted, a schedule is identified for
incorporating the change into the work product and other affected areas. [PA159.IG102.SP102.SubP105.N101]
Configuration control mechanisms can be tailored to categories of changes. For
example, the approval considerations could be less stringent for component
changes that do not affect other components. [PA159.IG102.SP102.SubP105.N102]
Changed configuration items are released after review and approval of
configuration changes. Changes are not official until they are released. [PA159.IG102.SP102.SubP105.N103]
SG 3 Establish Integrity
Integrity of baselines is established and maintained. [PA159.IG103]
The
integrity of the baselines, established by processes associated with the
Establish Baselines specific goal, and maintained by processes associated with
the Track and Control Changes specific goal, is provided by the specific
practices under this specific goal. [PA159.IG103.N101]
SP 3.1-1 Establish Configuration Management Records
Establish and maintain records describing configuration items. [PA159.IG103.SP101]
Typical Work Products
1. Revision
history of configuration items [PA159.IG103.SP101.W101]
2. Change log [PA159.IG103.SP101.W102]
3. Copy of the
change requests [PA159.IG103.SP101.W103]
4. Status of
configuration items [PA159.IG103.SP101.W104]
5. Differences
between baselines [PA159.IG103.SP101.W105]
Subpractices
1. Record configuration
management actions in sufficient detail so the content and status of each
configuration item is known and previous versions can be recovered.
[PA159.IG103.SP101.SubP101]
2. Ensure that relevant
stakeholders have access to and knowledge of the configuration status of the
configuration items. [PA159.IG103.SP101.SubP102]
Examples of activities for communicating configuration status include the
following: [PA159.IG103.SP101.SubP102.N101]
· Providing access permissions to authorized end users
· Making baseline copies readily available to authorized end users
3. Specify the latest version of
the baselines. [PA159.IG103.SP101.SubP103]
4. Identify the version of
configuration items that constitute a particular baseline.
[PA159.IG103.SP101.SubP104]
5. Describe the differences
between successive baselines. [PA159.IG103.SP101.SubP105]
6. Revise the status and history
(i.e., changes and other actions) of each configuration item as necessary. [PA159.IG103.SP101.SubP106]
SP 3.2-1 Perform Configuration Audits
Perform configuration audits to maintain integrity of the configuration
baselines. [PA159.IG103.SP102]
Audit
configuration management activities and processes to confirm that the resulting
baselines and documentation are accurate, and record the audit results as
appropriate. [PA159.IG103.SP102.N101]
Typical Work Products
1. Configuration
audit results [PA159.IG103.SP102.W101]
2. Action items [PA159.IG103.SP102.W102]
Subpractices
1. Assess the integrity of the
baselines. [PA159.IG103.SP102.SubP101]
2. Confirm that the configuration
records correctly identify the configuration of the configuration items. [PA159.IG103.SP102.SubP102]
3. Review the structure and
integrity of the items in the configuration management system.
[PA159.IG103.SP102.SubP103]
4. Confirm the completeness and
correctness of the items in the configuration management system.
[PA159.IG103.SP102.SubP104]
Completeness and correctness of the content is based on the requirements as
stated in the plan and the disposition of approved change requests.
[PA159.IG103.SP102.SubP104.N101]
5. Confirm compliance with
applicable configuration management standards and procedures.
[PA159.IG103.SP102.SubP105]
6. Track action items from the
audit to closure. [PA159.IG103.SP102.SubP106]
Generic Practices by Goal
(Note: The detailed description of the GPs is available in a separate web page. Using the hyperlink provided here will open that web page in a separate window. However, the GP elaborations pertinent to the process area of this web page are available below.)
GG 1 Achieve Specific Goals
The process supports and enables achievement of the specific goals of the process area by transforming identifiable input work products to produce identifiable output work products.
Perform the base practices of the configuration management process to develop
work products and provide services to achieve the specific goals of the process
area. [GP102]
GG 2 Institutionalize a Managed Process
The process is institutionalized as a managed process.
GP 2.1 Establish an Organizational Policy
Establish and maintain an organizational policy for planning and performing the
configuration management process. [GP103]
Elaboration:
This
policy establishes organizational expectations for establishing and maintaining
baselines, tracking and controlling changes to the work products (under
configuration management), and establishing and maintaining integrity of the
baselines. [PA159.EL101]
Establish and maintain the plan for performing the configuration management
process. [GP104]
Elaboration:
This plan
for performing the configuration management process can be included in (or
referenced by) the project plan, which is described in the Project Planning
process area. [PA159.EL112]
Provide adequate resources for performing the configuration management process,
developing the work products, and providing the services of the process. [GP105]
Elaboration:
Examples of resources provided include the following tools:
[PA159.EL104]
· Configuration management tools
· Data management tools
· Archiving and reproduction tools
· Database programs
Assign responsibility and authority for performing the process, developing the
work products, and providing the services of the configuration management
process. [GP106]
Train the people performing or supporting the configuration management process
as needed. [GP107]
Elaboration:
Examples of training topics include the following:
[PA159.EL105]
· Roles, responsibilities, and authority of the configuration management staff
· Configuration management standards, procedures, and methods
· Configuration library system
Place designated work products of the configuration management process under
appropriate levels of configuration management.
[GP109]
Elaboration:
Examples of work products placed under configuration management include the
following: [PA159.EL106]
· Access lists
· Change status reports
· Change request database
· CCB meeting minutes
· Archived baselines
GP 2.7 Identify and Involve Relevant Stakeholders
Identify and involve the relevant stakeholders of the configuration management
process as planned. [GP124]
Elaboration:
Examples of activities for stakeholder involvement include the following: [PA159.EL111]
· Establishing baselines
· Reviewing configuration management system reports and resolving issues
· Assessing the impact of changes for the configuration items
· Performing configuration audits
· Reviewing the results of configuration management audits
GP 2.8 Monitor and Control the Process
Monitor and control the configuration management process against the plan for
performing the process and take appropriate corrective action. [GP110]
Elaboration:
Examples of measures used in monitoring and controlling include the following: [PA159.EL108]
· Number of changes to configuration items
· Number of configuration audits conducted
GP 2.9 Objectively Evaluate Adherence
Objectively evaluate adherence of the configuration management process against
its process description, standards, and procedures, and address noncompliance. [GP113]
Elaboration:
Examples of activities reviewed include the following:
[PA159.EL109]
· Establishing baselines
· Tracking and controlling changes
· Establishing and maintaining integrity of baselines
Examples of work products reviewed include the following:
[PA159.EL110]
· Archives of the baselines
· Change request database
GP 2.10 Review Status with Higher Level Management
Review the activities, status, and results of the configuration management
process with higher level management and resolve issues.
[GP112]
GG 3 Institutionalize a Defined Process
The process is institutionalized as a defined process.
GP 3.1 Establish a Defined Process
Establish and maintain the description of a defined configuration management
process. [GP114]
GP 3.2 Collect Improvement Information
Collect work products, measures, measurement results, and improvement
information derived from planning and performing the configuration management
process to support the future use and improvement of the organization’s
processes and process assets. [GP117]
GG 4 Institutionalize a Quantitatively Managed Process
The process is institutionalized as a quantitatively managed process.
GP 4.1 Establish Quantitative Objectives for the Process
Establish and maintain quantitative objectives for the configuration management
process that address quality and process performance based on customer needs and
business objectives. [GP118]
GP 4.2 Stabilize Subprocess Performance
Stabilize the performance of one or more subprocesses to determine the ability
of the configuration management process to achieve the established quantitative
quality and process-performance objectives.
[GP119]
GG 5 Institutionalize an Optimizing Process
The process is institutionalized as an optimizing process.
GP 5.1 Ensure Continuous Process Improvement
Ensure continuous improvement of the configuration management process in
fulfilling the relevant business objectives of the organization.
[GP125]
GP 5.2 Correct Root Causes of Problems
Identify and correct the root causes of defects and other problems in the
configuration management process. [GP121]