What this heading covers
This is the characteristic most teams think they already measure, and the one where the population is most often wrong. Completeness needs a requirement set to be complete against. Correctness needs an expected result for every case. Appropriateness needs a task and a user, not a feature list. The draft separates the three into their own families, which is a warning against the single percentage of requirements met that many programmes report as functional quality. A product can meet every written requirement and still be functionally inappropriate for the task it is put to.
Record position: characteristic 1 of 9, carrying 3 of the 40 measure families in clause 6.
What the heading asks of a team
The population is the product
Requirements are a proxy for the intended function, not the function itself. A measure built only on requirements inherits every gap in the requirements.
Three questions, three measures
Was anything missing, was what exists right, and does it suit the task. The three families answer different questions and should not be collapsed into one score.
The model moved
The 2023 model adds functional adaptability under functional suitability. The draft contents gives it no separate measure family, so a team that needs it must define its own measure and label it as local.
The common confusion
Completeness, correctness and appropriateness are often collapsed into a single percentage of requirements met. The draft keeps them apart because each fails for a different reason, and the single percentage hides two of the three.
The measure families in this characteristic
6.2.2Functional completeness measures6.2.3Functional correctness measures6.2.4Functional appropriateness measures
What to put in place before publication
- Assemble the requirement baseline the completeness measure will use, with an identifier for every requirement and its status.
- Define the expected result for correctness at the level the product is tested, and record where the expectation came from.
- Name the tasks and user groups the appropriateness question is about, because it cannot be answered without them.
- Decide now how functional adaptability will be measured, and mark it as a local measure, since the draft has no family for it.
- Put the three results side by side in the report rather than averaging them.
The test a reviewer asks
- Does the completeness measure name its requirement baseline and date?
- Is there an expected result on record for every case counted in the correctness measure?
Where teams usually fall short
- One percentage of requirements met, presented as functional quality, with no correctness or appropriateness measure behind it.
- A baseline that was edited after testing, so completeness improves without any change to the product.
What happens next
Read the three family pages in order: completeness, correctness, appropriateness. The first two are the ones an acquirer will ask for; the third is the one that decides whether the product is any use.
Source
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 25010:2023, Product quality model https://www.iso.org/standard/78176.html 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