IEC 61508:2010 - Functional Safety of E/E/PE Safety-related Systems
Part 3, Clause 7: Software safety lifecycle – IEC 61508:2010 - Functional Safety of E/E/PE Safety-related Systems

IEC 61508:2010 - Functional Safety of E/E/PE Safety-related Systems 3-7.4.6: Part 3, 7.4.6 Requirements for code implementation

Every software module's code is reviewed (by an individual, a walk-through or formal inspection, in rising rigour). Code produced by an automatic tool meets the support tool requirements of 7.4.4; code reused from pre-existing software meets 7.4.2. Code should be readable, understandable and testable and satisfy the module design, the coding standard and the safety planning requirements.

Maintained by Gerard Blokdyk

What else in your programme already covers this

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.

  • 6:8.4 8.4 Software unit design and implementation

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 Part 3, Clause 7: Software safety lifecycle – IEC 61508:2010 - Functional Safety of E/E/PE Safety-related Systems

Query this from an agent

The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.