Design Patterns: Elements of Reusable Object-Oriented Software
Capturing a wealth of experience about the design of object-oriented software, four top-notch designers present a catalog of simple and succinct solutions to commonly occurring design problems. Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves.
The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently.
Each pattern describes the circumstances in which it is applicable, when it can be applied in view of other design constraints, and the consequences and trade-offs of using the pattern within a larger design. All patterns are compiled from real systems and are based on real-world examples. Each pattern also includes code that demonstrates how it may be implemented in object-oriented programming languages like C++ or Smalltalk.
Review By: Dmitri Ilkaev
12/16/2005"Design Patterns" is a classic that describes simple and effective solutions to common problems in object-oriented software design. The book, written in a catalog format, provides examples of how design patterns can improve the software design, together with reusability and flexibility of code. The authors describe the intent of the pattern, motivation, applicability, structure, participants, collaborations, consequences, and implementation considerations. They provide detailed sample code, known users of that pattern, and a list of related patterns. Authors Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides--frequently referred to as "The Gang of Four"--separate these patterns into creational, structural, and behavioral categories.
The first two chapters of this book introduce the pattern-based design world, while the rest present a catalog of design patterns. "Design Patterns" is most helpful for the skilled software developer or architect, especially on relatively large projects. Multiple diagrams--most UML based--make the design concept for a specific, easy-to-understand pattern, and every pattern description is accompanied by code samples in C++ or Smalltalk.
The author uses a common vocabulary, which if implemented, encourages effective communication with peers in the design and development field. This book creates a pattern-based mindset, which, once adopted, stays with a developer forever. The authors set the groundwork for pattern-based design, making this book a "must have" book on a developer’s desk.
I recommend this book to experienced developers or architects who need to look up specific cases and patterns related to their design challenges, yet the less-experienced developer should also find this book helpful because it sets a pattern-based direction and can be used as a guidebook.