Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Design around the… Single Responsibility Principle By Eyal Golan
Agenda 1. SOLID 2. SRP overview 3. Why SRP? 4. Recognizing SRP violation 5. Develop for SRP 6. Summarize 2
3
S O L I D • Robert C. Martin – Uncle Bob • http://en.wikipedia.org/wiki/SOLID_(objectoriented_design) 4
SOLID • Single responsibility principle • A class should have only a single responsibility 5
SOLID • Open/closed principle • Open for extension, but closed for modification • Alistair Cockburn: “…Identify points of ...
SOLID • Liskov substitution principle • Replace objects with instances of their subtypes without altering the correctness ...
SOLID • Interface segregation principle • Many client-specific interfaces are better than one general-purpose interface 8
SOLID • Dependency inversion principle • Abstractions should not depend on details • Don’t depend on anything concrete • W...
10
Single Responsibility Principle • Wikipedia • …the single responsibility principle states that every class should have a s...
Which Components? • • • • • Methods Classes Packages Modules System 12
13
Why SRP? • Organize the code George A. Miller 14
Why SRP? • A place for everything and everything in its place 15
Why SRP? • Less fragile code • Low coupling • High cohesion 16
Why SRP? • Easier code changes (Refactoring) 17
Why SRP? • Easier naming • The smaller and more focused class, it will be easier to name 18
Why SRP? • Maintainability • Testability and easier debugging 19
20
Recognizing By Structure • Class / method is too long 21
Recognizing By Structure • Too many dependencies (fields / parameters) Dependency 3 Dependency 4 Dependency 2 Dependenc...
Recognizing By Structure • Low cohesion 23
Recognizing By Structure • Description / name needs: “AND” • Generic name: “EmployeeManager” 24
Recognizing By Structure • A method with many levels 25
Recognizing By Behavior • Complicated test 26
Recognizing By Behavior • Change here, break there • Test may be broken elsewhere • The “shotgun effect” 27
Recognizing By Behavior • Unable to encapsulate the module 28
29
Develop for SRP • Awareness • The state or ability to perceive, to feel, or to be conscious of events, objects, or sensory...
Develop for SRP • Testable code Test • TDD Refactor Code 31
Develop for SRP • Code quality metrics • Coverage • SONAR 32
Develop for SRP • Use other principles • • • • High cohesion Decrease coupling Interfaces Real encapsulation • Law of Dem...
Develop for SRP Keep it simple and short! 34
Develop for SRP • Naming • Think about it • Role play your entities • Longer and more focused name 35
Develop for SRP • Extract method • Extract class 36
Develop for SRP • Refactor mercilessly • Use design patterns • Keep modularization clear 37
Example Short class, 35 lines Precise name (method, class) High cohesion 38
Conclusion • OOD • Clean code • Better practice SRP Do 1 t h i A s o c c l a s s h o u l d h a v e ne r e a s on t o h a...
Resources • http://butunclebob.com/ArticleS.UncleBob.Principles OfOod • Uncle Bob about SRP • http://www.codinghorror.com...
Simple, Isn’t It? 41
Q&A 42
Eyal Golan 43
Upcoming SlideShare
Loading in …5
×
Technology
4,000 views
Feb. 19, 2014

Single Responsibility Principle

This presentation is based on a blog post I made:
http://eyalgo.com/2014/02/01/the-single-responsibility-principle/

More details are in that blog post.
I had a presentation at work with these slides.

no profile picture user

  • Login to see the comments

Show More

