Configuration Management

CMMI-DEV v1.3

Introduction &
Expectations

Who we are?

Who you are ?

Name
Department & Job position
Course expectations

Configuration Management

7/5/2013

Course objectives
Understand Configuration Management.
Understand Configuration Management
functions and tools.
Understand CMMI Configuration
Management.

Configuration Management

7/5/2013

Contents
Introduction
Introduction
Definitions
Definitions
CM
CM activities
activities

Configuration Management

CM
CM concepts
concepts

CMMI
CMMI CM
CM process
process area
area

Configuration
Configuration planning
planning
Configuration
Configuration
identification
identification
Configuration
Configuration Control
Control
Status
Status Accounting
Accounting
Configuration
Configuration auditing
auditing
Release
Release Management
Management
CM
CM Tools
Tools

CMMI
CMMI support
support process
process
areas
areas
CM
CM process
process area
area

7/5/2013

Contents
Introduction
Introduction

CM
CM concepts
concepts

CMMI
CMMI CM
CM process
process area
area

Definitions
Definitions
CM
CM activities
activities

Configuration
Configuration planning
planning
Configuration
Configuration
identification
identification
Configuration
Configuration Control
Control
Status
Status Accounting
Accounting
Configuration
Configuration auditing
auditing
Release
Release Management
Management
CM
CM Tools
Tools

CMMI
CMMI support
support process
process
areas
areas
CM
CM process
process area
area

Configuration Management

7/5/2013

Do you allow customer to change

requirements?

How do you manage discrepancies?

How do you share project docs and code files?

Who builds the system?

How do you manage releases?

Configuration Management

7/5/2013

What is configuration ?
From Latin Configuratio
From Latin Configurare
From con- together + figurare to shape
(from figura shape or figure)

So configuration is a relative arrangement

of parts or elements

Configuration Management

7/5/2013

Definitions (ISO 24765)

System: combination of interacting elements

organized to achieve one or more stated
purposes.

The configuration of a system: the functional

and/or physical characteristics of hardware, or
software as set forth in technical documentation
and achieved in a product.

Configuration Management

7/5/2013

Definitions (ISO 24765)

Configuration management (CM), is A

discipline applying technical and administrative
direction and surveillance to: identify and
document the functional and physical
characteristics of a configuration item, control
changes to those characteristics, record and
report change processing and implementation
status, and verify compliance with specified
requirements.

Configuration Management

7/5/2013

The Four Functions of CM

1.

2.

3.

4.

Configuration identification. selecting the

configuration items for a system and recording their
functional and physical characteristics in technical
documentation.
Configuration control. the evaluation, coordination,
approval or disapproval, and implementation of changes
to configuration items after formal establishment of their
configuration identification..
Configuration status accounting. recording and
reporting of information needed to manage a
configuration effectively.
Configuration auditing. Verifying the integrity of a
system in terms of the degree to which it complies with its
specification.

Configuration Management

7/5/2013

10

CM activities

Configuration Management

7/5/2013

11

Contents
Introduction
Introduction

CM
CM concepts
concepts

CMMI
CMMI CM
CM process
process area
area

Definitions
Definitions
CM
CM activities
activities

Configuration
Configuration planning
planning
Configuration
Configuration
identification
identification
Configuration
Configuration Control
Control
Status
Status Accounting
Accounting
Configuration
Configuration auditing
auditing
Release
Release Management
Management
CM
CM Tools
Tools

CMMI
CMMI support
support process
process
areas
areas
CM
CM process
process area
area

Configuration Management

7/5/2013

12

CM concepts
Configuration
planning

CM context
Configuration Planning
SCMP

Configuration identification
Configuration Control
Status Accounting
Configuration auditing
Release Management
CM Tools
Configuration Management

7/5/2013

13

Project

Organization

CM context
Process Improvement
Training
, Procurement, HR, Finance
Project Planning / Monitoring & Control
Quality Assurance
Specification

Design

Construction

Validation

Deployment

Configuration Management
Configuration Management

7/5/2013

14

Configuration Planning

Organization and Responsibilities

Resources and Schedules

Tool Selection and Implementation

Configuration Management

7/5/2013

15

SCMP
IEEE Std 828.
a) A document with the title Software
Configuration Management Plan shall exist
either in standalone form or embedded in
another project document.
b) This document shall contain all SCM planning
information either by inclusion or by reference
to other locations, such as other documents or
automated systems.
c) A format for this document shall be defined.

