|
Build |
The final stage
in producing a usable configuration. The process involves
taking one of more input Configuration Items and processing
them (building them) to create one or more output
Configuration Items e.g. software compile and
load.
|
|
Category |
Classification
of a group of Configuration Items, Change documents or
Problems.
|
|
Configuration
baseline |
Configuration of
a product or system established at a specific point in time,
which captures both the structure and details of that product
or system, and enables that product or system to be rebuilt at
a later date.
|
|
Configuration
control |
Activities
comprising the control of Changes to Configuration Items after
formally establishing its configuration documents. It includes
the evaluation, coordination, approval or rejection of
Changes. The implementation of Changes includes changes,
deviations and waivers that impact on the
configuration.
|
|
Configuration
documentation |
Documents that
define requirements, system design, build, production, and
verification for a Configuration Item.
|
|
Configuration
identification |
Activities that
determine the product structure, the selection of
Configuration Items, and the documentation of the
Configuration Item's physical and functional characteristics,
including interfaces and subsequent Changes. It includes the
allocation of identification characters or numbers to the
Configuration Items and their documents. It also includes the
unique numbering of configuration control forms associated
with Changes and Problems.
|
|
Configuration
item (CI) |
Component of an
infrastructure - or an item, such as a Request for Change,
associated with an infrastructure - that is (or is to be)
under the control of Configuration Management. CIs may vary
widely in complexity, size and type, from an entire system
(including all hardware, software and documentation) to a
single module or a minor hardware
component.
|
|
Configuration
Management |
The process of
identifying and defining Configuration Items in a system,
recording and reporting the status of Configuration Items and
Requests for Change, and verifying the completeness and
correctness of Configuration Items.
|
|
Configuration
Management tool |
A software
product providing automatic support for Change, Configuration
or version control.
|
|
Configuration
Management
Database
(CMDB) |
A database that
contains all relevant details of each CI and details of the
important relationships between CIs.
|
|
Configuration
Management plan |
Document setting
out the organization and procedures for the Configuration
Management of a specific product, project, system, support
group or service.
|
|
Configuration
structure |
A hierarchy of
all the CIs that comprise a
configuration.
|
|
Interface |
Physical or
functional interaction at the boundary between Configuration
Items.
|
|
Software
Configuration Item
(SCI) |
As
'Configuration Item', excluding hardware and
services.
|
|
Version |
An identified
instance of a Configuration Item within a product breakdown
structure or configuration structure for the purpose of
tracking and auditing change history. Also used for software
Configuration Items to define a specific identification
released in development for drafting, review or modification,
test or production.
|
