Use Markdown Architectural Decision Records
Should we record the architectural decisions made in this project? And if we do, how to structure these recordings?
Considered Alternatives
- MADR - Markdown Architectural Decision Records
- Michael Nygard's template - The first incarnation of the term “ADR”. Maintainable by adr-tools.
- Sustainable Architectural Decisions - The Y-Statements
- DecisionRecord - Agile records by @schubmat
- Other templates listed at https://github.com/joelparkerhenderson/architecture_decision_record
- No records
Decision Outcome
- Chosen Alternative: MADR
- Implicit assumptions should be made explicit. Design documentation is important to enable people understanding the decisions later on. See also A rational design process: How and why to fake it.
- The MADR template is lean and fits our development style.