Write software requirements with examples from real work
Describe roles, input, expected results and exceptions in terms that can be checked at acceptance.

In short
- Instead of asking for an intuitive interface, say that a planner sees available crews, gets an overlap warning and can record an exception.
- What if a customer changes their address after approval?
- Attach a priority, test case and decision maker.
- Next steps
On this page
Describe observable behaviour
Instead of asking for an intuitive interface, say that a planner sees available crews, gets an overlap warning and can record an exception. Specify what the user sees and what the software saves.
Capture a counterexample
What if a customer changes their address after approval? Record which version is authoritative and whether a new decision is needed. Include a rejection, a missing field or a change for every important workflow.
Give requirements an owner
Attach a priority, test case and decision maker. Ask users to walk through the workflows before development. Keep business decisions and scope changes visible so that people can revisit them when new information appears.
Next steps
Creagrid / actie
Practical checklist
Describe the problem and intended outcome.
Involve the people who use the process every day.
Test the riskiest assumption with a small prototype.
Define tests, ownership and maintenance up front.

