The document discusses different creational design patterns including Factory, Singleton, Abstract Factory, and Prototype patterns. It provides details on the Factory pattern including its purpose of creating objects in situations where the constructor is inadequate, using methods to return required objects. It also covers the Singleton pattern's purpose of ensuring only one instance of a class and obtaining it from anywhere. Finally, it discusses the Abstract Factory pattern's purpose of providing an interface for creating families of related objects without specifying concrete classes and using a factory method for each family member.
The document discusses different creational design patterns including Factory, Singleton, Abstract Factory, and Prototype patterns. It provides details on the Factory pattern including its purpose of creating objects in situations where the constructor is inadequate, using methods to return required objects. It also covers the Singleton pattern's purpose of ensuring only one instance of a class and obtaining it from anywhere. Finally, it discusses the Abstract Factory pattern's purpose of providing an interface for creating families of related objects without specifying concrete classes and using a factory method for each family member.
The document discusses different creational design patterns including Factory, Singleton, Abstract Factory, and Prototype patterns. It provides details on the Factory pattern including its purpose of creating objects in situations where the constructor is inadequate, using methods to return required objects. It also covers the Singleton pattern's purpose of ensuring only one instance of a class and obtaining it from anywhere. Finally, it discusses the Abstract Factory pattern's purpose of providing an interface for creating families of related objects without specifying concrete classes and using a factory method for each family member.
The document discusses different creational design patterns including Factory, Singleton, Abstract Factory, and Prototype patterns. It provides details on the Factory pattern including its purpose of creating objects in situations where the constructor is inadequate, using methods to return required objects. It also covers the Singleton pattern's purpose of ensuring only one instance of a class and obtaining it from anywhere. Finally, it discusses the Abstract Factory pattern's purpose of providing an interface for creating families of related objects without specifying concrete classes and using a factory method for each family member.
Download as PPT, PDF, TXT or read online from Scribd
Download as ppt, pdf, or txt
You are on page 1/ 52
Chapter 7
Creational Design Pattern
Factory Singleton Abstract Factory Prototype 7.1 - Factory Design Pattern Design Purpose Create individual objects in situations where the constructor alone is inadequate. Design Pattern Summary Use methods to return required objects. Factory Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Factory Interface for Clients public static void main(String[] args) { RequiredClass instanceOfRequiredClass = MyClass.getNewInstanceOfRequiredClass();
} // End main
Demonstrates the use of a static method to create an instance of a class Factory Class Model Factory design pattern MyClass createObjectOfRequiredClass(): RequiredClass create object RequiredClass Client Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Design Goal At Work: Reusability and Corrrectness We want to write code about automobiles in general: Code that applies to any make, exercised repeatedly (thus reliably). Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Application of Factory design pattern Factory Example Ford createAutomobile() Toyota createAutomobile() Automobile createAutomobile(): Automobile Client create object create object Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Example Code class Ford extends Automobile {
static Automobile createAutomobile() { return new Ford(); } // End createAutomobile
} // End class createObjectOfRequiredClass() Sequence Diagram for Factory :MyClass :Client RequiredClass() :RequiredClass Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Typical Output of E-Mail Generation Example Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Word that was entered Design Goals At Work: Correctness and Reusability We want to separate the code common to all types of customers. We want to separate the specialized code that generates e-mail for each type of customer. This makes it easier to check for correctness and to reuse parts. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Application of Factory design pattern Customer getMessage() Client sendMessage() Frequent getMessage() Returning getMessage() Curious getMessage() Newbie getMessage() MailMessage text MailGenerationApplication getCustomerTypeFromUser() setup Factory: Email Generation Example Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. <<abstract>> Factory Applied to getGraphics() in Java Factory design pattern Component getGraphics(): Graphics create object Client Graphics Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. public static Box createVerticalBox()
public static Box createHorizontalBox()
7.2 - Singleton Design Pattern Key Concept: Singleton Design Pattern -- when a class has exactly one instance. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Design Purpose Ensure that there is exactly one instance of a class S. Be able to obtain the instance from anywhere in the application. Design Pattern Summary Make the constructor of S private; define a private static attribute for S of type S; define a public accessor for it. Singleton Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Design Goal At Work: Correctness Singleton enforces the intention that only one User object exists, safeguarding the application from unanticipated User instance creation. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. The Singleton Interface for Clients User mainUser = User.getTheUser(); Singleton: Class Model Singleton Design Pattern MyClass getSingletonOfMyClass(): MyClass Client 1 singletonOfMyClass static Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. The Singleton Design Pattern -- applied to MyClass 1. Define a private static member variable of MyClass of type MyClass private static MyClass singletonOfMyClass = new MyClass(); 1. Make the constructor of MyClass private private MyClass() { /* . constructor code . */ }; 1. Define a public static method to access the member public static MyClass getSingletonOfMyClass() { return singletonOfMyClass; } Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Application of Singleton to Experiment Example Experiment theExperiment: Experiment analyze() getTheExperiment(): Experiment reportResults() Client theExperiment 1 static Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Key Concept: Singleton Design Pattern When a class must have exactly one instance, make the constructor private and the instance a private static variable with a public accessor. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Example Code public class Runtime { private static Runtime currentRuntime = new Runtime();
// Returns the runtime object associated with the current // Java application.
public static Runtime getRuntime() { return currentRuntime; }
private Runtime() { }
} 7.3 - Abstract Factory Design Pattern Design Purpose Provide an interface for creating families of related or dependent objects without specifying their concrete classes.* Design Pattern Capture family creation in a class containing a factory method for each class in the family. Abstract Factory * Gamma et al Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Word Processor Interaction 1 of 2 ---> Enter title: My Life
---> Enter Heading or -done: Birth
---> Enter text: I was born in a small mountain hut .
---> Enter Heading or -done: Youth ---> Enter text: I grew up playing in the woods
---> Enter Heading or -done: Adulthood .
---> Enter Heading or -done: -done
(continued)
Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Word Processor Interaction 2 of 2: Output Options . >> Enter the style you want displayed: big
----- Title: MY LIFE -----
Section 1. --- BIRTH --- I was born in a mountain hut .
Section 2. --- YOUTH --- I grew up sturdy
Section 3. --- ADULTHOOD --- . . >> Enter the style you want displayed: small My Life
Birth I was born in a mountain hut .
Youth I grew up sturdy
Adulthood Option 2 Option 1 Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Abstract Factory* Abstract Factory Interface Style. Client StyleAFactory StyleBFactory Ensemble setAbstractFactory() doAFunction() AbstractFactory getAPart1Object() getAPart2Object() * relationships within pattern application not shown Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Application of Abstract Factory Interface of Abstract Factory Applied to Word Processor Client SmallStyle LargeStyle Style Document setStyle() display() . . . . . . . 1 Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. create Abstract Factory Style. AbstractFactory getAPart1Object() getAPart2Object() StyleAFactory StyleBFactory Part1 Part2 Part1StyleA Part1StyleB Part2StyleA Part2StyleB abstractFactory 1 Ensemble doAFunction() Client 1..n 1..n Part Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. } } Sequence Diagram for Abstract Factory StyleXFactory() :Client abstractFactory :StyleXFactory :Ensemble setAbstractFactory (abstractFactory ) getAPart_i() Part_iStyleX() Selecting a style Creating a Part_i object in required style getAPart_i() abstractFactory :AbstractFactory :Part_iStyleX doAFunction() Virtual function property Assume that this method requires a Part_i object. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Design Goals At Work: Correctness and Reusability We want to separate the code parts that format the document in each style. We also want to separate the common document generation code. This facilitates reusing parts and checking for correctness. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Abstract Factory Applied to Word Processor Document getAHeading() getATitle() grtDocumentFromUser( ) create SmallStyle getAHeading() getATitle() LargeStyle getAHeading() getATitle() Title value Heading value LargeHeading display() SmallHeading display() LargeTitle display() SmallTitle display() Text value 1 0..n 0..n Style getAHeading() getATitle() Displayable Displayable display() Client getStyleFromUser() displayDocument() style Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. An Abstract Factory Application: Java ToolKit ToolKit createButton() createImage() ConcreteToolkit1 createButton() createImage() ConcreteToolkit2 createButton() createImage() ButtonPeer ConcreteToolkit3 createButton() createImage() ButtonPeer implementation 3 ImagePeer implementation 3 ImagePeer Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Abstract Factory: Narrow Interface Style. AbstractFactory getAPart1Object() getAPart2Object() StyleAFactory StyleBFactory abstractFactory 1 Ensemble setStyleA() setStyleB()
Client . . . . Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Key Concept: Abstract Factory Design Pattern To design an application in which there are several possible styles for a collection of objects, capture styles as classes with coordinated factory methods. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. 7.4 - Prototype Design Pattern Design Purpose Create a set of almost identical objects whose type is determined at runtime. Design Pattern Assume that a prototype instance is known; clone it whenever a new instance is needed. Prototype Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Prototype Design Example: A Selection Graphics courtesy COREL Click on choice of storage: Click on choice of chair: Click on choice of desk: Furniture color Furniture hardware type colonial A Simplified Prototype Example Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Prototype Interface With Clients Ensemble createEnsemble() Client Part1 clone() Part2 clone() (optional part of interface) Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Code Example OfficeSuite myOfficeSuite = OfficeSuite.createOfficeSuite( myDesk, myChair, myStorage);
Prototype Design Pattern The Prototype Idea Ensemble createEnsemble() Client MyPart clone(): MyPart MyPartStyleA clone() MyPartStyleB clone() myPartPrototype 1 // To create a MyPart instance: MyPart p = myPartPrototype.clone(); Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Code Example Ensemble EnsembleA Ensemble.createEnsemble(. . .);
Ensemble EnsembleB Ensemble.createEnsemble(); // This code is inside the Ensemble class MyPart anotherMyPart = MyPartPrototype.clone(); MyPart yetAnotherMyPart = MyPartPrototype.clone();
Prototype Class Model Ensemble createEnsemble() Client Part1 clone() Part2 clone() Part1StyleA clone() Part1StyleB clone() Part2StyleA clone() Part2StyleB clone() part1Prototype part2Prototype 1 1 ..... // To create a Part1 object: Part1 p1 = part1Prototype.clone(); . Part1StyleB returnObject = new Part1StyleB(); . Part1StyleC clone() Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Sequence Diagram for Prototype partNPrototype :PartN :Ensemble createEnsemble() clone() partNPrototype :PartNStyleB :PartNStyleB PartNStyleB() (virtual function property) Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Contrasting Abstract Factory and Prototype Prototype allows the client to select any chair style, any desk style, and any cabinet style This is all done separately rather than have to select an overall office style Nevertheless, the client wants to keep a single style of chair and a single style of desk throughout the office suite Design Goals At Work: Correctness and Reusability We want to isolate the parts pertaining to each type of customer. We also want to isolate the common customer code. This makes it easier to check the design and implementation for correctness, and to reuse the parts. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. OfficeProcess doAProcess() Prototype Example Outline HiVolCustomer clone() LoVolCustomer clone() Customer clone(): Customer customerPrototype Client 1 MedVolCustomer clone() Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Requirement for (Deep) Cloning Class1 Class2 c1:Class1 c2:Class2 (2) c1 an instance of Class1: c1.clone should be as follows (deep clone): c1.clone:Class1 x*:Class2 * a clone of c2 In shallow cloning, c1.clone actually as follows! c1.clone:Class1
Given: (1) Class model: Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Key Concept: Prototype Pattern -- when designing for multiple instances which are the same in key respects, create them by cloning a prototype. Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission. Summary of Creational Design Patterns Use Creational Design Patterns when creating complex objects Factory when creating individuals Singleton for exactly one individual Abstract Factory when creating families Prototype to mix & match
Adapted from Software Design: From Programming to Architecture by Eric J. Braude (Wiley 2003), with permission.
Full Download Functional Python Programming: Use a functional approach to write succinct, expressive, and efficient Python code, 3rd Edition Lott PDF DOCX
Full Download Functional Python Programming: Use a functional approach to write succinct, expressive, and efficient Python code, 3rd Edition Lott PDF DOCX
