I'm going to write-up my notes from the last London user group (Sharing Architectures) later in the week, but I wanted to pose a question to you that I asked at the user group. How big is your software architecture document for your current project/system and what sort of information does it contain? Here's a graph summarising the size responses from the user group (small turnout this month).
As you can see, most people's software architecture documents are ~50 pages and above, which my experience suggests isn't uncommon. How does this compare to yours and does anybody read these documents?
Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.