Académique Documents
Professionnel Documents
Culture Documents
The purpose of this system is to express the requirements for Web applications that allow navigation between static hypertext pages. This is a simple example that shows how to express the modularization of the hypertext into pages and the elementary navigation step.
UWE models
This example was modelled with UWE Profile - v1.9 defined in the Magic Draw 16.8 CASE tool and is available as mdzip and emf. UWE specifies Web applications following the separation of concerns, i.e. modelling content, navigation structure and presentation separately. Content elements are specified using a plain UML class diagram, which contains classes, attributes, associations, inheritance relationships, association classes, and further UML model elements. Figure 1 shows the content model of the running example, with the classes defined for Project, Article, Section and Acknowledgement.
Figure 1. The content model of the running example The hypertext structure is described using a navigation diagram, which consists of a set of nodes and links. UWE distinguishes among different types of nodes, such as navigation class, menu, index and query. Figure 2 shows the navigation model of the running example. It includes several navigation classes as Project, Article, sections such as SectionRequirements, one index (ArticleIndex), one menu (SectionMenu), Navigation class Project is identified as entry point of the Web application with the tagged value {isHome}.
Figure 2. The navigation structure of the Simple Web Site Figure 3 shows the presentation model of the running example. UWE uses a class diagram for the representation of presentation models. The container form is selected in order to provide a more intuitive representation of pages.