What this heading covers
The four families describe different mechanisms and they need different data. Faultlessness is about the absence of failure in operation or test. Availability is about the proportion of time the service is usable. Fault tolerance is about continuing to operate when a component fails. Recoverability is about restoring service and data after a failure. A programme that reports availability alone has said nothing about how the product behaves when something breaks, and a faultlessness count without an operating window cannot be compared. Reliability measures are the ones most often built from operational data, which means the observability of the product is part of the measurement method.
Record position: characteristic 5 of 9, carrying 4 of the 40 measure families in clause 6.
What the heading asks of a team
Failure needs a definition
A failure is a departure from the required behaviour that a user or a monitor can observe. Without that definition, every support ticket becomes a failure or none does.
The window is part of the measure
Availability and failure rate are meaningless without the period and the population they cover.
Tolerance is tested, not hoped for
Fault tolerance needs an injected or observed component failure. A design document is not evidence of it.
The common confusion
Reliability is often reported as uptime. Availability is one of four families, and a product can be available, fragile, slow to recover and full of failures at the same time.
The measure families in this characteristic
6.6.2Faultlessness measures6.6.3Availability measures6.6.4Fault tolerance measures6.6.5Recoverability measures
What to put in place before publication
- Write the failure definition and the severity scale the reliability measures will use.
- Define the service window and the measurement period for availability, including planned maintenance.
- Plan the fault injection or the failure observation that will evidence fault tolerance.
- Write the recovery time objective and the recovery point objective, and measure against them.
- Connect the measures to the operational telemetry, and record the coverage of that telemetry.
The test a reviewer asks
- Is the failure definition written down and used consistently across the four families?
- Does the availability result state its window and whether maintenance is excluded?
Where teams usually fall short
- Availability computed from an uptime monitor that only checks one endpoint.
- Fault tolerance claimed from architecture diagrams, with no injected failure on record.
What happens next
Read faultlessness and availability together, then fault tolerance and recoverability. The first pair describes normal operation; the second describes a bad day.
Source
ISO Online Browsing Platform, free preview of ISO/IEC DIS 25000-23.2 https://www.iso.org/obp/ui#iso:std:iso-iec:25000:-23:dis:ed-1:v2:en read 22 October 2026
ISO/IEC 25010:2023, Product quality model https://www.iso.org/standard/78176.html read 22 October 2026
ISO/IEC 25023:2016, Measurement of system and software product quality https://www.iso.org/standard/35747.html read 22 October 2026