1. Advanced Object-oriented Design Patterns Creational Design Patterns

2. Summarizing the Design Themes Think differently about Types Vs. Classes Program to an interface (Type), not an implementation (Class). Favor object composition over class inheritance, black box over white box reuse. Design relationships between objects and their types to achieve good run-time structure. Don’t limit yourself to compile time structures.

3. Creational Design Patterns l Creational design patterns abstract the instantiation process l Encapsulate knowledge about which concrete classes the system uses.. l Hide how instances of these classes are created and put together l Result: Modules can be designed independent of how objects are created, composed and represented …

4. Topic 1: Singleton Pattern Ensure a class only has one instance, and provide a global point of access to it

5. Singleton: Applicability l Use singleton pattern when: there must be exactly one instance of a class, and it must be accessible to clients from a well-known access point. when the sole instance should be extensible by sub-classing, and clients should be able to use an extended instance without modifying their code.

6. Singleton Model

7. Singleton: Consequences l Notice that the constructor is protected. A client that tries to instantiate Singleton directly will get an error at compile-time. l Controlled access to sole instance, only through getInstance () method. l The Singleton class may be sub-classed, and it's easy to configure an application with an instance of this extended class. How ? l Permits a variable number of instances. How?

8. Singleton: Exercise l You are writing a Java application that makes use of a database connection to connect to a data server. Each application instance is allocated a single connection. The database connection is used by multiple data access classes to load and update data. l Variation: Could you used the Singleton pattern to implement a database connection pool manager object ? How ?

9. Topic 2: Factory Method Pattern Define an interface for creating an object, but let subclasses decide which class to instantiate

10. Factory Method: Applicability l Use the Factory Method pattern when a class can't anticipate the class of objects it must create. a class wants its subclasses to specify the objects it creates l Example: You are a class library developer, who is developing a framework for Workflow product with objects such as Workflow, WorkflowTask and WorkflowScheduler. But you obviously do not know all the specific types of workflow tasks that such as system would be used with.

11. Factory Method: Example

12. Factory Method: Model

13. Factory Method: Collaborations l Product (WorkflowTask) defines the interface of objects the factory method creates. l ConcreteProduct (InsuranceTask) implements the Product interface. l Creator (WorkflowManager) declares the factory method, which returns an object of type Product. Typically calls the factory method to create a Product object l ConcreteCreator (InsuranceWorkflowManager) overrides the factory method to return an instance of a ConcreteProduct.

14. Factory Method: Consequences l Eliminates the need to bind application-specific classes into your code. The code only deals with the Product interface; therefore it can work with any user-defined ConcreteProduct classes. l Factory Method gives subclasses a hook for providing an extended version of an object. l Could be used to connect parallel class hierarchies l Factory method can be parameterized to specify a specific concrete product type.

15. Factory Method: Exercise l Assume you have written a singleton Database connection pool manager, which manages a pool of Database connection objects. Your project manager comes with a new requirement that your Java application now has to support both DB2 and SQL Server in different installations. Also in the future there is a possibility of having to support Oracle. Your realize the way you connect to these different DB vendors is little different, though your logic within the Database Connection Pool Manager class is reusable. How would you go about addressing the new requirements?

16. Topic 3: Abstract Factory Pattern Provide an interface for creating families of related or dependent objects without specifying their concrete classes.

17. Abstract Factory: Applicability l Use the Abstract Factory pattern when a system should be independent of how its products are created, composed, and represented. a system should be configured with one of multiple families of products. a family of related product objects is designed to be used together, and you need to enforce this constraint. you want to provide a class library of products, and you want to reveal just their interfaces, not their implementations.

18. Abstract Factory: Example

19. Abstract Factory: Model

20. Abstract Factory: Collaborations l AbstractFactory (WidgetFactory) declares an interface for operations that create abstract product objects l ConcreteFactory (MotifWidgetFactory, OpenLookWidgetFactory) implements the operations to create concrete product objects l AbstractProduct (WindowWiget, ButtonWidget) declares an interface for a type of product object l ConcreteProduct (MotifWindow, MotifButton) defines a product object to be created by the corresponding concrete factory. implements the AbstractProduct interface l Client uses only interfaces declared by AbstractFactory and AbstractProduct classes

21. Abstract Factory: Consequences l Isolates concrete classes from Client l It makes exchanging product families easy: The class of a concrete factory appears only once in an application, where it's instantiated. l Ensures application use objects from only one family at a time l Supporting new kinds of products is difficult l A more flexible but less safe design is to add a parameter to operations that create objects. This parameter specifies the kind of object to be created.

22. Abstract Factory: Exercise l You are in charge of designing an Enterprise application that connects to your Magazine Fulfillment Service Providers and uploads/ download subscription lists. Though there are only 3 providers, each of them have different connection mechanism, communication mechanism and file structures. You would like to isolate your application from provider specific differences and and have identified a basic set of objects you want to work with in your application such a ProviderConnection, SubscriptionFile, SubscriptionOrder etc. How would you evolve your design ?

23. Topic 4: Builder Pattern Separate the construction of a complex object from its representation so that the same construction process can create different representations.

24. Builder: Applicability l Use the Builder pattern when the algorithm for creating a complex object should be independent of the parts that make up the object and how they're assembled. the construction process must allow different representations for the object that's constructed.

25. Builder: Example

26. Builder: Model

27. Builder: Collaborations l Builder (PolicyRecordBuilder) - specifies an abstract interface for creating parts of a Product object. l ConcreteBuilder (AcordPolicyRecBuiler) constructs and assembles parts of the product by implementing the Builder interface. defines and keeps track of the representation it creates. provides an interface for retrieving the product l Director (MasterPolicyRecordReader) - constructs an object using the Builder interface. l Product (AcordRecord, BillingRecord) - represents the complex object under construction. ConcreteBuilder builds the product's internal representation and defines the process by which it's assembled.

28. Builder: Consequences l Lets you vary a product's internal representation - Because the product is constructed through an abstract interface, all you have to do to change the product's internal representation is define a new kind of builder l Isolates code for construction and representation - Clients needn't know anything about the classes that define the product's internal structure; such classes don't appear in Builder's interface l Gives you finer control over the construction process - the Builder pattern constructs the product step by step under the director's control. Only when the product is finished does the director retrieve it from the builder.

29. Builder: Exercise l For your Enterprise application that integrates with your Magazine Fulfillment Service Providers, you need to read in a master subscription record and create multiple provider specific subscription formats. The subscription record structure is complex and has multiple data sections such as Subscribtion Info, Payment History, Credit Info etc. The target formats though containing the same inf. hold it in different order, format and data types. More over specific format have different summary data layouts. Your manager also decides to support an XML based subscription record format for integration with B2B Online subscription services. You know other formats are coming in the future.