Difference between Single Responsibility Principle and Separation of Concerns

separation-of-concerns solid-principles single-responsibility-principle
Rookian picture Rookian · Nov 12, 2009 · Viewed 18.3k times · Source

What is the difference between Single Responsibility Principle and Separation of Concerns?

Answer

luvieere picture luvieere · Nov 12, 2009

Single Responsibility Principle (SRP)- give each class just one reason to change; and “Reason to change” == “responsibility”. In example: Invoice class does not have a responsibility to print itself.

Separation of Concerns (since 1974). Concern == feature of system. Taking care of each of the concerns: for each one concern, other concerns are irrelevant. Hiding implementation of behavior.

From here.

Related questions

Import multiple Angular components via module

My Angular project is growing so I want to keep my project clean. I have one Angular component which depends on a nested Angular component. Now I need two import statements to use these components which cannot work without each …

Read More
How to map View Model back to Domain Model in a POST action?

Every article found in the Internet on using ViewModels and utilizing Automapper gives the guidelines of the "Controller -> View" direction mapping. You take a domain model along with all Select Lists into one specialized ViewModel and pass it …

Read More
RSpec in Rails: How to skip a before_filter?

I am trying to test my controller and maintain separation of concerns. The first concern is "Who is able to execute which action?" I am using authlogic for authentication and be9's acl9 for authorization. But this should not matter, …

Read More