Software Architecture Monday with Mark Richards is a free bi-weekly software architecture lesson containing a short video about some aspect of software architecture. These lessons contain tips, techniques, and advice to help you in your journey from developer to architect. New lessons will be posted every other Monday. You can see an index and description of each video by going to https://www.developertoarchitect.com/lessons/
Curated by: Software Architecture Monday (221 videos)
In lessons 55, 141, and 157 I talked about Architecture Decision Records (ADRs), and then in lesson 106 I talked about using Architecture Stories as a way of recording architecture refactorings that need to be implemented (like user stories). A viewer asked the question about the relationship between these artifacts, and I thought it would make a great lesson. In this lesson I use an architecture decision about breaking up a service as a way to illustrate the relationship between an ADR and it’s corresponding architecture story (or epic), and how to write an architecture story using the corresponding ADR as a guide. Reference Links: Architecture Decision Records: https://www.developertoarchitect.com/lessons/lesson55.html Managing Architecture Decisions: https://www.developertoarchitect.com/lessons/lesson141.html Incorporating ADRs into Existing Systems: https://www.developertoarchitect.com/lessons/lesson157.html Architecture Stories: https://www.developertoarchitect.com/lessons/lesson106.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