Skip to main content

Abstract Factory Pattern

Abstract Factory Pattern 


Gamma Categorization: Creational Design Patten
Summary: When the object construction is complicated, needing multiple arguments, we should create a separate function (Factory Method) or class (Factory), which is responsible for the creation of the all object.

Problem examples

Suport of multiple databases
Multiple data sources: Serial port, ethernet port, device driver
Diferent report types

Solution

Abstract class
Generalized interface
A Factory creates instances of the concrete classes

Sample Code

The abstract factory

public interface IPhotoFactory
{
    IAnaloguePhoto CreateAnaloguePhoto();
    IDigitalPhoto CreateDigitalPhoto();
}


The abstract products

public interface IAnaloguePhoto
{
    string GetName();
}

public interface IDigitalPhoto
{
    string GetName();
}

The concrete factories
public class CanonFactory : IPhotoFactory
{
    public IAnaloguePhoto CreateAnaloguePhoto()
    {
        return new CanonAnaloguePhoto();
    }

    public IDigitalPhoto CreateDigitalPhoto()
    {
        return new CanonDigitalPhoto();
    }
}

public class NikonFactory : IPhotoFactory
{
    public IAnaloguePhoto CreateAnaloguePhoto()
    {
        return new NikonAnaloguePhoto();
    }

    public IDigitalPhoto CreateDigitalPhoto()
    {
        return new NikonDigitalPhoto();
    }
}

The concrete products

public class CanonAnaloguePhoto : IAnaloguePhoto
{
    public string GetName()
    {
        return "Canon Analogue Photo";
    }
}

public class CanonDigitalPhoto : IDigitalPhoto
{
    public string GetName()
    {
        return "Canon Digital Photo";
    } 
}

public class NikonAnaloguePhoto : IAnaloguePhoto
{
    public string GetName()
    {
        return "Nikon Analogue Photo";
    }
}

public class NikonDigitalPhoto : IDigitalPhoto
{
    public string GetName()
    {
        return "Nikon Digital Photo";
    } 
}

The client

public class PhotoClient
{
    public enum Brand { Canon, Nikon};

    private IPhotoFactory photoFactory;

    public PhotoClient(Brand brand)
    {
        switch (brand)
        {
            case Brand.Canon:
                photoFactory = new CanonFactory();
                break;
                case Brand.Nikon:
                photoFactory = new NikonFactory();
                break;
        }
    }

    public string GetAnaloguePhoto() => photoFactory.CreateAnaloguePhoto().GetName();
    public string GetDigitalPhoto() => photoFactory.CreateDigitalPhoto().GetName();
}

Usage

var photoClient = new PhotoClient(PhotoClient.Brand.Canon);
WriteLine(photoClient.GetAnaloguePhoto());
WriteLine(photoClient.GetDigitalPhoto());

photoClient = new PhotoClient(PhotoClient.Brand.Nikon);
WriteLine(photoClient.GetAnaloguePhoto());
WriteLine(photoClient.GetDigitalPhoto());

Comments

Post a Comment

Popular posts from this blog

C# Extension Methods

 C# Extension Methods Extension methods      public   static   class   ExtensionMethods     {          public   static   Stopwatch   Measure ( this   Func < int >  f )         {              var   sw  =  new   Stopwatch ();              sw . Start ();              f ();              sw . Stop ();              return   sw ;         }          public   static   void   Save ( this   ISerializable   s...
Post a Comment
Read more

SOLID (4/5) - Interface segregation principle

Interface segregation principle In the field of software engineering, the interface-segregation principle (ISP) states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them. Such shrunken interfaces are also called role interfaces. ISP is intended to keep a system decoupled and thus easier to refactor, change, and redeploy. using   System ; namespace   interfacesegregation {      public   class   Document       {     }      public   interface   IMachine       {          void   Print ( Document   d );          void   Scan ( Document   d );     ...
Post a Comment
Read more

SOLID (1/5) - Single Resposibility Principle

 SOLID (1/5) - Single Resposibility Principle The single-responsibility principle (SRP) is a computer-programming principle that states that every class in a computer program should have responsibility over a single part of that program's functionality, which it should encapsulate. All of that module, class or function's services should be narrowly aligned with that responsibility. In the following example we have a TodoList class which only handles it's own functionality logic, and then we have a Persistance class which handles the saving logic, hence keeping the concerns separeted. using   System ; using   System . Collections . Generic ; namespace   Journal {      public   class   TodoList     {          private   readonly   List < string >  _entries  =  new   List < string >();          private...
Post a Comment
Read more