Abstract
In user interface engineering, scenarios are stories that capture information about users and their tasks, including the context of use. Scenarios are generally documented using natural languages in order to understand, validate and use them effectively and efficiently throughout the development lifecycle. Stakeholders and software developers need to understand scenarios and translate them into design solutions. This paper discusses how use case maps, a visual notation for representing scenarios, with the complicity of formal requirements engineering methods, can lead to a comprehensive framework for representing and validating scenarios while improving and mediating the communication between usability engineers and software development teams. Particular attention is given to the extended use case maps as well as to a number of heuristics for formal validation.
--
Daniel Amyot - 12 Aug 2006
Discussion
- Full paper can be obtained from the ACM Portal
- Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.