Professional Documents
Culture Documents
Dibyesh Giri
Nepal
Configuration Management
Configuration Management is the process which controls
the changes made to a system and manages the
different versions of the evolving software product.
Configuration management involves the development and
application of procedures and standards for managing an
evolving system and releasing them to customers.
Procedures should be developed for building systems and
releasing them to customers.
Standards should be developed for recording and
processing proposed system changes and identifying and
storing different versions of the system.
CM may be part of a more general software quality
management process.
In some organizations, the same manager may share
quality management and configuration management
responsibilities.
Configuration Management
• Software may be released by the developers to a
quality assurance team who are responsible for
checking that the system is of acceptable quality.
• It is then passed to the configuration management
team who become responsible for controlling changes
to the software.
• Controlled systems are sometimes called baselines as
they are a starting point for controlled evolution.
• Reasons why systems exist in different configurations.
1. For different computers.
2. For different operating systems.
3. Incorporating client-specific functions, etc.
Configuration Management
• Configuration managers are responsible for keeping
track of the differences between software versions and
for ensuring that new versions are derived in a controlled
way.
• Configuration managers are responsible for ensuring
that these new versions are released to the correct
customers at appropriate time.
• The configuration management process and associated
documentation should be based on a set of standards.
Within an organization, these standards should be
published in a configuration management handbook or
as part of a quality handbook. e.g. IEEE standard 828-
1983, which is a standard for configuration management
plans.
Configuration Management
Mainframe
PC
Version
Version
VMS
DEC-Digital Electronic Configuration Version
Version Identification
Identifying versions of a system appears to be
straightforward.
Linear Scheme – 1.0 subsequent 1.1,1.2,1.3,…
At some stage it is decided to create release 2.0
and process starts again 2.1,2.2,2.3,…
Version Management tools such as SCCS
(Rochkind, 1975) support this approach to
version identification.
Configuration Management – Version and
Release Management
Version Management
Linear Scheme is simple but it has associated problems:
• When should a new release (i.e. a new branch in the derivation
graph) rather than a new version be created?
V1.1b V1.1.1
V1.1a