CS307_Test2_DesignUMLs

The flashcards below were created by user rinyu on FreezingBlue Flashcards.

  1. Define a family of algorithms, encapsulate each one, and make them interchangeable.

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

    Observer
    Image Upload
  3. Attach additional responsibilities to an object dynamically. [This pattern] provide a flexible alternative to subclassing for extending functionality.

    Decorator
    Image Upload
  4. Define an interface for creating an object, but let subclasses decide which class to instantiate. [This pattern] lets a class defer instantiation to subclasses.

    Factory Method
    Image Upload
  5. Provide an interface for creating families of related or dependent objects without specifying their concrete classes.

    Abstract Factory
    Image Upload
  6. Ensure a class only has one instance, and provide a global point of access to it.

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

    Command
    Image Upload
  8. Convert the interface of a class into another interface clients expect. [This pattern] lets classes work together that couldn’t otherwise because of incompatible interfaces.

    Adapter
    Image Upload
  9. Provide a unified interface to a set of interfaces in a subsystem. [This pattern] defines a higher-level interface that makes the subsystem easier to use.

    Façade
    Image Upload
  10. Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. [This pattern] lets subclasses redefine certain steps of an algorithm without changing the algorithm’s structure.

    Template Method
    Image Upload
  11. Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.

    Iterator
    Image Upload
  12. Compose objects into tree structures to represent part-whole hierarchies. [This pattern] lets clients treat individual objects and compositions of objects uniformly.

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

    State
    Image Upload
  14. Provide a surrogate or placeholder for another object to control access to it.

    Proxy
    Image Upload
Author:
rinyu
ID:
109611
Card Set:
CS307_Test2_DesignUMLs
Updated:
2011-10-17 17:56:54
Tags:
CS307 Test2 Design UMLs
Folders:

Description:
The Design UMLs for Test #2 in CS307.
Show Answers: