Rule S1200: Classes should not be coupled to too many other classes (Single Responsibility Principle) #515

Evangelink · 2017-06-30T12:57:17Z

According to the Single Responsibility Principle, introduced by Robert C. Martin in his book "Principles of Object Oriented Design", a class should have only one responsibility:

Contributes to MMF-963.

Evangelink added this to the 6.2 milestone Jun 30, 2017

Evangelink added Area: Rules labels Jun 30, 2017

Evangelink self-assigned this Jul 5, 2017

Evangelink mentioned this issue Jul 10, 2017

Rule S1200: Classes should not be coupled to too many other classes #548

Merged

Evangelink assigned valhristov and michalb-sonar and unassigned Evangelink Jul 10, 2017

valhristov removed their assignment Jul 10, 2017

michalb-sonar assigned Evangelink and unassigned michalb-sonar Jul 11, 2017

Evangelink closed this as completed in #548 Jul 11, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Rule S1200: Classes should not be coupled to too many other classes (Single Responsibility Principle) #515

Rule S1200: Classes should not be coupled to too many other classes (Single Responsibility Principle) #515

Evangelink commented Jun 30, 2017 •

edited

Loading

Rule S1200: Classes should not be coupled to too many other classes (Single Responsibility Principle) #515

Rule S1200: Classes should not be coupled to too many other classes (Single Responsibility Principle) #515

Comments

Evangelink commented Jun 30, 2017 • edited Loading

Evangelink commented Jun 30, 2017 •

edited

Loading