Navigation auf uzh.ch

Suche

Department of Informatics Requirements Engineering Research Group

ADORA Features

Introduction

Most current method based tools have weaknesses in the visualization of object hierarchies as they provide only simple explosive zoom as the only means of visualization of these hierarchies. Therefore, in terms of tool development we have concentrated on an adequate visualization of ADORA models.

A good visualization concept is critical both for understandability and ease-of-use of graphical models. A good concept should:

  • Support orientation in the model by visualizing as much local detail as needed without losing the global context of the focused elements.
  • Minimize the cognitive overhead for navigation, increase expressiveness by including the semantics of the model in the visualization.
  • Foster understandability by supporting the abstraction mechanisms of the model.

Our approach to visualize hierarchical object models and ADORA models is based on the notion of fisheye views. This concept can display local detail and global context of a view in the same diagram, thus allowing a user to easily navigate in hierarchical structures.

Smart Visualization Techniques

Fisheye View

In ADORA, the modeled system can be decomposed into recursive objects (respectively into elements that may be part of an object, like states). We use a fisheye view concept for visualizing a component in its surrounding hierarchical context. This is done by setting one or more foci on the interesting parts of the model. By using fisheye views navigation through a set of hierarchical decomposed diagrams is simplified and comprehensibility is improved. The following figure illustrates the fisheye view with one main focus on the RoomModule object of the system. The elements of the RoomModule are shown in more detail and the surrounding context is also available.

Figure 1: An example for setting a focus in a model.

Space Management in Diagrams

With conventional graphical modeling tools, editing a diagram always entails layout problems. When inserting an element into an existing diagram, the space required for the new element has to be created manually by shifting existing elements of the diagram apart. On the other hand, removing elements from a diagram yields empty space. Compacting the resulting diagram again has to be done manually. Another aim is to preserve the so-called secondary notation - as it bears important clues for remembering and comprehending the meaning of a diagram, users typically want to preserve the secondary notation when modifying a diagram. Therefore the application of relayouting algorithmes should be avoided due to the fact that they cause the loss of the secondary notation.In the ADORA Tool Prototype, there is a layout adaptation technique which automatically expands or contracts a diagram layout when elements are inserted or removed, while preserving the secondary notation. Such a technique is not only convenient for inserting or deleting elements. It is a key prerequisite for implementing aspect-oriented visualization techniques. The following Figures 1 and 2 illustrate this visualization techniques.

Figure 2: Model before inserting of a further object - the model consists of objects A, B, C, D and E
Figure 3: Object F is inserted in the middle of the model, the surrounding objects are radially shifted away, so that this leads to enough place for inserting object F.

View Visualization

Beside using fisheye views, there is the possibility to show only specific aspects within a diagram of a model. Currently the ADORA Tool Prototype provides the following aspects which should be demonstrated by the following modeled System:

Figure 8: The context aspects are hidden. Context aspects means the actors in the system's context and its relationships to the system.
Figure 7: The user aspects are hidden. User aspects are expressed as szenarios. They are embedded into the component which corresponds to the scenario.
Figure 6: The behavioral aspects are hidden. Behavioral aspects contain the integrated statecharts of the model.
Figure 4: A fully modeled example system
Figure 5: The structural aspects are hidden. Structural aspects means the associations between objects visualizing the structural relationships.

Technical Features

Platform Independence

The ADORA Tool is implemented in Java and therefore portable to all systems which provide a Java Virtual Machine and the Eclipse Platform respectively. The prototype is runnable using Java 5, Java Runtime Environment 1.5.

Other Features

The ADORA Tool Prototype provides several other functionalities, like:

  • Storing models in a system independent XML file format.
  • Standard editing capabilities, such as copy, cut, paste and moving of objects.
  • Exporting models into Standard Vector Graphics (svg) format.
  • The ADORA Editor has its own Eclipse Perspective.

See also the screenshots of the ADORA Tool.

References

An introduction to the ADORA language can be found in [Glinz, Berner and Joos 2002] or [Glinz et al. 2001]. The current language definition is given in [Joos 1999]. The visualization concept for the language can be found in [Berner 2002]. A formal defintion of the language ADORA can be found in [Xia 2003]. The semi-formal simulation and model evolution features are summurized in [Glinz et al 2007]. An overview of the aspect-oriented features of the ADORA tool are described in [Meier et al. 2006].

Weiterführende Informationen

Title

Teaser text