PBCST304 / OOPS / MOD 4/ SOLID PRINCIPLES

The SOLID principles are five important rules that help make software design better. They make the code easier to understand, change, and reuse. These rules are: • Single Responsibility Principle (SRP) – A class should do only one job. • Open/Closed Principle – Code should be open to adding new features but closed to changing existing code. • Liskov Substitution Principle (LSP) – You should be able to use a child class wherever a parent class is used, without problems. • Interface Segregation Principle (ISP) – Don’t force a class to use methods it doesn’t need. • Dependency Inversion Principle (DIP) – Depend on abstractions (interfaces), not on concrete (real) classes.