Essential modeling: use cases for user interfaces
interactions
The use-case construct in object-oriented software engineering
Scenario-based design
An integration of scenarios with their purposes in task modeling
Proceedings of the 1st conference on Designing interactive systems: processes, practices, methods, & techniques
Maintaining a focus on user requirements throughout the development of clinical workstation software
Proceedings of the ACM SIGCHI Conference on Human factors in computing systems
Applying use cases: a practical guide
Applying use cases: a practical guide
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
Scenarios in System Development: Current Practice
IEEE Software
Towards A Task-Based Methodology For Designing GUIs
SEEP '96 Proceedings of the 1996 International Conference on Software Engineering: Education and Practice (SE:EP '96)
| Hi-index | 0.00 |
Use cases are increasingly recognized as a particularly versatile form of task model. Use cases are related to scenarios, which have a long history of application to computer-human interaction [2], but may offer distinct advantages. A use case comprises a single case of use of a system that is complete, well-defined, and meaningful from the perspective of an external user [5,8]. Concrete instances of multiple use cases can be combined into plausible sequences to form the narrative vignettes usually associated with scenario-based design, but because use cases are a finer-grained formal construct at a higher level of abstraction, they lend themselves to more rigorous definition and more systematic and structured expression. The structured narratives of use cases can be interrelated through formally defined constructs [6,8] to form a comprehensive model of the tasks to be supported by a system under design.