This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned on Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series.
We learn how to code and we build some cool applications, and then we learn about architecture and how to make the application maintainable for several years…
However when we need to explain to someone else (new developer, product owner, investor, …) how the application works, we need something more… we need documentation.
But what documentation options do we have that can express the whole application building blocks and how it works?!
In this post I’m going to write about:
- UML
- 4+1 Architectural view model
- Architecture Decision Records
- The C4 Model
- Dependency diagrams
- Application Map
