ISO/IEC/IEEE 29148:2018 - Systems and Software Engineering - Requirements Engineering
Clause 6: Requirements processes – ISO/IEC/IEEE 29148:2018 - Systems and Software Engineering - Requirements Engineering

ISO/IEC/IEEE 29148:2018 - Systems and Software Engineering - Requirements Engineering 6.6.2.2.3: 6.6.2.2.3 Configuration change management for requirements

Change requests, variance requests and the approved changes to each baseline are tracked to closure. As the operational concepts and the stakeholder, system, software and element requirements change, the changes are captured formally in documented baselines with configuration information identifying each change and its rationale, and requirements traceability is maintained. Requirements are configuration managed in line with the project's and organization's configuration management processes.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • SUP.10.BP4 SUP.10.BP4 Establish bidirectional traceability
  • 8.2.4 8.2.4 Provide means for traceability of change

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Clause 6: Requirements processes – ISO/IEC/IEEE 29148:2018 - Systems and Software Engineering - Requirements Engineering

Query this from an agent

The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.