GRASP (object-oriented design): Difference between revisions

Revision as of 06:20, 14 July 2020

Revision as of 06:21, 14 July 2020

Line 50:

The controller is defined as the first object beyond the UI layer that receives and coordinates ("controls") a system operation. The controller should delegate the work that needs to be done to other objects; it coordinates or controls the activity. It should not do much work itself. The GRASP Controller can be thought of as being a part of the application/service layer<ref>{{cite web |url=https://groups.yahoo.com/neo/groups/domaindrivendesign/conversations/messages/7582 |title=Application Layer like business facade? |work=Yahoo! Groups (domaindrivendesign) |accessdate=15 July 2010}}</ref> (assuming that the application has made an explicit distinction between the application/service layer and the [[___domain layer]]) in an object-oriented system with common layers in an information system logical architecture.

'''Related PatteranPattern or Principle''':[[Command]], [[Facade]], [[Layers]], Pure Fabrication

===Indirection===