GRASP - one more way to reach clean code
0 likes252 views
This document discusses the General Responsibility Assignment Software Patterns (GRASP) principles for object-oriented design. It introduces the nine GRASP patterns: information expert, creator, controller, low coupling, high cohesion, indirection, polymorphism, pure fabrication, and protected variations. For each pattern, it provides a brief definition and examples of how and when to apply the pattern to achieve better object-oriented designs with low coupling and high cohesion. The presentation aims to explain the importance of understanding and applying these fundamental GRASP patterns for assigning responsibilities in software design.
GRASP - one more way to reach clean code
- 1. Neversettle intive.com _GRASP Karol Kreft PHPers Summit 2019 06.09.2019, Poznań
- 5. Neversettle intive.com • www.craiglarman.com • UML, OOP, Analysis & Design • GRASP • Agile and LeSS 5 Craig Larman
- 6. Neversettle intive.com 6 The GRASP name was chosen to suggest the importance of grasping these principles to successfully design object-oriented software.
- 9. Neversettle intive.com • do something • know something{ Responsibilities
- 12. Neversettle intive.com GRASP 1. Information Expert 2. Creator 3. Controller 4. Low coupling 5. High cohesion 6. Indirection 7. Polymorphism 8. Pure Fabrication 9. Protected Variations
- 13. Neversettle intive.com Information Expert _Assign a responsibility to the information expert – the class that has the information necessary to fulfill the responsibility.
- 14. Neversettle intive.com Information Expert _Place responsibilities with data _That which knows, does _Do it Myself _Put Services with the Attributes They Work On
- 17. Neversettle intive.com Creator _Who should be responsible for creating a new instance of some class? _Choose class B when _B aggregates A objects _B contains A objects _B closely uses A objects _B as the initializing data that are required to creatingA
- 20. Neversettle intive.com Controller _Who should be responsible for handling system event?
- 22. Neversettle intive.com Bloated Controller _Controllers which handle too many system events leading to low cohesion. This can be avoided by addition of a few more controllers. _Always remember about delegating responsibilities to other objects. _Use Command Pattern in a message-handling systems.
- 24. Neversettle intive.com Low Coupling _How to support low dependency and increased reuse? High Cohesion _How to keep complexity manageable?
- 25. Neversettle intive.com Low Coupling _Assign responsibilities so that coupling remains low. High Cohesion _Assign responsibilities so that cohesion remains high.
- 26. Neversettle intive.com High Coupling _Changes in related classes force local changes _Harder to understand in isolation _Harder to reuse because its use requires the additional presence of the classes it dependent upon _Coupling may not be important if reuse is not a goal.
- 27. Neversettle intive.com Low Cohesion _Hard to comprehend _Hard to reuse _Hard to maintain _Delicate; constantly effected by change
- 28. Neversettle intive.com _Low Coupling and High Cohesion are principles to keep in mind during all design decisions. _They are evaluative patterns which a designer applies while evaluating all design decisions.
- 30. Neversettle intive.com 30 _Where to assign a responsibility to avoid direct coupling between two or more things?
- 31. Neversettle intive.com 31 _Where to assign a responsibility to avoid direct coupling between two or more things? _Assign the responsibility to an intermediate object to mediate between other components or services to avoid direct coupling.
- 33. Neversettle intive.com GRASP 1. Information Expert 2. Creator 3. Controller 4. Low coupling 5. High cohesion 6. Indirection 7. Polymorphism 8. Pure Fabrication 9. Protected Variations
- 34. Neversettle intive.com 34 Do we need object oriented design?
- 37. Neversettle intive.com 37 • Photo by La-Rel Easter on Unsplash • Photo by Feliphe Schiarolli on Unsplash • Photo by Andrej Lišakov on Unsplash • Photo by Rohit Choudhari on Unsplash • Photo by Javier Allegue Barros on Unsplash Photos