This blog contains information about techno news, hardware, software, games and life style
16 Mar
Product Description
This award-winning book, substantially updated to reflect the latest developments in the field, introduces the concepts and best practices of software architecture–how a software system is structured and how that system’s elements are meant to interact. Distinct from the details of implementation, algorithm, and data representation, an architecture holds the key to achieving system quality, is a reusable asset that can be applied to subsequent systems, and is crucial to a software organization’s business strategy. Drawing on their own extensive experience, the authors cover the essential technical topics for designing, specifying, and validating a system. They also emphasize the importance of the business cont… More >>
Software Architecture in Practice (2nd Edition)
5 Responses for "Software Architecture in Practice (2nd Edition)"
I received this book in new conditon super fast !!
I’m always satisfied with amazon.com purchases.
Rating: 5 / 5
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
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
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
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
Leave a reply