Scribd
Upload
15 views3 pages

Understanding SOLID Principles in OOP

The document discusses the SOLID principles for object-oriented design. SOLID is an acronym that stands for five principles - Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. These principles aim to make software easier to maintain and extend by avoiding code smells and allowing easy refactoring.

Uploaded by

Sabyasachi De
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
15 views3 pages

Understanding SOLID Principles in OOP

The document discusses the SOLID principles for object-oriented design. SOLID is an acronym that stands for five principles - Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. These principles aim to make software easier to maintain and extend by avoiding code smells and allowing easy refactoring.

Uploaded by

Sabyasachi De
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

SOLID Principles

In OOPS
S.O.L.I.D is an acronym for the first five object-oriented design
principles.

These principles, when combined together, make it easy for a


programmer to develop software that are easy to maintain and
extend. They also make it easy for developers to avoid code
smells, easily refactor code, and are also a part of the agile or
adaptive software development.

S - Single responsiblity principle


O - Open-closed principle
L - Liskov substitution principle
I - Interface segregation principle
D - Dependency Inversion Principle
Single responsiblity principle

The single responsibility principle states that a class or module should


do one thing only or

You might also like