Saved searches Use saved searches to filter your results more quickly You signed in with another tab or window. Reload to refresh your session.You signed…

You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You swit…

Two common phrasings for the Single Responsibility Principle (SRP) are "each module should be responsible for a single feature or functionality in a syst…

2 Answers 2 Theoretically, both of these could change independently from each other. So theoretically it is a violation of SRP. Still I would probably no…

The Single Responsibility Principle states that a class should do one and only one thing. Some cases are pretty clear cut. Others, though, are difficult …

I believe UpdateGroupBilling should not be called inside the save method as it violates the single responsibility principle. But, he says that each time …

I'm working on a team where the team leader is a virulent advocate of SOLID development principles. However, he lacks a lot of experience in getting comp…

In my spare time, I've been designing a CMS in order to learn more about actual software design and architecture, etc. Going through the SOLID principles,…

Third, a one-to-one but with a redundancy of the common fields (being as focused on authentication as a visible user information on the website): User(us…

In this example the class Product holds all the variables related to a Product it doesn't allow to do any operations on them. Inventory instead is a clas…

I have a class that represents a button on the screen. This class has two methods: one for click event; the other for long-click event. Both events do di…

I have been experimenting lately with enums, and I found out that in Java they can do much more than simply representing a fixed set of constants. Now, I…

I would say, there is nothing inherently wrong with both approaches; it depends on the architecture and other constraints. Sometimes it makes sense to us…

However, in cases where the tests did not force the separation, and the smells of Rigidity and Fragility become strong, the design should be refactored u…

I am trying to apply "SOLID" whenever I can and try to use common sense and avoid a pattern when I see that a pattern is creating more problems than it's…

I have a test scenario where in one module of application is responsible for creating ledger entries. There are three basic tasks which could be carried …

The SRP seens fairly reasonable when you first look at it. Every class should have one reason to change. Every class should take care of one thing. Right…

I have many classes in my application responsible for behaviour- views, controllers, models, network- often the state of one class or system depends on a…

I have a website. It allows users to make posts (can be anything) and add tags that describe the post. In the code, I have two classes that represent the…

1) ^What Euphoric said, and 2) there can be valid reasons to choose to structure your program or parts of it in a way that's different from the usual OOP…

You only need one class, and the single responsibility of that class is to manage ledgers. That's an instinctual approach and it's probably correct, as w…

SRP actually stands for Single Responsibility Principle . Mr. Martin is correct that the Modem interface violates SRP. You are correct that ModemImpl viol…

The Single Responsibility Principle is confusingly named and vaguely defined. Robert Martin who first named the principle has revised and clarified its m…

How do you apply Single Responsability Responsibility principle to a repository I am trying to apply "SOLID" whenever I can and try to use common sense an…

It's subtly different from the traditional "should do only one thing" definition, and I like this because it forces you to change the way you think about…

It's a discussion about follow very strictly the SRP (Single Responsability Principle) vs. be more flexible when you write simple codes, like setting or …

I my job, I am tasked with the responsibility of improving the code quality. To meet this responsibility I often pair program with developers and conduct …

5 Answers 5 Sometimes, the fact that you have this choice to make is itself a smell. It tells you that perhaps you are missing an abstraction, or that be…

In keeping with the SRP , my Book and Author classes shouldn't be aware of the database backend, or any elements used to display(ex. textbox , or Jtable )…

The other day, I came across this question on StackOverflow. In short, the user who asked the question wanted to extend a class from a third-party librar…

I'm writing a Java program with a custom event manager, which is of course the observer pattern. Should the calls to add event listeners/handlers be in t…

My question is about that DateEntered column: is it Ok to have it in Units table or not? I mean does not this tell us somehow that an instance (row) of t…

I have written a set of classes to interact with AutoCAD from an out-of-process .NET assembly, but it seems like my class architecture and interactions ar…

Same in principle but SoC alone doesn't appear to discourage over-separation. Overseparation isn't as bad as overcoupling, but it's bad, because it raise…

Questions tagged [single-responsibility-principle] For questions about the Single Responsibility Principle in object-oriented programming, one of the SOL…

Single Responsibility Principle Most people defining SRP are incorrect. SRP is typically mis-explained as: "The Employee class shouldn't UpdateDemographi…

S is for Single Responsibility Principle SOLID is a mnemonic acronym that helps define the five basic object-oriented design principles: Single Responsib…