Configuration Management

7/5/2013

16

SCMP contents
Class of
information

Description

Introduction

Describes the Plans purpose, scope of application, key

terms, and references
SCM management (Who?) Identifies the responsibilities and authorities for
accomplishing the planned activities
SCM activities
(What?) Identifies all activities to be performed in
applying to the project
SCM schedules
(When?) Identifies the required coordination of SCM
activities with the other activities in the project
SCM resources
(How?) Identifies tools and physical and human resources
required for execution of the Plan
SCM plan
maintenance
Identifies how the Plan will be kept current while in effect

Configuration Management

7/5/2013

17

CM concepts
CM management

Configuration
identification

Configuration
Configuration Item
Item (CI)
(CI)
CM
CM repository
repository
Baselines
Baselines
Versions
Versions Management
Management

Configuration Control
Status Accounting
Configuration auditing
Release Management
Configuration Tools
Configuration Management

7/5/2013

18

Configuration Item (CI)

Aggregation of work products that is designated

for configuration management and treated as a
single entity in the configuration management
process (ISO 24765).
It is anything associated with a software project
(design, code, test data, document, etc.) that has
been placed under configuration control.
There are often different versions of a CI.
CI has a unique name.
CIs can be placed under different levels of
control.

Configuration Management

7/5/2013

19

Configuration example

Configuration Management

7/5/2013

20

CIs levels of control

CIs could be placed under multiple levels of

control (For example):

Fully Controlled CI: formal changes.

Managed CI: informal changes.

Configuration Management

7/5/2013

21

CIs relationships

Relationships between CIs should be

tracked.

Traceability matrix is the tool used for this

purpose.

Configuration Management

7/5/2013

22

CM repository

Configuration Management

7/5/2013

23

Standard SCM Directories (IEEE 1042)

Programmers Directory
(IEEE Std: Dynamic Library)
Completely under control of one
programmer

Master Directory
(IEEE Std: Controlled Library)
Central directory of all promotions

Promotion
Central source
code archive
Release

Software Repository
(IEEE Std: Static Library)
Externally released baselines.

Foo95

Foo98

Codelines and baselines

Codeline: a sequence of versions of source code with later

versions in the sequence derived from earlier versions.
Codelines normally apply to components of systems so that
there are different versions of each component.
A baseline: specification or product that has been formally
reviewed and agreed upon, that thereafter serves as the
basis for further development, and that can be changed only
through formal change control procedures.
The baseline therefore specifies the component versions that
are included in the system plus a specification of the libraries
used, configuration files, etc.

Configuration Management

7/5/2013

25

Codeline & Baseline

Configuration Management

7/5/2013

26

Baselines

Configuration Management

7/5/2013

27

Baselines

Functional baseline: the initial approved technical

documentation for a configuration item.
Allocated baseline: the initial approved specifications
governing the development of configuration items that are
part of a higher-level configuration item
Product baseline: the initial approved technical
documentation (including, for software, the source code
listing) defining a configuration item during the production,
operation, maintenance, and logistic support of its life
cycle. (at the end of development/beginning of production)

Configuration Management

7/5/2013

28

Typical Baseline Components

Baseline

When Established
Completion of
Functional software requirements
review
Completion of
Allocated preliminary design
review
Completion of design
Design
review
Acceptanc Completion of
e test
integration testing

Product

Completion of
acceptance testing

Operationa Completion of
l
deployment
Configuration Management

Components
Concept of Operations Document, Software
Requirements Specification
High level design documents, interface control
documents
Detailed design documents
Source and executable code units, integration test plans,
test procedures, test cases and data sets and test
reports
Source and executable code units, final system
specifications, user and maintenance manuals,
acceptance test plans, test procedures, test cases and
data sets and test reports
Source and executable code units, final system
specifications, user and maintenance manuals,
acceptance test plans, test procedures, site integration
test cases and data sets and test reports
7/5/2013

29

Version Management

Version management (VM) is the process of keeping track

of different versions of software components or
configuration items and the systems in which these
components are used.

It also involves ensuring that changes made by different

developers to these versions do not interfere with each
other.

Therefore version management can be thought of as the

process of managing codelines and baselines.

Configuration Management

7/5/2013

30

Version management
systems

Version and release identification

Storage management

Change history recording

Independent development (simultaneous check-out)

Project support with shared components.

Configuration Management

7/5/2013

31

