Requirements capture identifies and records the item's requirements, including derived requirements arising from architecture, technology, basic and optional functionality, environment and performance, and those set by the system safety assessment. Its objectives are that requirements, including allocated PSSA requirements and derived requirements coming out of the hardware safety assessment, are identified, defined and documented; derived requirements go back to whichever process needs them; and omissions and errors are passed to the appropriate process for resolution. Establishing the method of tracing verification results to requirements during capture is desirable.
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.
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.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.