SOLID is an acronym coined by Michael Feathers for the following 5 design principles published by Robert Martin, to guide the developers when doing OOP (Object Oriented Programming) and code design:
A class should only have a single responsibility, that is, only changes to one part of the software's specification should be able to affect the specification of the class.
Read more: S: Single Responsibility Principle [ UNDER CONSTRUCTION ]
Software entities should be open for extension, but closed for modification.
Read more: O: Open/Closed Principle [ UNDER CONSTRUCTION ]
Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
Read more: L: Liskov's Substitution Principle [ UNDER CONSTRUCTION ]
Many client-specific interfaces are better than one general-purpose interface.
Read more: I: Interface Segregation Principle [ UNDER CONSTRUCTION ]
Depend on abstractions, not on concretions.
Read more: D: Dependency Inversion Principle [ UNDER CONSTRUCTION ]