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 lives in Jersey (the largest of the Channel Islands) and works as an independent consultant, helping teams to build better software. His client list spans over 20 countries and includes organisations ranging from small technology startups through to global household names. Simon is an award-winning speaker and the author of Software Architecture for Developers - a developer-friendly guide to software architecture, technical leadership and the balance with agility. He still codes too. You can tweet Simon at @simonbrown.