Architecture Decision Record[000] Title
Gie ilka ADR a nummer for easy reference an catalogin
NOTE: Aw italicised text gies hints an sud be taen awa for production
Status - DRAFT / ACTIVE / DEPRECATED by [000] / SUPERSEDES [000]
Context
Briefly describe the problem(s) that this ADR intends tae address, an why the problems exist.
Decided Approach
Detail the architecturally significant decisioun that haes been / will be made an describe hoo it addresses the problems outlined in the Context section.
Consequences
Whit is the impact o this decisioun on the architectur characteristics an functional requirements o the system?
Governance
Hoo will the outcomes o this decisioun be monitored?
Hoo will compliance wi this decisioun be ensured?
Options Analysis
If applicable, include or link tae onie trade-off analysis which haes been performed tae arrive at the decisioun made in this document.
Key
Optional: Provide visual aids tae stakeholders which can help tae quickly spot the positive an the negative trade-offs - for example simple traffic-licht highlichts wi positive or negative prefixes.
A green background indicates a guid fit, worsenin throu amber, wi red bein the warst fit.
+ indicates a positive impactin comment
- indicates a negative impactin comment
High-Level Overview
Hoo weel daes each option fit the problem context at a glance?
| Summary | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Ease o Implementation | + Dead easy | - Tricky | - Muckle implementation requirin expert knowledge |
| Timescales | + Unco quick | - Gey slaw | - Unco slaw |
| Strategic Value | - Nae strategic value, purely tactical | + Slichtly improves the customer onboardin experience | + Ideal for the upcomin merger |
Functional Requirements
Hoo weel daes each potential option fit the desired functional requirements?
| Scenario | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Scenario 1 | |||
| Scenario 2 | |||
| Scenario 3 |
Optional: Add rows / anither table tae cover kent future scenarios.
Non-Functional Requirements
Hoo weel daes each potential option fit the desired architectur characteristics? Note: ‘Architecture Characteristics’ wud be a mair appropriate title, but tailor this tae familiar leid for yer business domain.
| Architectur Characteristic | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Scalability | |||
| Performance | |||
| Availability |
Optional: Add in or link tae definitions o the architectur characteristics as they pertain tae yer business / product.