Check-in & Check-out

Configuration Management

7/5/2013

32

Check-in Check-out
problem

Configuration Management

7/5/2013

33

Lock-Modify-Unlock Solution

Issues:
A user can lock a file and forget about it.
Time is wasted while others wait to edit the file.

Unnecessary serialization.
Different parts of a file dont necessarily overlap.

Configuration Management

7/5/2013

34

Copy-Modify-Merge Solution
Or conflict

Configuration Management

7/5/2013

35

Tools:
KDiff3

Codeline branch & merge

Configuration Management

7/5/2013

37

CM concepts
CM management
Configuration identification

Configuration
Control

Change Management
The change management process
Change Control Board (CCB)

Status Accounting
Configuration auditing
Release Management
CM Tools
Configuration Management

7/5/2013

38

Change Management

Change management is intended to ensure that

system evolution is a managed process and that
priority is given to the most urgent and costeffective changes.

The change management process is concerned

with analyzing the costs and benefits of proposed
changes, approving those changes that are
worthwhile and tracking which components in the
system have been changed.

Configuration Management

7/5/2013

39

The change management process

Configuration Management

7/5/2013

41

Change Control Board

(CCB)

Evaluate and authorize formal changes.

Hierarchies of CCBs.

Evaluation process and rules.

Configuration Management

7/5/2013

42

CM concepts
CM management
Configuration identification
Configuration Control

Status
Accounting

Configuration
Configuration

status accounting
Status Report contents

Configuration auditing
Release Management
CM Tools
Configuration Management

7/5/2013

43

Configuration status accounting

Recording and reporting of information

needed to manage a configuration
effectively.

Configuration Management

7/5/2013

44

Configuration Status Report

contents

A list of the CIs that comprise a baseline

The date when each version of each CI was baselined
A list of the specifications that describe each CI
The history of baseline changes including rationales
for change
A list of open change requests by CI
Deficiencies identified by configuration audits
The status of works associated with approved change
requests by CI.

Configuration Management

7/5/2013

45

CM concepts
CM management
Configuration identification
Configuration Control
Status Accounting

Configuration
auditing

Functional Configuration Audit (FCA)

Physical Configuration Audit (PCA)

Release Management
CM Tools
Configuration Management

7/5/2013

46

Configuration auditing

Configuration auditing verifies that the product is

built according to the requirements, standards, or
contractual agreement.

It verifies that all product components have been

produced, correctly identified, and described, and
that all change requests have been resolved.

Configuration Management

7/5/2013

47

FCA

According to the IEEE-610, a FCA is an audit

conducted to verify that:
The development of a configuration item has
been completed satisfactorily
The item has achieved the performance and
functional characteristics specified in the
functional or allocated configuration identification
Its operational and support documents are
complete and satisfactory

Configuration Management

7/5/2013

48

FCA check list example

Readiness Criteria

Compliance
Yes
No

Does the code implement all and only the documented

software/system requirements?
Can each system/software requirement be traced forward into tests
(test cases, procedures, scripts) that verify that requirement?
Is comprehensive system/software testing complete, including
functional testing, interface testing and the testing of required
quality attributes (performance, usability, safety, security, etc.)?
Is the deliverable documentation consistent with the requirements
and asbuilt system/software?
Are the findings from peer reviews incorporated into the software
deliverables (system/software and/or documentation)?
Have approved corrective actions been implemented for all findings
from In-Process Software Configuration Management Product Audits?
Are all the anomalies reported during testing adequately resolved (or
the appropriate waivers/deviations were obtained and known defects
with workarounds are documented in the release notes)?
Configuration Management

7/5/2013

49

PCA

According to the IEEE, a PCA is an audit

conducted to verify that each configuration item,
as built, conforms to the technical documentation
that defines it. A PCA verifies that:
All items identified as being part of the configuration are
present in the product baseline
The correct version and revision of each part are included
in the product baseline
They correspond to information contained in the
baselines configuration status report

Configuration Management

7/5/2013

50

PCA check list example

Readiness Criteria

Compliance
Yes
No

Has each noncompliance from the FCA been appropriately

resolved?
Have all of the identified Configuration Items (e.g., source code,
documentation, etc.) been baselined?
Do all of the Configuration Items meet workmanship (coding, doc)
standards?
Has the software been built from the correct components and in
accordance with the specification?

Is the deliverable documentation set complete?

