A brief Pattern Catalog

Patterns include Design Patterns, Analysis Patterns, and Architectural Patterns. Additionally, these patterns can be classified according to their intentional area of application.

Design Pattern Catalog

(Class) Creational Patterns

Factory Method
Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.
Varying: subclass of object that is instantiated.

(Object) Creational Patterns

Abstract Factory
Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Varying: families of product objects.
Separate the construction of a complex object from its representation so that the same construction process can create different representations.
Varying: how a composite object gets created.
Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.
Varying: class of object that is instantiated.
Ensure a class only has one instance, and provide a global point of access to it.
Varying: the sole instance of a class.

(Class) Structural Patterns

Adapter (class)
Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldnt otherwise because of incompatible interfaces.
Varying: interface to an object.

(Object) Structural Patterns

Adapter (object)
Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldnt otherwise because of incompatible interfaces.
Varying: interface to an object.
Decouple an abstraction from its implementation so that the two can vary independently.
Varying: implementation of an object.
Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.
Varying: structure and composition of an object.
Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.
Varying: responsibilities of an object without subclassing.
Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to user.
Varying: interface to a subsytem.
Use sharing to support large numbers of fine-grained objects efficiently.
Varying: storage costs of objects.
Provide a surrogate or placeholder for another object to control access to it.
Varying: how an object is accessed; its location.

(Class) Behavioral Patterns

Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
Varying: grammar and interpretation of a language.
Template Method
Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithms structure.
Varying: steps of an algorithm.

(Object) Behavioral Patterns

Chain of Responsibility
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 objects and pass the request along the chain until an object handles it.
Varying: object that can fulfill a request.
Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
Varying: when and how a request is fulfilled.
Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation
Varying: how an aggregate's elements are accessed, traversed.
Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
Varying: how and which objects interact with each other.
Without violating encapsulation, capture and externalize an objects internal state so that the object can be restored to this state later.
Varying: what private information is stored outside an object, and when.
Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
Varying: number of objects that depend on another object; how the dependent objects stay up to date.
Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
Varying: states of an object.
Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
Varying: an algorithm.
Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operate.
Varying: operations that can be applied to object(s) without changing their class(es).

Additional Design Patterns (not yet classified)

Layer Architecture, Repository, Pipes and Filters, Event Channel, ADT, Module, Framework, Superclass, Blackboard, Master/Slave, Process-Control, Rule-Based Interpreter.

Analysis Pattern Catalog

A consits of a lot of B.
Multiple occurrences B of a type A.
A physically consits of A1, and A2.
A may consist of multiple As.
A coordinator is a resolved n-ary association class.
A plays multiple roles with respect to B.
Changing Roles
A plays different roles with respect to B at different times.
Document multiple facts that were true of A at different times.
Multiple A constitute a single group at the same time.
History of a Group
Multiple A constitute different groups at different times.

Design Pattern Categories