SOLID stands for
S - Single Responsibility
O - Open Closed
L - Liskov Substitution
I - Interface Segregation
D - Dependency Inversion
Single Reponsibility
A class can have a single responsibility at a time. Example Consider a class that sends an email to the respective recipients. It is inappropriate for the class to fetch the list of users who have access to a certain feature.
Open Closed
Software Entities like classes, modules & functions should be open for extension, but closed for modification.
Liskov Substitution
Functions that use pointers to base classes must be able to use objects of derived classes without knowing it.
Interface seggregation
It says that no client should depend on object/interfaces that is of no use to it. for ex. An email sending service may not depend on a user class.
Dependency Inversion
In object-oriented design, the dependency inversion principle is a specific form of decoupling classes. Example : High-level modules should not depend on low-level modules.
S - Single Responsibility
O - Open Closed
L - Liskov Substitution
I - Interface Segregation
D - Dependency Inversion
Single Reponsibility
A class can have a single responsibility at a time. Example Consider a class that sends an email to the respective recipients. It is inappropriate for the class to fetch the list of users who have access to a certain feature.
Open Closed
Software Entities like classes, modules & functions should be open for extension, but closed for modification.
Liskov Substitution
Functions that use pointers to base classes must be able to use objects of derived classes without knowing it.
Interface seggregation
It says that no client should depend on object/interfaces that is of no use to it. for ex. An email sending service may not depend on a user class.
Dependency Inversion
In object-oriented design, the dependency inversion principle is a specific form of decoupling classes. Example : High-level modules should not depend on low-level modules.
