Se 350 - Design Patterns And Concepts

Front 1

Simple Factory

Back 1

--"static" class with 1 or more builder methods

--builder methods: accept parameters, makes decision, creates an object and returns

Front 2

Abstraction

Back 2

--simplify

--well named, coherent, minimal, complete

Front 3

Separation

Back 3

separating interface from implementation

interface: visible, external, must be understood to use the software

implementation: hidden, internal

Front 4

Encapsulation

Back 4

"keeping all the stuff that works together in the same spot"

Front 5

Information Hiding

Back 5

Hiding details by only publicly exposing methods that are unlikely to change and keeping the rest private

Front 6

Inheritance

Back 6

building a new class based on an old one

Front 7

Polymorphism

Back 7

using the same code with different classes of data

ie:

for (vehicle v : myVehicles)

v.move();

Front 8

Composition

Back 8

an organized collection of objects interactive to achieve a coherent, common behavior

Front 9

Composition:

association

Back 9

a parts-whole relationship in which the "whole" is defined by the "parts" and the relationships among the parts.

Front 10

Composition:

aggregation

Back 10

a composition in which the "whole" subsumes and conceals its constituent "parts"

hiding parts of the composition

Front 11

Interface

Back 11

a named collection of method definitions without implementations

a type; defines methods. never implements; a class can implement multiple interfaces

Front 12

Interface Polymorphism

Back 12

Multiple classes may implement the same interface and a single class may implement one or more interfaces

Define how a class should respond

Front 13

Abstract Class vs Interface

Back 13

an abstract class is a class that cannot be instantiated but must be inherited from. an abstract class may be fully implemented, but is more usually partially implemented.

an interface is a totally abstract set of members that can be thought of as defining a contract for conduct. implementation is left completely to developer.

Front 14

Delegation

Back 14

a relationship between objects where one object forwards certain method calls to another objectD

Front 15

Design Pattern:

Strategy

Back 15

Lets you build software as a loosely coupled collection of interchangeable parts

-define family of algorithms

-encapsulate each one

-make them interchangeable

recognized by:

may replace multiple if statements, may be a group of impl classes

Front 16

Factory

Back 16

recognized by:

if statements with .equals, then return a certain kind of object

Front 17

Abstract Factory

Back 17

defines a technique where we create a set of individual factories with a common theme

Front 18

Factory Method

Back 18

defines a technique where we define an abstract method for creating objects in our simple factory, and then create subclasses that override that method to specify the actual types of objects that will be created

recognized by:

extends rather than implements

abstract method in the original factory class

Front 19

Facade

Back 19

specifies the creation of a class with a unified interface to a set of interfaces

makes the subsystem easy to use, decouples classes

recognized by:

often singletons, using a "manager" class

Front 20

Singleton

Back 20

restricts instantation of a class to one object

recognized by:

private constructor

final class

getInstance method

Front 21

Data Transfer Object

Back 21

only contains data, a constructor, no methods, holds data

Recognized by:

lack of methods

public data