I have a functional AdjacencyListGraph class that adheres to a defined interface GraphStructure. In order to layer limitations on this (eg. acyclic, non-null, unique vertex data etc.), I can see two p
In the SRP, a \'r开发者_运维问答esponsibility\' is usually described as \'a reason to change\', so that each class (or object?) should have only one reason someone should have to go in there and chang
For my purposes, I need to search for a specific node in an xml file and, if found, delet开发者_高级运维e it.Should I pull search functionality out into its own method and delete functionality out int
Closed. This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing
I\'m trying to adhere to Single Responsibility Principle better, and I\'m having issues grasping how to structure the general class design for communicating with a database. In a simplified version, I
In the system I\'m currently working on, I\'m following SRP (I think!) by separating the validation of domain business rules vs persistence constraints.Let\'s employ the overused customer example.Say
I\'ve got this question about form validation and business validation. I see a lot of frameworks that use some sort of form validation library. You submit some values and the library validates the val
I\'m getting push back on a design from a colleague, and am wondering if there\'s consensus as to who is correct on application of SRP in this case.
开发者_StackOverflow社区What is the difference between Single Responsibility Principle and Separation of Concerns?
加载中,请稍侯......