What this heading covers
Safety here is about harm to people, property or the environment from the product in its context, not about the absence of defects. The five families cover the constraints the product must operate within, its ability to identify risks, its behaviour when it fails, the warnings it gives, and its integration with other systems in a way that stays safe. This is the characteristic most likely to be new to a team whose measure library follows the earlier eight-characteristic model, and the one where a product quality measure can overlap with a sector safety case. The draft keeps the measure at the product level; it does not replace a hazard analysis or a sector regime. The 2023 model also adds intervenability under safety, and the draft gives it no separate family.
Record position: characteristic 9 of 9, carrying 5 of the 40 measure families in clause 6.
What the heading asks of a team
New in the model, new in the measures
A library built on the 2011 model has no safety characteristic at all. Adding the heading without measures would be a label, not a measurement.
Product measure, not a safety case
The measure says something about the product's safety properties. It does not discharge a sector obligation, and the page says so.
Fail safe needs a defined safe state
The measure depends on a state the product is supposed to reach on failure. Without that definition there is nothing to measure.
The common confusion
Safety is new to the product quality model, and it is often confused with the absence of defects. It is about harm in context: constraints, risk identification, safe failure, warning and integration.
The measure families in this characteristic
6.10.2Operational constraint measures6.10.3Risk identification measures6.10.4Fail safe measures6.10.5Hazard warning measures6.10.6Safe integration measures
What to put in place before publication
- Name the harm the product could cause and the context in which it could occur, before choosing any measure.
- Write the operational constraints the product must respect, and the measure that shows it does.
- Define the safe state for the product and the conditions that should trigger it.
- Record how hazards are identified and how warnings are delivered and acknowledged.
- Decide how intervenability will be measured, and label it as a local measure.
The test a reviewer asks
- Does each safety measure name the harm and the context it is about?
- Is the safe state defined, and is there evidence the product reaches it?
Where teams usually fall short
- Safety reported as a count of defects with a safety label, which measures nothing about harm.
- A hazard warning that is displayed but never acknowledged, so its effectiveness is unknown.
What happens next
Operational constraint and risk identification set the frame. Fail safe, hazard warning and safe integration are the three with the most direct evidence.
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