Webdynpro Architecture

Webdynpro Architecture

Webdynpro Architecture is based on MVC Architecture.

The Model View Controller (MVC) design pattern contains a clear distinction between processing control, data model and displaying the data in the interface. These three areas are formally distinguished from each other by three objects: model, view and controller. As a result, you can easily split Web applications into logical units.

The model is used as an application object of the application data administration. It responds to information requests about its status, which usually come from the view, as well as to statements for status changes, which are usually sent by the controller. In this way, only the model is used to process data internally, without making reference to the application and its user interface.

There can be different views for a model, which can be implemented using different view pages.

The view handles the graphical and textual output at the interface and therefore represents the input and output data in each interface element, such as pushbuttons, menus, dialog boxes and so on. The view takes of visualization. To visualize the status, the view queries the model, or the model informs the view about possible status changes.

The controller interprets and monitors the data that is input by the user using the mouse and the keyboard, causing the model or the view later to change if necessary. Input data is forwarded and changes to the model data are initiated. The controller uses the model methods to change the internal status and then informs the view about this. This is how the controller determines reactions to the user input and controls processing.

Benefits of MVC

• It keeps your business logic separate from your (HTML-based) views
• Keeps your code clean and neat in one place

 Model

• Represents the information and the data from the database
• Validation of the data

 View

•  Data presentation and user data
•  Rendering models into one or more formats, such as HTML,XHTML, XML, or even JavaScript

 Controller

•  Dispatches requests and control flows
•  Connects the model with the view
•  Process the data that comes from the model.



MVC Architecture

I think you would have got a clear idea about MVC which is the base of the Webdynpro.


Any Suggestions are most welcome.

Thanks