fasáda

Uses your system voice; voice and rate in settings.

The name shown is in cs. The article below is in English and is not a translation.

Q428170Snapshot

≈ 6 min read

Names in other languages

  • MagyarHomlokzat programtervezési minta
  • eopatroneo de fasado
  • العربيةنمط واجهة المبنىنمط فسّاد, نمط الواجهة, facade pattern
  • Englishfacade patternfaçade pattern
  • ItalianoFaçade pattern
  • ไทยฟะซาดแพตเทิร์น
  • Tiếng ViệtFacade pattern
  • mnФакэдэ загвар
  • nbfasademønster
  • 日本語Facade パターン
  • فارسیالگوی نما
  • DeutschFassade
  • bgФасада
  • caFacade
  • Češtinafasáda
  • EspañolFacade
  • FrançaisFaçade
  • glFacade
  • 한국어퍼사드 패턴
  • NederlandsFaçade
  • PolskiFasada
  • Portuguêsfaçade
  • slfasada
  • hyՃակատ
  • kyФасад
  • РусскийФасад
  • Svenskafasadfasadmönster
  • УкраїнськаФасад
  • 中文外觀模式

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

The facade pattern (also spelled façade) is a software design pattern commonly used in object-oriented programming. Analogous to a façade in architecture, it is an object that serves as a front-facing interface masking more complex underlying or structural code. A facade can:

Developers often use the facade design pattern when a system is very complex or difficult to understand because the system has many interdependent classes or because its source code is unavailable. This pattern hides the complexities of the larger system and provides a simpler interface to the client. It typically involves a single wrapper class that contains a set of members required by the client. These members access the system on behalf of the facade client and hide the implementation details.

Overview

edit edit source

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 edit source

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
Adapter Converts one interface to another so that it matches what the client is 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.

A good example of where a facade is used is in register indexed values like Modbus, I2C or Special function register.

Structure

edit edit source

UML class and sequence diagram

edit edit source 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 request.

UML class diagram

edit edit source

Facade
The facade class abstracts Packages 1, 2, and 3 from the rest of the application.
Clients
The objects are using the facade pattern to access resources from the packages.

See also

edit edit source

References

edit edit source
  1. ^ Gamma, Erich; Helm, Richard; Johnson, Ralph; Vlissides, John (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison Wesley. pp. 185ff. ISBN 0-201-63361-2.
  2. ^ "The Facade design pattern - Problem, Solution, and Applicability". w3sDesign.com. Archived from the original on 2020-06-12. Retrieved 2017-08-12.
  3. ^ Freeman, Eric; Freeman, Elisabeth; Sierra, Kathy; Bates, Bert (2004). Hendrickson, Mike; Loukides, Mike (eds.). Head First Design Patterns. Vol. 1. O'Reilly. pp. 243, 252, 258, 260. ISBN 978-0-596-00712-6.
  4. ^ "The Facade design pattern - Structure and Collaboration". w3sDesign.com. Archived from the original on 2020-06-12. Retrieved 2017-08-12.
edit edit source The Wikibook Computer Science Design Patterns has a page on the topic of: Facade implementations in various languages Wikimedia Commons has media related to Facade pattern. Software design patternsGang of Four
patterns
Concurrency
patterns
Architectural
patterns
Other
patterns Books People Communities See also

Text derived from https://en.wikipedia.org/w/index.php?oldid=1345700199 under CC BY-SA 4.0; modifications have been made.

Provenance

snapshot facade-pattern-049349-13327cdeb344ab1b · hash 13327cdeb344ab1bb2b2cfd7dbca462253d758e4cf35c15e09d1f9be9298d3aa · captured 1774625553.0 · version history

Cite this page as: encyclopegia.org, “fasáda”, snapshot facade-pattern-049349-13327cdeb344ab1b. https://encyclopegia.org/a/facade-pattern