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.5: Part 3, 7.4.5 Requirements for detailed design and development: software system design

Responsibility splits are documented in safety planning. Before detailed design starts, the architecture design, the software validation plan and the system's safety requirements are all available. Software is produced for modularity, testability and safe modification. Each major element of the architecture is refined by partitioning into modules (the software system design), with each module's design and its verification specified, and software system integration tests are specified to show the software system meets the software safety requirements at the SIL.

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.

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.