An suitable set of techniques and measures (Table B.2 and Part 3) is used to stop faults being introduced during hardware and software design and development; mass-produced standard ICs may rely on their own field experience, while new devices and ASICs follow the ASIC requirements. The design method chosen for the SIL supports transparency, modularity and complexity control; clear expression of functionality, subsystem and element interfaces, sequencing and timing, concurrency and synchronisation; clear documentation and communication; and verification and validation. Maintenance requirements that keep safety integrity in place are formalised at design. Automatic testing and integrated development tools are used where applicable. Integration tests are planned during design, recording test types and procedures, environment, tools, configuration and programs, and pass/fail criteria. Activities at the developer's premises are separated from those needing the user's site. ASIC design and development uses an suitable set of techniques and measures (Annex F).
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.
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 1 it maps to, and the evidence behind each claim, over MCP and REST.