Single Responsibility Responsible Principle (SRP)

-

Single Responsibility Responsible Principle (SRP)

The name itself explaining the concept , the class/module should have handle single unit of work.

Rather than handling multiple components in class/module/functionality.

Benefits :

  • Code becoming understandable
  • Better design
  • Less chance to code become complex (code is less fragile)
Implementation :

For example if we are implementing a login page we need maintain a user information, email notification, Logging exceptions 

Code before SRP 



If you observe above code all the functionalities related to login page included in one interface so we need to break the functionalities into single task.

Let's have a look after implementing Single Responsibility Principle



So at a glance always use a module should have a single reason to change the class/interface/function/module



Comments

  1. UnknownApril 9, 2022 at 8:15 PM

    What is the casino? - SEPT
    The best septcasino casino online https://jancasino.com/review/merit-casino/ is febcasino the One of the main reasons why people are spending money on a game 출장안마 is 토토 사이트 by having a few options. One of the reasons

    ReplyDelete

Post a Comment

Popular posts from this blog

Self introduction in interview for experienced candidates software - Simple way

-
Interviewer: Can you explain about yourself and technical experience? You: Hi, I am Satish, I have around 10 years of Work experience in Microsoft Technologies mainly in C#, ASP.NET and SQL Server. I have good exposure on creating Web applications and windows application with different domains like logistics, financial and Health care. I have been working in Company name for the past 2 years and my current project is Project name. Coming to my technical experience so far I have involved in all phases of the projects like designing, developing, testing and deploying activities. In this current project my key responsibilities are Involved in coding and developing functionalities. Involved in bug fixes and resolving PEN Test Issues Involved in implementing Thycotic server and Logging using log4net and integration with Application insight.  we are making sure to coverage Unit test cases for all the fixes/enhancements we have done. This is pretty much from my side. Cross Questions: Intervi
Read more

SOLID Design Principles Interview questions and answers with Simple Examples

-
  Interviewer : Why should we use SOLID principles ? Can you explain about SOLID design Principles ? You : SOLID design principles are used to develop the code in an efficient way and also it gives the benefits  Flexible, Maintainable and Understandable code. SOLID design principles are  S : Single Responsibility Principle (SRP) O : Open Closed Principle (OCP) L : Liskov Substitution Principle (LSP) I : Interface Segregation Principle (ISP) D : Dependency Inversion Principle (DIP)  SRP : class/module should have handle single unit of work E.g : When you are implementing a Login page, we have some Register/Email/Error functionalities instead of maintaining all methods in the ILogin interface. Create separate Interfaces for all the single unit of work IRegister/IEmail/IError. Code looks cleaner and easy to handle OCP : class/module should be open for extension and close for the modification E.g : Suppose we have a CalculateBonus() method in Employee class and implemented for Temporary an
Read more