Controller GRASP Pattern

Controller is the GRAS Patterns (General Responsibility Assignment Software Pattern)
Read about GRASP Patterns: GRASP Patterns Overview

Problem

Who should be responsible for handling an input system event?
An input system event is an event generated by an external actor. They are associated with system operations of the system in response to system events, just as messages and methods are related.
For example, when a writer using a word processor presses the "spell check" button, he is generating a system event indicating "perform a spell check."

A Controller is a non-user interface object responsible for receiving or handling a system event. A Controller defines the method for the system operation.

Who should be responsible for handling an input event, which object/s beyond the UI layer receives interaction?

Solution

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 <Use-CaseName>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).


Corollary: Note that "window," "applet," "widget," "view," and "document" classes are not on this list. Such classes should not fulfill the tasks associated with system events, they typically receive these events and delegate them to a controller.

Example

Benefits

  • Either the UI classes or the problem/software domain classes can change without affecting the other side.
  • The controller is a simple class that mediates between the UI and problem domain classes, just forwards
  • event handling requests
  • output requests

Related GRASP Patterns

    Comments

    Post a Comment

    Popular posts from this blog

    Design Patterns used in Hibernate Framework

    Image
    In this post, let's discuss a different kind of design patterns which are widely used in the Hibernate Framework. Design Patterns denote the best computer programming practices in the object-oriented software development. Hibernate framework has been built by using the following design pattern or standard practices. I list few known design patterns used in Hibernate Framework. Please mention in a comment, if you know any other design patterns used in Hibernate Framework. You can also read my post of  Design Patterns used in Spring Framework Domain Model Pattern The domain model is treated as POJO in Hibernate. The domain model is an object model of the domain that incorporates both behavior and data. Read more about Domain Model Pattern here https://stackoverflow.com/questions/41335249/domain-model-pattern-example Proxy Design Pattern Proxy Pattern for lazy loading - https://docs.jboss.org/hibernate/orm/3.3/reference/en/html/performance.html Proxy Pattern provides a surrogate or pl
    Read more

    Value List Handler

    The  Value List Handler  provides the search and iteration functionality. To perform a search, the Value List Handler uses a  Data Access Object  to execute the query and retrieve the matching results from the database. It is hard to understand this pattern so my suggestion is to go to  source code  section and have a look at code step by step gives you more clarity. This pattern is divided into a number of sections for simplicity like problem, forces, solution etc. Problem (Problem section describes the design issues faced by the developer) You have a remote client that wants to iterate over a large results list. Forces (This section describes Lists the reasons and motivations that affect the problem and the solution. The list of forces highlights the reasons why one might choose to use the pattern and provides a justification for using the pattern) You want to avoid the overhead of using EJB finder methods for large searches. You want to implement a read-only use-case that does
    Read more