This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
This boks looks to me like a summary of best practices with Software Architecture. Does this follow any methodology? Does it simply state that we follow the well known design patterns? Architecting what sort of applications os covered in the book?
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
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).