Book
Design Patterns
Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides
Summary
Design Patterns catalogs twenty-three patterns that recur across object-oriented software design, recording each one and compiling them into a structured reference. Naming and defining the patterns gives designers a shared vocabulary for discussing recurring design problems and their solutions precisely. The Japanese revised edition adds a CD-ROM carrying a browsable digital version of the catalog, plus Java sample code not present in the original edition.
Target Readers
- Engineers who have used a design-patterns primer and now want the original definitions of intent, applicability, and consequences for each pattern
- Architects who need precise, shared vocabulary for creational, structural, and behavioral design problems when discussing a design with a team
- Engineers who need a structured reference to look a pattern up by name while reading or reviewing code that already applies it
Tags
Colophon
- Publisher
- SB Creative
- ISBN
- 978-4797311129
- Published
- Oct 1999
- List price
- ¥5,280incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
Head First Design Patterns
Building Extensible and Maintainable Object-Oriented Software
Eric Freeman, Elisabeth Robson
Reason: After grasping patterns intuitively through illustrations and examples, you solidify the vocabulary with the original text, where intent, applicability, and consequences are rigorously defined. The Gang of Four codifies patterns into a shared design language that grounds discussion.
Next Books
- Related
Patterns of Enterprise Application Architecture
Martin Fowler
Reason: After learning general-purpose object patterns, you advance to patterns that address enterprise-specific contexts—layering, persistence, and distribution. Fowler's PoEAA supplies that vocabulary, such as Repository and Domain Model.
- Related
Clean Architecture
A Craftsman's Guide to Software Structure and Design
Robert C. Martin
Reason: After acquiring a vocabulary of class- and object-level patterns, you widen your view to governing the direction of dependencies and boundaries across the whole system. Clean Architecture pushes details outward and keeps business rules at the center.