Designing Web Dynpro Applications

1
Designing Web Dynpro Applications
2
Overview

• Analysis Phase
• Design Phase
• Architectural Design
• Detail Design
• Implementation Phase

3
Example Application
4
Architectural Design

• Modeling Development Components
• Modeling Web Dynpro Projects

5
Modeling Development Components

• Which development components are part of the
  software to be developed?
• Which development components must be developed,
  which can be reused?
• On which hierarchical structure are the
  development components based?
• Which dependencies exist between the development
  components?
• Which Public Parts are published?

6
Development Component Diagram
7
Modeling Web Dynpro Projects

• Which Web Dynpro components make up the Web
  Dynpro projects used?
• Which Web Dynpro components contain interface
  views of other Web Dynpro components?
• Which models are used in the Web Dynpro projects?
• Which Web Dynpro components use which model?
• Which Web Dynpro component interfaces are
  defined in the Web Dynpro projects?

8
Modeling Web Dynpro Projects

• Which Web Dynpro components implement which Web
  Dynpro component interfaces?
• Which Web Dynpro components use which Web Dynpro
  component interfaces?
• Which method calls exist between the Web Dynpro
  components and which results are used between the
  Web Dynpro components?
• Which context mappings exist between the Web
  Dynpro components?

9
Web Dynpro Project Diagram
10
Detail Design

• First, model the Web Dynpro components.
• Second, model the Web Dynpro windows.

11
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?

12
Web Dynpro Component Diagram
13
Web Dynpro Component Diagram
14
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?

15
Web Dynpro Window Diagram
16
Web Dynpro Window Diagram
17
Interface Design

• Simple applications
• Use the smallest possible number of UI elements
  that require input by the user
• Only offer a small number of navigation options
  to avoid confusing the user
• Have only a few or no dependencies between data
  and views

18
Interface Design

• Supportive applications
• Support the user in executing his or her tasks
  without requiring much training
• Allow the user to return to the previous page
• Provide the user with input help

19
Interface Design

• Intuitive applications
• Are as self-explanatory and easy to handle as
  possible
• Are easy to understand
• Do not require extensive instructions or
  documentation