| Allocated
baseline |
the
baseline that allocates functional requirements to specified
hardware and software items
|
| Allocation |
the
process of assigning functional requirements to hardware and
software items |
| Archive |
the
file, which contains the evolutionary history of a configuration
item |
| Baseline |
an
authorized software work product that can only be changed through
formal change control procedures |
| Blanket
builds |
the
process of rebuilding an entire software product |
| Branch |
a
variant development path that diverges from the primary development
path |
| Build
management |
the
process through which software work products are transformed into an
executable or usable format |
| Change
Advisory Board (CAB) |
ITIL
terminology, the same as the Change Control Board. |
| Change
Advisory Board/Executive Level (CAB/EC) |
Same
function as CAB, but used when urgent changes need to be evaluated. |
| Change
Control Board |
the
committee whose function is to govern the process of controlling
changes to a baseline |
| Change
history |
the
record of the modifications performed to a configuration item |
| Change
identification |
a
tool designed to assist in the tracking and controlling of changes
applied to configuration items.
It provides a label to correlate the activities required to
develop and maintain a configuration item |
| Change
initiation |
the
process of requesting changes to a configuration item |
| Change
management |
the
process of ensuring that only approved changes are incorporated into
a software work product. Role would includes risk minimization and
ensuring implementation is cost effective. |
| Change
request |
a
request to modify an existing software work product |
| Change
tracking |
the
process of monitoring the evolution of a change request as it
progresses through the various states |
| Configuration |
a
collection of items and their relative arrangements |
| Configuration
audit |
the
process of verifying that the configuration matches the baselines as
documented |
| Configuration
control |
the
process of evaluating, coordinating, disposing, and implementing a
change configuration item |
| Configuration
control process |
the
process of systematically evaluating, coordinating/tracking,
approving or disapproving, and implementing changes to the baseline
configuration identification |
| Configuration
identification |
the
process of uniquely identifying a selected software component |
| Configuration
item |
a
software component that has been selected for control under the
configuration management system |
| Configuration
Management |
the
collective duties associated with managing the hardware and software
configuration. Key disciplines include configuration identification,
control, relationship management, status accounting and audit. |
| Configuration
management plan |
the
document defining how configuration management will be implemented |
| Configuration
status accounting |
the
process of recording and reporting on the information required to
support the software configuration management process |
| Configurations |
composite
configuration items, the enumerated list of configuration items and
their relative arrangement |
| Definitive
Software Library (DSL) |
ITIL
Terminology. A repository to store authorised software applications.
A Tool of the Release Manager. |
| Definitive
Hardware Store (DHS) |
ITIL
Terminology. A repository to store authorised hardware components. A
Tool of the Release Manager. |
| Delta |
the
differences between versions of a configuration item |
| Design
change notice |
a
formal document prepared to provide notice of a design change |
| Developmental
baseline |
the
baseline defining the evolving developments of a configuration item |
| Engineering
change |
a
change to an approved configuration item at any point in the
life-cycle of the item |
| Engineering
change proposal |
the
formal documentation which describes and justifies an engineering
change |
| Entity
relationship |
a
diagramming technique depicting the relationships between
configuration items, or types of configuration items |
| Environment
management |
the
processes used to relate a software product to the domain in which
it exists |
| Error
management |
the
plan for error processing, an error is a deviation of a computed,
observed, or measured quantity from the true, specified or
theoretically correct value of the quantity |
| Evaluation |
the
process in determining if an item or activity meets its specified
criteria |
| Executable
environment |
the
domain in which the run-time components of a configuration exist |
| Footprinting |
a
process of inserting and tracking a string of characters into a
binary file that can later be interrogated |
| Functional
baseline |
the
approved documentation describing a system’s functional,
operational, and interface requirements and the verification
required to validate the specified requirements |
| Functional
configuration audit |
an
audit that verifies the performance of a configuration item against
specifications |
| Incremental
builds |
the
process of building only those configuration items affected by a
work package |
| ITIL |
IT
Infrastructure library. A framework of best practices for managing
IT operations. See ITIL article. |
| Labeling
scheme |
the
method for uniquely identifying each software configuration item |
| Library |
the
directory, path, or file that contains configuration items |
| Library
management |
the
process of managing the physical storage, retention, security and
backup of configuration items |
| Lock |
a
marker placed on the configuration status of an item, which prevents
the item from being modified |
| MAKE |
files
that contain rules for building a program, then a make program is
run using a makefile |
| Merge |
the
activity of ‘joining’ modifications performed simultaneously to
different copies of the same module |
| Migration |
the
process of ‘moving’ configuration items from one stage to
another in a hierarchical library structure |
| Parallel
development |
the
process of creating and maintaining multiple variants of a software
system concurrently |
| Permanent
variant |
a
variation of a configuration item that has been approved to exist
indefinitely |
| Physical
configuration audit |
an
audit that reviews the configuration items to verify their presence
and to validate that they were built to specifications |
| Process
integration |
the
activity of incorporating software configuration management
activities into the overall software process |
| Process
management |
the
rules and their implementation governing the software migration
process |
| Process
map |
a
diagram depicting a process, to include activities, inputs, and
outputs |
| Product
baseline |
the
approved release of a configuration item |
| Product
distribution |
the
process of software turnover to the environment from which the user
can perform the business functions |
| Product
management |
the
process used to define how to construct a configuration from set of
configuration items |
| Program
Temporary Fix |
a
correction, fix, or patch delivered in a temporary format usually to
solve a specific or emergency problem |
| Relationship
management |
the
process used to track the physical or implied relationships between
configuration items |
| Release |
the
action whereby an item is made officially available for its intended
use |
| Release
Management |
the
collective duties associated with releases e.g. planning, designing,
build, configuration and testing. |
| Release
and Level Strategy |
release
is increased for major changes, levels are increased with each
modification |
| Scheme |
a
combination of characters and numbers that ensure consistency across
projects, teams and applications |
| SCM
team |
the
functional team that is tasked with the support of the software
configuration management process |
| Software |
computer
instructions and data definitions required enabling the computer
hardware to perform functions |
| Software
configuration management |
a
discipline that supports and controls the changes to software work
products throughout its life-cycles |
| Software
development library |
the
collection of software, documentation, tools and procedures used to
develop and support software |
| Software
engineering environment |
the
tools, devices, and hardware necessary to perform the software
engineering efforts |
| Software
work product |
an
entity created during one of the phases of the software development
life-cycles |
| Temporary
variant |
a
variation of a configuration item that has been approved to exist
for a defined period of time |
| Tip |
the
revision of an item at the end of a branch |
| Traceability |
the
ability to link individual events and parts to each other, in time.
Traceability exists when a source can be examined to
determine actions that introduce pieces of code.
It provides linkage to help ensure that changes are made for
valid business reasons |
| Trunk |
the
primary development path of a configuration item |
| Variation |
an
alternative form of a configuration item |
| Version |
an
identified and documented software product |
| Version
Description Document |
a
document that identifies and describes a version of a configuration
item |
| Work
package |
a
unit of work that is to be performed |
