Chicago Information Technology Architects Group - Design Patterns
Upcoming SlideShare
Loading in...5
×
 

Chicago Information Technology Architects Group - Design Patterns

on

  • 1,292 views

 

Statistics

Views

Total Views
1,292
Views on SlideShare
1,292
Embed Views
0

Actions

Likes
0
Downloads
17
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Chicago Information Technology Architects Group - Design Patterns Chicago Information Technology Architects Group - Design Patterns Presentation Transcript

  • Design Patterns in Java and .NET
    Tim Murphy
    Technical Specialist
    Mike Vogt
    Vice President of Architecture
  • Objective
    Show the usefulness of Design Patterns when developing applications and how they apply no matter what the platform.
  • Agenda
    History of patterns
    What are patterns
    Why are patterns important
    Explore 6 common patterns
    Anti-Patterns
    View slide
  • History Of Patterns
    Gang Of Four
    POSA – Patterns of Software Architecture
    Patterns of Enterprise Application Architecture
    View slide
  • What Are Patterns
    Pattern Name
    Problem
    Solution
    Consequences
  • Why Are Patterns Important
    Common vocabulary
    Repositories of common solutions
  • Factory Method Pattern
    Method for object creation
    Lets subclasses decide which classes to create
  • Decorator Pattern
    Attach additional responsibilities to an object dynamically
    Allows behavior to be added via “wrappers”
    Avoids extensive inheritance hierarchies
    cost()
    Whip
    cost()
    Mocha
    cost()
    DarkRoast
  • Adapter Pattern
    Allows a system to use methods that do not match their interface
  • Visitor Pattern
    A way of separating an algorithm from an object structure it operates on.
    One can add new operations to existing object structures without modifying those structures
    <<interface>>
    CarElement
    + accept(CarElementVisitor v)
    Wheel
    Engine
    Body
    Car
  • Strategy Pattern
    Interchangeable algorithms
  • Composite Pattern
    Allows you to compose objects into tree structures to represent whole-part hierarchies.
    Lets clients treat individual objects and compositions of objects uniformly.
    <<interface>>
    Component
    + operation
    + add(Component c)
    + remove(Component c)
    + getChild(inti)
    Node
    Client
    Leaf
    Leaf
    Leaf
    Composite
    add, remove, getChild, operation
    Leaf
    + operation()
  • Anit-Patterns
    One pattern to rule them all
    Loosey Goosey
  • ResourcesDesign Patterns: Elements of Reusable Object-Oriented Software – Erich Gamma, Richard Helm, Ralph Johnson, and John VlissidesHead First Design Patterns – Eric Freeman and Elisabeth FreemanDesign Patterns In C# - Steven John Metsker
  • Thank You!Blogs –geekswithblogs.net/tmurphyEmail -tmurphy@psclistens.commvogt@psclistens.comTwitter –@twmurph@mvogt99PSC’s websitewww.psclistens.com