Design Patterns Illustrated
Upcoming SlideShare
Loading in...5
×
 

Design Patterns Illustrated

on

  • 16,891 views

Illustrations to show the essence of the 23 "classical" Gang Of Four design patterns. Plus some general info about object oriented progr

Illustrations to show the essence of the 23 "classical" Gang Of Four design patterns. Plus some general info about object oriented progr

Statistics

Views

Total Views
16,891
Views on SlideShare
16,358
Embed Views
533

Actions

Likes
56
Downloads
1,118
Comments
6

26 Embeds 533

http://www.slideshare.net 376
http://randomtower.blogspot.com 50
http://peepedangle.blogspot.com 46
http://www.lmodules.com 16
http://peepedangle.blogspot.in 11
http://www.proposable.com 4
http://peepedangle.blogspot.ca 4
http://randomtower.blogspot.mx 3
http://peepedangle.blogspot.de 3
url_unknown 3
http://randomtower.blogspot.de 2
http://www.linkedin.com 1
http://randomtower.blogspot.cz 1
http://peepedangle.blogspot.ru 1
http://randomtower.blogspot.fr 1
http://randomtower.blogspot.com.au 1
http://www.blogger.com 1
http://facebook.slideshare.com 1
http://local.mrc.medicalrecords.com 1
http://randomtower.blogspot.ca 1
http://randomtower.blogspot.it 1
http://randomtower.blogspot.pt 1
http://drizzlin.com 1
http://peepedangle.blogspot.co.nz 1
http://blendedschools.blackboard.com 1
http://www.peepedangle.blogspot.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

