Adoption of Requirements Engineering: Conditions for Success
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
A discourse model for interaction design based on theories of human communication
CHI '06 Extended Abstracts on Human Factors in Computing Systems
Generating an Abstract User Interface from a Discourse Model Inspired by Human Communication
HICSS '08 Proceedings of the Proceedings of the 41st Annual Hawaii International Conference on System Sciences
Modeling of interaction design by end users through discourse modeling
Proceedings of the 13th international conference on Intelligent user interfaces
Transforming Discourse Models to Structural User Interface Models
Models in Software Engineering
How to Combine Requirements Engineering and Interaction Design?
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Fully automatic user interface generation from discourse models
Proceedings of the 14th international conference on Intelligent user interfaces
UI prototyping for multiple devices through specifying interaction design
INTERACT'07 Proceedings of the 11th IFIP TC 13 international conference on Human-computer interaction
On confusion between requirements and their representations
Requirements Engineering
Automated generation of device-specific WIMP UIs: weaving of structural and behavioral models
Proceedings of the 3rd ACM SIGCHI symposium on Engineering interactive computing systems
A design process based on a model combining scenarios with goals and functions
IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans
| Hi-index | 0.00 |
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 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.