Single Responsibility Principle A class should have only one reason to change, meaning that a class should only have one responsibility or job. Single Res…

Saved searches Use saved searches to filter your results more quickly You signed in with another tab or window. Reload to refresh your session.You signed…

You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You swit…

Two common phrasings for the Single Responsibility Principle (SRP) are "each module should be responsible for a single feature or functionality in a syst…

2 Answers 2 Theoretically, both of these could change independently from each other. So theoretically it is a violation of SRP. Still I would probably no…

The Single Responsibility Principle states that a class should do one and only one thing. Some cases are pretty clear cut. Others, though, are difficult …

I believe UpdateGroupBilling should not be called inside the save method as it violates the single responsibility principle. But, he says that each time …

I'm working on a team where the team leader is a virulent advocate of SOLID development principles. However, he lacks a lot of experience in getting comp…

In my spare time, I've been designing a CMS in order to learn more about actual software design and architecture, etc. Going through the SOLID principles,…

Third, a one-to-one but with a redundancy of the common fields (being as focused on authentication as a visible user information on the website): User(us…

In this example the class Product holds all the variables related to a Product it doesn't allow to do any operations on them. Inventory instead is a clas…

I have a class that represents a button on the screen. This class has two methods: one for click event; the other for long-click event. Both events do di…

I have been experimenting lately with enums, and I found out that in Java they can do much more than simply representing a fixed set of constants. Now, I…

I would say, there is nothing inherently wrong with both approaches; it depends on the architecture and other constraints. Sometimes it makes sense to us…

However, in cases where the tests did not force the separation, and the smells of Rigidity and Fragility become strong, the design should be refactored u…

I am trying to apply "SOLID" whenever I can and try to use common sense and avoid a pattern when I see that a pattern is creating more problems than it's…

I have a test scenario where in one module of application is responsible for creating ledger entries. There are three basic tasks which could be carried …

The SRP seens fairly reasonable when you first look at it. Every class should have one reason to change. Every class should take care of one thing. Right…

I have many classes in my application responsible for behaviour- views, controllers, models, network- often the state of one class or system depends on a…

I have a website. It allows users to make posts (can be anything) and add tags that describe the post. In the code, I have two classes that represent the…

1) ^What Euphoric said, and 2) there can be valid reasons to choose to structure your program or parts of it in a way that's different from the usual OOP…

You only need one class, and the single responsibility of that class is to manage ledgers. That's an instinctual approach and it's probably correct, as w…

SRP actually stands for Single Responsibility Principle . Mr. Martin is correct that the Modem interface violates SRP. You are correct that ModemImpl viol…

The Single Responsibility Principle is confusingly named and vaguely defined. Robert Martin who first named the principle has revised and clarified its m…

How do you apply Single Responsability Responsibility principle to a repository I am trying to apply "SOLID" whenever I can and try to use common sense an…

It's subtly different from the traditional "should do only one thing" definition, and I like this because it forces you to change the way you think about…

It's a discussion about follow very strictly the SRP (Single Responsability Principle) vs. be more flexible when you write simple codes, like setting or …

I my job, I am tasked with the responsibility of improving the code quality. To meet this responsibility I often pair program with developers and conduct …

5 Answers 5 Sometimes, the fact that you have this choice to make is itself a smell. It tells you that perhaps you are missing an abstraction, or that be…

In keeping with the SRP , my Book and Author classes shouldn't be aware of the database backend, or any elements used to display(ex. textbox , or Jtable )…

The other day, I came across this question on StackOverflow. In short, the user who asked the question wanted to extend a class from a third-party librar…

I'm writing a Java program with a custom event manager, which is of course the observer pattern. Should the calls to add event listeners/handlers be in t…

My question is about that DateEntered column: is it Ok to have it in Units table or not? I mean does not this tell us somehow that an instance (row) of t…

I have written a set of classes to interact with AutoCAD from an out-of-process .NET assembly, but it seems like my class architecture and interactions ar…

Same in principle but SoC alone doesn't appear to discourage over-separation. Overseparation isn't as bad as overcoupling, but it's bad, because it raise…

Questions tagged [single-responsibility-principle] For questions about the Single Responsibility Principle in object-oriented programming, one of the SOL…

Single Responsibility Principle Most people defining SRP are incorrect. SRP is typically mis-explained as: "The Employee class shouldn't UpdateDemographi…

S is for Single Responsibility Principle SOLID is a mnemonic acronym that helps define the five basic object-oriented design principles: Single Responsib…