Architecture Decision Records
My reference for this article is this book: Fundamentals of Software Architecture: An Engineering Approach
To summarize, an ADR consists mainly of five entries:
- title
- status: Proposed, Accepted, Superseded (by …)
- context
- decision
- consequences
which is quite simple.
I find that the tools suggested in the book are not very practical: either command line or wiki. It is not difficult to create your own tool to manage this.
It is really important to track the dates and stakeholders to make it usable and to easily find information on the ADRs.
It is therefore necessary to be able to index and categorize the ADRs.