Keystroke-level model: Difference between revisions

Revision as of 14:00, 19 October 2007

Revision as of 10:13, 23 October 2007

Line 1:

'''KLM''' (or KLM-GOMS) stands for '''Keystroke-Level Model''', a hard science approach to [[human computer interaction]], based on CMN-[[GOMS]], developed by Card, Moran & Newell, and spelled out in their book ''The Psychology of Human Computer Interaction'', 1983.

It is designed to be easier to use than other [[GOMS]] methods, such that companies who cannot afford HCI[[human computer interaction]] specialists can use it.

The [http://www.cs.cmu.edu/~bej/cogtool/ CogTool] project has developed an open-source tool to support KLM-GOMS analysis.

==How does it work==

Line 21 ⟶ 19:

KLM is not the only technique for evaluating interfaces, but it can be used to compare the speed of two different interfaces designed to accomplish the same task.

==Problems with this model==

This method assumes that operator times are invariant and do not depend on the previous sequence of events. New physical operators can be added if their timing can be represented as a simple context-free function. KLM-GOMS does not account for either slips or mistakes automatically -- the analyst must create separate models of error sequences and perform their own sensitivity analysis.

The placement of the keystrokes and pointer operations are straightforward, but the placement of the mental operations is not. Mental operations are placed by a set of rules that require some interpretation, such as determining a conceptual "cognitive unit" or grouping of actions. For instance, pressing ctrl and c simultaneously to perform a "copy" would be considered a single cognitive unit. Mental operations are inserted before each cognitive unit to account for cognitive preparation and decision-making.

The main reason a designer or analysts would use this technique is that it is a very fast. Different designs or systems can be compared against one another quickly. It does not require that the evaluator be an expert in GOMS because the procedure is an explicitly laid out recipe. A major caution is that the algorithm is designed to estimate the execution time for an expert user, which is typically faster than the time for a new user or an unfamiliar task.

==External links==

*[http://www.cc.gatech.edu/classes/cs6751_97_fall/projects/closet2000+/FinalEssays/goms.html GOMS Analysis Techniques - Final Essay]

*The [http://www.cs.cmu.edu/~bej/cogtool/ CogTool] project has developed an open-source tool to support KLM-GOMS analysis.

*[http://www.cs.umd.edu/class/fall2002/cmsc838s/tichi/goms.html GOMS by Lorin Hochstein]

*[http://www.cs.cmu.edu/~bej/cogtool/ The CogTool project] at [[Carnegie Mellon University]]

Line 29 ⟶ 37:

==References==

*This article incorporates text from [http://www.cc.gatech.edu/classes/cs6751_97_fall/projects/closet2000+/FinalEssays/goms.html Dr. G. Abowd: GOMS Analysis Techniques - Final Essay], which has been released into [[GFDL]] by its author (see [http://en.wikipedia.org/w/index.php?title=Talk:GOMS&oldid=19999716]). Original references follow.

:*Dix, A., Finlay, J., Abowd, G., Beale, R., [http://www.hiraeth.com/books/hci/ Human Computer Interaction] , Prentice Hall, 1993

:*[http://c2000.gatech.edu/zenpad/classes/cs6751_97_Fall/Nov.4.1997.1/html/ Lecture Notes], Abowd, G., CS6751, Georgia Institute of Technology, Nov-1997

:*Kieras, D., John, B., [http://www.cs.cmu.edu/afs/cs.cmu.edu/user/clamen/mosaic/reports/1994.html The GOMS Family of Analysis Techniques: Tools for Design and Evaluation], CMU-HCII-94-106, 1994

:*Kieras, D., John, B., Using GOMS for User Interface Design and Evaluation: Which Technique?, June-1996

:*Kieras, D., John, B., The GOMS Family of User Interface Analysis Techniques: Comparison and Contrast

:*[http://ei.cs.vt.edu/~cs5724/g2/index.html Lecture Notes], CS5724, Virginia Tech, Fall 1996

{{Harvard reference

Line 48 ⟶ 69:

| URL = ftp://www.eecs.umich.edu/people/kieras/GOMS/KLM.pdf }}

<references/>

[[Category:Human-computer interaction]]

{{comp-sci-stub}}