Creational Pattern - Builder

Creational Pattern - Builder
AuthorDate Of SubmissionUser Level
Ashish Jaiman02/19/2002Beginner

Reference: E. Gamma et al., "Design Patterns: Elements of Reusable Object-Oriented Software" ISBN 0-201-63361-2, Addison Wesley, 1995. 

Source Code: CreationalPatterBuilderCode.zip 2 KB

The Builder pattern allows a client object to construct a complex object by specifying only its type and content. The client is shielded from the details of the object抯 construction.

It is a pattern for step-by-step creation of a complex object so that the same construction process can create different representations is the routine in the builder pattern that also makes for finer control over the construction process. All the different builders generally inherit from an abstract builder class that declares the general functions to be used by the director to let the builder create the product in parts.

Builder has a similar motivation to the abstract factory but, whereas in that pattern, the client uses the abstract factory class methods to create its own object, in Builder the client instructs the builder class on how to create the object and then asks it for the result. How the class is put together is up to the Builder class. It's a subtle difference.

The Builder pattern is applicable when the algorithm for creating a complex object should be independent of the parts that make up the object and how they are assembled and the construction process must allow different representations for the object that抯 constructed.

Example

Below is an example of creating a House, the clients asks the Director (CDirector class) to create a House by calling BuildHouse method which takes a boolean parameter (blnBackyard), the director then creates an Apartment (Concrete Builder) if the blnBackyard is false or a Single Family Home (Concrete Builder) if the blnBackyard is true (both of them implements IHouse interface) and returns IHouse (Abstract Builder) Interface.

The director does the complex building of a House and the client gets back IHouse interface that it codes against without worrying about the creation of House, Rooms, backyard etc.

C# Implementation

using System;
using System.Collections; 

public interface IHouse
{
           
bool GetBackyard();
           
long NoOfRooms();
           
string  Discription();

public class CApt:IHouse
{          private bool mblnBackyard;
           
private Hashtable Rooms;
           
public CApt()
           
{          CRoom room; 
                       
Rooms = new Hashtable();
                       
room = new CRoom();
                       
room.RoomName = "Master Bedroom";
                       
Rooms.Add ("room1",room); 

                        room = new CRoom();
       
room.RoomName = "Second Bedroom";
                       
Rooms.Add ("room2",room); 

                        room = new CRoom();
                       
room.RoomName = "Living Room";
                       
Rooms.Add ("room3",room);                       

                        mblnBackyard = false;
           

            public bool GetBackyard()
           
{
                       
return mblnBackyard;
           
}
           
public long NoOfRooms()
           
{
                       
return Rooms.Count;
           
}
           
public string  Discription()
           
{
                       
IDictionaryEnumerator myEnumerator  = Rooms.GetEnumerator();
       
string strDiscription;
       
strDiscription = "This is an Apartment with " + Rooms.Count + " Rooms /n";
       
strDiscription = strDiscription + "This Apartment doesn't have a backyard /n";              
                        while (myEnumerator.MoveNext())
                       
{
                                   
strDiscription = strDiscription + "/n" + myEnumerator.Key + "/t" + ((CRoom)myEnumerator.Value).RoomName;
                       
}
       
return strDiscription;
           
}

public class CSFH:IHouse
{   private bool mblnBackyard;
           
private Hashtable Rooms;
           
public CSFH()
           
{
                       
CRoom room;
                       
Rooms = new Hashtable(); 

                        room = new CRoom();
                       
room.RoomName = "Master Bedroom";
                       
Rooms.Add ("room1",room); 

                        room = new CRoom();
                       
room.RoomName = "Second Bedroom";
                       
Rooms.Add ("room2",room); 

                        room = new CRoom();
                       
room.RoomName = "Third Room";
                       
Rooms.Add ("room3",room);                       

                        room = new CRoom();
                       
room.RoomName = "Living Room";
                       
Rooms.Add ("room4",room); 

                        room = new CRoom();
                       
room.RoomName = "Guest Room";
                       
Rooms.Add ("room5",room); 

                        mblnBackyard = true; 

           

            public bool GetBackyard()
           
{
                       
return mblnBackyard;
           
}
           
public long NoOfRooms()
           
{
                       
return Rooms.Count;
           
}

            public string  Discription()
           
{
                       
IDictionaryEnumerator myEnumerator  = Rooms.GetEnumerator();
                       
string strDiscription;
                       
strDiscription = "This is an Single Family Home with " + Rooms.Count + " Rooms /n";
                       
strDiscription = strDiscription + "This house has a backyard /n";
       
while (myEnumerator.MoveNext())
                       
{
                                   
strDiscription = strDiscription + "/n" + myEnumerator.Key + "/t" + ((CRoom)myEnumerator.Value).RoomName;
                       
}     
                       
return strDiscription;
           
}

public interface IRoom
{
           
string RoomName{get;set;}

public class CRoom:IRoom
{
           
private string mstrRoomName;
           
public string RoomName
           
{
                       
get
                       
{
                                   
return mstrRoomName;
                       
}
                       
set
                       
{
                                   
mstrRoomName = value;
                       
}
           
}

public class CDirector
{
           
public IHouse BuildHouse(bool blnBackyard)
           
{
                       
if (blnBackyard)
                       
{
                                   
return new CSFH();
                       
}
                       
else
                       
{
                                   
return new CApt();
                       
}
           
}

public class Client
{
           
static void Main(string[] args)
           
{
                       
CDirector objDirector = new CDirector();
                       
IHouse objHouse;
                       
objHouse = objDirector.BuildHouse(bool.Parse(args[0]));       
                       
Console.WriteLine(objHouse.Discription());
           
}
}


  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
资源包主要包含以下内容: ASP项目源码:每个资源包中都包含完整的ASP项目源码,这些源码采用了经典的ASP技术开发,结构清晰、注释详细,帮助用户轻松理解整个项目的逻辑和实现方式。通过这些源码,用户可以学习到ASP的基本语法、服务器端脚本编写方法、数据库操作、用户权限管理等关键技术。 数据库设计文件:为了方便用户更好地理解系统的后台逻辑,每个项目中都附带了完整的数据库设计文件。这些文件通常包括数据库结构图、数据表设计文档,以及示例数据SQL脚本。用户可以通过这些文件快速搭建项目所需的数据库环境,并了解各个数据表之间的关系和作用。 详细的开发文档:每个资源包都附有详细的开发文档,文档内容包括项目背景介绍、功能模块说明、系统流程图、用户界面设计以及关键代码解析等。这些文档为用户提供了深入的学习材料,使得即便是从零开始的开发者也能逐步掌握项目开发的全过程。 项目演示与使用指南:为帮助用户更好地理解和使用这些ASP项目,每个资源包中都包含项目的演示文件和使用指南。演示文件通常以视频或图文形式展示项目的主要功能和操作流程,使用指南则详细说明了如何配置开发环境、部署项目以及常见问题的解决方法。 毕业设计参考:对于正在准备毕业设计的学生来说,这些资源包是绝佳的参考材料。每个项目不仅功能完善、结构清晰,还符合常见的毕业设计要求和标准。通过这些项目,学生可以学习到如何从零开始构建一个完整的Web系统,并积累丰富的项目经验。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值