On the one hand, you can use the Model View Controller (MVC) concept to divide a Web Dynpro application into the three levels data retrieval, user interface, and data flow. On the other hand, you can split a Web Dynpro application into its individual components - that is, the different Web Dynpro units. The units model, view, and controller are three of the Web Dynpro units that you will implement during the development of a complex Web Dynpro application. A third way of looking at a Web Dynpro application is, of course, at file system level. All Web –Dynpro units consist of one or more Java classes and/or XML files, which are created automatically by the Web Dynpro Generator.
This section deals with the concepts and uses of the Web Dynpro elements, one example being the Web Dynpro Project. The purpose of these glossary sections is to provide an introduction to Web Dynpro technology and an opportunity to become familiar with the programming model.
The subsections of the individual sections, such as Creating a Web Dynpro Project, describe how to work with, create and edit Web Dynpro units. The subsections also contain more detailed information on the individual Web Dynpro units. This introduction to the procedural methods of working with the Web Dynpro units is a preliminary stage to completing the Web Dynpro tutorials, which are also part of the Web Dynpro documentation.
The relevant Java classes and XML files are discussed in the individual sections on the Web Dynpro units; the sections also inform you where these classes and files are stored.
The following graphic shows a possible Web Dynpro application scenario. In this application, existing SAP data is accessed, and the role of each Web Dynpro unit can be seen in the graphic.