15 of 6 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • That's a good idea to illustrate the patterns with real-life metaphors, though some are more difficult than others. Cheers
    Are you sure you want to
    Your message goes here
    Processing…
  • The video is also available now: http://jandbeyond.org/video/monday-may-31st-2010/item/229-design-patterns-illustrated-herman-peeren.html

    Unfortunately the video doesn't show the slides. You should see both at the same time.

    Before the talk I showed a picture of Saint Isidoro di Sevilla: http://sjsm.files.wordpress.com/2009/04/san-isidoro2-jpegggg.jpg . That is what I talk about in the beginning.
    Are you sure you want to
    Your message goes here
    Processing…
  • Thanks for the rectification’s Herman. One further remark, the coupling you describe with mixins is actually an advantage and it’s done by design :

    - If you mix in a method in a base class, you can later choose to override that method in an extended class. This give you the ability to re-use the mixin functionality and specialize it by extending the class.

    - If you mix in a method and you want to override that method you could also do so by mixing in a new mixin that specifies the same method. The mixins are mixed using a LIFO array.

    In both scenarios you are not coupling, but de-coupling.

    As a bonus, the mixin implementation in Nooku Framework is even more powerful then the one in Rails. We have added the concept of dynamic and selective mixing.

    - Dynamic mixing allows you to instantiate a mixin and mix it with multiple objects as in a one to many relationship. This offers a number of benefits and some interesting flexibility.

    - Selective mixing allows the mixin to make available a number of it’s public methods to the mixer based on a set of conditions, or it can choose to not make available any methods at all.

    Both the dynamic mixing and selective mixing bring Nooku Framework very close to the basic concepts of AOP (Aspect Oriented Programming).

    Hope this helps to further clarify.
    Are you sure you want to
    Your message goes here
    Processing…
  • Comment by @johanjanssens via Twitter: slide 47 : NFW mixes objects against their public interface mixing only public methods and properties.

    That is a comment on my remark 'beware of tight coupling'. I made that remark mainly because IMHO there could be a problem if mixing in a method with a name that allready exists in the 'native' or mixed methods of that KObject. You have to know those names in order to prevent conflicts. So that is tight coupling.

    A mixin is a very powerful and handy way to put the same functionality in several parts in the code. Nothing wrong with it. I think it is very useful if the number of mixins is limited and their methods are treated as 'reserved words'.
    Are you sure you want to
    Your message goes here
    Processing…
  • Correction for slide 35 (Chain of Command):

    The commands in a KCommandChain in Nooku are command-objects (see: Command-pattern). They are KCommandHandlers, that implement the KCommandInterface. So: they are objects that execute their task upon calling their execute()-method.

    When running the command-chain you run a task and look in the chain which command-object will handdle it. Just like here:
    https://www.ibm.com/developerworks/library/os-php-designptrns/#N101DE
    (the IComand in that code has the same purpose as the KCommandInterface in Nooku).
    The NFW chain of command == chain of responsibility + command pattern.
    Thank you, Johan, for showing this to me.

    So: I was wrong thinking the KCommandChain was just a kind of macro, meant for running a series of commands. The confusion is that the commandhandlers are called 'commands'. The commandhandlers are command-objects and they handle the request (the parameters of run()).
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Design Patterns Illustrated Design Patterns Illustrated Presentation Transcript

  • Design Patterns illustrated Herman Peeren May 31st 2010 (DP-illustrations: Nelleke Verhoeff)
  • Design Patterns ●● recipes against common (OO-) programming problems ●● code reuse: no need to reinvent the wheel ●● common language ●● GOF: 23 “classical” patterns classic, The Book very nice!
  • The one constant in software development:
  • The one constant in software development: CHANGE!
  • The one constant in software development: CHANGE! I knew it ...
  • Ideal: code as modular black boxes
  • Wish list and OOP-principles ●● loose coupling: 1 change = ceteris paribus ●● code reuse (is not the same as copy/paste) ●● open for extension, closed for modification ●● encapsulate what varies ●● single responsibility principle ●● program against an interface not against an imple- mentation. Dependency injection ●● prefer composition over inheritance (in fact this is all the same with different words)
  • Avoid: tight coupling!
  • It might get you into trouble...
  • Beware of: Code smells!
  • some code smells: 1.● duplicate code: DRY 2.● long method, huge class: SRP 3.● combinatorial explosion (similar classes) 4.● conditional complexity, switch statements 5.● “exhibitionistic” classes
  • some code smells: 1.● duplicate code: DRY 2.● long method, huge class: SRP 3.● combinatorial explosion (similar classes) 4.● conditional complexity, switch statements 5.● “exhibitionistic” classes
  • Classic pattern categories creational, structural and behavioral patterns: ●● creational: object instantiation ●● structural: larger structures of classes or objects ●● behavioral: interaction and distribution of responsibility
  • Creational design patterns ●● Factory Method: Allow subclasses to “decide” which class to instantiate. ●● Abstract Factory: Encapsulate a set of analo- gous factories that produce families of objects. ●● Builder: Encapsulate the construction of com- plex objects from their representation; so, the same building process can create various repre- sentations by specifying only type and content. ●● Singleton: Ensure that only a single instance of a class exists and provide a single method for gaining access to it. ●● Prototype: Create an initialized instance for cloning or copying.
  • Factory Method Provide an interface for the creation of objects. Allow subclasses to “decide” which class to instantiate. c
  • Abstract Factory Povide an interface for creating families of related or dependent objects. A factory for factories. c
  • Builder Seperate the construction process (how) of a complex object from the concrete representations (what). c
  • Singleton Ensure a class only has one instance, and provide a global point of access to it. Oh, I’m so loooooooonly c
  • Joomla! ●● JFactory: a class with static methods to instantiate objects like JDatabase, JUser, JDocument, JTemplate, etc. ●● most of those methods are singletons Nooku ●● KFactory: any class can be instantiated ●● get() = singleton, tmp() = any instantiation
  • “Every advantage has its disadvantages” (free to Johan Cruyff, Dutch Football Pattern Designer and Ajax-fan...)
  • Prototype Make variations on copies of a basic-object. COPY-SERVICE c
  • Structural design patterns ●● Adapter: Adapt an interface to an expected interface. ●● Bridge: Decouple an interface from its implementation. ●● Composite: Create a tree structure for part-whole hierarchies. ●● Decorator: Extend functionality dynamically. ●● Facade: Simplify usage by defining a high-level interface. ●● Flyweight: Support fine-grained objects efficiently by sharing. ●● Proxy: Represent an object with another object for access control.
  • Adapter (= Wrapper) c Adapt an interface to an expected interface.
  • Joomla! ●● new in 1.6: JAdapter and JAdapterInstance ●● JUpdateAdapter extends JAdapterInstance JUpdaterExtension & JUpdaterExtension extend JUpdateAdapter wanted: documentation and examples! what does it adapt?
  • Bridge Decouple an abstraction from its implementation. COLA 1 LITER 1 LITER COLA 1 LITER 1 LITER COLA MILK COLA MILK COLA MILK c
  • Composite Create a tree structure for part-whole hierarchies. A node is also a (part of a) tree. Recursive: c
  • Decorator Add extra functionallity (at runtime), while keeping the interface the same. Matroushka’s... c
  • Decorator Nooku ●● KPatternDecorator: a general decorator ●● e.g. extended by KDecoratorJoomlaApplication
  • Facade Provide a general (simpler) interface for a set of interfaces. looks simple c
  • Flyweight Use one instance of a class to provide many “virtual” instances. c
  • Proxy Provide a surrogate or placeholder for another object to control access to it. c
  • Behavioral design patterns ●● Chain of Responsibility: Define a method of passing a request among a chain of objects. ●● Command: Encapsulate a command request in an object. ●● Interpreter: Allow inclusion of language elements in an appli- cation. ●● Iterator: Enable sequential access to collection elements. ●● Mediator: Define simplified communication between classes. ●● Memento: Save and restore the internal state of an object. ●● Observer: Define a scheme for notifying objects of changes to another object. ●● State: Alter the behavior of an object when its state changes. ●● Strategy: Encapsulate an algorithm inside a class. ●● Template Method: Allow subclasses to redefine the steps of an algorithm. ●● Visitor: Define a new operation on a class without changing it.
  • Command Encapsulate a command request in an object. YOU,DO YOUR TASK! TASK TASK LIGHT LIGHT ON OFF c
  • Chain of Responsibility c Define a method of passing a request among a chain of objects.
  • Nooku ●● KCommandChain + KCommandContext, KCommandEvent, KCommandHandler and KCommandInterface ●● N.B.: executes a series of commands instead of passing a command to a series of handlers (like in Tapestry e.g.) ...correct me if I’m wrong....
  • Interpreter Domain -> (little) language -> grammar -> objects (DSL) HÉ! he means: do this, do that, and after finishing it, go there! c
  • Iterator Enable sequential access to collection elements, without showing the underlying data-structures (array, list, records, etc) next next c
  • Mediator c Layer in between: communication via one object.
  • Memento Save and restore the internal state of an object. ME c
  • Observer Notify “subscribers” of changes. ME NO ME ME WHO? c
  • Joomla! ●● JObserver and JObservable ●● JObserver extended by JEvent and that by JPlugin Nooku ●● KPatternObserver and KPatternObservable
  • State Let an object show other methods after a change of internal state (as if it changes it’s class). in a.....hick......different state, ....hick....I behave differently....hick..... c
  • Strategy When something can be done in several ways, make those ways interchangeable. POSSI- BILITIES c
  • Template Method The skeleton of an algorithm is fixed, but parts can be filled in differently. c
  • Visitor Make a kind of plugin-possibility for methods: in that way me- thods can be added in runtime. printservice! c
  • extra: Mixin ●● Used in Nooku (and a.o. in Ruby and Python) ●● a kind of abstract class that is mixed into another object ●● all methods of the mixin are now part of the object ●● handle with care: beware of tight coupling....
  • Golden OO-principles ●● encapsulate what varies, OCP ●● 1class, 1 responsibility, SRP ●● program against an interface, not against an imple- mentation, DIP ●● prefer composition over inheritance ●● loose coupling, modular black boxes
  • Some books GOF: 23 “classical” patterns: very nice! classic, The Book handy examples
  • good start Fowler: extended e.g. with patterns for web Fowler: also known from refactoring combi: re- factoring & patterns
  • Resign Patterns: Ailments of Unsuitable Project-Disoriented Software
  • Joomla! Could be improved by studying design patterns and applying them. Loose coupling...
  • Questions? Contact info: Herman Peeren herman@yepr.nl © Yepr The artwork in this presentation is provided under the Creative Commons Public License for noncommercial use. http://creativecommons.org/licenses/by-nc/3.0/legalcode