The design requirements spec (DRS) is derived from the SRS of Part 1, 7.10, typically by decomposing each safety function and allocating its parts to subsystems such as sensor groups, logic solvers and actuators, which may be decomposed further into elements. It must be expressed and structured so its requirements are clear and precise, free of ambiguity, verifiable, testable, maintainable and feasible; readable by anyone using it at any lifecycle phase; and traceable back to the system safety requirements spec (SRS).
This control maps to 2 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.
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.