posted 10 years ago
Good question, Joe, and what might surprise you is that the book isn't about architecting any specific type of application and it doesn't talk about technology all that much. It's really about what I believe to be the minimum set of methodology independent, lightweight software architecture practices that pretty much every software project should consider. This includes ensuring that you understand what the significant driving forces are on your architecture, doing "just enough" up front design, communicating the architecture through a simple set of sketches and ensuring that you look after any high priority risks (to prevent your project being cancelled or you being fired).