Single Responsibility Principle

  1. 1. Design around the… Single Responsibility Principle By Eyal Golan
  2. 2. Agenda 1. SOLID 2. SRP overview 3. Why SRP? 4. Recognizing SRP violation 5. Develop for SRP 6. Summarize 2
  3. 3. 3
  4. 4. S O L I D • Robert C. Martin – Uncle Bob • http://en.wikipedia.org/wiki/SOLID_(objectoriented_design) 4
  5. 5. SOLID • Single responsibility principle • A class should have only a single responsibility 5
  6. 6. SOLID • Open/closed principle • Open for extension, but closed for modification • Alistair Cockburn: “…Identify points of predicted variation and create a stable interface around them…” 6
  7. 7. SOLID • Liskov substitution principle • Replace objects with instances of their subtypes without altering the correctness of that program Rectangle Square 7
  8. 8. SOLID • Interface segregation principle • Many client-specific interfaces are better than one general-purpose interface 8
  9. 9. SOLID • Dependency inversion principle • Abstractions should not depend on details • Don’t depend on anything concrete • Work with interfaces 9
  10. 10. 10
  11. 11. Single Responsibility Principle • Wikipedia • …the single responsibility principle states that every class should have a single responsibility, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility… • Clean Code • A class or module should have one, and only one, reason to change 11
  12. 12. Which Components? • • • • • Methods Classes Packages Modules System 12
  13. 13. 13
  14. 14. Why SRP? • Organize the code George A. Miller 14
  15. 15. Why SRP? • A place for everything and everything in its place 15
  16. 16. Why SRP? • Less fragile code • Low coupling • High cohesion 16
  17. 17. Why SRP? • Easier code changes (Refactoring) 17
  18. 18. Why SRP? • Easier naming • The smaller and more focused class, it will be easier to name 18
  19. 19. Why SRP? • Maintainability • Testability and easier debugging 19
  20. 20. 20
  21. 21. Recognizing By Structure • Class / method is too long 21
  22. 22. Recognizing By Structure • Too many dependencies (fields / parameters) Dependency 3 Dependency 4 Dependency 2 Dependency 1 Dependency 5 Class Dependency 6 22
  23. 23. Recognizing By Structure • Low cohesion 23
  24. 24. Recognizing By Structure • Description / name needs: “AND” • Generic name: “EmployeeManager” 24
  25. 25. Recognizing By Structure • A method with many levels 25
  26. 26. Recognizing By Behavior • Complicated test 26
  27. 27. Recognizing By Behavior • Change here, break there • Test may be broken elsewhere • The “shotgun effect” 27
  28. 28. Recognizing By Behavior • Unable to encapsulate the module 28
  29. 29. 29
  30. 30. Develop for SRP • Awareness • The state or ability to perceive, to feel, or to be conscious of events, objects, or sensory patterns 30
  31. 31. Develop for SRP • Testable code Test • TDD Refactor Code 31
  32. 32. Develop for SRP • Code quality metrics • Coverage • SONAR 32
  33. 33. Develop for SRP • Use other principles • • • • High cohesion Decrease coupling Interfaces Real encapsulation • Law of Demeter 33
  34. 34. Develop for SRP Keep it simple and short! 34
  35. 35. Develop for SRP • Naming • Think about it • Role play your entities • Longer and more focused name 35
  36. 36. Develop for SRP • Extract method • Extract class 36
  37. 37. Develop for SRP • Refactor mercilessly • Use design patterns • Keep modularization clear 37
  38. 38. Example Short class, 35 lines Precise name (method, class) High cohesion 38
  39. 39. Conclusion • OOD • Clean code • Better practice SRP Do 1 t h i A s o c c l a s s h o u l d h a v e ne r e a s on t o h a n g e ! 39
  40. 40. Resources • http://butunclebob.com/ArticleS.UncleBob.Principles OfOod • Uncle Bob about SRP • http://www.codinghorror.com/blog/2007/03/curlyslaw-do-one-thing.html • Coding Horror • https://docs.google.com/file/d/0ByOwmqah_nuGNH EtcU5OekdDMkk/ • PDF about SRP • http://eyalgo.com/2014/02/01/the-singleresponsibility-principle/ • My blog post about SRP 40
  41. 41. Simple, Isn’t It? 41
  42. 42. Q&A 42
  43. 43. Eyal Golan 43

×