What this heading covers
The three headings are a sequence. Clause 5.1 is called the requirement of this document to be applied, which suggests the draft says what applying it means rather than leaving it to taste. Clause 5.2 is product quality measurement concepts, which is where the quality property, the quality measure element and the measurement function are put to work. Clause 5.3 is the approach to quality measurement, which is where a team would find the guidance on selecting measures, setting targets and reading results. The public text does not carry the three subclauses, so this page describes the shape and the decisions they force, and marks each as our reading rather than the draft wording.
Record position: clause page 5 of 6. The heading is public; the text is not.
What the heading asks of a team
5.1 Requirement of this document to be applied
The heading implies a statement about what it means to apply the document. A team should expect to record which measures it applied, to which product, at which lifecycle stage, and with what target values.
5.2 Product quality measurement concepts
The concepts are public through clause 3 and 25020: property, QME, measurement function, measure. This subclause is where they are combined into a measurement programme.
5.3 Approach to quality measurement
The approach is the part a buyer has to defend: why these measures, why these targets, how the result is read and what is done when it is poor. The draft does not set the targets, as the scope says.
What to put in place before publication
- Write a one page measurement plan that names the product, the characteristics, the measures, the lifecycle stage and the target values.
- Record why each measure was selected, in one line, so the plan can be defended when the result is challenged.
- State how a result will be read: against a target, against a baseline, or as a trend, and who decides.
- Name the person accountable for the programme and the person who signs a published result.
- Set a review date for the plan, and a trigger for revising it when the model or the product changes.
The test a reviewer asks
- Can the team show the plan, the selection rationale and the target values together?
- Does the plan say what happens when a measure misses its target, rather than only what the number was?
Where teams usually fall short
- A dashboard with no plan behind it, so nobody can say why a measure is there or what a good value would be.
- Target values copied from another product category, which the scope explicitly says they depend on.
What happens next
Clause 6 is the measure set itself: nine characteristics and forty measure families. The model page is the fastest way to see the whole shape before reading a family page.
Source
ISO/IEC DIS 25000-23.2, standard record 89069 https://www.iso.org/standard/89069.html read 22 October 2026
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 25023:2016, Measurement of system and software product quality https://www.iso.org/standard/35747.html read 22 October 2026