What this heading covers
The scope is wider than software. It speaks of product quality for ICT products, which the terms clause explains can include hardware, software, data and communication facilities, and it ties every measure to a characteristic or subcharacteristic in the 25010 model. It is written to be used alongside 25010, not instead of it, and it points to the requirements division and the evaluation division for the work that comes before and after measurement. The measures are described as a basic set for each characteristic, not a complete catalogue, and the annexes carry the supporting material: considerations for use, the measurement elements, and the measure data types.
Record position: clause page 1 of 6. The text is public in the free preview.
What the heading asks of a team
What the scope fixes
The target is product quality, measured quantitatively through the 25010 model. The draft does not set ranges, rating levels or grades of compliance, because those depend on the product category, its integrity level and the needs of its users.
What the scope leaves open
Which measures a team selects, how it combines them and what target values it sets are decisions for the organisation and its requirements. The standard supplies the measures and the measurement functions, not the thresholds.
Who it is written for
The introduction names development, quality management, supply, acquisition and maintenance. In practice that is the test lead, the quality manager, the supplier answering a tender, the acquirer running acceptance and the maintainer measuring a release.
What to put in place before publication
- Write down which ICT products are in scope this year: the software, the data, the hardware and the communication facilities whose quality you report on.
- Name the 25010 characteristics you already report against, and mark the ones you report on by anecdote rather than by measure.
- Decide where in the lifecycle each measurement will be taken, because an internal measure and an external measure of the same property answer different questions.
- Record the product categories and integrity levels in use, since the draft says target values depend on them and your register has to carry that context.
- Agree who signs a published quality result, and on what evidence, before the first number leaves the team.
The test a reviewer asks
- Can you name the product, its boundary and the characteristics the result covers, in one sentence?
- Does every reported measure trace to a characteristic or subcharacteristic in the 25010 model?
- Is any number published without the product category and integrity level that give it meaning?
Where teams usually fall short
- A quality report that mixes the product with the project, so a schedule result is read as a product property.
- Measures collected because a tool emits them, with no characteristic behind them and no decision they inform.
What happens next
Clause 2 names the three documents the draft depends on. Read that page next if you need to know what a measure is built from; read clause 5 if you need to know how a measurement programme is meant to run.
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