The SOLID Principles from Wider Angle — SRP

SOLID is an acronym for five design principles intended to make object-oriented class designs more flexible, reusable, understandable and maintainable. Robert C. Martin first coined these principles which was later brought to light by many people.

Many articles have covered these topics and pointed out these principles with a common perspective — The OOP.

These principles are generally looked at from the perspective of object-oriented class designs. But if we closely look, they are applied in many software paradigms such as API Design, Architecture, User Interface Diagrams, and Microservice designs. This article is an attempt to point out where else these principles can be applied other than in the object-oriented paradigm.

Here are the five design principles.

1. SRP — Single Responsibility Principle
2. OCP — Open-Closed Principle
3. LSP — Liskov Substitution Principle
4. ISP — Interface Segregation Principle
5. DIP — Dependency Inversion Principle

In this article, we will look at Single Responsibility Principle(SRP) from a different perspective. There will be separate articles for other principles. This article concentrates on SRP.

Single Responsibility Principle (SRP)

The Single Responsibility Principle suggests that every component should have one single responsibility…