tag:blogger.com,1999:blog-7442262522977329981.post4357396950825672170..comments2011-05-03T11:38:59.822-05:00Chris Ammermanhttps://profiles.google.com/118440544456036580001noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7442262522977329981.post-44833668398557962752011-05-03T11:38:59.822-05:002011-05-03T11:38:59.822-05:00Great post! I think all three are spot on. In my own SRP wrestlings, I've found that it's common to hear myself or other devs give what appears to be a 'single' responsibility, when it's actually more an aggregate of several distinct responsibilities. Like "Process Customer File" (for a highly contrived example). If 'process' means, upload, persist and display summary to screen - then good grief we practically have a sub-module of classes. :-) Asking the kinds of questions you're recommending is key, since it will not only help you separate out the responsibilities, but to then group them compositionally (as opposed to hierarchically through inheritance).Jimhttp://ifandelse.comnoreply@blogger.com