Hi Will, the book is technology agnostic and it's about introducing a minimal set of lightweight software architecture practices rather than designing specific types of applications. This includes doing "just enough" up front design, communicating the resulting architecture using a collection of simple sketches and ensuring that key risks are taken care of. There are some example diagrams and documentation about an open source Java project though.
Will Myers wrote:I want to pick the right tool for the job so is there a framework in the book that would help me do this?
In an abstract, high-level sense, I think the book actually can provide you with a framework that will help you make good technological decisions. As I mentioned in another post, the book makes you think about architecture in a broad, almost philosophical way, seeing the forest for the trees. One section of #sa4d gives you a way to evaluate risks and their importance. Another part gives you a good outline for a Software Guidebook that is very comprehensive and inclusive of many aspects of software development that often get overlooked from focusing too much on specific technologies. Other parts offer more ways to think about architecture and development. Choosing the right tool for a task is only part of the work of a software developer/architect so in the sense that a framework gives you a way to organize your work and decisions, then this book certainly has a number of elements that you can use to do that.
The hard part will be having the patience and diligence to read through, understand, and reflect on what Simon writes and recognize the parts of the book that can be used to form that kind of framework. If this sounds like something that you can do, then definitely get the book (or hope that you win it )