Does the actual system delivery media conform to specification?
Has the delivery media been appropriately marked/labeled?

Do the deliverables for shipment match the list of required

deliverables?

Have 3rd party licensing requirements been met?

Have export compliance requirements been met?

Configuration Management

7/5/2013

51

When to perform FCA,

PCA?

On every milestone.

Before baseline.

PCA when needed.

PCA after baseline.

Configuration Management

7/5/2013

52

CM concepts
CM management
Configuration identification
Configuration Control
Status Accounting
Configuration auditing

Release
Management

Platforms
System building
Release management

CM Tools
Configuration Management

7/5/2013

53

Platforms: Dev, Build,

Target

Configuration Management

7/5/2013

54

System building

Configuration Management

7/5/2013

55

Release management

A system release is a version of a software system that

is distributed to customers.
For mass market software, it is usually possible to
identify two types of release: major releases which
deliver significant new functionality, and minor
releases, which repair bugs and fix customer problems
that have been reported.
For custom software or software product lines, releases
of the system may have to be produced for each
customer and individual customers may be running
several different releases of the system at the same
time.

Configuration Management

7/5/2013

56

Release tracking

In the event of a problem, it may be necessary to

reproduce exactly the software that has been delivered to a
particular customer.
When a system release is produced, it must be documented
to ensure that it can be re-created exactly in the future.
This is particularly important for customized, long-lifetime
embedded systems, such as those that control complex
machines.
Customers may use a single release of these systems for many
years and may require specific changes to a particular software
system long after its original release date.

Configuration Management

7/5/2013

57

Release reproduction

To document a release, you have to record the specific

versions of the source code components that were used to
create the executable code.

You must keep copies of the source code files,

corresponding executables and all data and configuration
files.

You should also record the versions of the operating

system, libraries, compilers and other tools used to build
the software.

Configuration Management

7/5/2013

58

Release planning

As well as the technical work involved in creating a release

distribution, advertising and publicity material have to be
prepared and marketing strategies put in place to convince
customers to buy the new release of the system.

Release timing
If releases are too frequent or require hardware upgrades,
customers may not move to the new release, especially if
they have to pay for it.
If system releases are too infrequent, market share may
be lost as customers move to alternative systems.

Configuration Management

7/5/2013

59

Release components

As well as the the executable code of the system,

a release may also include:
configuration files defining how the release should be
configured for particular installations;
data files, such as files of error messages, that are
needed for successful system operation;
an installation program that is used to help install the
system on target hardware;
electronic and paper documentation describing the
system;
packaging and associated publicity that have been
designed for that release.

Configuration Management

7/5/2013

60

CM concepts
CM management
Configuration identification
Configuration Control
Status Accounting
Configuration auditing
Release Management

CM Tools

Configuration Management

CM Tools classification
TFS
7/5/2013

61

CM tools classification

Individual support tools

Version control tools.
Build handling tools.
Change control tools.

Project-related support tools

Company-wide-process support tools,
support more formal development process
and include certification requirements.

Configuration Management

7/5/2013

62

Microsoft Team Foundation Server

(TFS)
Version
manageme
nt

System
Building

Release
manageme
nt

Change
manageme
nt

Configuration Management

7/5/2013

63

Contents
Introduction
Introduction

CM
CM concepts
concepts

CMMI
CMMI CM
CM process
process area
area

Definitions
Definitions
CM
CM activities
activities

CM
CM management
management
Configuration
Configuration
identification
identification
Configuration
Configuration Control
Control
Status
Status Accounting
Accounting
Configuration
Configuration auditing
auditing
Release
Release Management
Management
CM
CM Tools
Tools

CMMI
CMMI support
support process
process
areas
areas
CM
CM process
process area
area

Configuration Management

7/5/2013

64

CMMI support process areas

Support Process Areas

Basic
Configuration Management
Process and Product Quality Assurance
Measurement and Analysis

Advanced
Decision Analysis and Resolution
Causal Analysis and Resolution

Configuration Management

7/5/2013

66

Basic Support Process Areas

Measurements,
analyses
MA

Information
needs

All process
areas

Configuration
items;
change
requests

Quality and
noncompliance
issues
Processes and
work products;
standards and
procedures

Baselines;
audit reports

CM

Configuration Management

67

7/5/2013

PPQA

CMMI CM process
area

Purpose
Establish and maintain the integrity of work
products using configuration
identification, configuration control,
configuration status accounting, and
configuration audits.
Support.
Level 2.

