The Z notation: a reference manual
The Z notation: a reference manual
Formal methods: state of the art and future directions
ACM Computing Surveys (CSUR) - Special ACM 50th-anniversary issue: strategic directions in computing research
Programs that offer fast, flawless, logical reasoning
Communications of the ACM
Supporting Scenario-Based Requirements Engineering
IEEE Transactions on Software Engineering
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Software for use: a practical guide to the models and methods of usage-centered design
Software for use: a practical guide to the models and methods of usage-centered design
Object Oriented Systems Development
Object Oriented Systems Development
Object-Oriented Systems Design: An Integrated Approach
Object-Oriented Systems Design: An Integrated Approach
What design heuristics may enhance the utility of a formal specification?
SAICSIT '02 Proceedings of the 2002 annual research conference of the South African institute of computer scientists and information technologists on Enablement through technology
Towards a UML for Interactive Systems
EHCI '01 Proceedings of the 8th IFIP International Conference on Engineering for Human-Computer Interaction
Scenario Usage in System Development: A Report on Current Practice
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Use Case Maps: A Roadmap for Usability and Software Integrated Specification
Proceedings of the IFIP 17th World Computer Congress - TC13 Stream on Usability: Gaining a Competitive Edge
Use case evaluation (UCE): a method for early usability evaluation in software development
INTERACT'07 Proceedings of the 11th IFIP TC 13 international conference on Human-computer interaction
Hi-index | 0.00 |
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.