What are SOLID principals?

Question

Accepted Answer

SOLID principles are five design principles aimed at making software designs more understandable, flexible, and maintainable.

S - Single Responsibility Principle: A class should have one, and only one, reason to change. Example: A class handling user data should not also handle logging.
O - Open/Closed Principle: Software entities should be open for extension but closed for modification. Example: Using interfaces to allow new functionalities without changing existing code.
L - Liskov Substitution Principle: Subtypes must be substitutable for their base types without altering the correctness of the program. Example: If a function uses a base class, it should work with any derived class.
I - Interface Segregation Principle: Clients should not be forced to depend on interfaces they do not use. Example: Instead of one large interface, create smaller, specific ones.
D - Dependency Inversion Principle: High-level modules should not depend on low-level modules; both should depend on abstractions. Example: Using dependency injection to manage class dependencies.

Top Accenture Software Development Senior Analyst interview questions & answers