23ISO 25000-23Part 23 measurement record

Home / The record / 6.2 Functional suitability measures

ISO/IEC DIS 25000-23.2, 6.2 ยท Headings only

6.2 Functional suitability measures

Functional suitability is about whether the product does the job it was meant to do, completely, correctly and appropriately for the task. The draft gives it three measure families.

The free preview lists this heading and its subheadings but not the requirement text. This page states what the heading requires in our words and never invents the wording.

Not legal advice; does not certify. This page states our reading of a public draft, not the standard's wording, and it is not an official interpretation.

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

What to put in place before publication

  1. Assemble the requirement baseline the completeness measure will use, with an identifier for every requirement and its status.
  2. Define the expected result for correctness at the level the product is tested, and record where the expectation came from.
  3. Name the tasks and user groups the appropriateness question is about, because it cannot be answered without them.
  4. Decide now how functional adaptability will be measured, and mark it as a local measure, since the draft has no family for it.
  5. 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

The rules this is built from

Read from the real rules, not invented.

This page is read from the public record for 6.2: the heading in the free contents, and where public, the text the preview carries.

  • Read from the real rules
  • 63 record pages behind it
  • 116 public headings checked
  • Check any line yourself

The measure set is read from the public contents; the model table is read from the public 25010:2023 model. Where the draft text is not public, the page says so instead of filling the gap.

Nothing here is guessed while you wait. Each page is written from the public record and points to the exact page it came from. Record updated 22 October 2026