Configuration Management

7/5/2013

69

CM Specific Goals and

Practices

SG 1 Establish Baselines

SP 1.1 Identify Configuration Items

SP 1.2 Establish a Configuration Management System
SP 1.3 Create or Release Baselines

SG 2 Track and Control Changes

SP 2.1 Track Change Requests
SP 2.2 Control Configuration Items

SG 3 Establish Integrity
SP 3.1 Establish Configuration Management Records
SP 3.2 Perform Configuration Audits

Configuration Management

7/5/2013

70

SG 1 Establish Baselines
Baselines of identified work products
are established.
SP 1.1 Identify Configuration Items
SP 1.2 Establish a Configuration Management System
SP 1.3 Create or Release Baselines

Configuration Management

7/5/2013

71

SP 1.1 Identify Configuration Items

Identify configuration items, components, and related
work products to be placed under configuration
management.
configuration item: An aggregation of work products that is
designated for configuration management and treated as a single
entity in the configuration management process.
work product: A useful result of a process.
This result can include files, documents, products, parts of a
product, services, process descriptions, specifications, and
invoices. A key distinction between a work product and a product
component is that a work product is not necessarily part of the
end product.
The selection of CI should be based on criteria established during
planning.
Configuration Management
7/5/2013

72

SP 1.1 Identify Configuration Items

Subpractices:
1.
Select CIs based on criteria.
2.
Assign unique ID to CIs.
3.
Specify the important characteristics of each CI.
4.
Specify when each CI is placed under CM.
5.
Identify the owner responsible for each CI.
6.
Specify relationships among CIs.

Configuration Management

7/5/2013

73

SP 1.2 Establish a Configuration Management

System

Establish and maintain a configuration

management and change management
system for controlling work products.

1.

2.

3.

Example Work Products

Configuration management system with controlled work
products
Configuration management system access control
procedures
Change request database

Configuration Management

7/5/2013

74

SP 1.2 Establish a Configuration Management

System

1.

2.

3.

4.

Subpractices:
Establish a mechanism to manage multiple levels of
control.
Provide access control to ensure authorized access to the
configuration management system.
Store and retrieve configuration items in a configuration
management system.
Share and transfer configuration items between control
levels in the configuration management system.

Configuration Management

7/5/2013

75

SP 1.2 Establish a Configuration Management

System
5.

6.

7.

8.

9.

Store and recover archived versions of configuration

items.
Store, update, and retrieve configuration management
records.
Create configuration management reports from the
configuration management system.
Preserve the contents of the configuration management
system.
Revise the configuration management structure as
necessary.

Configuration Management

7/5/2013

76

SP 1.3 Create or Release Baselines

Create or release baselines for internal use

and for delivery to the customer.

Baseline: A set of specifications or work

products that has been formally reviewed and
agreed on, which thereafter serves as the basis
for further development, and which can be
changed only through change control procedures.

Configuration Management

7/5/2013

77

SP 1.3 Create or Release Baselines

1.

2.

3.

4.

Subpractices:
Obtain authorization from the CCB before creating or
releasing baselines of configuration items.
Create or release baselines only from configuration items
in the configuration management system.
Document the set of configuration items that are
contained in a baseline.
Make the current set of baselines readily available.

Configuration Management

7/5/2013

78

SG 2 Track and Control Changes

Changes to the work products under
configuration management are tracked
and controlled.
SP 2.1 Track Change Requests
SP 2.2 Control Configuration Items

Configuration Management

7/5/2013

79

SP 2.1 Track Change Requests

Track change requests for configuration
items.

1.

2.

3.
4.

5.

Subpractices:
Initiate and record change requests in the change request
database.
Analyze the impact of changes and fixes proposed in change
requests.
Categorize and prioritize change requests.
Review change requests to be addressed in the next baseline
with relevant stakeholders and get their agreement.
Track the status of change requests to closure.

Configuration Management

7/5/2013

80

SP 2.2 Control Configuration Items

Control changes to configuration items.
Subpractices:
1. Control changes to configuration items throughout the life of the
product or service.
2. Obtain appropriate authorization before changed configuration items
are entered into the configuration management system.
3. Check in and check out configuration items in the configuration
management system for incorporation of changes in a manner that
maintains the correctness and integrity of configuration items.
4. Perform reviews to ensure that changes have not caused unintended
effects on the baselines.
5. Record changes to configuration items and reasons for changes as
appropriate.

