Architecture Decision Language
5 exercises — practise the vocabulary of ADR writing and architecture governance: ADR field vocabulary (Context vs. Decision), Status lifecycle including Superseded, well-structured Consequences sections, decision drivers, and Architecture Review Board scope and bypass conditions.
ADR and architecture governance quick reference
- Context field: answers WHY the decision was needed — forces, constraints, quality attribute requirements
- Decision field: answers WHAT was decided
- Consequences field: positive (gains), negative (accepted costs), risks (uncertain outcomes)
- Status: Superseded by ADR-NNN: old decision replaced; old ADR kept as permanent historical record
- Decision driver: a constraint or quality attribute requirement that shaped which options were viable — not a person
- ARB: governs high-impact, cross-team, or hard-to-reverse decisions; bypassed for low-impact, single-team, reversible ("two-way door") decisions
- One-way door: irreversible or costly to undo — warrants ARB review
Question 1 of