DOT NET Interview Questions - DotNetSpider

The below two class diagrams will provide overview of what the actual difference is.
First figure shows a sample implementation of Factory Patterns. In this figure there are
two basic sections:-
√
√
√
√
The actual product section i.e. Class “Product” it inherits from a abstract
class “AbstractProduct”.
The creational aspect section that’s “ConcreteCreator” class which inherits
from class “Creator”.
Now there are some rules the client who will need the “Product” object will
have to follow. He will never refer directly to the actual “Product” object he
will refer the “Product” object using “AbstractProduct”.
Second client will never use “New” keyword to create the “Product” object
but will use the “Creator” class which in turn will use the “ConcreteCreator”
class to create the actual “Product” object.
Figure: - 8.1 Class diagram of a factory Pattern
So what are benefits from this architecture? All creational and initializing aspects are
now detached from the actual client. As your creational aspect is now been handled in
“ConcreteCreator” and the client has reference to only “Creator”, so any implementation
change in “CreateProduct” will not affect the client code. In short now your creational
aspect of object is completely encapsulated from the client’s logic.
Now let’s look at the second class diagram which provides an overview of what actually
“Abstract factory” pattern is. It creates objects for families of classes. In short it describes
collection of factor methods from various different families. In short it groups related
151