<< 1 >>
Rating: 
Summary: Loved it.
Review: A great book on basic architectural patterns. The authors did a fine job of codifying the essence of architecture you have probably seen in practice (much like Gamma, et al did with design patterns. Great for telling your clueless boss what architecture is.
Rating:
Summary: Loved it.
Review: A great book on basic architectural patterns. The authors did a fine job of codifying the essence of architecture you have probably seen in practice (much like Gamma, et al did with design patterns. Great for telling your clueless boss what architecture is.
Rating: 
Summary: Trivial treatise on software architecture
Review: I had very high hopes for this book, but they were all dashed. The first two chapters Introdution and Architectural Styles were a good overview of Software Architecture in general and some of the major architectural styles such as "pipe and filter" which is used in systems such as Microsoft SQL Server 7.0 DTS. Although it was great to read about the different styles, they were treated trivially--not in-depth. The rest of the book has very basic case studies that may be good for a Software Architecture 101 course in junior college--not Carnegie Mellon. I would have loved to have found some more "real world" case studies with UML (which this book does not address).
Rating: 
Summary: ----
Review: I want this book. I have to read this
Rating:
Summary: ----
Review: I was disappointed in that Sofware Architecture focused more on a few specific approaches to systems design than on an adaptive approach for creating architectures.Although published in 1996, I found much of the material to be based on the past (e.g., a pipe and filter model, shared repository, etc.) moreso than on newer/emerging technologies, such as the role of component-based architectures. I think this is a good text for a traditional summary of the SW industry and some solid practices, but it did not offer the foresight needed by "seasoned" professionals to earn a permanent spot on the bookshelf.
Rating: 
Summary: Software Architecture hits the basics, but is dated
Review: I was disappointed in that Sofware Architecture focused more on a few specific approaches to systems design than on an adaptive approach for creating architectures. Although published in 1996, I found much of the material to be based on the past (e.g., a pipe and filter model, shared repository, etc.) moreso than on newer/emerging technologies, such as the role of component-based architectures. I think this is a good text for a traditional summary of the SW industry and some solid practices, but it did not offer the foresight needed by "seasoned" professionals to earn a permanent spot on the bookshelf.
Rating: 
Summary: Architectural paradigms and research topics
Review: This book is often cited as one of the seminal references on software architecture. The first chapter explains how software architecture fits into the developing field of software engineering. The second chapter illustrates common architectural styles such as pipes and filters, object-oriented organization, event-based invocation, layered systems, repositories, interpreters, process control, distributed process, main program/subroutine, blackboard, and state transition. Case studies are used to compare and contrast the selection of different architectural solutions. The case studies are key word in context, instrumentation software, mobile robotics, cruise control, three vignettes using mixed styles, and shared information systems. The final half of the book is focused on academic research such as quantified design space, formal models, formal specifications, Z notation, connector models, automated case tools, Wright Model of architectural description, and education of software architects.
Rating:
Summary: A unique container of software architecture
Review: This book is very good for novice as well as experienced software professional. One can be easily acquinted with various techniques of Software achitecture for his/her project. It emphasizes all the techniques of S/A very well. I just took this book and went through, I found this book very good. Soon I will purchase this book. This is text book in Universities for post grduation course.
Rating:
Summary: solidating your understanding of the software architecture
Review: This is a book for these who begin to wonder what is the software architecture while they begin to design software, after going through the existing architecture styles, you will understand the bad thing and good thing about one particular style, and you will have the ability to frame your problem in term of these existing styles, if there is a solution existing, you will have a proved solution for your problem, provided you did a careful analysis on your problem. Again, software architecture is a engineering issue, you realy need practice to grasp it.
<< 1 >>
| 
