Model-view-controller explained

Model-view-controller (MVC) is an architectural pattern, which at the same time is also a Multitier architecture, used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the

user interface will not affect data handling, and that the data can be reorganized without changing the userinterface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller.

History

The pattern was first described in 1979[1] by Trygve Reenskaug, then working on Smalltalk at Xerox research labs. The original implementation is described in depth in the influential paper Applications Programming in Smalltalk-80: How to use Model-View-Controller.[2]

Pattern description

It is common to split an application into separate layers: presentation (UI), domain logic, and data access. In MVC the presentation layer is further separated into view and controller. MVC encompasses more of the architecture of an application than is typical for a design pattern.

Model
  • The domain-specific representation of the information on which the application operates. Domain logic adds meaning to raw data (e.g., calculating if today is the user's birthday, or the totals, taxes, and shipping charges for shopping cart items).

    Many applications use a persistent storage mechanism (such as a database) to store data. MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the Model.

    View

    Renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes.

    Controller

    Processes and responds to events, typically user actions, and may invoke changes on the model.

    MVC is often seen in web applications, where the view is the actual HTML page, and the controller is the code that gathers dynamic data and generates the content within the HTML. Finally, the model is represented by the actual content, usually stored in a database or XML files.

    Though MVC comes in different flavors, control flow generally works as follows:

    1. The user interacts with the user interface in some way (e.g. presses a button).
    2. A controller handles the input event from the user interface, often via a registered handler or callback.
    3. The controller accesses the model, possibly updating it in a way appropriate to the user's action (e.g. controller updates user's Shopping cart).[3]
    4. A view uses the model (indirectly) to generate an appropriate user interface (e.g. the view produces a screen listing the shopping cart contents). The view gets its own data from the model. The model has no direct knowledge of the view.
    5. The user interface waits for further user interactions, which begins the cycle anew.

    By decoupling models and views, MVC helps to reduce the complexity in architectural design, and to increase flexibility and reuse.

    Selected frameworks

    GUI frameworks

    Java: Java Swing

    Java Swing is different from the other frameworks, in that it supports two MVC patterns.

    Model (Frame level)
  • Like the other frameworks, the design of the real model is usually left to the developer.
    Model (Control level)

    Swing also supports models on the level of controls (elements of the graphical user interface). Unlike other frameworks, Swing exposes the internal storage of each control as a model.

    View
  • The view is represented by a class that inherits from Component.
    Controller

    Java Swing doesn't necessarily use a single controller. Because its event model is based on interfaces, it is common to create an anonymous action class for each event. In fact, the real controller is in a separate thread (the Event dispatching thread). It catches and propagates the events to the view and model.

    Web frameworks

    Python: Django

    The Django (web framework) web framework, among others, supports the MVC pattern, but prefers to call it *MTV*, for Model-Template-View

    Combined frameworks

    Java: Java Enterprise Edition (Java EE)

    Unlike the other frameworks, Java EE defines a pattern for model objects.

    Model

    The model is commonly represented by entity beans, although the model can be created by a servlet using a business object framework such as Spring.

    View
  • The view in a Java EE application may be represented by a Java Server Page, which may be currently implemented using JavaServer Faces Technology (JSF). Alternatively, the code to generate the view may be part of a servlet.
    Controller

    The controller in a Java EE application may be represented by a servlet, which may be currently implemented using JavaServer Faces (JSF).

    Implementations of MVC as GUI frameworks

    Smalltalk's MVC implementation inspired many other GUI frameworks, such as the following:

    Visual FoxExpress is a Visual FoxPro MVC framework.

    Implementations of MVC as web-based frameworks

    In the design of web applications, MVC is implemented by web template systems as "View for web" component.

    MVC is also known as a "Model 2" architecture in Sun parlance. Complex web applications continue to be more difficult to design than traditional applications, and MVC is being pushed as a potential solution to these difficulties.

    ASP

    .NET

    ActionScript

    ColdFusion

    Erlang

    Java

    MVC web application frameworks:

    JavaScript

    Informix 4GL

    Perl

    PHP

    Python

    Ruby

    See also

    References

    1. http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html
    2. http://st-www.cs.uiuc.edu/users/smarch/st-docs/mvc.html
    3. Complex controllers are often structured using the command pattern to encapsulate actions and simplify extension.

    External links

    General information regarding MVC