Understanding SOLID Principles
S : Single responsibility principle
Each software module should have one and only one reason to change.
https://dotnettutorials.net/lesson/single-responsibility-principle/
O : Open/Closed Principle
Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification.
https://dotnettutorials.net/lesson/open-closed-principle/
L : Liskov Substitution Principle
Subtypes must be substitutable for their base type.
https://dotnettutorials.net/lesson/liskov-substitution-principle/
I : Interface Segregation Principle :
Clients should not be forced to depend on methods they do not use.
https://dotnettutorials.net/lesson/interface-segregation-principle/
D : Dependency Inversion Principle
High-level modules should not depend on low-level modules. Both should depend on abstraction
https://dotnettutorials.net/lesson/dependency-inversion-principle/
Comments
Post a Comment