• Introduction
• ADR example templates
• How to start using ADRs
• How to start using ADRs with tools
• How to start using ADRs with git
• ADR file name conventions
• Contributing
• Sources

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).

The goal of this document is to provide a fast overview of ADRs, how to create them, and where to look for more information.

ADR example templates that we have collected on the net:

• ADR template by Michael Nygard (simple and popular)
• ADR template by Jeff Tyree and Art Akerman (more sophisticated)
• ADR template for Alexandrian pattern (simple with context specifics)
• ADR template for business case (more MBA-oriented, with costs, SWOT, and more opinions)
• ADR template using Planguage (more quality assurance oriented)

To start using ADRs, talk with your teammates about these areas.

1. Decision identification

   • How urgent and how important is the AD?
   • Does it have to be made now, or can it wait until more is known?
   • Both personal and collective experience, as well as recognized design methods and practices, can assist with decision identification.
   • Ideally maintain a decision todo list that complements the product todo list.

2. Decision making

   • A number of decision making technqiues exists, both general ones and software and software architecture specific ones, for instance, dialogue mapping.
   • Group decision making is an active research topic.

3. Decision documentation

   • Many templates and tools for decisison capturing exist.
   • See agile communities, e.g. M. Nygard's ADRs.
   • See traditional software engineering and architecture design processes, e.g. table layouts suggested by IBM UMF and by Tyree and Akerman from CapitalOne.

4. Decision enactment and enforcement

   • ADs are used in software design; hence they have to be communicated to, and accepted by, the stakeholders of the system that fund, deveop, and operate it.
   • Architecturally evident coding styles and code reviews that focus on architectural concerns and decisions are two related practices.
   • ADs also have to be (re-)considered when modernizing a software sytem in software evolution.

5. Decision sharing (optional)

   • Many ADs recur across projects.
   • Hence, experiences with past decisions, both good and bad, can be valuable reusable assets when employing an explicit knowledge management strategy.

You can start using ADRs with tools any way you want.

For example:

• If you like using Google Drive and online editing, then you can create a Google Doc, or Google Sheet.

• If you like use source code version control, such as git, then you can create a file for each ADR.

• If you like using project planning tools, such as Atlassian Jira, then you can use the tool's planning tracker.

• If you like using wikis, such as MediaWiki, then you can create an ADR wiki.

If you like using git version control, then here's how we like to start using ADRs with git for a typical software project with source code.

1. Create a directory for ADR files.

   mkdir adr

2. For each ADR, create a text file, such as database.txt.

   vi database.txt

3. Write anything you want in the ADR. See the templates in this repo for ideas.

If you choose to create your ADRs using typical text files, then you may want to come up with your own ADR file name convention.

We prefer to use a file name convention that has a specific format.

Examples:

• 2017-01-01 Choose a database.md

• 2017-01-02 Handle more users.md

• 2017-01-03 Improve application security.md

Our file name convention:

• The name has the date as YYYY-MM-DD. This is ISO standard and helps for sorting by date.

• The name has a present tense imperative verb phrase. This helps readability and matches our commit message format.

• The name uses sentence capitalization and spaces. This is helpful for readability.

• The extension is markdown. This can be useful for easy formatting.

Your comments and suggestions are welcome.

You can open a GitHub issue, or create a pull request, or email [email protected].

Introduction:

• Architectural Decision - Wikipedia
• Architecturally significant requirements

Templates:

• Documenting architecture decisions - Michael Nygard
• Template for documenting architecture alternatives and decisions - Stack Overflow

In-depth:

• ADMentor XML project - GitHub
• Architectural Decision Guidance across Projects: Problem Space Modeling, Decision Backlog Management and Cloud Computing Knowledge
• The Decision View's Role in Software Architecture Practice
• Documenting Software Architectures: Views and Beyond
• Architecture Decisions: Demystifying Architecture
• ThoughtWorks Technology Radar: Lightweight Architecture Decision Records

See also:

• REMAP (Representation and Maintenance of Process Knowledge)
• DRL (Decision Representation Language)
• IBIS (Issue-Based Information System)
• QOC (Questions, Options, and Criteria)
• DRL (Decision Representation Language),
• IBM’s e-Business Reference Architecture Framework