MVC

MVC (Model-View-Controller) is a pattern in software design commonly used to implement user interfaces, data, and controlling logic. It emphasizes a separation between the software's business logic and display. This "separation of concerns" provides for a better division of labor and improved maintenance. Some other design patterns are based on MVC, such as MVVM (Model-View-Viewmodel), MVP (Model-View-Presenter), and MVW (Model-View-Whatever).

The three parts of the MVC software-design pattern can be described as follows:

  • Model: Manages data and business logic.
  • View: Handles layout and display.
  • Controller: Routes commands to the model and view parts.
  • Model View Controller example

    Imagine a simple shopping list app. All we want is a list of the name, quantity and price of each item we need to buy this week. Below we'll describe how we could implement some of this functionality using MVC.

    The Model

    The model defines what data the app should contain. If the state of this data changes, then the model will usually notify the view (so the display can change as needed) and sometimes the controller (if different logic is needed to control the updated view).

    Going back to our shopping list app, the model would specify what data the list items should contain — item, price, etc. — and what list items are already present.

    The View

    The view defines how the app's data should be displayed.

    In our shopping list app, the view would define how the list is presented to the user, and receive the data to display from the model.

    The Controller

    The controller contains logic that updates the model and/or view in response to input from the users of the app.