Simple, Understandable definition of solid principle

SOLID
# S -> single responsibility 
     Each componenet need to have it's one responsible , Need to have multiple component as the feture

# O ->   Open/Close Principle 
    software entities should be open for the extension but closed for the modification

# L ->   Liskov Substitution Principle 
    Functions that are use pointers or references to base classes must be able to use objects of derived classes without knowing it.
    child class shouldn't break the parent class object 

# I ->   Interface segregation Service
    Many client-specific interfaces are better than one general purpose interface

# D ->   Dependency Inversion Principle
    High-level modules should not depend on low-level modules 
    both should depend on abstraction