Example 1 — Turn a client's wish into a spec
Show the steps and the answer
Pull out what the system does. F1: a customer can choose a drink, size and milk and sees the price before paying. F2: the customer gets an order number and a notification when the drink is ready.
Functional requirements are actions the user takes or the system performs; 'order coffee from their phones' hides these two.
Turn 'slow' and 'crash' into numbers. N1: the order page loads in under 2 seconds on a 4G phone. N2: the system handles 200 orders between 12:00 and 13:00 without failing.
Those words are the owner's real worries; numbers make them testable and give the developer a target.
Write an acceptance test for N2: simulate 200 orders in one hour; all 200 receive order numbers and none returns an error.
An acceptance criterion is an experiment the client can watch, so 'finished' is not a matter of opinion.
Read the spec for technology names; there are none.
The developer is still free to build a website or a phone app, which is a design decision, not a requirement.
Answer: F1: choose drink, size and milk and see the price. F2: get an order number and a ready notification. N1: page loads in under 2 s on 4G. N2: 200 lunchtime orders in an hour with no failures. Acceptance: a simulated 200-order hour completes with zero errors.
Takeaway: Split a brief into what the system does and how well it must do it, then attach a number and a test to every 'how well'.