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
3.2
ISO/IEC 25059
Scope, references and terms

Clause 3.2: Product quality terms

AmendedISO/IEC 25059:2023, Clause 3.2Published edition 2023Second edition at FDIS

The product quality terms define the characteristics the model adds or changes: user controllability, functional adaptability, functional correctness, intervenability and robustness.

What clause 3.2 is

The product quality terms define the characteristics the model adds or changes: user controllability, functional adaptability, functional correctness, intervenability and robustness. The second edition adds environmental sustainability. Each definition is short and each carries a judgement about degree, which is why the requirement has to add the measure.

What the 2023 edition said

The first edition defined the five product terms and placed them in the model.

What the second edition changes

Environmental sustainability is added as a sixth product term. Functional correctness is restated against the 2023 base model.

What is not public

The FDIS text is not public. The change line above is read from the public draft, which is not the FDIS and may differ. No clause level diff is invented here. The ISO stage record is the authority for the dates.

Why it matters to the buyer

The definitions are the only place where the model says what each characteristic means. A requirement that does not use the definition drifts, and a reviewer can show the drift by reading the two side by side.

What to write in the requirement

Write each requirement with the definition in front of you, then add the measure, the condition and the threshold that the definition does not supply. Keep the definition and the requirement in the same document so the link is visible.

Evidence a reviewer asks for

A reviewer will ask which definition a requirement uses. A requirement that paraphrases the definition without a measure is not evaluable.

  • Requirement setOne requirement per characteristic in scope, each quoting the definition it uses and adding a measure
  • TraceabilityA table linking each requirement to its characteristic and to the evidence that will show it
  • Review recordThe date the definitions were checked against the edition in force

Where it commonly fails

  • The requirement repeats the definition and stops
  • Two requirements use the same measure for different characteristics
  • The definition is from an older edition

What to do before publication

Rebuild the requirement set from the definitions rather than editing the old wording. It is faster and it removes inherited assumptions.

Read across

← 3.1 General terms 3.3 Quality-in-use terms →

Full record / Revision record

Source for clause 3.2: ISO/IEC 25059, Clause 3.2, retrieved 20 October 2026. The change line rests on the public draft of the second edition and ISO page 88234. The requirement, evidence and gaps are written from our record. Every source.