Sommerville-Software-Engineering-10ed

734 Chapter 25 ■ Configuration management
Term
Baseline
Branching
Codeline
Configuration (version) control
Configuration item or software
configuration item (SCI)
Mainline
Merging
Release
Repository
System building
Version
Workspace
Explanation
A collection of component versions that make up a system. Baselines
are controlled, which means that the component versions used in the
baseline cannot be changed. It is always possible to re-create a baseline
from its constituent components.
The creation of a new codeline from a version in an existing codeline.
The new codeline and the existing codeline may then develop
independently.
A set of versions of a software component and other configuration items
on which that component depends.
The process of ensuring that versions of systems and components are
recorded and maintained so that changes are managed and all versions
of components are identified and stored for the lifetime of the system.
Anything associated with a software project (design, code, test data,
document, etc.) that has been placed under configuration control.
Configuration items always have a unique identifier.
A sequence of baselines representing different versions of a system.
The creation of a new version of a software component by merging
separate versions in different codelines. These codelines may have been
created by a previous branch of one of the codelines involved.
A version of a system that has been released to customers (or other
users in an organization) for use.
A shared database of versions of software components and metainformation
about changes to these components.
The creation of an executable system version by compiling and linking
the appropriate versions of the components and libraries making up the
system.
An instance of a configuration item that differs, in some way, from other
instances of that item. Versions should always have a unique identifier.
A private work area where software can be modified without affecting
other developers who may be using or modifying that software.
Figure 25.3 CM
terminology
The definition and use of configuration management standards are essential for
quality certification in both ISO 9000 and the SEI’s capability maturity model (Bamford
and Deibler 2003; Chrissis, Konrad, and Shrum 2011). CM standards in a company
may be based on generic standards such as IEEE 828-2012, an IEEE standard for
configuration management. These standards focus on CM processes and the documents
produced during the CM process (IEEE 2012). Using the external standards as a
starting point, companies may then develop more detailed, company-specific standards
that are tailored to their specific needs. However, agile methods rarely use these standards
because of the documentation overhead involved.