#SINGLE RESPONSIBILITY PRINCIPLE JAVA SOFTWARE#

Rahul: 'Stop talking nonsense! If we don’t duplicate, then who will pay for your salary? :)' Mohan: 'In that case, why do we need a V2? Can’t we use the same code here?' So now it’s our responsibility to sunset their current project The Dosa Maker and come up with an innovative design for the brand new The Dosa Maker V2.0.'

Rahul: 'As you already know, the US team is moving on to another project. Rahul: 'Congratulation on your promotion Mohan!' Mohan: 'Thanks, Rahul.' Mohan was sitting in his room, waiting for his next task to be assigned after promotion. S - Single Responsibility Principle O - Open Closed Principle L - Liskov Substitution Principle I - Interface Segregation D - Dependency Inversion. It’s part of a group of 5 design principles commonly known by the acronym SOLID.

#SINGLE RESPONSIBILITY PRINCIPLE JAVA SOFTWARE#

The Single Responsibility Principle (SRP) states that a class should have only one reason to change. Open Closed Design Principle is one of the most important design principles in the world of software development. This principle helps us to maintain, test and scale the codebase easily because changes in requirements do not affect multiple areas of the codebase. In this blog, we have covered the five SOLID principles and provided code examples in Java. In other words, a class should have only one reason to change and it should be focused on doing one thing well. The Single Responsibility Principle (SRP) is one of the SOLID principles in software engineering that states that every module or class should have only one responsibility and that responsibility should be entirely encapsulated within the class.

Single responsibility principle java