Detail Design 

Purpose

The following process steps should be executed when designing a Web Dynpro application in detail. These steps provide a more detailed description of the architecture, on which the implementation is based.

Prerequisites

Before starting the detail design, you should perform the architecture design. Results of this step will be a development component diagram and a Web Dynpro project diragram. The development component diagram is the result of modeling on development component level. The Web Dynpro project diagram summarizes the results of modeling on Web Dynpro project level. These diagrams represent the rough architecture design of the Web Dynpro application and determine its structure.

Process Flow

Based on the Web Dynpro project diagram you created, you now start the detail design. First of all, the detailed design models the Web Dynpro components, followed by the Web Dynpro windows. Below, we summarize the questions to which you try to find answers on the modeling levels mentioned above.

 

·        Modeling Web Dynpro components:

¡        Which views make up the Web Dynpro component?

¡        Which custom controllers are used in the Web Dynpro components?

¡        Which methods and events are defined within the Web Dynpro components?

¡        In which controllers are the methods and events defined within the Web Dynpro components?

¡        Which context elements are defined within the Web Dynpro components?

¡        In which controllers are the context elements defined within the Web Dynpro components?

¡        Which context elements are bound or mapped?

·        Modeling Web Dynpro windows:

¡        How should the views be arranged?

¡        Which navigation paths exist between the views?

¡        Which UI elements are contained in the views?

¡        How should the UI elements of a view be arranged?

¡        To which context elements are the UI elements bound?

¡        To which actions are the UI elements bound?