Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Challenging Universal Truths of Requirements Engineering
IEEE Software
Steps toward a partnership: ethnography and system design
Requirements engineering
The Muse method for usability engineering
The Muse method for usability engineering
Requirements Elicitation and Validation with Real World Scenes
IEEE Transactions on Software Engineering
Information ecologies: using technology with heart
Information ecologies: using technology with heart
Usability engineering: scenario-based development of human-computer interaction
Usability engineering: scenario-based development of human-computer interaction
Model-Based Design and Evaluation of Interactive Applications
Model-Based Design and Evaluation of Interactive Applications
Goal-Based Requirements Analysis
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
A unified description formalism for complex HCI-systems
SEFM '05 Proceedings of the Third IEEE International Conference on Software Engineering and Formal Methods
HOPS: A Prototypical Specification Tool for Interactive Systems
Interactive Systems. Design, Specification, and Verification
Proceedings of the 1st ACM SIGCHI symposium on Engineering interactive computing systems
An Exploration of Perspective Changes within MBD
Proceedings of the 13th International Conference on Human-Computer Interaction. Part I: New Trends
Effective integration of task-based modeling and object-oriented specifications
HCI'07 Proceedings of the 12th international conference on Human-computer interaction: interaction design and usability
Towards activity representations for describing task dynamics
TAMODIA'07 Proceedings of the 6th international conference on Task models and diagrams for user interface design
Hi-index | 0.00 |
In this paper, a small case study is presented to illustrate our conceptual understanding of a task-based requirements process. We argue that sub-models as known in model-based design (e.g. task models, dialog models) support the reflection about an existing work situation at a conceptual level and allow a formal specification of requirements. However, it is also shown that the integration of complementary analysis approaches facilitates a richer consideration of social as well as technical aspects. An intertwined creation of models differing in their focus and in the degree of abstraction and formality supports a more effective requirements elicitation and elaboration. In addition, the paper discusses some crucial issues in task- and model-based design such as the 'myth' of generalised task models, the different roles of task and dialog models, or the influence of intentions on models of current situations. We hope to contribute to a further clarification of the problem space.