Home > Store > Software Development & Management > Object Technology
Design Patterns: Elements of Reusable Object-Oriented Software
- By Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides
- Published Oct 31, 1994 by Addison-Wesley Professional. Part of the Addison-Wesley Professional Computing Series series.
- Copyright 1995
- Dimensions: 7-3/8x9-1/4
- Pages: 416
- Edition: 1st
- Book
- ISBN-10: 0-201-63361-2
- ISBN-13: 978-0-201-63361-0
Register your product to gain access to bonus material or receive a coupon.
Product Author Bios
Dr. Erich Gamma is technical director at the Software Technology Center of Object Technology International in Zurich, Switzerland. Dr. Richard Helm is a member of the Object Technology Practice Group in the IBM Consulting Group in Sydney, Australia. Dr. Ralph Johnson is a faculty member at the University of Illinois at Urbana-Champaign's Computer Science Department.
John Vlissides is a member of the research staff at the IBM T. J. Watson Research Center in Hawthorne, New York. He has practiced object-oriented technology for more than a decade as a designer, implementer, researcher, lecturer, and consultant. In addition to co-authoring Design Patterns: Elements of Reusable Object-Oriented Software, he is co-editor of the book Pattern Languages of Program Design 2 (both from Addison-Wesley). He and the other co-authors of Design Patterns are recipients of the 1998 Dr. Dobb's Journal Excellence in Programming Award.
0201633612AB09122003
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.
0201633612B07092001
Source Code
Download the Source Code for Design Patterns: Elements of Reusable Object-Oriented Software
Related Articles
A Look Back: Why We Wrote Design Patterns: Elements of Reusable Object-Oriented Software
An Interview with John deVadoss on Patterns and Practices at Microsoft
Brian Foote on the 15th Anniversary of Design Patterns
Design Patterns 15 Years Later: An Interview with Erich Gamma, Richard Helm, and Ralph Johnson
Erik M. Buck on the 15th Anniversary of Design Patterns
Gerard Meszaros on the 15th Anniversary of Design Patterns
Grady Booch on Design Patterns, OOP, and Coffee
John Crupi on the 15th Anniversary of Design Patterns
Josh Bloch on the 15th Anniversary of Design Patterns
Linda Rising on the 15th Anniversary of Design Patterns
Marshall Cline on the 15th Anniversary of Design Patterns
Rebecca Wirfs-Brock on the 15th Anniversary of Design Patterns
Russ Olsen on the 15th Anniversary of Design Patterns
Steve Vinoski on the 15th Anniversary of Design Patterns
Thomas Erl on the 15th Anniversary of Design Patterns
William Wake on the 15th Anniversary of Design Patterns
Search Term
Eric gof
|
368 of 387 people found the following review helpful
The best way to really learn object-oriented design,
By A Customer
This review is from: Design Patterns: Elements of Reusable Object-Oriented Software (Hardcover)
This book really changed my way of thinking about object-oriented design. The idea is that when designing a new class hierarchy, though implementation details may differ, you often find yourself using the same kinds of solutions over and over again. Rather than approaching each design task out of context as an individual, isolated problem, the strategy is to study the task and identify the underlying design pattern most likely to be applicable, and follow the class structure outlined by that pattern. It's a "cookbook" school of design that works amazingly well.There are other advantages to this book. It isolates 23 of the most common patterns and presents them in detail. You wouldn't think that 23 patterns would be enough, but once you become adept at recognizing patterns, you'll find that a large fraction of the patterns you use in practice are among these 23. For each pattern, the book carefully presents the intent of the pattern, a motivating example, consequences of... Read more
218 of 228 people found the following review helpful
Must read, but requires some sophistication, By
This review is from: Design Patterns: Elements of Reusable Object-Oriented Software (Hardcover)
As you probably already realize from the large number of reviews, this book is one of the seminal books on patterns in software development. If you are a professional software developer, you must read this. If you are learning to write good software, this is a book that you will need to take on at some point, but I urge some caution.In particular, many of the patterns in this book represent highly distilled wisdom about effective solutions -- distilled so far that, unless you have implemented code that realizes the pattern in question already, you may have trouble absorbing the material. I find that programmers-to-be who dive into this book, often end up talking annoyingly about "applying patterns" without having a real grasp of how these things translate (with some distortion and compromise) into real projects. That being said, an excellent way to bridge the gap is to read this book along with "Pattern Hatching : Design Patterns Applied" by John... Read more
285 of 308 people found the following review helpful
Now that the hype is over..., By Dave O'Hearn (Boston, MA United States) - See all my reviews
This review is from: Design Patterns: Elements of Reusable Object-Oriented Software (Hardcover)
... well, it's over. "Patterns" have not revolutionized the world. Nor does this book need to be "studied" for deep insights.What it seems patterns are actually good for is giving common names to popular solutions to problems, to make them easier to call to mind, and easier to discuss with others. Even this much is overrated. Before the advent of patterns, you could have said "callbacks" and people would have understood. Now you say "the Observer pattern". _Design Patterns_ is none the less valuable, because it is one of those few books that EVERYONE is expected to have read. This is helpful in practice, as you can expect everyone to be familiar with its vocabulary. Few books truly fall into this "required reading" category. The only other that comes to mind is the MIT algorithms text. Many tech pundits claim that every next book is "required reading", and the claim becomes tiring after a while, but this is one of the few that really is. I would not... Read more |
Praise For Design Patterns: Elements of Reusable Object-Oriented Software
Reviews
"This is the famous "Gang of Four" book, covering over 20 of the key design patterns of object-oriented programming. Highly recommended."
"This book is an important contribution to practicing object designers and developers! Have you ever tried to describe an idea that you don't have a precise name for? It can be frustrating. Design Patterns organizes and presents a catalog of proven design idioms for structuring, creating, and manipulating objects. Most importantly, it names these design constructs, allowing teams to share a common vocabulary."
"Design Patterns leaves the debates about code reuse behind and shows the real key to software reuse: reusable design. You'll find yourself applying and reusing these patterns in your own designs in no time."
"...(Design Patterns) makes two important contributions. First, it shows the role that patterns can play in architecting complex systems. Second, it provides a very pragmatic reference to a set of well-engineered patterns that the practicing developer can apply to crafting his or her own specific applications."
"Overall, I think this book (Design Patterns) represents an extremely valuable and unique contribution to the field because it captures a wealth of object-oriented design experience in a compact and reusable form. This book is certainly one that I shall turn to often in search of powerful object-oriented design ideas; after all, that's what reuse is all about, isn't it?"
"Design Patterns (Addison-Wesley), by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, is an amazing string that will guide you through the design maze. This much-anticipated book lives up to its full year of advance buzz. The metaphor (and, believe me, everyone and their dog will be presenting this metaphor to you over the next year) is of an architect's pattern book filled with time-tested, usable designs. The authors have chosen 23 patterns from decades of object-oriented experience. The brilliance of the book lies in the discipline represented by that number...Give a copy of Design Patterns to every good programmer you know who wants to be better. It's Ariadne's string for the labyrinth of design."
"This (Design Patterns) is one of the best written and wonderfully insightful books that I have read in a great long while. Although the idea of design patterns by itself often sounds simplistic - something experienced programmers already do unconsciously and which they tend to pooh-pooh (or at least when I attempt to describe it) - this book establishes the legitimacy of patterns in the best way: not by argument but by example."
Excerpts
Design Patterns: Abstract Factory
Design Patterns: Chain of Responsibility
Table of Contents
Preface.
Foreword.
Guide to Readers.
1. Introduction.
2. A Case Study: Designing a Document Editor.
Design Pattern Catalog.
3. Creational Patterns.
4. Structural Pattern.
5. Behavioral Patterns.
6. Conclusion.
Appendix A: Glossary.
Appendix B: Guide to Notation.
Appendix C: Foundation Classes.
Bibliography.
Index.
Preface
This book isn't an introduction to object-oriented technology or design. Many books already do a good job of that. This book assumes you are reasonably proficient in at least one object-oriented programming language, and you should have some experience in object-oriented design as well. You definitely shouldn't have to rush to the nearest dictionary the moment we mention "types" and"polymorphism," or "interface" as opposed to "implementation" inheritance.
On the other hand, this isn't an advanced technical treatise either. It's a book of design patterns that describes simple and elegant solutions to specific problems in object-oriented software design. Design patterns capture solutions that have developed and evolved over time. Hence they aren't the designs people They reflect untold redesign and recoding as developers have struggled for greater reuse and flexibility in their software.Design patterns capture these solutions in a succinct and easily applied form.
The design patterns require neither unusual language features nor amazing programming tricks with which to astound your friends and managers. All can be implemented in standard object-oriented languages, though they might take a little more work than ad hoc solutions. But the extra effort invariably pays dividends in increased flexibility and reusability.
Once you understand the design patterns and have had an "Aha!" (and not just a "Huh?") experience with them, you won't ever think about object-oriented design in the same way. You'll have insights that can make your own designs more flexible, modular, reusable, and understandable - which is why you're interested in object-oriented technology in the first place, right?
A word of warning and encouragement: Don't worry if you don't understand this book completely on the first reading. We didn't understand it all on the first writing! Remember that this isn't a book to read once and put on a shelf. We hope you'll find yourself referring to it again and again for design insights and for inspiration.
This book has had a long gestation. It has seen four countries, three of its authors' marriages, and the birth of two (unrelated) offspring.Many people have had a part in its development. Special thanks are due Bruce Andersen, Kent Beck, and Andre Weinand for their inspiration and advice. We also thank those who reviewed drafts of the manuscript: Roger Bielefeld, Grady Booch, Tom Cargill, Marshall Cline, Ralph Hyre, Brian Kernighan, Thomas Laliberty, Mark Lorenz, Arthur Riel, Doug Schmidt, Clovis Tondo, Steve Vinoski, and Rebecca Wirfs-Brock. We are also grateful to the team at Addison-Wesley for their help and patience: Kate Habib, Tiffany Moore, Lisa Raffaele, Pradeepa Siva, and John Wait. Special thanks to Carl Kessler, Danny Sabbah, and Mark Wegman at IBM Research for their unflagging support of this work.
Last but certainly not least, we thank everyone on the Internet and points beyond who commented on versions of the patterns, offered encouraging words, and told us that what we were doing was worthwhile. These people include but are not limited to Ran Alexander, Jon Avotins, Steve Berczuk, Julian Berdych, Matthias Bohlen, John Brant, Allan Clarke, Paul Chisholm, Jens Coldewey, Dave Collins, Jim Coplien, Don Dwiggins, Gabriele Elia, Doug Felt, Brian Foote, Denis Fortin, Ward Harold, Hermann Hueni, Nayeem Islam, Bikramjit Kalra, Paul Keefer, Thomas Kofler, Doug Lea, Dan LaLiberte, James Long, Ann Louise Luu, Pundi Madhavan, Brian Marick, Robert Martin, Dave McComb, Carl McConnell, Christine Mingins, Hanspeter Mossenbock, Eric Newton, Marianne Ozcan, Roxsan Payette, Larry Podmolik, George Radin, Sita Ramakrishnan, Russ Ramirez, Dirk Riehle, Bryan Rosenburg, Aamod Sane, Duri Schmidt, Robert Seidl, Xin Shu, and Bill Walker.
We don't consider this collection of design patterns complete and static; it's more a recording of our current thoughts on design. We welcome comments on it, whether criticisms of our examples, references and known uses we've missed, or design patterns we should have included. You can write us care of Addison-Wesley, or send electronic mail to design-patterns@cs.uiuc.edu. You can also obtain softcopy for the code in the Sample Code sections by sending the message "send design pattern source" to design-patterns-source@cs.uiuc.edu.
Mountain View, California - E.G.
Montreal, Quebec - R.H.
Urbana, Illinois - R.J.
Hawthorne, New York - J.V.
August 1994
0201633612P04062001
This book includes free shipping!
This book includes free shipping!
eBook (Watermarked)
$47.99
$38.39
Includes EPUB, MOBI, and PDF
About eBook Formats
This eBook includes the following formats, accessible from your Account page after purchase:
EPUBThe open industry format known for its reflowable content and usability on supported mobile devices.
MOBIThe eBook format compatible with the Amazon Kindle and Amazon Kindle applications.
PDFThe popular standard, used most often with the free Adobe® Reader® software.
This eBook requires no passwords or activation to read. We customize your eBook by discretely watermarking it with your name, making it uniquely yours.
- Request an Instructor or Media review copy.
- Corporate, Academic, and Employee Purchases
- International Buying Options
Get access to thousands of books and training videos about technology, professional development and digital media from more than 40 leading publishers, including Addison-Wesley, Prentice Hall, Cisco Press, IBM Press, O'Reilly Media, Wrox, Apress, and many more. If you continue your subscription after your 30-day trial, you can receive 30% off a monthly subscription to the Safari Library for up to 12 months. That's a total savings of $199.
