The Facade design pattern provides a solution:
Define a separate Facade object that provides an unified interface for a set of interfaces in a subsystem.
Work through a Facade to minimize dependencies on a subsystem.
Describing the Facade design in more detail is the theme of the following sections.
See Applicability section for all problems Facade can solve.

• The key idea in this pattern is to work through a separate Facade object that provides a simple interface for (already existing) objects in a subsystem.
  Clients can either work with a subsystem directly or its Facade.
• Define a separate Facade object:
  • Define an unified interface for a set of interfaces in a subsystem (Facade).
  • Implement the Facade interface
    in terms of (by delegating to) the interfaces in the subsystem.
• Working through a Facade object minimizes dependencies on a subsystem (loose coupling), which makes clients easier to implement, change, test, and reuse.
  Clients that need more lower-level functionalities can access the objects in the subsystem directly.