/architecture_decision_record

Architecture decision record (ADR) examples for software planning, IT leadership, and template documenation

Architecture Decision Record (ADR)

An architectural decision record (ADR) is a document that captures an important architectural decision made along with its context and consequences.

Contents:

What is an Architecture Decision Record?

An architectural decision record (ADR) is a document that captures an important architectural decision made along with its context and consequences.

An architectural decision (AD) is a software design choice that addresses a significant requirement.

An architecturally significant requirement (ASR) is a requirement that has a measurable effect on a software system’s architecture.

A decision log is the collection of all ADRs created and maintained for a particular project (or organization).

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

ADR example templates that we have collected on the net:

How to start using ADRs

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 techniques 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 decision 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, develop, 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.

The steps above are adopted from the Wikipedia entry on Architectural Decision

How to start using ADRs with tools

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.

How to start using ADRs with git

If you like using git version control, then here is 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 repository for ideas.

  4. Commit the ADR to your git repo

ADR file name conventions

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:

* choose_database.md
* format_timestamps.md
* manage_passwords.md
* handle_exceptions.md

Our file name convention:

* The name has a present tense imperative verb phrase. This helps readability and matches our commit message format.
* The name uses lowercase and underscores (same as this repo). This is a balance of readability and system usability.
* The extension is markdown. This can be useful for easy formatting.

Suggestions for writing good ADRs

  1. Characteristics of a good ADR:

    • Point in Time - Identify when the AD was made
    • Rationality - Explain the reason for making the particular AD
    • Immutable record - The decisions made in a previously published ADR should not be altered
    • Specificity - Each ADR should be about a single AD

  2. Characteristics of good Context in an ADR:

    • Explain your organization's situation and business priorities
    • Include rationale and considerations based on social and skills makeups of your teams

  3. Characteristics of good Consequences in an ADR:

    • Right approach - "We need to start doing X instead of Y"
    • Wrong approach - Do not explain the AD in terms of "Pros" and "Cons" of having made the particular AD

  4. A new ADR may take the place of a previous ADR

    • When an AD is made that replaces or invalidates a previous ADR, a new ADR should be created

Organizations and Projects using ADRs

Contributing

Your comments and suggestions are welcome.

You can open a GitHub issue, or create a pull request, or email joel@joelparkerhenderson.com.

Sources

Introduction:

Templates:

In-depth:

Tools:

Examples:

See also:

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