This document discusses the fifth principle of SOLID, Dependency Inversion. It states that high-level modules should not depend on low-level modules, but instead both should depend on abstractions. Additionally, abstractions should not depend on details, but details should depend on abstractions. Dependency injection is described as giving components their dependencies through constructors, methods, or fields. Advantages of dependency injection include decoupling, testability, and reusability, while disadvantages include increased code complexity.

1. Dependency Inversion
S.O.L.I.D Fifth principle

2. What are we going to talk about?
- What is S.O.L.I.D
- Dependency inversion and dependency injection
- Code examples of dependency injection

3. S.O.L.I.D
S.O.L.I.D stands for Five basic principles of object-oriented
programming and design. Those principles are:
1.Single responsibility
2.Open/Closed
3.Liskov substitution
4.Interface segregation
5.Dependency inversion

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

8. Dependency Injection
Dependency injection is where components are given their
dependencies through their constructors, methods, or directly
into fields.
- Constructor injection
- Setter injection
- Property injection
- Reflection injection

9. Code Examples

10. Advantages
Decoupling
Testability
Reusability

11. Disadvantage
s
● Code Complexity

12. Questions?
Links:
https://www.novoda.com/blog/designing-something-
solid/?utm_source=Android+Weekly&utm_campaign=309f4188e7-
Android_Weekly_229&utm_medium=email&utm_term=0_4eb677ad19-309f4188e7-337883869
https://scotch.io/bar-talk/s-o-l-i-d-the-first-five-principles-of-object-oriented-design
https://realm.io/news/donn-felker-solid-part-1/