We have a problem with software architecture. Let’s face it. Find the architecture diagrams of the products you’re working on and answer these questions:
- Did you find it?
- Does everyone in your team know where to find it?
- Is it up-to-date?
- Can you see how this system scales, handles failover, monitors performance, or how it’s secured?
- Can you see how it evolved over time?
- Can you train a new team-member using this diagram?
This is the first micro-post of a series of such as I aim to build a compelling case for fundamentally changing software architecture diagrams.