Skip to content

Latest commit

 

History

History
66 lines (54 loc) · 4.08 KB

0001-architectural-decision-records.md

File metadata and controls

66 lines (54 loc) · 4.08 KB

ADR-0001 - Architectural Decision Records

  • Status: accepted
  • Dates: proposed - 2020-10-27
  • Authors: Damir Murat (damir.murat.git at gmail.com)
  • Reviewers: None

Context

We want a light way means of tracking and describing architecturally significant decisions made during this project. Selected methodology should include appropriate templates and possibly other tools to help with documentation consistency.

Architectural Context

  • System (klokwrk-project)

Decision

We will use the architecture decision log expressed as a time-ordered collection of Architecture Decision Records (ADRs). Architecture decision log is nothing more than a simple index of all available ADRs.

We will use custom ADR template. It includes parts of following "standard" ADR templates:

Consequences

Positive

  • ADRs provide a way for communicating, collaborating, and documenting architecturally significant decisions.
  • Writing ADRs requires conscious thinking and light elaboration of significant decisions, which leads to better decisions.
  • The provided architecture decision log helps with maintaining and onboarding.

Negative

  • Writing ADRs takes time. As we progress and gain experience, time requirements should shrink.
  • Using custom template might cause problems with available ADR tools. However, we don't consider tooling support as important requirement.

Neutral

  • Writing ADRs requires some time to get used to, and have some (minimal) learning curve.

Considered Options

  • Not documenting critical decisions.
  • Using more elaborated process, for example, using RFC documents and process as proposed by Patrik Kua in CROZ internal workshop.
    • We do not want any overhead at this point, so more light way approach is preferable.

References

ADR Methodology

ADR Examples

ADR Template Examples