Clause 6.6.2.1: Change management
Whatever causes a requirement change, the project has to expect it and manage the effect.
What clause 6.6.2.1 asks
Whatever causes a requirement change, the project has to expect it and manage the effect. A proposed change goes through impact assessment, review and approval that are defined in advance. Requirements tracing and version management are applied. Requirements engineering therefore runs across the life cycle, not only at the front end: the management activities evolve from elicitation to change management as the project proceeds.
Why it matters
The clause is short and easy to under-implement. The defined process has to cover the impact on the set, the architecture, the verification and the schedule, not only the document edit. The change board needs the trace links to do that assessment, which is why change management and traceability are treated together.
No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.
What good looks like
Define the change request fields, the impact questions and the approval authority. Require a trace report with every request. Record the decision and the version that results. Review the change backlog at each baseline.
Evidence an assessor asks for
The assessor will follow one change from request to approved version. A record that shows only the final edit is not a change record.
- Change procedure The request, impact assessment, review, approval and implementation steps, with the authority for each
- Impact assessment The effect on requirements, architecture, verification, cost and schedule
- Change record The request, the decision, the approver, the date and the resulting version
- Backlog review The open changes and their age, reviewed at each baseline
Where it commonly fails
- Changes approved by email with no impact assessment
- The change board sees the document but not the trace links
- The backlog is never reviewed, so old changes sit open for months
What to do before the revision
Make the impact assessment a one-page form with five questions: requirements, architecture, verification, cost and schedule. It is short enough to be used.
Read across
- 6.6.1 Management overview
- 6.6.2.2.3 Configuration change control
- 6.4.3.5 Manage system or software requirements
- 5.2.8 Requirements attributes
← 6.6.1 Management overview 6.6.2.2.2 Configuration identification →
Source for clause 6.6.2.1: ISO/IEC/IEEE 29148:2018, Clause 6.6.2.1, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.