In this video we will discuss
1. Dependency Inversion Principle Introduction
2. Understand the intention of DIP usage
In the first video of SOLID Introduction we have understood that D in SOLID stands for Dependency Inversion Principle which is also known as DIP
The Dependency Inversion Principle introduced by Robert C Martin states that
High-level modules should not depend on low-level modules. Both should depend on abstractions.
AND
Abstractions should not depend on details. Details should depend on abstractions.
To simplify this we can state that while designing the interaction between a high-level module and a low-level one, the interaction should be thought of as an abstract interaction between them.
Usage Intention : Before understanding the intention of usage, let’s try to understand a traditional application architecture implementation.
During the process of the application design, lower-level components are designed to be consumed by higher-level components which enable increasingly complex systems to be built. In this Process of Composition, higher-level components depend directly upon lower-level components to achieve some task.
Text version of the video
Slides
SOLID Design Principles Tutorial
SOLID Design Principles Text Articles & Slides
All Dot Net and SQL Server Tutorials in English
All Dot Net and SQL Server Tutorials in Arabic