Configuration Management

7/5/2013

81

SG 3 Establish Integrity
Integrity of baselines is established and
maintained.
SP 3.1 Establish Configuration Management Records
SP 3.2 Perform Configuration Audits

Configuration Management

7/5/2013

82

SP 3.1 Establish Configuration Management

Records

Establish and maintain records describing

configuration items.

1.
2.
3.
4.
5.

Example Work Products

Revision history of configuration items
Change log
Change request records
Status of configuration items
Differences between baselines

Configuration Management

7/5/2013

83

SP 3.1 Establish Configuration Management

Records

1.

2.

3.
4.

5.
6.

Subpractices:
Record configuration management actions in sufficient detail so
the content and status of each configuration item is known and
previous versions can be recovered.
Ensure that relevant stakeholders have access to and knowledge
of the configuration status of configuration items.
Specify the latest version of baselines.
Identify the version of configuration items that constitute a
particular baseline.
Describe differences between successive baselines.
Revise the status and history (i.e., changes, other actions) of
each configuration item as necessary.

Configuration Management

7/5/2013

84

SP 3.2 Perform Configuration Audits

Perform configuration audits to
maintain the integrity of configuration
baselines.
configuration audit: An audit conducted to verify that a
configuration item or a collection of configuration items that make
up a baseline conforms to a specified standard or requirement.

Configuration Management

7/5/2013

85

Examples of audit types include the following

Functional configuration audits (FCAs): Audits conducted to verify

that the development of a configuration item has been completed
satisfactorily, that the item has achieved the functional and
quality attribute characteristics specified in the functional or
allocated baseline, and that its operational and support
documents are complete and satisfactory.
Physical configuration audits (PCAs): Audits conducted to verify
that a configuration item, as built, conforms to the technical
documentation that defines and describes it.
Configuration management audits: Audits conducted to confirm
that configuration management records and configuration items
are complete, consistent, and accurate.

Configuration Management

7/5/2013

86

SP 3.2 Perform Configuration Audits

Example Work Products
1.
Configuration audit results
2.
Action items
Subpractices:
3.
Assess the integrity of baselines.
4.
Confirm that configuration management records correctly identify
configuration items.
5.
Review the structure and integrity of items in the configuration
management system.
6.
Confirm the completeness, correctness, and consistency of items in the
configuration management system.
7.
Confirm compliance with applicable configuration management standards
and procedures.
8.
Track action items from the audit to closure.

Configuration Management

7/5/2013

87

Establish Integrity
Establish Baselines

Identify
Configuration
Items

Establish
.a Config
Management
System
Create or
Release
Baselines

Configuration Management

Configuration
Management
System
Change
Request
Database
Change
Requests
Track
and
Control
Changes

Track
Change
Requests

Establish
Config Mgmt
Records

Perform
Configuration
Audits

Reports

Audit
Results
Action
Items

Control
Configuration
Items

7/5/2013

88

CM procedures example

Configuration Management

Planning
Establishing CM Environment
Maintaining CM Environment
Functional Configuration Audit
Physical Configuration Audit
Baselining
Change Control
7/5/2013

89

CM Planning

Purpose: develop the required guidance for

the deployment of the configuration
management procedures.

This procedure involves the identification of

the project configuration controller,
developing the CM plan and ensuring its
integration with the overall project plan.

Configuration Management

7/5/2013

90

CM Planning Procedure

Input
Approved
Approved
Candidate
Candidate
Requirements
Requirements
Partial
Partial PMP
PMP

Configuration Management

CM
Planning

Output
Approved
Approved
Configuration
Configuration
Management
Management Plan
Plan
Approved
Approved CIs
CIs List
List

7/5/2013

91

Establishing CM
Environment

Purpose: establish the configuration

management system, including the storage
media, system, and the tools for accessing
the configuration system.

The procedure will produce the required

infrastructure for the overall development
project.

Configuration Management

7/5/2013

92

Establishing CM Environment Procedure

Input
Partial
Partial PMP
PMP

Configuration Management

Establishing
CM
Environment

Output
Approved CM
Environment

7/5/2013

93

Maintaining CM
Environment

Purpose: maintain the configuration

management system, including the storage
media, system, and the tools for accessing
the configuration system.

The procedure will produce the required

infrastructure for the overall development
project.

Configuration Management

7/5/2013

94

Maintaining CM Environment Procedure

