SOLID Principles

Transcript

1. !Smelly Code clean development
2. S.O.L.I.D
3. A term describing a collection of design principles for good code that was coined by Robert C. Martin aka Uncle Bob What?
4. Why? help developers facilitate the development of maintainable and extensible systems
5. OOP COMPOSITION over INHERITANCE Polymorphism encapsulate
6. OOP encapsulate
7. encapsulate
8. encapsulate
9. encapsulate
10. encapsulate
11. encapsulate
12. encapsulate
13. S SINGLE RESPONSIBILITY PRINCIPLE A class should have only one reason to change.
14. SINGLE RESPONSIBILITY PRINCIPLE
15. SINGLE RESPONSIBILITY PRINCIPLE
16. O OPEN-CLOSED PRINCIPLE You should be able to extend a class behavior, without modifying it.
17. This class violates the Open/Closed principle. It is not closed for modification and it is not open to extension. Every time a new shape comes along we have to modify the OPEN-CLOSED PRINCIPLE
19. OPEN-CLOSED PRINCIPLE
20. L LISKOV SUBSTITUTION PRINCIPLE Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
21. LISKOV SUBSTITUTION PRINCIPLE
23. I INTERFACE SEGREGATION PRINCIPLE Make fine grained interfaces that are client-specific.
26. D DEPENDENCY INVERSION PRINCIPLE High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions. Depend on Abstractions. Do not depend on concretions.
29. https://realm.io/news/donn-felker-solid-part-1/ http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod