Architecture Decision Records (ADRs) are an effective way of documenting a software architecture, providing justification for an architecture decision, and also recording tradeoff analysis. But what if you’ve never done ADRs before? Does it make sense to start using them on an existing system or wait for a new project to start using them? In this lesson I address these questions and show how to go about incorporating ADRs into an existing system.
Reference Links:
Lesson 55: https://www.developertoarchitect.com/lessons/lesson55.html
Lesson 141: https://www.developertoarchitect.com/lessons/lesson141.html
Software Architecture Monday: https://bit.ly/3dadEe3
Fundamentals of Software Architecture: https://amzn.to/3rgFLjY
Software Architecture: The Hard Parts: https://amzn.to/3BjMMF2