Model-View-Controller (MVC)

In the model-view-controller concept, the representation of information is separated from the user's interaction:

• The view is responsible for defining and rendering the UI.
• The model manages the application data.
• The controller reacts to view events and user interaction by modifying view and model.

The purpose of data binding in the UI is to separate the definition of the user interface (view), the data that visualized by the application (model), and the code for the business logic for processing the data (controller). The separation has the following advantages: It provides a better readability, maintainability, and extensibility and it allows you to change the view without touching the underlying business logic and to define several views of the same data.

With this pattern, a separation of concerns is achieved that facilitates development and change of parts independently.

Views and controllers often form a 1:1 relationship, but it is also possible to have controllers without UI, these controllers are called application controllers. It is also possible to create views without controllers. From a technical position, a view is a SAPUI5 control and can have or inherit a SAPUI5 model.

View and controller represent reusable units and distributed development is highly supported.