Configuration Management

Activities

Identification, Status Accounting, Verification, Audit

Source of Truth

Baselined artifacts, version-controlled

≠

Change Control

Configuration management is broader than change control

every baselined item has a history you can prove

Version Timeline

how to read this

› Each dot is a baselined version of the product or document. Every change creates a new version.
› The version number, the date, and the approved change request are all linked — that's status accounting.
› The rejected branch shows that even failedchanges get recorded. "Never happened" is not acceptable bookkeeping.
› Configuration audits check that the current real product matches the latest approved version. Drift is a finding.

Identification

Name and version every baselined item.

Status Accounting

Record what changed, who approved, when applied.

Verification

Confirm real state matches approved state.

Audit

Formal review. Findings become corrective actions.

Change control manages decisions about changes. Configuration management tracks what the product actually is across versions.

Deliverables, documents, and designs all get version identifiers. Without versioning you cannot audit or reproduce results.

Configuration audits check that the as-built state matches the approved configuration. Gaps are findings.

Baseline everything

If it changes and matters, version it. Scope, schedule, deliverables, documents.

Do not confuse the two

Change control decides. Configuration management records and audits.

Identification

Every version gets a name and number. v1.0, v1.1, v2.0. You know which one is current.

Status Accounting

A change log tracks every edit. Who changed what, when, and why.

Verification and Audit

Periodic check that the document matches the approved version. Find and fix drift.

Identify, track, verify, audit. Version everything that matters.

reading is not enough, you gotta practice

1,800 practice questions written by certified professionals.