Meeting the needs of your business from a distance

Common Software Redesign Causes and Design Patterns to Help Avoid Them

by Mark Shiffer 11/20/2007 8:56:00 AM

This is paraphrased/summarized from the classic "Design Patterns: Elements of Reusable Object-Oriented Software" by Gamma, Helm, Johnson and Vlissides.

1. Creating an object by specifying a class explicitly: Abstract Factory, Factory Method, Prototype

2. Dependence on specific operations: Chain of Responsibility, Command

3. Dependence on hardware or software platform: Abstract Factory, Bridge

4. Dependence on object representations or implementations: Abstract Factory, Bridge, Memento, Proxy

5. Algorithmic dependencies: Builder, Iterator, Strategy, Template Method, Visitor

6. Tight coupling: Abstract Factory, Bridge, Chain of Responsibility, Command, Facade, Mediator, Observer

7. Extending functionality by subclassing: Bridge, Chain of Responsibility, Composite, Decorator, Observer, Strategy

8. Inability to alter classes conveniently: Adapter, Decorator, Visitor

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

Research

Related posts

Add comment


(Will show your Gravatar icon)  

  Country flag





Live preview

July 9. 2008 00:18

About the author

Name of author Mark Shiffer
CEO & CIO of MS Consulting

E-mail me Send mail

Calendar

<<  July 2008  >>
MoTuWeThFrSaSu
30123456
78910111213
14151617181920
21222324252627
28293031123
45678910

View posts in large calendar

Pages

    Recent posts

    Recent comments

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

    © Copyright 2008

    Sign in

    Copyright © 2001-2008 MS Consulting, Inc. All Rights Reserved.