Second edition at FDIS, stage 50.00, 23 July 2026/ Planning date 15 February 2027, an estimate/ ISO/IEC 25059:2023 applies today
25059ISO 25059 Revision CheckerThe AI quality model, clause by clause, and the edition that follows it
ANSWER

How do you write an AI quality requirement?

Name the characteristic, state the task and the context, give a measure and a method, set a threshold, state the conditions the result holds under, name the evidence and give an owner. A requirement that repeats a definition without a measure cannot be evaluated, and a single accuracy figure is not a correctness requirement.

Start with the definition

Take the characteristic from the model and read its definition. The definition tells you what the quality is; it does not tell you what good looks like for your system. That is the work.

Add the five parts

A task, a measure, a method, a threshold and the conditions. For functional correctness that means the error rate and the evaluation set as well as the success rate. For robustness it means a labelled case in each named category. For transparency it means the information and the audience.

Name the evidence

Before the requirement is approved, name the artefact that will show it is met and where it is kept. A requirement whose evidence cannot be named is not ready.

Give it an owner and a date

A requirement with no owner is not controlled, and one with no review date drifts. Put both on the row, and add the trigger for an earlier review, such as a model change.

Use the model for completeness

When the set is written, compare it against the characteristics in the model and record the include or exclude decision for each. The free check does a first pass.

Check it yourself. The model is on the record, clause by clause, and the revision is on the revision page. The sources are on the sources page. Not legal advice; does not certify.

Where to go next