University of Rostock, Department of Computer Science
Albert-Einstein-Str. 21, 18051 Rostock Germany
Up to now, there have been different points of view on how to develop interactive software. On one hand, the community of traditional software engineers insisted and part of it still insists in a more or less complete and more or less formal specification of the functionality of an application in the course of design that has finally to be implemented. After finishing these steps the specification of user interfaces is performed, thus leading to a more or less complete integration of the user interface into the application. As an example have a look at the papers concerning UML. On the other hand the community of software ergonomists mostly pursues a completely orthogonal strategy: The user interface is designed and specified before the functionality of an application is going to be specified. As a consequence, the desired functionality of a software system has to be derived from more or less complex interaction feature and modality specifications.
We are going to show the mutual relationships involved in model-based development based on end-user tasks (section 2). We then proceed with discussing the role of the existing and envisioned models (section 3). We will finally give a strategy for the implementation (section 4). Section 5 concludes the paper summarising the achievements and identifying topics for further research.
In this section we are going to develop an understanding on how many steps have to be performed before a dialog or application model can be specified in the context of end-user tasks. Interactive system development that takes into