Menu

 

Thoughts on Software Engineering

Design Patterns Course @ Sofia Univeristy

With a few collagues I teach a course in Design Patterns in Sofia University for the summer semester of 2007/2008. We will cover the classical GoF patterns (creational, functional and behavioral) and as well as some additional topics like architectural patterns (like MVC). Our curriculum is based on the classical book “Design Patterns: Elements of Reusable Object-Oriented Software”:

Creational Patterns

  • Abstract Factory groups object factories that have a common theme.
  • Builder constructs complex objects by separating construction and representation.
  • Factory Method creates objects without specifying the exact class to create.
  • Prototype creates objects by cloning an existing object.
  • Singleton restricts object creation for a class to only one instance.

Structural Patterns

  • Adapter allows classes with incompatible interfaces to work together by wrapping its own interface around that of an already existing class.
  • Bridge decouples an abstraction from its implementation so that the two can vary independently.
  • Composite composes one-or-more similar objects so that they can be manipulated as one object.
  • Decorator dynamically adds/overrides behaviour in an existing method of an object.
  • Facade provides a simplified interface to a large body of code.
  • Flyweight reduces the cost of creating and manipulating a large number of similar objects.
  • Proxy provides a placeholder for another object to control access, reduce cost, and reduce complexity.

Behavioral Patterns

  • Chain of responsibility delegates commands to a chain of processing objects.
  • Command creates objects which encapsulate actions and parameters.
  • Interpreter implements a specialized language.
  • Iterator accesses the elements of an object sequentially without exposing its underlying representation.
  • Mediator allows loose coupling between classes by being the only class that has detailed knowledge of their methods.
  • Memento provides the ability to restore an object to its previous state (undo).
  • Observer is a publish/subscribe pattern which allows a number of observer objects to see an event.
  • State allows an object to alter its behavior when its internal state changes.
  • Strategy allows one of a family of algorithms to be selected on-the-fly at runtime.
  • Template method defines the skeleton of an algorithm as an abstract class, allowing its subclasses to provide concrete behavior.
  • Visitor separates an algorithm from an object structure by moving the hierarchy of methods into one object.

Architectural Patterns:

  • Layers / Multi-tiered systems
  • Model-View-Controller

Visit the official site of the Design Patterns course for lecture materials, enrollment, news and forum: http://patterns.dev.bg/.

Previews (5,855), Views (187), Comments (0)

RSS feed for comments on this post. TrackBack URL

LEAVE A COMMENT