Architecture Decision Record[000] Title
Give each ADR number so e go easy to reference and catalog
NOTE: All di italicised text na hints and dem suppose remove dem for production
Status - DRAFT / ACTIVE / DEPRECATED by [000] / SUPERSEDES [000]
Context
Describe briefly di problem(s) wey dis ADR wan address, and why di problems dey exist.
Approach Wey We Decide
Detail di architecturally significant decision wey dem don make / go make and describe how e address di problems wey dem outline for di Context section.
Consequences
Wetin be di impact of dis decision on di architecture characteristics and functional requirements of di system?
Governance
How dem go monitor di outcomes of dis decision?
How dem go ensure compliance with dis decision?
Options Analysis
If e apply, include or link to any trade-off analysis wey dem perform to reach di decision wey dem make for dis document.
Key
Optional: Give stakeholders visual aids wey fit help dem spot quick di positive and di negative trade-offs - for example simple traffic-light highlights with positive or negative prefixes.
A green background mean good fit, wey dey get worse through amber, with red as di worst fit.
+ mean comment wey get positive impact
- mean comment wey get negative impact
High-Level Overview
How well each option fit di problem context for one look?
| Summary | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Ease of Implementation | + Super easy | - E tricky | - Big implementation wey need expert knowledge |
| Timescales | + E quick well well | - E slow small | - E slow well well |
| Strategic Value | - No strategic value, na just tactical | + E improve di customer onboarding experience small | + E perfect for di merger wey dey come |
Functional Requirements
How well each potential option fit di functional requirements wey we want?
| Scenario | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Scenario 1 | |||
| Scenario 2 | |||
| Scenario 3 |
Optional: Add rows / another table to cover future scenarios wey dem don know.
Non-Functional Requirements
How well each potential option fit di architecture characteristics wey we want? Note: ‘Architecture Characteristics’ go be more appropriate title, but tailor dis to language wey familiar for your business domain.
| Architecture Characteristic | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Scalability | |||
| Performance | |||
| Availability |
Optional: Add or link to definitions of di architecture characteristics as dem relate to your business / product.