 |
The Eighth International Conference on Digital Telecommunications ICDT 2013 April 21 - 26, 2013 - Venice, Italy |
| Tutorials |
Requirements Meet Interaction Design
by Prof. Dr. Hermann Kaindl, Vienna University of Technology, Austria
When the requirements and the interaction design of a system are separated, they will most likely not fit together, and the resulting system will be less than optimal. Even if all the real needs are covered in the requirements and also implemented, errors may be induced by human-computer interaction through a bad interaction design and its resulting user interface. Such a system may even not be used at all. Alternatively, a great user interface of a system with features that are not required will not be very useful as well.
So, the main topics of this tutorial are requirements and (communicative) interaction design, as well as their joint modeling through discourse models and ontologies. Our discourse models are derived from results of human communication theories, cognitive science and sociology (even without employing speech or natural language). While these models were originally devised for capturing interaction design, it turned out that they can be also viewed as specifying classes of scenarios, i.e., use cases. In this sense, they can also be utilized for specifying requirements. Ontologies are used to define domain models and the domains of discourse for the interactions with software systems. User interfaces for these software systems can be generated semi-automatically from our discourse models, domain-of-discourse models and specifications of the requirements. This is especially useful when user interfaces for different devices are needed. So, requirements meet interaction design to make applications both more useful and usable.
