SOLID Design Principles - An Introduction
What is SOLID Principle?
In
this article I am going to explain very briefly "what is SOLID
principle?",
"What are the benefits of using SOLID in software development
process?".
As
software developers, we are expected to be aware of these principles at the
very beginning of our career itself. The sooner we get used to them, the
better. The main aim of this post is to give a short and brief introduction of
these principles.
We’ll
discuss each of the principle in details with easy-to-understand examples in
our forthcoming posts.
What is SOLID?
SOLID
is the short form for the five important design principles that are followed in
software development process.
These
principles are as below:
S - Single
Responsibility Principle
O - Open-Closed
Principle
L - Liskov's
Substitution Principle
I - Interface
Segregation Principle
D - Dependency
Inversion Principle
What are the benefits of
following SOLID?
The
primary focus is to have a software codebase that is more readable, more
flexible for change, and quite easier to maintain in a long term view.
Following
are some of the important benefits of SOLID principle:
·
It results in a highly maintainable
codebase that can be expandable easily without much hassle.
·
Code becomes very clean and efficient
·
Results in zero code smells
·
Codebase becomes highly testable
·
These principles are very much suitable
for Agile methodologies/Scrum
·
They can be employed in any object
orientated programming language
