Skip to end of banner
Go to start of banner

Architecture Decision Record

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

  • Documents a decision that addresses a functional or non functional requirement that is architecturally significant
  • An Architecturally Significant Requirement is a requirement that has a measurable effect on a software system’s architecture and quality.
  • Collection of ADR is referred as ADL (Architecture Decision Log)
  • Solution to a problem can start as an RFC to facilitate discussion and collaboration within the community members. The outcome of the RFC must be recorded as an ADR
  • ADR can also be used to document patterns/standards that forms naturally. Patterns can be identified when doing code reviews
  • Status
    • DRAFT
    • ACCEPTED
    • SUPERSEDED by ADR-xxx
    • OBSOLETE
  • Add label to confluence pages that has an ADR




Resources

https://github.com/npryce/adr-tools

Questions

  • Is there any value in maintaining a decision log at the repo level ? Won't be an ADR. 
  • Can we categorize ADRs? DB, Frontend, Spring, Java, Python, CI/CD, Security, Performance
  • No labels