Abstract Factory
Type : Creational design pattern
Intent
Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Applicability
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.
Structure
Members
Product Interface
All products will implement this inteface so that any classes that need to use products will refer to this interface instead of referring the concrete product class.
ConcreteProducts
Concrete products that implement the Product interface.
ConcreteFactories
Overrides the factory method to return an instance of a ConcreteProduct.
Creator
- Declares the factory method, which returns an object of type Product. Creator may also define a default implementation of the factory method that returns a default ConcreteProduct object.
- May call the factory method to create a Product object.
Creator relies on its subclasses to define the factory method so that it returns an instance of the appropriate ConcreteProduct.
Outcome
Factory methods eliminate 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.
A potential disadvantage of factory methods is that clients might have to subclass the Creator class just to create a particular ConcreteProduct object. Subclassing is fine when the client has to subclass the Creator class anyway, but otherwise the client now must deal with another point of evolution.
