Terms related to trustworthiness · 3.5.12
robustness
the ability of a system to hold its level of performance whatever the circumstances
What this term settles
The definition fixes what robustness means inside this vocabulary and, just as usefully, where the boundary sits. A reader who means something wider or narrower is using a different term and should say so.
Who it binds
Nothing here creates an obligation by itself, and the obligation for robustness arrives when the firm writes the term into a control, a specification or a purchase order.
What to do in your practice
Add robustness to the vocabulary register and to the onboarding pack. A term that is only in a PDF is not controlled; it is controlled when a new joiner can find it and a reviewer can test it.
Evidence an auditor or regulator asks for
- A controlled vocabulary entry for robustness with the citation 3.5.12, an owner and a review date.An auditor can check that robustness is controlled rather than assumed.
- An assurance argument that links the property to the test, the review or the incident record behind it. The row names robustness.Shows robustness in use in the artefact the firm relies on, not only in a glossary.
- A register row with the owner, the date and the evidence reference for the claim. The record carries the robustness entry and its date.The assurance case asserts the property without naming the test, review or incident record that supports it. The gap is tested against robustness.
Common gaps this page catches
- robustness is used in the assurance argument without a written definition, so two teams can mean different things.
- A local synonym has grown up beside robustness and the two are now used interchangeably.
What to prepare before the amendment lands
Brief the owners who use robustness most often, then ask each to return one artefact that shows the entry in use. File the artefacts against the register row.
How to test it here
Take one live artefact rather than a template, find the sentence or field where robustness is used, and put this page beside it. Record the answer, the artefact and the date, because that record is the evidence and a glossary entry on its own is only an intention.
What this page does not claim
The page does not reproduce the standard, certify the firm or predict the wording the amendment will use; it states robustness at the claim level "definition" and stops where the public record stops.
Common questions
- What does robustness mean in ISO 22989?
- the ability of a system to hold its level of performance whatever the circumstances
- What evidence should we keep for 3.5.12?
- A controlled vocabulary entry for robustness with the citation 3.5.12, an owner and a review date. An assurance argument that links the property to the test, the review or the incident record behind it. The row names robustness.
- Is robustness a requirement?
- No: robustness is a definition or clause of a terminology standard, and it becomes binding only when a firm writes it into a policy, a contract or a procedure, or when another standard incorporates it.
Related units
Source. ISO/IEC 22989:2022, Clause 3.5.12, Terms and definitions. Open the ISO public entry. Retrieved 21 October 2026.
https://www.iso.org/obp/ui/en/#iso:std:iso-iec:22989:ed-1:v1:en
ISO catalogue record 88145, the amendment status, stage and dates. Catalogue record 74296, the base standard.
Claim level: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text.
Last updated: 2026-10-21 · Markdown version · Check your vocabulary