23ISO 25000-23Part 23 measurement record

Home / The record / 6.3 Performance efficiency measures

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

6.3 Performance efficiency measures

Performance efficiency covers how quickly the product responds, how much resource it consumes and how much work it can carry. 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

The three families are related but not interchangeable. Time behaviour is about response and processing time under stated conditions. Resource utilization is about what the product consumes while doing the work. Capacity is about the limit it can carry before a property fails. A programme that reports only response time has measured one third of the characteristic. The conditions matter as much as the number: a response time without the load, the data volume and the environment is not reproducible, and the scope says target values depend on the product and its context.

Record position: characteristic 2 of 9, carrying 3 of the 40 measure families in clause 6.

What the heading asks of a team

Conditions are part of the measure

Load, data volume, hardware, network and concurrent users decide the value. Record them beside the result or the result cannot be compared.

Resource is not only compute

Memory, storage, network and energy all count as consumption. The 2023 model adds environmental sustainability here, and the draft gives it no separate family.

Capacity needs a failure definition

A capacity figure is meaningless without saying which property fails at the limit: response time, error rate, or a hard stop.

The common confusion

Performance efficiency is often reduced to response time. The draft separates time, resource and capacity because a product can be fast, hungry and unable to scale, all at once.

The measure families in this characteristic

What to put in place before publication

  1. Write the load and environment profile for every performance test, and keep it with the result.
  2. Name the resource dimensions the product is accountable for, and the instrument that measures each one.
  3. Define what counts as failure at capacity, because the limit is only meaningful against that definition.
  4. Decide how environmental sustainability will be reported, and label any measure of it as local.
  5. Separate production measurement from test measurement in the report, since the environments differ.

The test a reviewer asks

  • Can the response time be reproduced from the recorded profile?
  • Does the capacity result state which property fails and at what value?

Where teams usually fall short

  • A single response time from a developer laptop, presented as the product's performance.
  • Capacity quoted as a user count without the failure definition or the data volume.

What happens next

The time behaviour page is the one most buyers start with. Resource utilization and capacity are the two that explain why a product that felt fast in test falls over in operation.

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.3: 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