Question

Select the option that best describes the Dependency Inversion Principle.

a. High-level modules should not depend on low-level modules.
b. Abstractions should not depend on details.
c. Classes should depend on interfaces.
d. Inheritance should be avoided.

Answer 1

The best description for the Dependency Inversion Principle is that abstractions should not depend on details, indicating that high-level modules should not depend upon low-level modules, but both should depend on abstractions for better flexibility and maintainability of software.

Step-by-step explanation:

The option that best describes the Dependency Inversion Principle is: Abstractions should not depend on details. This principle is one of the five SOLID principles of object-oriented design and programming which aims to reduce dependencies among the code modules.

The Dependency Inversion Principle states two key points:

1. High-level modules should not depend on low-level modules. Both should depend on abstractions.
2. Abstractions should not depend upon details. Details should depend upon abstractions.

This principle facilitates a modular architecture where higher-level components, which provide complex logic, are separated from the lower-level components that provide utility features. By depending on interfaces or abstract classes rather than concrete classes, the software becomes more flexible, extensible, and easier to maintain.