The main reasons for using the extension mechanisms of the UML instead of a proprietary modelling techniques is the acceptance of the UML in thedevelopment of software systems, flexibility for the definition of a Web domain specific modelling language: a so-called UML profile, and wide visual modelling support by existing UML CASE tools.
UWEuses "pure" UML notation and UML diagram types whenever possible for the analysis and design of Web applications, i.e. without extensions of any type. For the Web specific features, such as nodes andlinks of the hypertext structure, the UWE profile includes stereotypes, tagged values and constraints defined for the modelling elements. The UWE extension covers navigation, presentation, businessprocesses and adaptation aspects. The UWE notation is defined as a "lightweight" extension of the UML.
Overview of the UWE models:
(UMLet source file of this image)
The UWE design approachfor Web business processes consists of introducing specific process classes that are part of a separate process model with a defined interface to the navigation model. To model adaptive features of Webapplications in a non-invasively way, UWE uses techniques of aspect-oriented modelling (AOM). Following the separation of concerns principle UWE proposes to build an adaptive model for personalized orcontext-dependent systems and weave the models afterwards.
Example for a Navigation Diagram: (more examples in the Model Examples section)
Computer aided design using the UWE method is...