Let\'s use as example: class AccountDAO { create(){..} read(){..} 开发者_运维问答update(){..} delete() {..}
Title probably doesn\'t describe my problem too well, I\'ll be glad if somebody could edit it to something more appropriate. Anyways:
I downloaded srp-2.1.2 source from http://srp.stanford.edu/source/srp-2.1.2.tar.gz. Type: ./configure ---> everything ok
I can grasp the part \"do one thing\" via encapsulation, Dependency Injection, Principle of Least Knowledge, and You Ain\'t Gonna Need It; but how do I understand the second part \"do it well?\"
I\'m designing/building a medium-scale ASP.NET web application using WebForms. The main work in the project is building each web form, and I don\'t know how to design (in a code/data/data flow sense)
I\'ve just read SRP, as easy as 123…, and all of it resonates with me except one paragraph, in a section named \"Cohesion\" (I\'ve claimed before to \"get\" Cohesion, but this talk of parameters vs i
Closed. This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this
Sticking to Apple\'s guidelines, I create one subclass of UIViewController per screen of my iPhone applicatio开发者_如何转开发n.However I consistently find that these classes become very large, both i
The Single Responsibility Principle says, for example, that an Invoice class should not contain the code to print itself. Printing should be separated out into a different class.
Most of the ASP.NET MVC examples I have seen depi开发者_如何学运维ct scenarios where a user is viewing an object (or collection of objects) and then moves from that page to one that displays a form th
加载中,请稍侯......