#SRP SINGLE RESPONSIBILITY PRINCIPLE UPDATE#
#SRP SINGLE RESPONSIBILITY PRINCIPLE REGISTRATION#
#SRP SINGLE RESPONSIBILITY PRINCIPLE CODE#

Email sending code should be removed from EmployeeService class. So, there are two changes in the application. He needs to make it independently so that it could be used as another place in the application. He needs to change in the email sending functionality. Mark knows that he needn’t build the entire application. But he needs to implement these changes without violating SRP. He knows very well where he needs to change in the existing code. Mark has an understanding that a class should have a single responsibility.

#SRP SINGLE RESPONSIBILITY PRINCIPLE UPDATE#

He starts to update in existing code for SRP. Now, he knows about the Single Responsibility Principle. Mark understood that what he did wrong here and how violates the SRP principle. In other words, EmployeeService class can have multiple methods related to the Employee entity such as registration, update and delete etc. A class can have multiple methods but these are related to one entity of the application. It doesn’t mean that a class can’t have more than one method. The EmployeeService class has two responsibilities so it violates the SRP principle. If we change email sending process such as change provider, add attachment and use SSL etc then EmplyeeService class should not be changed but it isn't possible in preceding code.īob explained to Mark that a class should have only reason to change and have a single responsibility.

#SRP SINGLE RESPONSIBILITY PRINCIPLE REGISTRATION#

The email send and employee registration are totally different functionalities. The email sending functionality is not related to the employee entity directly. The EmployeeService class holds two methods ,one for registration of employee while another method is for sending mail to the employee. The preceding code is working perfectly but it is still violating the Single Responsibility Principle.

He defines a separate class for employee storage which is static.

The methods are separated based on functionalities.

He defines separate classes for both employee data and functionality.

All things are looking good and working as per expectation such as, the module was ready, Mark demonstrated the same to Bob, and Bob again appreciates the architecture. It will be worked with valid credentials and domain.Īs Mark uses same console application for UI interaction so he updates it as per following code snippet. This email send code is used for demonstration purpose. NET Core MailKit Nuget package is used to send an email. The following code snippet is for the same. Each method defines as per functionality so that these don’t violate SRP. This class holds two methods, one for registration of employee while another method is for sending mail to the employee. Mark defines registration and mail sending functionality in the EmployeeService class. Public static List Employees = new List() It has a property to store employee list. Mark uses local storage to store data rather than database so he defines another class named StaticData. Public void EmployeeRegistration(EmployeeService employee) It holds both employee data and registration operation as per following code snippet. Mark defines a class named EmployeeService.

One of the primary requirements was to build a module which will have employee registration functionality. We will see how Mark progresses his knowledge about Single Responsibility Principle day by day and how finally he come up with a great solution.īob (Tech Lead) explains requirements to Mark (a. The story begins on the day when Bob contacts Mark and asks him to take up a role of an architect in his project called “Employee Management System”. In this article for discussion and explanation purposes, I am introducing to you, two fictional characters Mark (a. A method’s code doesn’t depend on other methods. In the maintenance, when a functionality changes then we don’t need to test the entire model. Increased readability, extensibility, and maintenanceĪs each method has a single functionality so it is easy to read and maintain.Īs code separates based functionality so if the same functionality uses somewhere else in an application then don’t write it again.A method holds logic for a single functionality or task.

Srp single responsibility principle