| <<O>> Difference Topic GraspSoftwareArchitecturePatterns (r1.2 - 18 Aug 2006 - CraigSchwartz) |
General Responsibility Assignment Software Patterns (GRASP) | ||||||||
| Line: 36 to 36 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Added: | ||||||||
| > > |
Low CouplingHow to support low dependency and increased reuse ? Assign responsibilities so that coupling remains low.High CohesionHow to keep complexity manageable ? Assign responsibilities so that cohesion remains high.PolymorphismWo, when behavior varies by type ? When related alternatives or behaviors vary by type(class), assign responsibility for the behavior - using polymorphic operations - to the types for which the behavior varies. | |||||||
| <<O>> Difference Topic GraspSoftwareArchitecturePatterns (r1.1 - 16 Aug 2006 - CraigSchwartz) |
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
General Responsibility Assignment Software Patterns (GRASP)ExpertWho, in the general case, is responsible ? Assign a responsibility to the information expert - the class that has the information necessary to fulfill the responsibility.CreatorWho Creates ? Assign class B the responsibility to create an instance of class A if one of the following is true:
ControllerWho handles a system event ? Assign the responsibility for handling a system event message to a class representing one of these choices:
| |||||||
|
Revision r1.1 - 16 Aug 2006 - 16:00 - CraigSchwartz Revision r1.2 - 18 Aug 2006 - 17:01 - CraigSchwartz |