Architectural Decision Records
An architectural decision (AD) is a software design choice that addresses a significant requirement. An architectural decision record (ADR) is a way to track an AD, such as by writing notes, or logging information. An architecturally significant requirement (ASR) is a requirement that has a measurable effect on a software system’s architecture. All these are within the topic of architectural knowledge management (AKM). source
The aim of the GitHub adr organization is to (i) strenghten the tooling around ADRs and to (ii) provide provide pointers to all avaiable public knowledge in the context of ADRs.
We currently focus on the Sustainable Architectural Decisions by Zdun et al., but are open to other formats of ADRs as shown at https://github.com/joelparkerhenderson/architecture_decision_record.
We offer one tool for sustainable ADs: Embedded Architectural Decisions, which shows how ADRs can be embedded in Java Code.
- Existing Architectural Decision Records
- Overview: Architectural Decision Records
- Overview: Zimmermann et al.: Architectural Decision Guidance Across Projects - Problem Space Modeling, Decision Backlog Management and Cloud Computing Knowledge. WICSA 2015: 85-94. Author’s copy available at ADMentor.
- DecisionCapture - Templates for agile projects. example.
- Sustainable Architectural Decisions