Output
Input
Approved
Approved CM
CM
Environment
Environment
Approved
Approved CIs
CIs List
List

Configuration Management

Maintaining
CM
Environment

Approved
Approved CM
CM
Reports
Reports
Approved
Approved Tested
Tested
Backups
Backups
Closed
Closed CM
CM
Environment
Environment

7/5/2013

95

Functional Configuration
Audit

Purpose: guide the performance of the functional audit

activities on the configuration management system
including the storage media, system, and the tools for
accessing the configuration system.
The procedure, when performed, ensures the logical
consistency between the contents of the configuration
management system and approves the readiness for
performing the baselining.
This audit is not related to the quality assurance audit, the
quality assurance audit is just seeking the compliance with
predefined standards, while this audit is seeking the
integrity and compliance to the requirements specification.

Configuration Management

7/5/2013

96

FCA Procedure
Input
Approved
Approved Configuration
Configuration Management
Management Plan
Plan
Approved
CM
Environment
Approved CM Environment
Current
Current version
version of
of the
the CI
CI list
list
Current
version
of
the
RTM
Current version of the RTM
Approved Updated
Updated Work
Work Products
Products
Approved
Approved
Component
test
Approved Component test Defect
Defect Summary
Summary Report
Report
Approved
Integration
Test
Defect
Summary
Report
Approved Integration Test Defect Summary Report
Approved
Approved System
System Test
Test Defect
Defect Summary
Summary Report
Report
Approved Closed
Closed NCs
NCs
Approved
Approved
Approved Escalation
Escalation Reports
Reports
Approved
Closed
CRs
Approved Closed CRs
Approved
Approved Required
Required System
System Documentation
Documentation

Configuration Management

FC
A

Output
Approved
Approved
Closed
Closed NCs
NCs

7/5/2013

97

Physical Configuration
Audit

Purpose: guide the physical audit activities on the

configuration management system including the storage
media, system, and the tools for accessing the
configuration system.
The procedure, when performed, ensures the physical
existence and consistency between the contents of the
configuration management system and approves the
readiness for performing the baselining.
This procedure is not only performed before the baselining,
as in the functional audit case, but also can be done in any
time to ensure the required level of integrity.

Configuration Management

7/5/2013

98

PCA Procedure
Input
Approved
Approved configuration
configuration management
management plan
plan
Approved
CM
environment
Approved CM environment
Current version
version of
Current
of the
the CI
CI List
List
Approved
Closed
CRs
Approved Closed CRs
Approved
Approved Baselines
Baselines
Approved
Approved Tested
Tested Backups
Backups

Configuration Management

PCA

Output
Approved
Approved
Closed
Closed NCs
NCs

7/5/2013

99

Baselining

Purpose: produce baselines from the identified

CIs.

The procedure, when performed, ensures the

existence and existences announcement of the
baselines that will be considered as a starting
point for further development phases in the
product development life cycle. The quality of the
baseline is completely dependent on the
functional and physical audits done before the
baselining.

Configuration Management

7/5/2013

100

Baselining Procedure

Input
Approved
Approved Closed
Closed
NCs
NCs
Approved
Approved Closed
Closed
NCs
NCs

Configuration Management

Baselinin
g

Output
Approved
Approved Baseline
Baseline
CM
CM Status
Status
Accounting
Accounting Report
Report

7/5/2013

101

Change Control

Purpose: guide the performing of save

changes to any stable work product.

The change control procedure starts by

raising a change request, then being
evaluated, implemented and verified. The
impact of these changes should be
estimated and then evaluated at the end of
the project at the project closure phase.

Configuration Management

7/5/2013

102

Change Control Procedure

Input
None
None

Configuration Management

Change
Control

Output
Approved
Approved Closed
Closed
Change
Change
Change
Change Log
Log

7/5/2013

103

References

CMMI Product Team. (November 2010). CMMI for

Development, Version 1.3. Carnegie Mellon University.
Sommerville, I. (2011). SOFTWARE ENGINEERING, Ninth
Edition. Addison-Wesley.
ISO 24765. (2010). Systems and software engineering
Vocabulary.
IEEE 828. (1990). IEEE Standard for Software Configuration
Management Plans.
IEEE 1042. (1987). Guide to Software Configuration
Management.
SECC. (2009). SPIG Product Suite Handbook V1.2.

Configuration Management

7/5/2013

104

Thank you
Configuration Management

7/5/2013

105