SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Decorator Pattern

lucius avatar
lucius
21 diapositives · 393 Views · Jul 13, 2014

The Decorator Pattern offers versatile options for creating customized coffee beverages at Starbuzz Coffee. By establishing a superclass for beverages and subclasses for various combinations, we can easily manage costs and descriptions of drinks such as Espresso, Decaf, and specialty options. This design allows the addition of new condiments without altering existing code, adhering to the design principle that classes should be open for extension but closed for modification. Learn how decorators enable adding capabilities dynamically, enhancing the user experience through seamless customization.

Decorator Pattern - slide 1
01 / 21Decorator Pattern
1 / 17

Télécharger la présentation

Decorator Pattern
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Decorator Pattern So many options!

  2. Starbuzz Coffee • Want to offer a variety of combinations of coffee and condiments • Cost of a cup depends on the combination that was ordered

  3. First Design • Make a beverage class and a subclass for each legal combination

  4. <<abstract>> Beverage String description getDescription() <<abstract>> cost() … Espresso cost() Decaf cost() HouseBlend cost() DarkRoast cost() But where are the fancy coffees? I could make this at home!

  5. <<abstract>> Beverage String description getDescription() <<abstract>> cost() … Espresso cost() Decaf cost() HouseBlend cost() DarkRoast cost() EspressoWith SteamedMilk cost() DecafWith SteamedMilk cost() HouseBlendWith SteamedMilk cost() DarkRoastWith SteamedMilk cost()

  6. <<abstract>> Beverage String description getDescription() <<abstract>> cost() … Espresso cost() Decaf cost() HouseBlend cost() DarkRoast cost() EspressoWith SteamedMilk cost() DecafWith SteamedMilk cost() HouseBlendWith SteamedMilk cost() DarkRoastWith SteamedMilk cost() Espresso Mocha cost() Decaf Mocha cost() HouseBlend Mocha cost() DarkRoast Mocha cost()

  7. <<abstract>> Beverage String description getDescription() <<abstract>> cost() … Espresso cost() Decaf cost() HouseBlend cost() DarkRoast cost() EspressoWith SteamedMilk cost() DecafWith SteamedMilk cost() HouseBlendWith SteamedMilk cost() DarkRoastWith SteamedMilk cost() Espresso Mocha cost() Decaf Mocha cost() HouseBlend Mocha cost() DarkRoast Mocha cost() Espresso WithWhip cost() Decaf WithWhip cost() HouseBlend WithWhip cost() DarkRoast WithWhip cost()

  8. Second Design • Make the superclass contain booleans to specify which condiments are included and subclasses for each type of coffee • How do we compute cost? • What does it take to add a new condiment?

  9. <<abstract>> Beverage String description milk soy mocha whip getDescription() <<abstract>>cost() hasMilk() setMilk() hasSoy() setSoy() hasMocha() setMocha() hasWhip() setWhip() … Decaf cost() HouseBlend cost() Espresso cost() DarkRoast cost()

  10. Design Principle • Classes should be open for extension, but closed for modification • “extension” is NOT subclassing • It means the addition of new behavior (without modifying the code!)

  11. 0.99 0.99+0.20 0.99+0.20+0.10 Decorator Pattern • Start with an instance of the “basic”classes and then decorate it with new capabilities Whip Mocha Dark Roast cost() cost() cost()

  12. Key Points • Decorators have the same supertypes as the objects they decorate • This lets us pass around the decorated object instead of the original (unwrapped) object • Decorator add behavior by delegating to the object it decorates and then adding its own behavior • Can add decorations at any time

  13. Decorator Pattern

  14. <<interface/abstract>> Component methodA() HAS-A <<abstract>> Decorator methodA() ConcreteComponent methodA() ConcreteDecoratorA Component wrappedObj methodA() newBehavior() ConcreteDecoratorB Component wrappedObj Object newState() methodA()

  15. Let’s Look at the Code

  16. public abstract class Beverage{ String description = “Unknown”; public String getDescription() { return description; } public abstract double cost(); } public abstract class CondimentDecorator extends Beverage { public abstract String getDescription(); public abstract double cost(); } public class Espresso extends Beverage { public Espresso() { description = “Espresso”; } public double cost() { return 1.99; } }

  17. public class Mocha extends CondimentDecorator { Beverage bev; public Mocha(Beverage bev) { this.bev = bev; } public String getDescription { return bev.getDescription() + “, Mocha”; } public double cost() { return .20 + bev.cost(); } }

  18. public class StarBuzz { public static void main(String args[]) { Beverage bev = new Espresso); bev = new Mocha(bev); bev = new Mocha(bev); bev = new Whip(bev); bev = new Soy(bev); System.out.println(bev.getDescription() + “ $”+ bev.getCost()); }

  19. Concrete decorators Component BufferedInputStream LineNumberInputStream FileInputStream Decorators in Java • File I/O Example

  20. abstract component InputStream abstract decorator FileInputStream FilterInputStream StringBufferInputStream BufferedInputStream LineNumberInputStream concrete components concrete decorators

  21. Lab Set Up • Using the Decorator Pattern to customize weapons