Requirements and design

Verification method How a requirement is checked: inspection, analysis, demonstration or test.

Acceptance criteria The pass/fail conditions, stated with numbers or observable conditions, that show a requirement is m...

Requirement source Where a requirement comes from: a goal, a stakeholder need, a regulation citation, a risk, a scenari...

Rationale Why a requirement exists, and the consequence of its absence.

Requirement scope (includes / excludes) What a requirement covers (includes) and what it excludes. Stating both keeps the requirement from b...

Role register The list of roles in an analysis document with the person who currently holds each. It is the only p...

Owner role (requirement owner) The requirement owner is a role taken from the role register, never a person. Every requirement has...

Requirement level Where a requirement sits in the decomposition. One of: business, stakeholder, system or software.

Requirement type The kind of a requirement. One of: business, stakeholder, functional, quality, service-level, securi...

Requirement attribute A named field every requirement carries: id, title, statement, type, level, owner, scope, rationale,...

Requirement A statement of what the system must do, or the constraint it must respect, in the target state. It i...