Task models as basis for requirements engineering and software execution

Abstract

In this paper we discuss an approach linking GUI specifications to abstract dialog models. Both specifications are based on task models describing behavioral features. It will be shown how first prototypes of interactive systems, which are generated from user interface models, can help to capture requirements. Users can interactively play with prototypes. Tool support is also provided for co-operative work of different users, which starts with abstract canonical prototypes that can evolve to concrete GUI specifications.

Automatic Generation of User Interface Models and Prototypes from Domain and Use Case Models

“…Elkoutbi's approach is then able to derive UI prototypes for every interface object defined in the class diagram. Forbrig et al (Wolff et al, 2005a;Wolff et al, 2005b;Javahery et al, 2007;Radeke et al, 2007;Forbrig et al, 2004;Reichart et al, 2004) developed an approach that interactively generates an abstract UI model, and then a concrete UI, by applying UI-patterns to elements of UI submodels (e.g. task models).…”

Automated Usability Evaluation during Model-Based Interactive System Development

“…During the analysis process, the UIM has to handle four different situations: receiving new information (1), already known information (2), known information with differing values (3), or a request for information (4). Situations 1 and 2 are easy to handle.…”

“…In order to attend to these issues we combined two approaches: The Mental Models (MeMo) workbench, a workbench for AUE and the Multi-Access Service Platform (MASP), a model-based framework for UI generation. Model-based UI development approaches [1,2,3,4] already support the generation of multi-platform user-interfaces as well as context-of-use adaptation. They contain semantics stored in a well-structured form of declarative design models.…”

Task Model-Based Usability Evaluation for Smart Environments

“…Task models in this approach are constructed in CTT (Concurrent Task Trees) [6] notation, describing single actions and their hierarchical and temporal relations. One of the tools called DiaTask [8] allows developing a dialog graph that represents the navigation structure of the interactive system. Such a graph is based on the previous specified task model.…”

“…Each record of the captured task event trace comprises a time stamp, the conducted test case, the task model, the task, the fired event and the success value. The applied task model simulation engine [8] instantiates a task model and conducts a simulation through receiving events from user interactions and exchanging events between task nodes within the task model. Events cause state changes of the task nodes.…”