Editing Model–view–controller (section)

==Interactions==
In addition to dividing the application into a model, a view and a controller component, the MVC [[Software design pattern|design pattern]] defines the interactions between these three components :<ref name="posa">Buschmann, Frank (1996) ''Pattern-Oriented Software Architecture''.</ref>
* The model is responsible for managing the data of the application. It receives user input from the controller.
* The view renders presentation of the model in a particular format.
* The controller responds to the user input and performs interactions on the data model objects. The controller receives the input, optionally validates it and then passes the input to the model.

As with other software patterns, MVC expresses the "core of the solution" to a problem while allowing it to be adapted for each system.<ref name="gof">Gamma, Erich et al. (1994) ''Design Patterns''</ref> Particular MVC designs can vary significantly from the traditional description here.<ref>Moore, Dana et al. (2007) ''Professional Rich Internet Applications: Ajax and Beyond'': "Since the origin of MVC, there have been many interpretations of the pattern. The concept has been adapted and applied in very different ways to a wide variety of systems and architectures."</ref>