About IEC 61508-3 (Software Requirements)
This hands-on workshop builds applied knowledge and team exercises around the certification requirements of IEC 61508-3.
Part 3 of IEC 61508 defines the software safety lifecycle: requirements specification, architecture, design, coding, verification, integration, validation, and modification of safety-related software, with techniques graded by SIL.
What it regulates
Embedded and application software performing or supporting safety functions, including the selection of languages, coding standards, verification techniques, and tool qualification.
Who must comply
Developers of safety PLC firmware and runtime systems, application programmers of safety logic, and suppliers of software elements or libraries claiming systematic capability.
Frequently asked questions: IEC 61508-3
Do software tools such as compilers need certification?
Tools are classified T1-T3; a T3 tool (whose output goes into the safety system, like a compiler or code generator) needs qualification evidence — certified status, proven-in-use history, or validation of its output — proportionate to the SIL.
How is pre-existing or open-source software handled?
As a pre-existing software element it must be justified via the routes the standard allows: compliant development evidence, proven-in-use data, or assessment of the element against the requirements for its role, plus wrapping and constraints defined in the safety manual.
Which programming languages are acceptable for SIL software?
The standard favors languages, subsets and coding standards that support unambiguous, analyzable code — for example limited-variability languages for application logic, or C constrained by a recognized subset with static analysis. Justification of the language and subset choice is part of the compliance argument.