SOLID Principles With .NET - Single Responsibility Principle

 Single Responsibility Principle 

                    The acronym SRP states that "A class should take one responsibility and there should be one reason to change that class". In this article I want to share my knowledge on how we can make sure to follow this in our career as a developer .

Every software module should have only one reason to change .The single responsibility principle gives you a good way of identifying classes at the design phase of an application.A good separation of responsibilities is done only when we have the full picture of how the application should work . 

Now let's go into our example . And to go through SOLID principles , I have taken a real case scenario of a banking system  as an example for clear understanding and to give everyone a wider view about how one should act while he starts to code . 

And we have three different sections  

    - Banking Service without SRP

    - Banking Service with SRP

    - Conclusion 


In the above  code we see that

Account class is not only calculating the interest but also has method to generate report which is completely violating the single responsibly principle . 

But after few days , if the business asks to replace the crystal reports with excel generation , then this class need to be changed and which is not a good approach.

But according to SRP , one class should take one responsibility. So now the responsibility to generate report is moved into a new class and so that account class do have a single responsibility to taken care . 


So according to the SRP , the responsibilities are given to two different classes . This helps code to be easily maintained and readable .

In the next article , we can go through Open Closed Principle(OCP) .

For the source code of this : Git Hub 

Comments

Post a Comment

Popular posts from this blog

SOLID Principles With .NET - Liskov Substitution Principle

Image
 Liskov Substitution Principle           is a fundamental SOLID principle that states " You should be able to use any derived class instead of a parent class and have it to behave in the same manner without modification". It ensures that a derived class does not affect the behaviour of the base class . Before going into implementation of LSP , please do go through the previous article on OCP . We are continuing with the same example . This article is divided into three parts :  - Banking Service without LSP  - Banking Service Example with LSP  - Conclusion And now business want to provide the Additional Compound Interest to Salary Accounts , so in our base abstract class we are now adding another method called CalculateCompundInterest . And our abstract class looks like this  and now the derived classes looks something like below and everything looks fine till there .  Now check the below code which  violate the LSP ...
Read more

SOLID Principles With .NET - Open Closed Principle

Image
The Open Closed Principle           is the SOLID principle which states that the software entities (classes or methods) should be open for extension but closed for modification. Open for extension but closed for modification ? Oh what does it really mean ?  In real time every business requirements changes so frequently, so while developing an application we should strive to write a code that doesn't require modification every time  business changes it requirement. The biggest benefit for an application to be adhered to OCP is, it potentially streamlines code maintenance and reduces the risk of breaking the existing implementation. Here , I will show you how we can implement a requirement with and without OCP rules.  This article is divided into the following sections :  Banking Service - Without  OCP   Example - Without  OCP  implemented  Conclusion     So let's start  Banking Service C...
Read more