Scribd
Upload
13 views2 pages

Gof Design Patterns: Adapter Polymorphic Decorator

The Facade design pattern provides a simplified interface to access a complex subsystem. It defines a Facade object that delegates to interfaces in the subsystem and may perform additional functionality. This minimizes dependencies on the subsystem by allowing clients to work through the Facade object instead of accessing subsystem classes directly.

Uploaded by

nishant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
13 views2 pages

Gof Design Patterns: Adapter Polymorphic Decorator

The Facade design pattern provides a simplified interface to access a complex subsystem. It defines a Facade object that delegates to interfaces in the subsystem and may perform additional functionality. This minimizes dependencies on the subsystem by allowing clients to work through the Facade object instead of accessing subsystem classes directly.

Uploaded by

nishant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Overview[edit]

The Facade [1] design pattern is one of the twenty-three well-known GoF design
patterns that describe how to solve recurring design problems to design flexible and
reusable object-oriented software, that is, objects that are easier to implement,
change, test, and reuse.

What problems can the Facade design pattern solve? [2]

 To make a complex subsystem easier to use, a simple interface should be


provided for a set of interfaces in the subsystem.
 The dependencies on a subsystem should be minimized.
Clients that access a complex subsystem directly refer to (depend on) many different
objects having different interfaces (tight coupling), which makes the clients hard to
implement, change, test, and reuse.

What solution does the Facade design pattern describe?

Define a Facade object that

 implements a simple interface in terms of (by delegating to) the interfaces in the
subsystem and
 may perform additional functionality before/after forwarding a request.
This enables to work through a Facade object to minimize the dependencies on a
subsystem.
See also the UML class and sequence diagram below.

Usage[edit]
A Facade is used when an easier or simpler interface to an underlying object is
desired.[3] Alternatively, an adapter can be used when the wrapper must respect a
particular interface and must support polymorphic behavior. A decorator makes it
possible to add or alter behavior of an interface at run-time.

Pattern Intent

Converts one interface to another so that it matches what the client is


Adapter
expecting

Decorator Dynamically adds responsibility to the interface by wrapping the original code

Facade Provides a simplified interface

The facade pattern is typically used when

 a simple interface is required to access a complex system,


 a system is very complex or difficult to understand,
 an entry point is needed to each level of layered software, or
 the abstractions and implementations of a subsystem are tightly coupled.
Structure[edit]
UML class and sequence diagram[edit]

A sample UML class and sequence diagram for the Facade design pattern.

In this UML class diagram, the Client class doesn't access the subsystem classes
directly. Instead, the Client works through a Facade class that implements a simple
interface in terms of (by delegating to) the subsystem classes (Class1, Class2,
and Class3). The Client depends only on the simple Facade interface and is
independent of the complex subsystem.[4]

The sequence diagram shows the run-time interactions: The Client object works
through a Facade object that delegates the request to the Class1, Class2,
and Class3 instances that perform the

You might also like