Scribd
Upload
50 views

Session 15

The Controller pattern assigns responsibility for dealing with system events to a non-UI class that coordinates system operations. A Controller receives and handles system events, delegating work to other objects and coordinating activity without doing much work itself.

Uploaded by

ganesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
50 views

Session 15

The Controller pattern assigns responsibility for dealing with system events to a non-UI class that coordinates system operations. A Controller receives and handles system events, delegating work to other objects and coordinating activity without doing much work itself.

Uploaded by

ganesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

CONTROLLER:

The Controller pattern assigns the responsibility of dealing with system events to a non-UI

class that represents the overall system or a use case scenario. A Controller object is a non-user

interface object responsible for receiving or handling a system event.

A use case controller should be used to deal with all system events of a use case, and may be

used for more than one use case (for instance, for use cases Create User and Delete User, one can

have a single UserController, instead of two separate use case controllers).

It 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

(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.

You might also like