How do you turn quality requirements into measurable scenarios?

Question

IT Interview Practice · Accepted Answer

Turn a vague quality goal into a **scenario with an observable response and a measurement rule**. “The portal must be fast” is not enough to choose a design or decide whether a release meets the requirement.

## Structure the scenario

Identify the stimulus source, stimulus, affected system, operating conditions, expected response and response measure. These parts make assumptions explicit so different teams can test the same claim.

## Worked example

For an illustrative returns portal, agree on this scenario with its business owner:

- **Source:** an authenticated customer.
- **Stimulus:** submission of a valid return request.
- **System:** the portal’s submission path.
- **Conditions:** 100 submissions per second for 30 minutes with a representative dataset and healthy dependencies.
- **Response:** persist the request and return an acknowledgment.
- **Measure:** at least 99% succeed, and p95 acknowledgment latency for successful requests is at most 500 milliseconds, measured from the test client.

These numbers are example targets, not industry defaults. Report failures separately so a fast rejection cannot make the latency result look healthy. An acknowledgment is also different from warehouse completion; that needs its own business timing criterion.

## Use the scenario to drive design

The design might accept the request durably and process warehouse work asynchronously. Test that exact path, including realistic network conditions. Write separate scenarios for an unavailable dependency and recovery; a healthy-system load test proves neither.

## Common mistakes

Average latency hides slow users. An undefined dataset makes results hard to reproduce. “Always available” provides no failure boundary or measurement window. A strong interview answer defines what is measured, from where, under which conditions, and who agrees that the target is sufficient.

Reference: [SEI: specifying quality attribute requirements](https://sei.cmu.edu/documents/5465/2013_018_101_60984.pdf).

Structure the scenario

Worked example

Use the scenario to drive design

Common mistakes

Related questions