Object-oriented development in an industrial environment
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
Improving a human-computer dialogue
Communications of the ACM
Cognitive dimensions of notations
Proceedings of the fifth conference of the British Computer Society, Human-Computer Interaction Specialist Group on People and computers V
A mathematical model of the finding of usability problems
INTERCHI '93 Proceedings of the INTERCHI '93 conference on Human factors in computing systems
Usability inspection methods
The cognitive walkthrough method: a practitioner's guide
Usability inspection methods
Scenario-based design: envisioning work and technology in system development
Scenario-based design: envisioning work and technology in system development
Evaluating a multimedia authoring tool
Journal of the American Society for Information Science - Special issue on current research in human-computer interaction
Applying UML and patterns: an introduction to object-oriented analysis and design
Applying UML and patterns: an introduction to object-oriented analysis and design
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
The unified software development process
The unified software development process
Writing Effective Use Cases
Comparing and reconciling usability-centered and use case-driven requirements engineering processes
AUIC '01 Proceedings of the 2nd Australasian conference on User interface
Use Case Modeling
Towards an inspection technique for use case models
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Guest Editors' Introduction: Introducing Usability
IEEE Software
Usability Basics for Software Developers
IEEE Software
Making use of scenarios: a field study of conceptual design
International Journal of Human-Computer Studies
The human-computer interaction handbook
The human-computer interaction handbook
SAICSIT '03 Proceedings of the 2003 annual research conference of the South African institute of computer scientists and information technologists on Enablement through technology
Reconditioned merchandise: extended structured report formats in usability inspection
CHI '04 Extended Abstracts on Human Factors in Computing Systems
Instant data analysis: conducting usability evaluations in a day
Proceedings of the third Nordic conference on Human-computer interaction
Situating evaluation in scenarios of use
CSCW '04 Proceedings of the 2004 ACM conference on Computer supported cooperative work
What do usability evaluators do in practice?: an explorative study of think-aloud testing
DIS '06 Proceedings of the 6th conference on Designing Interactive systems
How natural is natural language?: how well do computer science students write use cases?
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Proceedings of the 11th Brazilian Symposium on Human Factors in Computing Systems
Hi-index | 0.00 |
It is often argued that usability problems should be identified as early as possible during software development, but many usability evaluation methods do not fit well in early development activities. We propose a method for usability evaluation of use cases, a widely used representation of design ideas produced early in software development processes. The method proceeds by systematic inspection of use cases with reference to a set of guidelines for usable design. To validate the method, four evaluators inspected a set of use cases for a health care application. The usability problems predicted by the evaluators were compared to the result of a conventional think-aloud test. About one fourth of the problems were identified by both think-aloud testing and use case inspection; about half of the predicted problems not found by think-aloud testing were assessed as providing useful input to early development. Qualitative data on the evaluators' experience using the method are also presented. On this background, we argue that use case inspection has a promising potential and discuss its limitations.