Season Architecture Overview Template
Show how subsystems satisfy requirements.
System diagram
- Intake → indexer → shooter; drivetrain; climb; electronics; vision.
Interfaces
- Envelopes, mounts, power budgets, data links.
Choices and rationale
- Why this drivetrain, why this intake path, why this sensor stack.
Risks and mitigations
- Top 3–5 risks with owners and dates.
Instructions (numbered)
- Draw system diagram with power/data/air paths.
- Define envelopes, mounts, power budgets, data links per subsystem.
- Record choices and rationale tied to requirements.
- List top risks and mitigations with owners/dates.
- Review with leads (mech/CAD/EE/SW/strategy) before locking.
Best practices
- Keep diagrams updated as design changes.
- Tie architecture choices back to requirements and fouls/constraints.
- Include serviceability/access in the architecture review.
Common mistakes
- Ignoring power/weight budgets; no plan for access/maintenance.
- Risks unowned or undated.
Checklist
- Diagram current
- Interfaces (envelopes/power/data) defined
- Choices linked to requirements
- Risks with owners/dates
- Cross-team review done