← Back to slide 03Repository →

Read more · slide 03 / 07 · specified · functional

What it must do.

The functional spec says what the work must do, in plain language, one numbered line at a time. Each line has a check, so you can prove it was met.

1 Specified · functional2 Agreed3 Met

A worked example

The Garden shop's checkout, the same one the slides carry. Three requirements, each with an id and the check that proves it.

IdRequirementCheck
FS-010Show the basket with totalsThe total equals the lines plus delivery.
FS-011Show the delivery dayThe day shown matches the slot chosen.
FS-012One clear action to payopenThe page has exactly one primary button.

Why every line has an id

An id makes a requirement citable. The technical spec can say which line it serves, the storyboard can pin a requirement to a button, and the build can say exactly which lines it delivered. When something changes later, the change can name what moved.

Why every line has a check

Without a check, "done" is an opinion. With one, it is a test anyone can run. The check is written when the requirement is written, not after the build, so the build is aimed at it from the start.

Unknowns are allowed. Hidden ones are not.

A first draft will have gaps. A placeholder with no question and no owner is how a gap gets built around by guesswork. So a placeholder left in a spec is flagged. You can leave something open, but you must say what is open and who will answer it, and it is closed before review.

Carries forward: FS-012 reappears on slide 03 (the technical line that meets it), slide 04 (the Pay button, sent back and redrawn) and slide 05 (cited by the build).