Difference between revisions of "Facade"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Added category) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 66: | Line 66: | ||
<references/> | <references/> | ||
[[Category:Design_patterns]] [[Category:Patlet]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | [[Category:Design_patterns]] [[Category:Patlet]] [[Category:Software Design Patterns]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | ||
Latest revision as of 12:09, 15 May 2017
| Facade | |
| Contributors | Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides |
|---|---|
| Last modification | May 15, 2017 |
| Source | Gamma, Helm, Johnson & Vlissides (1995)[1], Facade Pattern (2016)[2] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
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. This can be used to simplify a number of complicated object interactions into a single interface.[1][2]
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 Gamma, E., Helm, R., Johnson, R. & Vlissides, J. (1995). Design Patterns: elements of reusable object-oriented software. Addison-Wesley: Boston, MA.ISBN 0-201-63361-2.
- ↑ 2.0 2.1 Facade Pattern. (2016). Retrieved November 15, 2016 from http://wiki.c2.com/?FacadePattern.