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.5.3.3: 6.5.3.3 Requirements activities in managing validation results

The trace is kept for every element that has been validated. Validation shows that what was built meets the needs and requirements the stakeholders expressed, in other words that the right system was built, and the trace can be held in an RTM or a comparable information item.

Maintained by Gerard Blokdyk

What else in your programme already covers this

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

  • VAL.1.BP4 VAL.1.BP4 Ensure consistency and establish bidirectional traceability

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 1 it maps to, and the evidence behind each claim, over MCP and REST.