Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, Second Edition

16.10. Controller

Assign the responsibility for receiving or handling a system event message to a class representing one of the following choices:

• Represents the overall system, device, or subsystem (facade controller).

• Represents a use case scenario within which the system event occurs, often named <UseCaseName>Handler, <UseCaseName>Coordinator, or <UseCaseName>Session (use-case or session controller).

  • Use the same controller class for all system events in the same use case scenario.

  • Informally, a session is an instance of a conversation with an actor. Sessions can be of any length, but are often organized in terms of use cases (use case sessions).

Solution

Corollary: Note that “window,” “applet,” “widget,” “view,” and “document” classes are not ...