Heuristic
Give each requirement one behavior to prove
One sentence can hide three different definitions of done.
Before you use it
- Use when
- A sentence contains several actions, exceptions and outcomes joined by 'and' so partial completion is hard to see.
Keep this limit in mind
- Do not fragment a single coherent condition into tiny statements that lose necessary context; the unit is one independently meaningful behavior.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Split independently verifiable behaviors into separate requirement or acceptance statements. Keep shared rationale outside the statements. If two behaviors must always be verified together, explain why rather than joining them for convenience.
An example
'The service validates the file, rejects invalid rows and emails a report' becomes three checkable outcomes with their own error cases.
Check your result
Each statement can be marked pass or fail without the answer depending on another clause in the same sentence.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingGive each requirement one behavior to prove
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaWrite the need before naming the implementation
Evidence and sources
NASA's requirements checklist emphasizes clarity, one thought per requirement, completeness, explicit assumptions, consistency, traceability, feasibility and verifiability.
The checklist is for systems engineering; smaller tasks can apply the principles proportionally.
Appendix C: How to Write a Good Requirement · Requirements validation checklist
NASA recommends identifying a verification approach for requirements and keeping each requirement uniquely identifiable with a definitive source.
The appropriate verification method and documentation depth depend on risk and project scale.
Appendix D: Requirements Verification Matrix · Requirements Verification Matrix
Edition and review
Version 0.1.0
No review details are supplied for this edition.