Content deleted Content added
No edit summary |
Entranced98 (talk | contribs) Importing Wikidata short description: "Form of human–computer interaction" |
||
(34 intermediate revisions by 18 users not shown) | |||
Line 1:
{{Short description|Form of human–computer interaction}}
== Structure of the
The
* '''K''' (keystroke or button press): it is the most frequent operator and means keys and not characters (so e.g. pressing SHIFT is a separate K operation). The time for this operator depends on the motor skills of the user and is determined by one
* '''P''' (pointing to a target on a display with a mouse): this time differs depending on the distance to the target and the size of the target,<ref>{{cite journal|last1=Fitts|first1=Paul M|title=The information capacity of the human motor system in controlling the amplitude of movement|journal=Journal of Experimental Psychology: General|date=1992|volume=
* '''H''' (homing the hand(s) on the keyboard or other device): This includes movement between any two devices as well as the fine positioning of the hand.
* '''D''' (drawing (manually) n<sub>D</sub> straight-line segments with a total length of D(n<sub>D</sub>, l<sub>D</sub>) cm): where n<sub>D</sub> is the number of the line segments drawn and l<sub>D</sub> is the total length of the line segments. This operator is very specialized because it is restricted to the mouse and the drawing system has to constrain the cursor to a .56 cm grid.
* '''M''' (mentally preparing for executing physical actions): denotes the time a user needs for thinking or decision making. The number of Ms in a method depends on the knowledge and skill of the user. Heuristics are given to help decide where an M should be placed in a method. For example, when pointing with the mouse a button press is usually fully anticipated and no M is needed between both operators.<ref>{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=400–401|doi=10.1145/358886.358895|s2cid=5918086|ref=5|doi-access=free}}</ref> The following table shows the heuristics for placing the M operator:<ref>{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=400|doi=10.1145/358886.358895|s2cid=5918086|ref=5|doi-access=free}}</ref>
{| class="wikitable collapsible" border="1"
Line 26 ⟶ 27:
|}
* '''R''' (response time of the system): the response time depends on the system, the command and the context of the command. It is only used when the user actually has to wait for the system. For instance, when the user mentally prepares (M) for executing
The following table shows an overview of the times for the mentioned operators as well as the times for suggested operators:
Line 35 ⟶ 36:
|-
| K || total typing test time/total number of non-error keystrokes<br />
Guidelines:<ref name="klm-paper-operators-table">{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=399|doi=10.1145/358886.358895|s2cid=5918086|ref=5|doi-access=free}}</ref><ref name="klm-book-operators-table">{{cite book|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The Psychology of Human-Computer Interaction|date=1983|publisher=L. Erlbaum Associates Inc|___location=Hillsdale|isbn=
.08 (135 wpm: best typist)<br />
.12 (90 wpm: good typist)<br />
Line 48 ⟶ 49:
| H || 0.4<ref name="klm-paper-operators-table" /><ref name="klm-book-operators-table" />
|-
| D || .9n<sub>D</sub> + {{not a typo|. 16 l}}<sub>D</sub><ref name="klm-paper-operators-table" /><ref name="klm-book-operators-table" />
|-
| M || 1.35<ref name="klm-paper-operators-table" /><ref name="klm-book-operators-table" />
Line 56 ⟶ 57:
| colspan="2" | suggested operators
|-
| B (mouse button press or release) || 0.1<ref>{{cite web|last1=Kieras|first1=David|title=Using the Keystroke-Level Model to Estimate Execution Times|url=http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|accessdate=22 June 2015|ref=9|page=2|archive-date=19 March 2015|archive-url=https://web.archive.org/web/20150319195627/http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|url-status=dead}}</ref>
|-
| Click a Link/ Button || 3.73<ref name="sauro-suggested-operators">{{cite
|-
| Pull-Down List (No Page Load) || 3.04<ref name="sauro-suggested-operators" />
Line 75 ⟶ 76:
== Comparison with GOMS ==
The KLM is based on the keystroke level, which belongs to the family of [[GOMS]] models.<ref>{{cite book|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The Psychology of Human-Computer Interaction|date=1983|publisher=L. Erlbaum Associates Inc|___location=Hillsdale|isbn=
== Advantages ==
The KLM was designed to be a quick and easy to use system design tool, which means that no deep knowledge about [[psychology]] is required for its usage.<ref name="klm-paper-advantages">{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=409|doi=10.1145/358886.358895|s2cid=5918086|ref=19|doi-access=free}}</ref> Also, task times can be predicted (given the [[#Limitations|limitations]]) without having to build a [[prototype]], recruit and test users, which saves time and money.<ref>{{cite
== Limitations ==
The
* It measures only one aspect of performance: time,<ref>{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=400|doi=10.1145/358886.358895|s2cid=5918086|ref=21|doi-access=free}}</ref> which means execution time and not the time to acquire or learn a task <ref>{{cite book|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The Psychology of Human-Computer Interaction|date=1983|publisher=L. Erlbaum Associates Inc|___location=Hillsdale|isbn=
* It considers only expert users. Generally, users differ regarding their knowledge and experience of different systems and tasks, motor skills and technical ability <ref name="klm-paper-limitations-users">{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=397, 409|doi=10.1145/358886.358895|
* It considers only routine unit tasks <ref name="klm-paper-limitations">{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=409|doi=10.1145/358886.358895|s2cid=5918086|ref=24|doi-access=free}}</ref>
* The method has to be specified step by step.<ref name="klm-paper-limitations" /> This makes it more accessible to use for an average person without advanced technical skills.
* The execution of the method has to be error-free <ref name="klm-paper-limitations" />
* The mental operator aggregates different mental operations and therefore cannot model a deeper representation of the user’s mental operations. If this is crucial, a GOMS model has to be used (e.g. model K2)<ref>{{cite book|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The Psychology of Human-Computer Interaction|date=1983|publisher=L. Erlbaum Associates Inc|___location=Hillsdale|isbn=
Also, one should keep in mind when assessing a computer system that other aspects of performance (errors, learning, functionality, recall, concentration, fatigue, and acceptability),<ref>{{cite journal|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The keystroke-level model for user performance time with interactive systems|journal=Communications of the ACM|date=1980|volume=23|issue=7|pages=396–397|doi=10.1145/358886.358895|s2cid=5918086|ref=26|doi-access=free}}</ref> types of users (novice, casual)<ref name="klm-paper-limitations-users" /> and non-routine tasks have to be considered as well.<ref name="klm-paper-limitations-users"
Furthermore, tasks which take more than a few minutes take several hours to model and a source of errors is forgetting operations.<ref>{{cite
In addition, the KLM can not make a perfect prediction and has a root-mean-square error of 21%.<ref>{{cite book|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The Psychology of Human-Computer Interaction|date=1983|publisher=L. Erlbaum Associates Inc|___location=Hillsdale|isbn=
== Example ==
Line 99 ⟶ 100:
{| class="wikitable"
|-
! Design A: drag the file into the trash can<ref>{{cite web|last1=Kieras|first1=David|title=Using the Keystroke-Level Model to Estimate Execution Times|url=http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|accessdate=22 June 2015|ref=31|page=3|archive-date=19 March 2015|archive-url=https://web.archive.org/web/20150319195627/http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|url-status=dead}}</ref> !! Design B: use the short cut “control + T”<ref>{{cite web|last1=Kieras|first1=David|title=Using the Keystroke-Level Model to Estimate Execution Times|url=http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|accessdate=22 June 2015|ref=31|page=6|archive-date=19 March 2015|archive-url=https://web.archive.org/web/20150319195627/http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|url-status=dead}}</ref>
|-
| method encoding (operator sequence)<ref>{{cite web|last1=Kieras|first1=David|title=Using the Keystroke-Level Model to Estimate Execution Times|url=http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|accessdate=22 June 2015|ref=32|page=9|archive-date=19 March 2015|archive-url=https://web.archive.org/web/20150319195627/http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|url-status=dead}}</ref>|| method encoding (operator sequence)<ref>{{cite web|last1=Kieras|first1=David|title=Using the Keystroke-Level Model to Estimate Execution Times|url=http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|accessdate=22 June 2015|ref=33|page=10|archive-date=19 March 2015|archive-url=https://web.archive.org/web/20150319195627/http://www-personal.umich.edu/~itm/688/KierasKLMTutorial2001.pdf|url-status=dead}}</ref>
|-
|
Line 132 ⟶ 133:
== Adaptions ==
The six operators of the KLM can be reduced, but this decreases the accuracy of the model. If this low of an accuracy makes sense (e.g. “back-of-the-envelope” calculations) such a simplification can be sufficient.<ref>{{cite book|last1=Card|first1=Stuart K|last2=Moran|first2=Thomas P|last3=Newell|first3=Allen|title=The Psychology of Human-Computer Interaction|date=1983|publisher=L. Erlbaum Associates Inc|___location=Hillsdale|isbn=
While the existing KLM applies to desktop applications, the model might not fulfill the range of mobile tasks,<ref>{{cite
While Li and Holleis <ref>{{cite
Rice and Lartigue <ref>{{cite
They retain the operators Keystroke (K/B), Homing (H), Mental (M) and Response Time (R(t)) and suggest new touch specific operators partly based on Holleis’ suggested operators:
Line 157 ⟶ 158:
* [[CMN-GOMS]]
* [[CPM-GOMS]]
==References==▼
{{reflist|2}}
==External links==
Line 162 ⟶ 166:
*Simple [http://www.syntagm.co.uk/design/klmcalc.shtml KLM calculator] (free, downloadable Windows app)
*The [http://klmformanalyzer.weebly.com/index.html KLM Form Analyzer (KLM-FA)], a program which automatically evaluates web form filling tasks (free, downloadable Windows app).
*The [
*[http://www.cs.umd.edu/class/fall2002/cmsc838s/tichi/goms.html GOMS by Lorin Hochstein]
▲==References==
[[Category:Human–computer interaction]]
|