Itqualityassurance
- What does Abstract Factory pattern do?
- What is the difference between factory and Abstract Factory pattern?
- When should we use Abstract Factory pattern?
- Why use an abstract factory?
What does Abstract Factory pattern do?
Abstract Factory provides interfaces for creating families of related or dependent objects without specifying their concrete classes. Client software creates a concrete implementation of the abstract factory and then uses the generic interfaces to create the concrete objects that are part of the family of objects.
What is the difference between factory and Abstract Factory pattern?
Factory pattern provides a method of creating objects without specifying the exact class used to create it. In contrast, abstract factory pattern provides a method to combine a group of individual factories without specifying their concrete classes.
When should we use Abstract Factory pattern?
When to Use Abstract Factory Pattern: The client is independent of how we create and compose the objects in the system. The system consists of multiple families of objects, and these families are designed to be used together. We need a run-time value to construct a particular dependency.
Why use an abstract factory?
The Abstract Factory pattern helps you control the classes of objects that an application creates. Because a factory encapsulates the responsibility and the process of creating product objects, it isolates clients from implementation classes. Clients manipulate instances through their abstract interfaces.
