Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.


Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove ads
Don't know
Know
remaining cards
Save
0:01
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
Retries:
restart all cards




share
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

OO Patterns

Object Oriented Software Patterns (from Gamma, Helm Johnson, Vlissides)

NameDescription
Abstract Factory Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Builder Separate the construction of a complex object from its representation so that the same construction process can create different representations.
Factory Method Define an interface for creating an object, but let subclasses decide which class to instantiate. Lets a class defer instantiation to subclasses.
Prototype Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.
Singleton Ensure a class only has one instance, and provide a global point of access to it.
Adapter Convert the interface of a class into another interface clients expect. Lets classes work together that couldn't otherwise because of incompatible interfaces.
Bridge Decouple an abstration from its implementation so that the two can very independently.
Composite Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.
Decorator Attach additional responsibilities to an object dynamically. Provides a flexible alternative to subclassing for extending functionality.
Facade Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.
Flyweight Use sharing to support large numbers of fine-grained objects efficiently.
Proxy Provide a surrogate or placeholder for another object to control access to it.
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.
Command Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
Interpreter Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
Iterator Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.
Mediator Define an object that encapsulates how a set of objects interact. Promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
Memento Without violating encapsulation, capture and externalize an objects's internal state so that the object can be restored to this state later.
Observer Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
State Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
Strategy Define a family of algorithms, encapsulate each one, and make them interchangeable. Lets the algorithm vary independently from clients that use it.
Template Method Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.
Visitor Represent an operation to be performed on the elments of an object structure. Lets you define a new operation without changing the classes of the elements on which it operates.
Created by: JohnW