Facade Pattern

Question 1

Facade

Answer 1

A single class that provides a simplified, high-level interface to a complex subsystem. It delegates client requests to the appropriate internal classes.

Question 2

Client

Answer 2

The part of the system that interacts with the facade. It has no direct knowledge of the underlying subsystem classes.

Question 3

Subsystem Classes

Answer 3

The internal components or classes of the large, complex system. These are hidden from the client and accessed only through the facade.

Question 4

facadeFunction()

Answer 4

A method in the Facade class that coordinates calls to subsystem methods.

Question 5

Low Coupling

Answer 5

Client remains independent of the internal workings of the subsystem. This allows changes within the system without affecting the client code.

Question 6

Reusability

Answer 6

The ability to reuse the complex system in new applications or with new clients by simply creating new facade interfaces.

Question 7

Maintainability

Answer 7

The ease of modifying the underlying system without disrupting the client. The facade acts as a buffer.

Question 8

Structural Pattern

Answer 8

A type of design pattern concerned with how classes and objects are composed to form larger structures. Facade belongs to this category.

Question 9

Facade Pattern

Answer 9

A structural design pattern that provides a simplified, high-level interface to a complex system of classes, functions, or subsystems.

Question 10

3 Roles in the Facade Pattern

Answer 10

Client
Facade
Subsystem Classes