- Prime Student members get an extra 10% off this product Here's how (terms and conditions apply)
Pattern-Oriented Software Architecture Volume 1: A System of Patterns Hardcover – 12 Jul 1996
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Special offers and product promotions
Frequently bought together
Customers who bought this item also bought
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Would you like to tell us about a lower price?
If you are a seller for this product, would you like to suggest updates through seller support?
The GoF book concentrates on design-level patterns, whereas out patterns span several levels of abstraction... from high-level architectural patterns through design patterns to low-level idioms' writes Beushcmann and his four co-authors from Siemens of Germany about Pattern-oriented software architecture. An example of an architectural pattern is the mocrokernal which 'separates a minimal r-specific parts'. They (prophetically) illustrate with a fictitious operating system named - Hydra! For design patterns they cite (among others) the master-slave pattern that supports fault-tolerance, parallel computation and computational accuracy. Idioms are 'low-level patterns specific to a programming language'.
Two alternative versions of a string copy function, written in C are compared: one by a devotee of Kernighan & Ritchie's terse style takes three lines and includes masterpieces of compaction such as (*d++=*s++); while the other by a Pascal enthusiast takes eight lines but is more readable. There is plenty of discussion and explanation and two interesting closing chapters. One describes the leading figures in the 'Pattern Community', many of them the authors reviewed here, plus Ward Cunningham and Kent Beck who first translated Alexander's ideas into software. The other asks where patterns are heading, for example a new area is organisational structures to support software development, such as Architect Controls Product which ensures team output is elegant and cohesive, not shapeless and nondescript. Other shadows in the crystal ball are the use of repositories and indexing (this has, inevitably, given birth to a new creature; the pattlet) and the development of specific pattern languages. -- Unix & NT News, January 99
From the Back Cover
Pattern – Oriented Software Architecture A System of Patterns Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal of Siemens AG, Germany Pattern–oriented software architecture is a new approach to software development. This book represents the progression and evolution of the pattern approach into a system of patterns capable of describing and documenting large–scale applications. A pattern system provides, on one level, a pool of proven solutions to many recurring design problems. On another it shows how to combine individual patterns into heterogeneous structures and as such it can be used to facilitate a constructive development of software systems. Uniquely, the patterns that are presented in this book span several levels of abstraction, from high–level architectural patterns and medium–level design patterns to low–level idioms. The intention of, and motivation for, this book is to support both novices and experts in software development. Novices will gain from the experience inherent in pattern descriptions and experts will hopefully make use of, add to, extend and modify patterns to tailor them to their own needs. None of the pattern descriptions are cast in stone and, just as they are borne from experience, it is expected that further use will feed in and refine individual patterns and produce an evolving system of patterns. Visit our Web Page http://www.wiley.com/compbooks/
What other items do customers buy after viewing this item?
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
I would suggest that reading Design Patterns first is a good introduction to the field of patterns. After that, read this book to see the power of patterns. The explanations of layers (eg ISO/OSI), broker systems (eg CORBA), and MVC systems (eg most spreadsheets) as generic systems are absolutely second to none.
Most helpful customer reviews on Amazon.com
This book is full of new patterns, and fortunately they are good ones: Command, Broker, Layers and worth the price of the book in itself Presentation-Abstraction-Controller.
PAC can be seen as a generalization and extension of Model/View/Controller. The Abstraction is the domain-specific part of the architecture, effectively the Model. The Presentation exposes the Model in some interesting way, either as a user-interface in which case it is a View, or as an API, in which case the Presentation becomes a new Abstraction used by the next level up. The Controller is left with the job of coordinating the Presentation and the Model. The key to the pattern is that PAC agents can be built up into layers with the Presentation API of each lower agent creating a higher abstraction for the next level. Thus PAC becomes MVC for all or your architecture, not just the UI.
The book goes into this at length and adds useful discussion of MVC. Highly recommended.
If you are new to patterns, I suggest that you first read this book and refer to "Design Patterns" when needed.
In "Pattern-Oriented Software Architecture", there are some chapters on pattern and software architecture concepts, but most of the book is dedicated to describing architectural and design patterns (there are a few pages on idioms). Some of the architectural patterns are well known: layers, pipes, filters, broker and microkernel.
The code is clear and written mainly in C++. The notations used are easy to understand (OMT notation is addopted for the object models and an adaptation of Message Sequence Charts to object interations).
The production (cover, paper, etc) is excellent.