[000] Title
Allocate each ADR a number for easy reference and cataloging \ NOTE: All italicised text provides hints and should be removed for production
Status - DRAFT / ACTIVE / DEPRECATED by [000] / SUPERSEDES [000]
Context
Briefly describe the problem(s) that this ADR intends to address, and why the problems exist.
Decided Approach
Detail the architecturally significant decision that has been / will be made and describe how it addresses the problems outlined in the Context section.
Consequences
What is the impact of this decision on the architecture characteristics and functional requirements of the system?
Governance
How will the outcomes of this decision be monitored? \ How will compliance with this decision be ensured?
Options Analysis
If applicable, include or link to any trade-off analysis which has been performed to arrive at the decision made in this document.
Key
Optional: Provide visual aids to stakeholders which can help to quickly spot the positive and the negative trade-offs - for example simple traffic-light highlights with positive or negative prefixes.
A green background indicates a good fit, worsening through amber, with red being the worst fit. \ + indicates a positive impacting comment \ - indicates a negative impacting comment
High-Level Overview
How well does each option fit the problem context at a glance?
| Summary | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Ease of Implementation | + Super easy | - Tricky | - Large implementation requiring expert knowledge |
| Timescales | + Very quick | - Fairly slow | - Very slow |
| Strategic Value | - No strategic value, purely tactical | + Slightly improves the customer onboarding experience | + Ideal for the upcoming merger |
Functional Requirements
How well does each potential option fit the desired functional requirements?
| Scenario | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Scenario 1 | |||
| Scenario 2 | |||
| Scenario 3 |
Optional: Add rows / another table to cover known future scenarios.
Non-Functional Requirements
How well does each potential option fit the desired architecture characteristics? Note: ‘Architecture Characteristics’ would be a more appropriate title, but tailor this to familiar language for your business domain.
| Architecture Characteristic | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Scalability | |||
| Performance | |||
| Availability |
Optional: Add in or link to definitions of the architecture characteristics as they pertain to your business / product.