Sage Journals: Discover world-class research

Abstract

This paper proposes a technique to apply the protocol analysis method to usability testing. The “trouble analysis” method is offered for data analysis tasks. These techniques involve a procedure to improve time efficiency and convenience. As a criterion for data analysis, a “trouble model”, which consists of 22 trouble categories, is also offered. Most of the problems in a user-interface can be identified by extracting troubles from the verbal protocols using the model. In the trouble analysis technique, analyses of the human cognitive/thought processes, which usually requires expert knowledge and a lot of time, are not taken into consideration. Quick and easy detection of problems is first considered. The “trouble analysis” technique contributions to usability testing were empirically verified through 9 tests, employed on different kinds of products. The evaluation extent limitation, and user behavior during trouble situations, are also discussed.

Get full access to this article

View all access options for this article.

References

Asahi

Miyai

(1988). “Troubles” in human-computer dialogue. Proc. of Human Interface Symposium, 4, 235–238 (in Japanese).

Bailey

W.A.

Kay

E.J.

(1986). Towards the standard analysis of verbal data. IEEE Systems, Man, and Cybernetics Proceedings, 582–587.

Dumas

J.S.

(1989). Stimulating change through usability testing. ACM SIGCHI Bulletin, 21, 1, 37–44.

Ericsson

K.A.

Simon

H.A.

(1984). Protocol Analysis: Verbal reports as data. Cambridge, Massachusetts, MIT Press.

Gould

J.D.

(1988). Designing for usability: The next iteration is to reduce organizational barriers. Proc. of the Human Factors Society 32nd annual meeting, 1988, 1–9.

Kato

(1986). What “question-asking protocols” can say about the user interface. International Journal of Man-Machine Studies, 25, 659–673.

Mills

C.B.

(1987). Usability testing in the real world. ACM SIGCHI Bulletin, 19, 1, 43–46.

Mack

R.L.

Lewis

C.H.

Carroll

J.M.

(1983). Learning to use word processors: Problems and prospects. ACM Trans. on Office Information Systems, 1, 3, 254–271.

Montfold

S.J.

(1989). User observation: Guidelines for Apple developers. ACM SIGGRAPH 1989 COURSE NOTES, Usability Testing and Design Guidelines for Graphical User Interfaces.

10.

Schell

D.A.

(1986). Usability testing of screen design; Beyond standards, principles, and guidelines. Proc. of the Human Factors Society 30th annual meeting, 1212–1215.

11.

Shneiderman

(1987). Designing the user interface (Chap. 1). Addison-Wesley Publishing Co. Inc.

12.

Tyldesley

D.A.

(1988). Employing usability engineering in the development of office products. The Computer Journal, 31, 5, 431–436.

A Usability Testing Method Employing the “Trouble Model”

Abstract

Get full access to this article

References