|
The Builder Pattern is a software design pattern. The intention is to separate the construction of a complex object from its representation so that the same construction process can create different representations. In software engineering, a design pattern is a general repeatable solution to a commonly occurring problem in software design. ...
Often, Builder Pattern builds Composite pattern, a structure pattern. This does not cite any references or sources. ...
Class Diagram
 Image File history File links No higher resolution available. ...
Builder Abstract interface for creating objects. An abstraction layer is a way of hiding the implementation details of a particular set of functionality. ...
Concrete Builder Provide implementation for Builder. Construct and assemble parts to build the objects. Make concrete and lay it.
Director The Director class is responsible for managing the correct sequence of object creation. It receives a Concrete Builder as a parameter and executes the necessary operations on it.
Product The complex object under construction.
Useful tips - Sometimes creational patterns are complementary: Builder can use one of the other patterns to implement which components get built. Abstract Factory, Builder, and Prototype can use Singleton in their implementations.
- Builder focuses on constructing a complex object step by step. Abstract Factory emphasizes a family of product objects (either simple or complex). Builder returns the product as a final step, but as far as the Abstract Factory is concerned, the product gets returned immediately.
- Builder often builds a Composite.
- Often, designs start out using Factory Method (less complicated, more customizable, subclasses proliferate) and evolve toward Abstract Factory, Prototype, or Builder (more flexible, more complex) as the designer discovers where more flexibility is needed.
A software design pattern, the Abstract Factory Pattern provides a way to encapsulate a group of individual factories that have a common theme. ...
A prototype pattern is a creational design pattern used in software development when the type of objects to create is determined by a prototypical instance, which is cloned to produce new objects. ...
In software engineering, the singleton pattern is a design pattern that is used to restrict instantiation of a class to one object. ...
This does not cite any references or sources. ...
The factory method pattern is an object-oriented design pattern. ...
Examples
Java /** "Product" */ class Pizza { private String dough = ""; private String sauce = ""; private String topping = ""; public void setDough(String dough) { this.dough = dough; } public void setSauce(String sauce) { this.sauce = sauce; } public void setTopping(String topping) { this.topping = topping; } } /** "Abstract Builder" */ abstract class PizzaBuilder { protected Pizza pizza; public Pizza getPizza() { return pizza; } public void createNewPizzaProduct() { pizza = new Pizza(); } public abstract void buildDough(); public abstract void buildSauce(); public abstract void buildTopping(); } /** "ConcreteBuilder" */ class HawaiianPizzaBuilder extends PizzaBuilder { public void buildDough() { pizza.setDough("cross"); } public void buildSauce() { pizza.setSauce("mild"); } public void buildTopping() { pizza.setTopping("ham+pineapple"); } } /** "ConcreteBuilder" */ class SpicyPizzaBuilder extends PizzaBuilder { public void buildDough() { pizza.setDough("pan baked"); } public void buildSauce() { pizza.setSauce("hot"); } public void buildTopping() { pizza.setTopping("pepperoni+salami"); } } /** "Director" */ class Waiter { private PizzaBuilder pizzaBuilder; public void setPizzaBuilder(PizzaBuilder pb) { pizzaBuilder = pb; } public Pizza getPizza() { return pizzaBuilder.getPizza(); } public void constructPizza() { pizzaBuilder.createNewPizzaProduct(); pizzaBuilder.buildDough(); pizzaBuilder.buildSauce(); pizzaBuilder.buildTopping(); } } /** A customer ordering a pizza. */ class BuilderExample { public static void main(String[] args) { Waiter waiter = new Waiter(); PizzaBuilder hawaiianPizzaBuilder = new HawaiianPizzaBuilder(); PizzaBuilder spicyPizzaBuilder = new SpicyPizzaBuilder(); waiter.setPizzaBuilder( hawaiianPizzaBuilder ); waiter.constructPizza(); Pizza pizza = waiter.getPizza(); } }
C# //Implementation in C#. class Pizza { string dough; string sauce; string topping; public Pizza() {} public void SetDough( string d){ dough = d ;} public void SetSauce( string s){ sauce = s ;} public void SetTopping( string t){ topping = t ;} } //Abstract Builder abstract class PizzaBuilder { protected Pizza pizza; public PizzaBuilder(){} public Pizza GetPizza(){ return pizza; } public void CreateNewPizza() { pizza = new Pizza(); } public abstract void buildDough(); public abstract void buildSauce(); public abstract void buildTopping(); } //Concrete Builder class HawaiianPizzaBuilder : PizzaBuilder { public override void buildDough() { pizza.SetDough("cross"); } public override void buildSauce() { pizza.SetSauce("mild"); } public override void buildTopping() { pizza.SetTopping("ham+pineapple"); } } //Concrete Builder class SpicyPizzaBuilder : PizzaBuilder { public override void buildDough() { pizza.SetDough("pan baked"); } public override void buildSauce() { pizza.SetSauce("hot"); } public override void buildTopping() { pizza.SetTopping("pepparoni+salami"); } } /** "Director" */ class Waiter { private PizzaBuilder pizzaBuilder; public void setPizzaBuilder (PizzaBuilder pb) { pizzaBuilder = pb; } public Pizza GetPizza() { return pizzaBuilder.GetPizza(); } public void constructPizza() { pizzaBuilder.CreateNewPizza(); pizzaBuilder.buildDough(); pizzaBuilder.buildSauce(); pizzaBuilder.buildTopping(); } } /** A customer ordering a pizza. */ class BuilderExample { public static void Main(String[] args) { Waiter waiter = new Waiter(); PizzaBuilder hawaiianPizzaBuilder = new HawaiianPizzaBuilder(); PizzaBuilder spicyPizzaBuilder = new SpicyPizzaBuilder(); waiter.setPizzaBuilder ( hawaiianPizzaBuilder ); waiter.constructPizza(); Pizza pizza = waiter.GetPizza(); } }
C++ // Implementation in C++. #include <iostream> #include <memory> // Product class Pizza { std::string dough; std::string sauce; std::string topping; public: Pizza() { } ~Pizza() { } void SetDough(const std::string& d) { dough = d; }; void SetSauce(const std::string& s) { sauce = s; }; void SetTopping(const std::string& t) { topping = t; } void ShowPizza() { std::cout << " Yummy !!!" << std::endl << "Pizza with Dough as " << dough << ", Sauce as " << sauce << " and Topping as " << topping << " !!! " << std::endl; } }; // Abstract Builder class PizzaBuilder { protected: std::auto_ptr<Pizza> pizza; public: PizzaBuilder() {} virtual ~PizzaBuilder() {} std::auto_ptr<Pizza> GetPizza() { return pizza; } void createNewPizzaProduct() { pizza.reset (new Pizza); } virtual void buildDough()=0; virtual void buildSauce()=0; virtual void buildTopping()=0; }; // ConcreteBuilder class HawaiianPizzaBuilder : public PizzaBuilder { HawaiianPizzaBuilder() : PizzaBuilder() {} ~HawaiianPizzaBuilder(){} void buildDough() { pizza->SetDough("cross"); } void buildSauce() { pizza->SetSauce("mild"); } void buildTopping() { pizza->SetTopping("ham and pineapple"); } }; // ConcreteBuilder class SpicyPizzaBuilder : public PizzaBuilder { SpicyPizzaBuilder() : PizzaBuilder() {} ~SpicyPizzaBuilder() {} void buildDough() { pizza->SetDough("pan baked"); } void buildSauce() { pizza->SetSauce("hot"); } void buildTopping() { pizza->SetTopping("pepperoni and salami"); } }; // Director class Waiter { PizzaBuilder* pizzaBuilder; public: Waiter() : pizzaBuilder(NULL) {} ~Waiter() { } void SetPizzaBuilder(PizzaBuilder* b) { pizzaBuilder = b; } std::auto_ptr<Pizza> GetPizza() { return pizzaBuilder->GetPizza(); } void ConstructPizza() { pizzaBuilder->createNewPizzaProduct(); pizzaBuilder->buildDough(); pizzaBuilder->buildSauce(); pizzaBuilder->buildTopping(); } }; // A customer ordering a pizza. int main() { Waiter waiter; HawaiianPizzaBuilder hawaiianPizzaBuilder; waiter.SetPizzaBuilder (&hawaiianPizzaBuilder); waiter.ConstructPizza(); std::auto_ptr<Pizza> pizza = waiter.GetPizza(); pizza->ShowPizza(); SpicyPizzaBuilder spicyPizzaBuilder; waiter.SetPizzaBuilder(&spicyPizzaBuilder); waiter.ConstructPizza(); pizza = waiter.GetPizza(); pizza->ShowPizza(); return EXIT_SUCCESS; }
Product Visual Prolog, also formerly known as PDC Prolog and Turbo Prolog, is a strongly typed object-oriented extension of Prolog. ...
interface pizza predicates setDough : (string Dough). setSauce : (string Sause). setTopping : (string Topping). end interface pizza class pizza : pizza end class pizza implement pizza facts dough : string := "". sauce : string := "". topping : string := "". clauses setDough(Dough) :- dough := Dough. clauses setSauce(Sauce) :- sauce := Sauce. clauses setTopping(Topping) :- topping := Topping. end implement pizza Abstract Builder interface pizzaBuilder predicates getPizza : () -> pizza Pizza. createNewPizzaProduct : (). predicates buildDough : (). buildSauce : (). buildTopping : (). end interface pizzaBuilder Visual Prolog does not support abstract classes, but we can create a support class instead: interface pizzaBuilderSupport predicates from pizzaBuilder getPizza, createNewPizzaProduct end interface pizzaBuilderSupport class pizzaBuilderSupport : pizzaBuilderSupport end class pizzaBuilderSupport implement pizzaBuilderSupport facts pizza : pizza := erroneous. clauses getPizza() = pizza. clauses createNewPizzaProduct() :- pizza := pizza::new(). end implement pizzaBuilderSupport ConcreteBuilder #1 class hawaiianPizzaBuilder : pizzaBuilder end class hawaiianPizzaBuilder implement hawaiianPizzaBuilder inherits pizzaBuilderSupport clauses buildDough() :- getPizza():setDough("cross"). clauses buildSauce() :- getPizza():setSauce("mild"). clauses buildTopping() :- getPizza():setTopping("ham+pineapple"). end implement hawaiianPizzaBuilder ConcreteBuilder #2 class spicyPizzaBuilder : pizzaBuilder end class spicyPizzaBuilder implement spicyPizzaBuilder inherits pizzaBuilderSupport clauses buildDough() :- getPizza():setDough("pan baked"). clauses buildSauce() :- getPizza():setSauce("hot"). clauses buildTopping() :- getPizza():setTopping("pepperoni+salami"). end implement spicyPizzaBuilder Director interface waiter predicates setPizzaBuilder : (pizzaBuilder PizzaBuilder). getPizza : () -> pizza Pizza. predicates constructPizza : (). end interface waiter class waiter : waiter end class waiter implement waiter facts pizzaBuilder : pizzaBuilder := erroneous. clauses setPizzaBuilder(PizzaBuilder) :- pizzaBuilder := PizzaBuilder. clauses getPizza() = pizzaBuilder:getPizza(). clauses constructPizza() :- pizzaBuilder:createNewPizzaProduct(), pizzaBuilder:buildDough(), pizzaBuilder:buildSauce(), pizzaBuilder:buildTopping(). end implement waiter A customer ordering a pizza. goal Hawaiian_pizzabuilder = hawaiianPizzaBuilder::new(), Waiter = waiter::new(), Waiter:setPizzaBuilder(Hawaiian_pizzabuilder), Waiter:constructPizza(), Pizza = Waiter:getPizza().
perl ## Product package pizza; sub new { return bless { dough => undef, sauce => undef, topping => undef }, shift; } sub set_dough { my( $self, $dough ) = @_; $self->{dough} = $dough; } sub set_sauce { my( $self, $sauce ) = @_; $self->{sauce} = $sauce; } sub set_topping { my( $self, $topping ) = @_; $self->{topping} = $topping; } 1; ## Abstract builder package pizza_builder; sub new { return bless { pizza => undef }, shift; } sub get_pizza { my( $self ) = @_; return $self->{pizza}; } sub create_new_pizza_product { my( $self ) = @_; $self->{pizza} = pizza->new; } # This is what an abstract method could look like in perl... sub build_dough { croak("This method must be overridden."); } sub build_sauce { croak("This method must be overridden."); } sub build_topping { croak("This method must be overridden."); } 1; ## Concrete builder package hawaiian_pizza_builder; use base qw{ pizza_builder }; sub build_dough { my( $self ) = @_; $self->{pizza}->set_dough("cross"); } sub build_sauce { my( $self ) = @_; $self->{pizza}->set_sauce("mild"); } sub build_topping { my( $self ) = @_; $self->{pizza}->set_topping("ham+pineapple"); } 1; ## Concrete builder package spicy_pizza_builder; use base qw{ pizza_builder }; sub build_dough { my( $self ) = @_; $self->{pizza}->set_dough("pan baked"); } sub build_sauce { my( $self ) = @_; $self->{pizza}->set_sauce("hot"); } sub build_topping { my( $self ) = @_; $self->{pizza}->set_topping("pepperoni+salami"); } 1; ## Director package waiter; sub new { return bless { pizza_builder => undef }, shift; } sub set_pizza_builder { my( $self, $builder ) = @_; $self->{pizza_builder} = $builder; } sub get_pizza { my( $self ) = @_; return $self->{pizza_builder}->get_pizza; } sub construct_pizza { my( $self ) = @_; $self->{pizza_builder}->create_new_pizza_product; $self->{pizza_builder}->build_dough; $self->{pizza_builder}->build_sauce; $self->{pizza_builder}->build_topping; } 1; ## Lets order pizza (client of Director/Builder) package main; my $waiter = waiter->new; my $hawaiian_pb = hawaiian_pizza_builder->new; my $spicy_pb = spicy_pizza_builder->new; $waiter->set_pizza_builder( $hawaiian_pb ); $waiter->construct_pizza; my $pizza = $waiter->get_pizza; print "Serving a nice pizza with:n"; for (keys %$pizza) { print " $pizza->{$_} $_n"; } 1;
External links | Design patterns in Design Patterns | Creational: Abstract factory • Builder • Factory • Prototype • Singleton
In software engineering, a design pattern is a general repeatable solution to a commonly occurring problem in software design. ...
This article is about the book by Gamma et al. ...
A software design pattern, the Abstract Factory Pattern provides a way to encapsulate a group of individual factories that have a common theme. ...
The factory method pattern is an object-oriented design pattern. ...
A prototype pattern is a creational design pattern used in software development when the type of objects to create is determined by a prototypical instance, which is cloned to produce new objects. ...
In software engineering, the singleton pattern is a design pattern that is used to restrict instantiation of a class to one object. ...
Structural: Adapter • Bridge • Composite • Decorator • Façade • Flyweight • Proxy
In computer programming, the adapter design pattern (often referred to as the wrapper pattern or simply a wrapper) adapts one interface for a class into one that a client expects. ...
The bridge pattern is a design pattern used in software engineering which is meant to decouple an abstraction from its implementation so that the two can vary independently (Gamma et. ...
This does not cite any references or sources. ...
In object-oriented programming, a decorator pattern is a design pattern. ...
The façade pattern is an object-oriented design pattern. ...
Flyweight is a software design pattern. ...
// In computer programming, the proxy pattern is a software design pattern. ...
Behavioral: Chain of responsibility • Command • Interpreter • Iterator • Mediator • Memento • Observer • State • Strategy • Template method • Visitor In Object Oriented Design, the chain-of-responsibility pattern is a design pattern consisting of a source of command objects and a series of processing objects. ...
In object-oriented programming, the Command pattern is a design pattern in which objects are used to represent actions. ...
In computer programming, the interpreter pattern is a particular design pattern. ...
In object-oriented programming, an iterator is an object allowing one to sequence through all of the elements or parts contained in some other object, typically a container or list. ...
The mediator pattern is a software design pattern that provides a unified interface to a set of interfaces in a subsystem. ...
The memento pattern is a software design pattern that provides the ability to restore an object to its previous state (undo by rollback). ...
The observer pattern (sometimes known as publish/subscribe) is a design pattern used in computer programming to observe the state of an object in a program. ...
A behavioral software design pattern, state pattern is used in computer programming to represent the state of an object. ...
In computer programming, the strategy pattern is a particular software design pattern, whereby algorithms can be selected on-the-fly at runtime. ...
Template method: UML class diagram. ...
In object-oriented programming and software engineering, the visitor design pattern is a way of separating an algorithm from an object structure. ...
| | 
Feeds |
Contact