public:99_annexes:annex-b-terms-and-definitions:b:baseline

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:b:baseline [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:b:baseline [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Baseline ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Baseline is an approved and uniquely identifiable configuration of one or more [[public:99_annexes:annex-b-terms-and-definitions:c:configuration_management|Configuration Management]] items established at a defined point in their lifecycle.
 +
 +A Baseline provides a controlled reference against which later configurations, changes, implementations, deployments, assessments, or results can be compared.
 +
 +A Baseline may identify source revisions, requirements, models, software, machine images, infrastructure definitions, dependencies, compliance settings, operating procedures, evidence, or combinations of these items.
 +
 +An organization changes a Baseline through an authorized change process. Creating a later Baseline does not alter the identity or content of the earlier Baseline.
 +
 +===== Definition =====
 +
 +//approved and uniquely identifiable configuration of one or more configuration items established at a defined point in their lifecycle//
 +
 +===== Source =====
 +
 +Generalized from systems engineering, software engineering, quality management, and configuration-management usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Baseline is more than the latest available version. It identifies a configuration that an authorized process has selected and placed under change control.
 +
 +Different baselines may exist for requirements, architecture, software, machine images, infrastructure, compliance, deployment, and operations.
 +
 +===== Example =====
 +
 +A software factory establishes a Baseline containing pinned source revisions, a hardened machine image, an infrastructure definition, a compliance profile, approved dependencies, and associated evidence. Later changes produce a new Baseline while preserving the earlier Baseline for comparison and reproduction.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>