Structural Facade
FACADE
Object Diagram for
Facade using Phone
Order Example
The Facade defines a unified, higher level interface to a
subsystem, that makes it easier to use. Consumers encounter a
Facade when ordering from a catalog. The consumer calls one
number and speaks with a customer service representative. The
customer service representative acts as a Facade, providing an
interface to the order fulfillment department, the billing
department, and the shipping department.
Structural Facade
Intent
Provide a unified interface to a set of interfaces in a
subsystem. Facade defines a higher-level interface
that makes the subsystem easier to use.
Problem:
A segment of the client community needs a simplified
interface to the overall functionality of a complex subsystem
Structural Facade
Illustration: Problem
Consider for example a programming envirnoment that gives
application access to its compiler subsystem. This
subsystem contains classes such as Scanner,
Parser,ProgramNode, ByteCodeStream, and
ProgramNodeBuilder that implements te Compiler. Some
Specialized applications might need to access these classes
directly.
But most clients of a compiler generally don’t care about
details like parsing and byte code generation; they merely
want to complier subsysem only complicate their task.
Structural Facade
Illustration : solution
Facade
Compiler class in the above can act as a façade, which will
provide higher-level interface that can shield clients form these
classes, the compiler subsystem also includes a Compiler class.
This class defines a unified interface to the compiler’s
functionality.
It offers client a single, simple interface to the compiler
subsystem. It glues together the classes that implement compiler
functionality without hiding them completely.
[Compiler façade makes easier for most programmers without
hiding the lower-level functionality form the few that need it]
Structural Facade
Illustration: solution
Structural Facade
Applicability
Use the Façade pattern when
• You want to provide a simple interface to a complex subsystem.
– To tackle the complexity of subsystem as they evolve
– Most patterns, when applied, result in more and smaller classes.
This makes the subsystem more reusable and easier to
customize, but it also becomes harder to use for clients that
don’t need to customize it.
– A façade can provide a simple default view of the subsystem
that is good enough for most client. Only clients needing more
customizability will need to look beyond the façade
Structural Facade
Applicability……...
Use the Façade pattern when
• Façade to decouple the subsystem for clients and other
subsystems, thereby promoting subsystem independence
and portability which tackle the disadvantage of
dependencies between clients and the implementation
classes on an abstraction.
• To layer your subsystem. Use façade to define an entry
point to each subsystem level. If subsystems are
dependent, then you can simplify the dependencies
between them by making them communicate with each
other solely through their facades.
Structural Facade
Structure
Facade
Subsystem classes
Structural Facade
Collaborations
• Clients communicate with the subsystem by sending
request to Façade, which forwards them to the appropriate
subsystem object(s). Although the subsystem objects
perform the actual work, the façade may have to do work
of its own to translate its interface to subsystem interfaces.
• Clients that user the façade don’t have to access its
subsystem objects directly.
Structural Facade
Consequences
• The Façade Patterns offers the following
benefits:
• 1. It shields client from subsystem components, thereby
reducing the number of objects that clients deal with and
making the subsystem easier to use.
• It promotes weak coupling between the subsystem and its
clients.
• It doesn’t prevent applications form using subsystem
classes if they need to. Thus you can choose between ease
of use and generality
Structural Facade
Model
