Software Architecture: Perspectives on an Emerging Discipline

by Mary Shaw and David Garlan

Book Overview

Good software developers often adopt one or several architectural patterns as strategies for system organization. But, although they use these patterns purposefully, they often use them informally and... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0131829572
• ISBN13: 9780131829572
• Release Date: April 1996
• Publisher: Pearson
• Length: 264 Pages
• Weight: 0.95 lbs.
• Dimensions: 0.6" x 6.9" x 9.4"

Customer Reviews

Founding text of SW architecture studies

This text is arguably the grandfather of many books that now address software architecture. And, as so sadly happens in the grandfather's generation, it shows some signs of senility. The primary authors wrote and invited studies in a number of useful formats. After an introduction, the second chapter lays out a few basic styles of software architecture. The next two chapter examine case studies and common examples. The next chapter (number 5) includes distinctive material: the notion of a design space with clear, orthogonal axes, and with a utility function that applies to each point in that space. They don't make the mistake of taking their quantitation too seriously. The numbers used in the analyses are openly acknowledged to have no physical meaning. Instead, the authors lay out the factors of a subjective analysis in a clear way, creating a rational framework for holding admittedly irrational discussions of "better" and "worse." I applaud this effort. Too many analyses apply no formal reasoning at all and too many mistake numbers for knowledge - this middle way is worth study and adaptation. Discussion becomes increasingly concrete in the next chapters, not always with good effect. Formal reasoning about programs has been around since the 1970s, in my experience. It's never caught on for about the same reason that quantum mechanics never caught on in designing skyscrapers. Yes, it addresses all the basic phenomena. Even so, very few can wield it competently, and never at the scale of significant industrial constructions. My most serious objections relate entirely to the book's age. It predates wide acceptance of the UML notations for reasoning about systems, so its many different box-and-arrow diagrams need to be learned from the ground up, separately for each diagram. Ch.7, "Linguistic Issues," has been overtaken by commercial languages like C# and Java, and was behind the cutting edge even when it was written. Static configuration and heterogeneity (p.158) are no longer the dealbreakers they were in the link-and-load world (though I admit that world still exists). Interface abstractions have moved way past dot-h files and into the development environment - ideas floating around the Ada world and elsewhere since the 1980s. Even their way-out-there discussion of "implicit invocation" (p.172) could credibly be subsumed under today's aspect oriented programming. And, because they skip the idioms of the Patterns community, the authors lack good ways to unify and contrast their studies of architectural basics. I do not fault a book for being a product of its time, and this one is a remarkable product of a time gone by. I do evaluate a book according to its relevance to practitioners of the moment, and this book's moment has largely passed. It offers good service to people exploring basic issues in developing large systems, but says little to to poor slob meeting the next deadline, or the deadline after. //wiredweird

Loved it.

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.

solidating your understanding of the software architecture

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.

A unique container of software architecture

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.