Core Principle

Summary Principle Name SOLID Principles Acronym SOLID Principle Type SOLID Purpose Implementing Design Patterns Factory Pattern Related Principles Single Responsibility Principle(SRP) Open/Closed Principle(OCP) Liskov Substitution Principle(LSP) Interface Segregation Principle(ISP) Dependency Inversion Principle(DIP) Definition SOLID Principles refer to a collection of five(5) individual principles. The term “SOLID” is derived from the first letter of each of … Read more

This principle says- High-level modules should not depend directly on low-level modules. Instead, both should depend on abstractions (abstract class or interface) High-level modules are those that contain the complex implementation logic. Low-level modules are those modules that deal with the specific implementation.

The Interface Segregation Principle says- We should create smaller and more specific interfaces, instead of having large monolithic interface with many methods. Each interface should only contain methods that are relevant to the purpose of the interface. Then classes can implement one or more of those interfaces are required. Also, a class should only implement the interface(s) which are required.

Liskov Substitution Principle(LSP) says-Objects of superclass should be replaceable by the objects of a subclass, without affecting the correctness of the program. When subclass object replaces super class object, the result might not be exactly same, but rather it – should be consistent, has the same intended behavior, should not break any functionality.

Open/Close Principle(OCP) says- Software entities(classes, modules, etc.), should be open for extension but closed for modification. It means that once a software entity is defined and implemented, we should not directly change it to add new functionality. Instead, we should extend it using inheritance or interfaces to accommodate new behavior or functionality.

This Single Responsibility Principle(SRP) says- A class should have only one responsibility (and a single reason for it to be changed). Class should have only one job/responsibility, and that job/responsibility should be encapsulated inside that class.

The “Program to Interfaces, Not Implementations” principle is- Design your code to depend on interfaces, and avoid the dependency on concrete classes. The process is to define interfaces that specify required behavior. Classes then implement the interface and allow the system to extend and modify the implementation, without changing the dependent code.

The Composition Over Inheritance(COI) principle is- We should prefer composing objects while creating a complex object, rather than relying on inheritance. This means, whenever possible we should avoid hierarchies of class inheritance, and compose objects of a class when we need it.

This Encapsulate What Varies(EWV) principle is- Isolate the part of the code that is likely to be changed later, by encapsulating them. So that the encapsulation works as a shield for the rest of the code.