SOLID Principles Quiz

SOLID Principles

Single Responsibility Principle (S.R.P)

• A class or module should have only one reason to change, i.e., it should have a single responsibility or task.
• This principle aims to ensure that a class is not overly complex and has a single, well-defined purpose.

Open/Closed Principle (O.C.P)

• A software entity (such as a class, module, or function) should be open for extension but closed for modification.
• This means that you can add new functionality without modifying the existing code.

Liskov Substitution Principle (L.S.P)

• Derived classes should be substitutable for their base classes, i.e., any code that uses a base class should be able to work with a subclass without knowing the difference.
• This principle ensures that inheritance is used correctly and that subclasses are true substitutes for their base classes.

Interface Segregation Principle (I.S.P)

• A client should not be forced to depend on interfaces it does not use, i.e., clients should not be forced to implement interfaces that have operations they do not need.
• This principle aims to ensure that interfaces are designed to meet the needs of specific clients, making them more flexible and easier to use.

Dependency Inversion Principle (D.I.P)

• High-level modules should not depend on low-level modules, but both should depend on abstractions.
• This principle focuses on decoupling dependencies between modules, making the system more flexible and maintainable.