We've built up a decent amount of architecture related content over the last two years and I'm pleased to announce that we're going to take this step further by extending and formalizing what we have already into a book. We're still working through the details, but our goal is to come up with a practical and pragmatic guide to software architecture. There are lots of books about the process side of software architecture, but very few about how you actually undertake the role. That's the gap that our book will be attempting to fill.

We've already put up a page about the book, detailing the sorts of topics it will cover, with the book itself being broken down into the following chapters.

1. What is Architecture?
2. About the Architect Role
3. Non-Functional Requirements
4. Technology Selection
5. Defining and Sharing an Architecture
6. Applying the Architecture
7. Software Architecture in the Real World

We're still thinking about the best way to publish the book, although we're leaning towards structuring the book as a series of essays (like Getting Real by 37signals) and by publishing each of the essays in a number of formats. We have a couple of essays that are nearly ready to go and we'll be looking to build up the book incrementally over the coming weeks and months. If there's anything extra that you'd like to see in the book, please let us know.

Responses[1]

Posted by Simon Brown on 25 April 2008 10:32:53 BST #