top of page
Purpose & Scope
Learning objectives
CM terminology

Incomplete capability

  • Confusion arise when terms related to Configuration Management are used. People involved in and/or are dependent of configuration management are not able to communicate CM issues effectively.


  • Understanding the purpose and scope of CM terminology.

  • Being aware of the differences in terminology used within different domains.

Performed capability

  • Co-workers dependent on configuration management uses terms that need to be explained to communicate configuration management and related information with in some degree of unclear meaning or understanding of the used terms.

Managed capability

  • Co-workers dependent of configuration management uses the preferred terms to communicate configuration management and related information with the same meaning and understanding of the used terms.

The lack of a common terminology can cause confusion and misinterpretations. This becomes evident when trying to communicate between different organisations, across disciplines and between softwares. Sometimes the terms are not recognized at all, and sometimes the same term (from different sources) can have a totally different meaning. Collecting and using information from different sources therefore makes it necessary to have a common understanding of the used terminology.

A shared Configuration Management capability is dependent on a shared terminology for Configuration Management and related information. This includes terminology such as:


- Configuration item

- Product configuration information

- Change request

- Configuration

- Baseline

- Design authority

- Version

- Variant

- etc


It is important that terms (like the above) have a clear definition and a defined meaning. Understanding and applying the definitions instills a deepened understanding of the concept of Configuration Management.


bottom of page