Requirements analysis

What it is

Requirements describe outcomes, rules, and constraints.

When to use it

Start by translating prose into observable acceptance criteria.

Syntax

Actor -> action -> outcome -> acceptance test

Example

Requirement: an owner can cancel a pending order.
Acceptance: owner + pending -> cancelled.
Denied: other user -> forbidden.
Conflict: settled order -> unchanged + conflict.

Common mistakes

Do not implement unspecified features before required outcomes.

Related topics