This article is taken from the book Brownfield Application Development in .NET from Manning Publications. As part of a chapter on bringing better object-oriented principles into your Brownfield project, this segment discusses the benefits (and limitations) of the Single Responsibility Principle, which makes classes easier to maintain by delegating responsibility. For the table of contents, the Author Forum, and other resources, go to

Separation of Concerns/Single Responsibility Principle (PDF)