Skip to main content

Configuration Management

Configuration Management is the process of identifying and defining the items in the system, controlling the change of these items throughout their lifecycle, recording and reporting the status of items and change requests, and verifying the completeness and correctness of items. [IEEE-Standard-729-1983].

The CM process applies to both software and hardware and supports the management of different types of information, e.g. code, documents, drawings, tools, etc.

If Functional Safety or High Integrity products are affected then follow the specific Functional Safety related CM processes Functional Safety.

Process Overview​

Principles​

  • Ensure efficient routines exist to prepare, deliver and maintain releases
  • Ensure configuration items are identified and managed in a CM environment and controlled, audited, and baselined
  • Support continuous integration and delivery of components, products, and systems
  • Continuously monitor the status of configuration items of ongoing development, as well as released systems and products
  • Perform audits to ensure the integrity of baselines
  • Communicate changes and provide training on how to use the CM environment
  • Ensure backup/restore routines exist to recreate releases
  • Ensure documents included in releases are versioned and baselined in accordance with the relevant DMS
  • Ensure bugs are properly managed

Activities​

CMP-1

Configuration Management Activities are structured and planned according to the SPI cadence.

Cadence

Artifacts​

Artifact​Description​RACI​Receiver​Comments
CM PlanDescribes the CM processes during the system or product lifecycle for a stream.(R): Configuration Manager
(A): Stream Owner
(C): Quality Control Manager, Release Owner, Technical Coordinator, Safety Engineer
(I): Cyber Security Engineer, Head of Cyber Security, Development Team, Product Owner, Test Lead, Product Manager		Team-
CM audit reportReports from auditing the result of the CM process.(R): Configuration Manager
(A): Release Owner
(C): -
(I): Cyber Security Engineer, Development Team, Quality Control Manager, Test Lead, Safety Engineer		R&D-
Dashboard and reportsDashboard and reports, mainly from Azure DevOps(R): Configuration Manager
(A): Stream Owner
(C): -
(I): -		R&D-
CI/CD PipelineContinuous Integration / Continuous Deploy. A framework for builds, automated tests, quality gates, code quality metrics, etc.(R): Configuration Manager
(A): Configuration Manager
(C): -
(I): -		TeamThe pipeline is adapted to each stream, depending on maturity, automation, etc.
BaselinesBaseline for a build or release - Snapshot of configuration items and artifacts with traceability between work items, code, pipelines, documentation and produced artifacts(R): Configuration Manager
(A): Configuration Manager
(C): -
(I): -		Team-
Azure TemplatesTemplates for Azure DevOps(R): Configuration Manager
(A): Head of OpEx (R&D)
(C): -
(I): -		Team-
Team ConfigurationsConfiguration of the Azure DevOps structure for teams (areas, iterations, access, pipeline, etc.)(R): Configuration Manager
(A): Configuration Manager
(C): -
(I): -		R&DAdapted to each stream/team depending on the system/product developed
BugAn error, flaw or fault in the design, development, or operation of that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.(R): -
(A): Product Owner
(C): Architect, Cyber Security Engineer, Development Team, Ex Representative, Release Owner, Test Lead, Safety Engineer
(I): Quality Control Manager, Product Manager		R&D-

Dependencies​

CMP-2

References​

Owner: Configuration Management Team