Skip to main content

Creational Design Patterns-Factory Method Pattern


Design Patterns can be categorized under the following Heads
  1. Creational
  2. Structural
  3. Behavioral


This section deals with the creational design patterns,

Creational Patterns
The creational patterns aim to separate a system from how its objects are created, composed, and represented.
Creational Patterns can be classified as follows
1. Abstract Factory
2. Builder
3. Factory
4. Prototype
5. Singleton

Creational patterns encapsulate the knowledge about which classes a system uses, but they hide the details of how the instances of these classes are created and put together.


Factory Method Pattern

The Factory Method pattern is a way of creating objects, but letting subclasses decide exactly which class to instantiate.

Various subclasses might implement the interface; the Factory Method instantiates the appropriate subclass based on information supplied by the client or extracted from the current state.

Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.

Example:
The Example presented below is a basic document creation factory, where different types of documents(Resumes, Reports etc.) can be created using the Factory Pattern

public abstract class DocPage
  {
     public string Header
     {

         set { Header = "P.Solutions"; }
    
     }
     public string Footer
     {

         set { Footer = "Confidential Document"; }

     }

  }

  class SkillSetPage : DocPage
  {
   
  }

  class EducationalDetailsPage : DocPage

  {

  }

  class ExperienceSummaryPage : DocPage

  {

  }
  class BriefInrtoPage : DocPage

  {

  }

  class FindingsPage : DocPage

  {

  }
 
  class ConclusionPage : DocPage

  {

  }

 class SummaryPage : DocPage

  {

  }

 class BibliographyPage : DocPage
  {

  }



//The 'Creator' abstract class. This is class that acts as creator of  Documents, depending upon the requirements


 public abstract class Document
  {

    private List<DocPage> _pages = new List<DocPage>();

     // Constructor calls abstract Factory method

    public Document()
    {

      this.CreatePages();

    }

  public List<DocPage> Pages
    {
      get { return _pages; }
    }
    // Factory Method

    public abstract void CreatePages();

  }

  // 'ConcreteCreator' classes. These Classes  are called in by Client , hieding the details as to how the classes produce documnents

 public class Resume : Document
  {
    // Factory Method implementation

    public override void CreatePages()
    {
      Pages.Add(new SkillsPage());
      Pages.Add(new EducationPage());
      Pages.Add(new ExperiencePage());
    }

  }

 
  /// A 'ConcreteCreator' class

  ///

  class Report : Document

  {
   // Factory Method implementation
    public override void CreatePages()
    {

      Pages.Add(new IntroductionPage());

      Pages.Add(new ResultsPage());

      Pages.Add(new ConclusionPage());

      Pages.Add(new SummaryPage());

      Pages.Add(new BibliographyPage());

    }

  }

All in Place, Let’s now call these classes to get the documents.

protected void Page_Load(object sender, EventArgs e)
    {
          
        Resume rs = new Resume();
        Response.Write("");
        foreach( DocPage dp in rs.Pages)
        {
           Response.Write("
");
            Response.Write(dp.GetType().Name);
       
        }
       
     
   }

 
When called, as shown above, Following pages become part of Resume document.
SkillsPage
EducationPage
ExperiencePage 


Please note that instead of the abstract classes, Interface is generally considered for implementing the Factory pattern. In case you feel the need, feel free to modify the code for using interfaces.

For further understanding  implementation of the pattern in .Net, go to the following link.
 http://aspalliance.com/1751_Exemplifying_the_Factory_Method_Pattern_inside_the_NET_Framework.all

Hope this was helpful,

Till next time. Happy Coding!!
 



Comments

Post a Comment

Popular posts from this blog

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...
Post a Comment
Read more

Covariance and Contravariance-General Discussion

If you have just started the exploration of .Net Framework 4.0, two terms namely Covariance and Contravariance might have been heard. The concept that these terms encapsulate are used by most developer almost daily, however there has never been any botheration about the terminologies. Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them. Enough philosophy, let’s get to the business. Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further. Invariance: Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either ...
1 comment
Read more

WCF-REST Services-Part-I

What is REST? REST stands for Representational State Transfer. REST as described in MSDN, “is an architectural style that can be used to build software in which clients (user agents) can make requests of services (endpoints)”. REST is one way to implement a client-server architectural style. A service that uses the architectural style of REST is generally referred to as a RESTful service or endpoint. RESTful endpoint Building Blocks 1. Resources(What resources would the service Serve/Offer) 2. URI(Identifiers used to represent the resources) 3. HTTP Verbs (What parts of the uniform interface (HTTP verbs) are each URI going to support, like Get/Post etc.) I’ll develop a hypothetical system that will make use of these blocks in the next article, let us consider the theoretical aspects of the REST in this post. Why REST? As explained above, REST internally implements a Client/Server model that can be easily achieved by using SOAP with ASMX or WCF. Just for the discussion sake ...
Post a Comment
Read more