5.5.18 · D1Embedded Systems & Real-Time Software

Foundations — Safety-critical standards — DO-178C (airborne software), IEC 61508, ISO 26262

2,990 words14 min readBack to topic

This page assumes nothing. Before you read the parent note, you must be able to read every symbol it throws at you without pausing. Let's build them one at a time, each on top of the last.


1. The starting picture: hazard, harm, and rigor

Before any letter or number, hold this image in your head.

Figure — Safety-critical standards — DO-178C (airborne software), IEC 61508, ISO 26262
Figure s01 — A see-saw: on the left, a heavy pan labelled HAZARD (possible harm) tips down; on the right, a pan labelled RIGOR (effort to prove safe) rises. An arrow marks the pivot with "must balance." It shows the single rule of the whole topic — more possible harm demands more engineering rigor.

Every symbol below is a tool for measuring one side of that see-saw — either how big is the danger or how thoroughly did we check.


2. Failure, fault, and error — the three words people mix up

The picture: a fault is a landmine buried in the field. An error is stepping on it. A failure is the explosion everyone sees.

Why the topic needs this: every standard is obsessed with dangerous failures — the explosions that reach a person and can cause harm. Faults that never become failures don't hurt anyone. See Fault Tolerance & Redundancy for how systems catch errors before they become failures.


3. Probability — a number between 0 and 1

The picture: a ruler from 0 to 1. Slide a marker; near 0 means "basically never," near 1 means "basically always."

The parent note writes numbers like . That's not a mistake or a weird unit — it's just a very small probability. Let's earn that notation next.


4. Powers of ten and — writing tiny numbers

The picture: each minus-one in the exponent shifts the decimal point one step left, making the number ten times smaller.

Figure — Safety-critical standards — DO-178C (airborne software), IEC 61508, ISO 26262
Figure s02 — A horizontal number line of dots labelled with their decimal values (1, 0.1, ..., 0.000001) underneath, and an arrow noting "each step: 10x smaller (safer)." It defines how to read the tiny probabilities used in the SIL bands.

Why the topic needs this: failure probabilities are naturally tiny ( in a million per hour). Writing them as is error-prone; is clean. Every safety band is a range of these.


5. Rate: (lambda), time , and "per hour"

The picture: imagine tally marks appearing on a wall, one each time something fails. is how fast the marks appear. A drippy tap dripping once an hour has "drip rate" .

Why the subscript ? The parent tags it: Dangerous, Undetected. Not every fault is dangerous, and some dangerous ones get caught by diagnostics. counts only the ones that are both dangerous and silent — the truly scary ones. See Failure Rate & Reliability.


6. The constant and why the exponential appears

The parent uses without explaining it. First we must earn the letter itself.

Why the exponential and not, say, a straight line? A straight line would eventually hit zero and go negative — impossible for a fraction. Exponential decay glides toward zero and never crosses it, and it's the only curve where the shrink rate is proportional to how much is left. That "proportional to what remains" is exactly what constant-rate, memoryless failure means.

Figure — Safety-critical standards — DO-178C (airborne software), IEC 61508, ISO 26262
Figure s03 — Two curves against time: the lavender "still working" survival curve falling from 1, and the coral "already failed" curve rising from 0, with a dashed straight line hugging the failed curve near the origin (shaded butter region). It shows why the exact risk can be replaced by the straight line only for small .

The picture: zoom into the very start of the falling curve — it looks straight. That straight bit is . This is why the parent can replace the scary exponential with the simple product but only because is far below 1 in real safety systems.


7. Integral , and the average failure probability

The parent computes . Three things are new: , , and .

The picture: the failure probability grows from (just tested, perfect) up to about (just before the next test) along a nearly straight ramp. The integral is the area under that ramp. Dividing by turns "total area" into "average height," which is .

Figure — Safety-critical standards — DO-178C (airborne software), IEC 61508, ISO 26262
Figure s04 — A coral ramp rising from 0 at "just tested" to at "just before next test," with the triangular area under it shaded, and a dashed mint line at half-height marking the average . It shows geometrically why averaging the straight risk ramp gives the factor of one-half.

Why the integral: it's the honest way to turn "risk that keeps growing between tests" into a single average number () you can compare to a safety band. (The approximation makes that integral a triangle instead of a curve — fine because .)


8. The level letters and numbers — and why they point in different directions

The picture: three staircases. On the DAL staircase, the top step is labelled A. On the SIL staircase, the top is 4. On the ASIL staircase, the top is D. Same height (max rigor) — different label at the top.

Why the topic needs levels at all: rigor is expensive and grows roughly exponentially with strictness. Levels are how you spend effort where lives depend on it — the see-saw made into a dial. See Functional Safety and FMEA & Hazard Analysis for how the hazard side is measured.


9. Coverage words: statement, decision, MC/DC

The picture: think of a road map of the program. Statement coverage = "did we drive every road?" Decision coverage = "did we take every fork both ways?" MC/DC = "did we prove each individual signpost actually matters to where we end up?"

Why the topic needs three: stricter coverage catches subtler bugs but costs more tests — so the parent ties the deadliest level (DAL A) to the strictest coverage (MC/DC). Full detail lives in Code Coverage Metrics.


10. Prerequisite map

Node names below match the section concepts; boxes marked (see …) point to related vault topics linked in the text, not to sections of this page.

Probability 0 to 1

Powers of ten 10 to minus n

SIL probability bands

Failure rate lambda per hour

Exponential survival P of t

Constant e about 2.71

Small t shortcut lambda times t

Integral as area under ramp

PFD average equals lambda T over 2

Fault error failure words

see Fault Tolerance and Redundancy

IEC 61508 SIL

Hazard harm rigor see-saw

DAL SIL ASIL levels

DO-178C DAL

ISO 26262 ASIL

Coverage statement decision MCDC

see Code Coverage Metrics


Equipment checklist

Cover the right side; can you answer before revealing?

What does equal as a decimal?
— one in ten thousand.
What is the difference between a hazard and harm?
A hazard is the possibility of danger; harm is the actual injury or loss that results.
What is the difference between a fault and a failure?
A fault is a hidden flaw; a failure is the flaw actually causing wrong outside behaviour (the visible explosion).
What does measure, and in what units?
A failure rate — how many failures per unit time, usually per hour ().
What does the symbol stand for here?
A duration of elapsed time, in hours.
Why does carry the letters D and U?
Dangerous and Undetected — the failures that both matter and stay silent.
What does the survival function represent?
The probability the component is still working at time after its last test; , falling toward 0.
What number is , and what makes it special?
; is the one curve whose rate of change equals times itself ().
What modeling assumption lets us use for survival?
A constant-rate, memoryless (Poisson) failure process — chance of failing next moment doesn't depend on age.
Why is for small , and when is it valid?
Near the origin the rising "already failed" curve leaves with slope , so it hugs the straight line ; the approximation is valid only while (very few failures so far).
What does mean, and what is ?
Probability of Failure on Demand — the chance the safety function is already broken when needed; is that averaged over the test interval.
What does compute geometrically here?
The area under the risk-vs-time ramp between a test and the next.
Where does the in come from?
The average height of a straight ramp is its midpoint — half the peak.
In DO-178C, is DAL A the safest or the most critical?
The most critical (worst-case failure) — it demands the most rigor, including MC/DC.
In ISO 26262, which letter is most demanding?
D (with QM being "no safety requirement").
What extra thing does MC/DC require beyond decision coverage?
Each individual condition must be shown to independently flip the outcome.

Back to the parent topic.