Explain like I'm five · SW Eng

What is Software/Functional Safety?

Software and functional safety, told as a story about putting a book — like a first-aid manual, where one typo can cost a life — through several layers of extra-strict verification.

first-aid manuala single typo in a dosage unit almost slipped throughin an ordinary book it's a small typo — in a first-aid manual, lives depend on it

A single typo in a dosage unit almost slipped through.In an ordinary book it's a small typo — in a first-aid manual, lives depend on it.

just review it like any other bookthis one has lives on the linenot every book can be checked at the same intensity

The editor says to review it like any other book; the proofreader objects that lives are at stake.Not every book can be checked at the same intensity.

1st check2nd checkindependent re-checksoftware/functional safety = putting higher-risk books through several extra-strict layers of checkingthe number of checking layers changes with the risk grade

A higher-risk book goes through several extra-strict layers of checking.The number of checking layers changes with the risk grade.

Grade the riskbooks carry different sizes of risk
Cross-check with twocatching each other's mistakes
An independent team re-checkslooking at it apart from the original team
Actually trial ittrying the manual out before real use
VERIFICATION INTENSITY BY RISKlow — one proofreader is enoughmedium — two proofreaders cross-checkhigh — a separate team re-checkshighest — real trials before real usethe same typo is more dangerous in some booksthe higher the risk, the slower and costlier the verification

Verification intensity changes with the risk grade.The same typo is more dangerous in some books than in others. The table's four grades are a simplified example; real requirements vary by standard.

layered checks lower the risk by a lotbut the book can't wait for zero risk to go outsafety isn't eliminating risk — it's lowering it to a level you can live with

Verification doesn't bring risk down to zero.Safety means lowering risk to a level you can live with.

In one breath

Software/functional safety = putting a higher-risk book through several extra-strict layers of verification.

Functional safety ensures that even if a system fails, people aren't harmed — by applying verification levels (like SIL grades) in proportion to risk. The higher the risk, the more layered safeguards are required: independent review, redundancy, real-world trials. The goal isn't perfect zero-defect — it's lowering risk to an acceptable level.

When grown-ups say it

Functional Safety
Designing so a failure doesn't hurt anyone. Requirements differ by risk grade.
Safety Integrity Level
The 1–4 scale for how reliable a safety function must be. From IEC 61508: level 4 is highest, and a higher level demands stricter verification.
Independent Verification
A separate team checking it again. One side's blind spot gets caught by the other.
Redundancy
A structure where one failing still leaves another standing. Works on a similar principle to cross-checking.
Risk Analysis
Gauging in advance which books carry more risk. Done before grading risk.
White-box/Black-box Testing
Checking methods split by looking inside or only outside. The higher the risk, the deeper and more often both get done. → looking inside, or just reading the outside
IS Audit/PMO
The checker who watches the whole publishing run. Audit can also check that safety verification went as planned. → the checker who watches the whole publishing run
Safety Case
The dossier gathering evidence that it's safe enough. Compiles verification records to explain to outsiders.
Next story
Tracing Back a Lost Original to Rebuild It →
Want another term as a picture book? Request →