Design Pattern

Front 1

Provides an interface for creating families of related or dependent objects without specifying their concrete class

Back 1

Abstract Factory

Front 2

Separate the construction of complex object from its representation so that the same construction process can create different representations

Back 2

Builder

Front 3

Define an interface for creating an object, but let subclasses decide which to instantiate. Lets defer instantiations to subclasses.

Back 3

Factory Method

Front 4

Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.

Back 4

Prototype

Front 5

Ensure a class only has one instance, and provide a global point of access to it.

Back 5

Singleton

Front 6

Convert the interface of a class into another interface clients expect. Lets classes work together that couldn't otherwise because of incompatible interfaces

Back 6

Adapter

Front 7

Decouple an abstraction from its implementation so that the two can vay independently.

Back 7

Bridge

Front 8

Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of object uniformly.

Back 8

Composite

Front 9

Attach additional responsibilities to an object dynamically. Provide a flexible alternative to subclassing for extending functionalities

Back 9

Decorator

Front 10

Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.

Back 10

Facade

Front 11

Use sharing to support large number of fine-grained objects efficiently.

Back 11

Flyweight

Front 12

Provide a surrogate or placeholder for another object to control access to it.

Back 12

Proxy

Front 13

Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving object and pass the request along the chain until an object handles it.

Back 13

Chain of Responsabilities

Front 14

Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.

Back 14

Command

Front 15

Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.

Back 15

Interpreter

Front 16

Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation

Back 16

Iterator

Front 17

Define an object that encapsulate how a set of object interact. It Promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.

Back 17

Mediator

Front 18

Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.

Back 18

Memento

Front 19

Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.

Back 19

Observer

Front 20

Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.

Back 20

State

Front 21

Define a family of algorithms, encapsulate each one, and make them interchangeable. Lets the algorithm vary independently from clients that use it.

Back 21

Strategy

Front 22

Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Let subclasses redefine certain steps of an algorithm without changing the algorithm structure.

Back 22

Template Method

Front 23

Represent an operator to be performed on the elements of an object structure. Lets you define a new operation without changing the classes of the elements on which it operates

Back 23

Visitor