Comments on: Software Architecture in Practice (2nd Edition)

By: M. Sharperson

M. Sharperson — Wed, 17 Mar 2010 09:40:54 +0000

This text is chock full of “Case Studies” in Architectural design & development methods, but surpringinly sparse in specifics. The authors’ take an approach that is almost entirely qualitative; I was hoping to see a more analytical set of methods for analysing architectures, but found little.

Rating: 2 / 5

By: M. P. Williams

M. P. Williams — Wed, 17 Mar 2010 08:29:31 +0000

I was so taken aback by the comments on this volume that I could not resist a retort. First, SEI transformation methodologies are abstract by intent. They are not how-to methodologies or roadmaps for composing class structures, web sites, or a coding guideline standard. The ATAM is immensely valuable for collecting and rating architectural drivers from stakeholders using a very novel approach to tradeoffs. We actually augmented the process with Force-field analysis templates to speed up the tradeoff process. Also, OAR is designed as a guideline to harvesting and rehabilitating pre-existing system components not for a detailed analysis of a systems component code-base. Again, this is not a coding guide for those of us who are new to the architectural profession and are thinking in code-modelling terminology. Last, (but of greatest concern), is the use of SEI transformation methodologies for plotting logical and physical design. They are not intended to be used for this level of design work. (One might compare this to the misanthropic notion of using BPMN to design a network topology). Other than possibly CBAM, these are also not cost modelling methodologies. Comparing COCOMO II to CBAM is paramount to comparing an abacus to an accounting algorithm for future value. Sorry if I stepped on any toes…off the soapbox.
Rating: 5 / 5

By: Stefan

Stefan — Wed, 17 Mar 2010 06:45:29 +0000

Contrary to the title, I found the book more on the theoretical side. Lots of classifications with questionable practical value. The examples are high-level ending up with more classifications. Same observation about the simplistic figures.

Chapter 13-The World Wide Web gives an introduction of the initial Web requirements, while Chapter 16-J2EE/EJB explains general ideas about EJB. My benchmark for an “solid” book, with somehow related topic, would be “Design Patterns” by Gamma,Helm,Johnson,Vlissides.
Rating: 2 / 5

By: simplesoul

simplesoul — Wed, 17 Mar 2010 04:40:00 +0000

This book is great to gain theoritical knowledge about software architecture, but it lacks practical insights. May be it’s my specific problem, because I was trying to find a good book on architecture of web applications, which this book does not provide.
Rating: 3 / 5

By: Hamed Sepahani

Hamed Sepahani — Wed, 17 Mar 2010 02:34:58 +0000

I received this book in new conditon super fast !!

I’m always satisfied with amazon.com purchases.
Rating: 5 / 5