Skip to content

SOLID principles guide software design for maintainability and scalability. Using real-life examples like User (Single Responsibility), Notification systems (Open/Closed), Media player (Liskov Substitution), different type of Document (Interface Segregation), and Database connection (Dependency Inversion)

Notifications You must be signed in to change notification settings

ashvin27/SOLID-Principles-with-Real-Life-Examples

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SOLID-Principles-with-Real-Life-Examples

  1. Single Responsibility Principle (SRP): A class should have only one reason to change.

  2. Open/Closed Principle (OCP): Software entities should be open for extension but closed for modification.

  3. Liskov Substitution Principle (LSP): Subtypes must be substitutable for their base types without altering the correctness of the program.

  4. Interface Segregation Principle (ISP): A client should not be forced to implement interfaces it does not use.

  5. Dependency Inversion Principle (DIP): High-level modules should depend on abstractions, not on concrete implementations.

About

SOLID principles guide software design for maintainability and scalability. Using real-life examples like User (Single Responsibility), Notification systems (Open/Closed), Media player (Liskov Substitution), different type of Document (Interface Segregation), and Database connection (Dependency Inversion)

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published