The principle states: * High-level modules should not depend on low-level modules. Both should depend on abstractions (e.g., interfaces). * Abstractions should not depend on details. Details (concrete implementations) should depend on abstractions. In object-oriented design, the dependency inversion principle is a specific form of decoupling software modules. When following this principle, the conventional dependency relationships established from high-level, policy-setting modules to low-level, dependency modules are reversed, thus rendering high-level modules independent of the low-level module implementation details.