Season Requirements Template

Tie requirements directly to game rules and strategy.

Functional requirements

• Itemize and number (R1, R2, …); cite rule or strategic need.

Performance targets

• Example: “Cycle time ≤ N s”, “Hold ±X deg”, “Drive speed Y fps”.

Test/acceptance criteria

• How we will prove each requirement in practice.

Traceability

• Map requirements → subsystems → tests → owner.

Instructions (numbered)

1. List requirements (R1, R2…) with rule/strategy citations.
2. Add performance targets (time, accuracy, speed, force).
3. Define acceptance tests for each requirement.
4. Map requirements to subsystems and owners.
5. Review and reprioritize as strategy evolves.

Best practices

• Keep requirements specific and testable.
• Trace each subsystem back to a requirement; avoid orphan features.
• Update when rules/Q&A change.

Common mistakes

• Vague/non-testable requirements.
• Features with no requirement linkage.

Checklist

• Requirements numbered and cited
• Targets and tests defined
• Traceability map complete
• Owners assigned