Clause 6.6.2.2.3: Configuration change control

Current editionISO/IEC/IEEE 29148:2018, Clause 6.6.2.2.3Edition 3 at DIS ballotNo public change recorded

The process tracks and manages baseline changes, change requests and variance requests.

What clause 6.6.2.2.3 asks

The process tracks and manages baseline changes, change requests and variance requests. As the operational concepts and the requirements change, the change is formally captured in documented baselines, together with configuration data identifying the specific change and the rationale. Requirements traceability is maintained. Requirements are configuration managed in accordance with the project and organization configuration management processes.

Why it matters

This is where the change record meets the baseline. The clause expects the change and its rationale to be in the baseline, not only in a ticket. The traceability is what lets the change board see what else moves when one requirement moves.

What good looks like

Link every approved change to the baseline version and to the affected trace links. Record requests for variance separately, because a variance is a deliberate departure and needs its own acceptance. Review the baseline history at each gate.

Evidence an assessor asks for

The assessor will compare the change log with the baseline history. A change that appears in one but not the other is uncontrolled.

• Change log Each approved change, the baseline version, the rationale and the affected items
• Variance register Each request for variance, the reason, the acceptance and the expiry
• Trace update The trace links updated in the same change as the requirement
• Baseline history The versions of the baseline and the changes that produced each

Where it commonly fails

• The ticket is closed but the baseline is not updated
• A variance is treated as an approved change with no expiry
• Trace links are updated in a later batch, so the change is briefly untraceable

What to do before the revision

Update the requirement, the trace links and the baseline in one transaction. A partial update is the defect that survives audits.

Read across

• 6.6.2.1 Change management
• 6.6.2.2.2 Configuration identification
• 6.6.1 Management overview
• 6.4.3.5 Manage system or software requirements

← 6.6.2.2.2 Configuration identification 6.6.2.3.3 Perform information management →

Full register / Revision record