Activities should produce detailed design data from the requirements and concept (HDL, component, assembly and interconnection data, test methods, and data on the hardware/software interface); implement architectural techniques as needed (safety monitors, dissimilarity between function and monitor, preventing design errors affecting safety, fault tolerance); design in test features to allow safety requirements to be verified, including at acceptance and return-to-service testing; assess unused functions for safety effects and address adverse ones; identify design, installation or operating constraints whose violation could affect safety; feed derived requirements back; and pass omissions and errors on for resolution.
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.