Single Responsibility Principle (SRP)
This is one of the SOLID principles and it states:
“A module should be responsible to one, and only one, actor.”
In simpler terms, a module should have only one reason to change.
Example
Let’s consider an example from the Wikipedia article on SRP. Suppose you have some code that compiles and then produces a report. There might be two reasons for wanting to change the code:
- To modify the content of the report.
- To alter the format of the report.
According to SRP, these two functionalities should be implemented in separate modules.
An important takeaway from this example is that you’ll need to define an interface between the two modules. This interface standardizes how information is passed from one module to another, ensuring proper separation of concerns.