Tuesday, April 5, 2011

Design Pattern : Facade

It falls into structural pattern categories. The Facade Pattern defines a higher level interface to a subsystem, that makes it easier to use. It provides unified interface to a set of interfaces in a subsystem.

Use the Facade 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 of the clients. Only clients needing more customizability will need to look beyond the façade

•Facade 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.

The structure of the Façade Pattern looks as below


•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.

The Facade 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

Illustration: Problem

Consider for example a programming environment that gives application access to its compiler subsystem. This subsystem contains classes such as Scanner, Parser,ProgramNode, ByteCodeStream, and ProgramNodeBuilder that implements the 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.

Illustration : solution


Compiler class in the above can act as a facade, 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]

Class Diagram Solution:


1 comment:

Darshan Gopinath said...

Good work! That was information much needed!!