GOMS

GOMS is a specialized human information processor model for human-computer interaction observation that describes a user's cognitive structure on four components. In the book The Psychology of Human Computer Interaction.[1] written in 1983 by the authors introduce: "a set of Goals, a set of Operators, a set of Methods for achieving the goals, and a set of Selections rules for choosing among competing methods for goals."[1] GOMS is a widely used method by usability specialists for computer system designers because it produces quantitative and qualitative predictions of how people will use a proposed system.

Overview

The concepts behind a GOMS model and their relationships

A GOMS model is composed of methods that are used to achieve specific goals. These methods are then composed of operators at the lowest level. The operators are specific steps that a user performs and are assigned a specific execution time. If a goal can be achieved by more than one method, then selection rules are used to determine the proper Method.

There are several different GOMS variations which allow for different aspects of an interface to be accurately studied and predicted.
For all of the variants, the definitions of the major concepts are the same. There is some flexibility for the designer's/analyst's definition of all of the entities. For instance, an operator in one method may be a goal in a different method. The level of granularity is adjusted to capture what the particular evaluator is examining. For a simple applied example see CMN-GOMS.

Qualification

Advantages

The GOMS approach to user modeling has strengths and weaknesses. This method is not necessarily the most accurate method to measure human-computer interface interaction but it certainly has its advantages, like the visibility of all procedural knowledge. With GOMS an analyst can easily estimate a particular interaction and can calculate it with little effort in a short amount of time and at little cost. This is only possible if the average Methods-Time Measurement data for each specific task has previously been measured experimentally to a high degree of accuracy.[2]

Disadvantages

GOMS only applies to skilled users. It does not work for beginners or intermediates for errors may occur which can alter the data.[3] Also the model doesn't apply to learning the system or a user using the system after a longer time of not using it.[3] Another big disadvantage is the lack of account for errors, even skilled users make errors but GOMS does not account for errors.[3] Mental workload is not addressed in the model, making this an unpredictable variable. The same applies to fatigue.[3] GOMS only addresses the usability of a task on a system, it does not address its functionality.[3]
User personalities, habits or physical restrictions (for example disabilities) are not accounted for in any of the GOMS models. All users are assumed to be exactly the same. Recently some extensions of GOMS were developed, that allow to formulate GOMS models describing the interaction behavior of disabled users.[4] [5] [6]

Variations

Basically there are four different GOMS models: the Keystroke-Level Model , CMN-GOMS, NGOMSL and CPM-GOMS. Each model has a different complexity and varies in activities.

KLM

The Keystroke-Level Model (KLM) is the first and simplest GOMS technique Stuart Card, Thomas P. Moran and Allen Newell created.[6] Estimating an execution time for a task is done by listing the sequence of operators and then totaling the execution times for the individual operators. With KLM the analyst must specify the method used to accomplish each particular task instance. Furthermore, the specified methods are limited to being in sequence form and containing only keystroke-level primitive operators.

KLM's execution part is described in four physical-motor operators:

One mental operator M that stands for the time a user has to mentally prepare himself to do an action, and a system response operator R in with the user has to wait for the system. Execution time is the sum of the times spent executing the different operator types:

Texecute = TK + TP + TH + TD + TM + TR.[1]

Each of these operators has an estimate of execution time, either a single value, a parameterized estimate.

Touch Level Model (TLM)

GOMS and it variants were designed for keyboard interfaces, nowadays a new type of interface is omnipresent. This addition to the GOMS family, together with updates to the existing KLM operators, is called the Touch Level Model (TLM). Andrew D. Rice and Jonathan W. Lartigue propose this model for the used to model human task performance on a constrained input touchscreen device and, with proper benchmarking, accurately predict actual user performance.[7]

The goal is to provide an instrument for quantitative analysis of touchscreen interfaces.
A number of operators are added for touchscreen interactions:

CMN-GOMS

CMN-GOMS is the original GOMS model proposed by Stuart Card, Thomas P. Moran and Allen Newell.
CMN stands for Card, Moran and Newell and it takes the KLM as its basic and adds subgoals and selection rules. This model can predict operator sequence as well as execution time. A CMN-GOMS model can be represented in program form, making it amenable to analysis as well as execution. CMN-GOMS has been used to model word processors [1] and CAD systems for ergonomic design(see CAD). [2] The CMN method can predict the operator sequence and the execution time of a task on a quantitative level and can focus its attention on methods to accomplish goals on a qualitative level.
In the example by Bonnie E. John and David E. Kieras a simple CMN-GOMS on editing a manuscript is shown.[2]

GOAL: EDIT-MANUSCRIPT

GOAL: EDIT-UNIT-TASK ...repeat until no more unit tasks
GOAL: ACQUIRE UNIT-TASK ...if task not remembered
GOAL: TURN PAGE ...if at end of manuscript
GOAL: GET-FROM-MANUSCRIPT
GOAL: EXECUTE-UNIT-TASK ...if a unit task was found
GOAL: MODIFY-TEXT
select: GOAL: MOVE-TEXT* ...if test is to be moved
GOAL: DELETE-PHRASE ...if a phrase is to be deleted
GOAL: INSERT-WORD ... if a word is to be inserted
VERIFY-EDIT

NGOMSL

NGOMSL is a structured natural language notation for representing GOMS models and a procedure for constructing them. This program form provides predictions of operator sequences, execution time and time to learn methods. An analyst constructs an NGOMSL model by performing a top-down, breadth-first expansion of the user's top-level goals into methods, until the methods contain only primitive operators, typically keystroke-level operators. This model explicitly represents the goal structure just like the CMN-GOMS and can so represent high-level goals.[8]
Shown below is a simple example.[2]

NGOMSL Statements
METHOD for GOAL: MOVE TEXT

STEP 1: ACCOMPLISH GOAL: CUT TEXT
STEP 2: ACCOMPLISH GOAL: PASTE TEXT
STEP 3: RETURN WITH GOAL ACCOMPLISHED

METHOD for GOAL: CUT TEXT

STEP 1: ACCOMPLISH GOAL: HIGHLIGHT TEXT
STEP 2: RETAIN THAT COMMAND IS CUT, AND
ACCOMPLISH GOAL: ISSUE A COMMAND
STEP 3: RETURN WITH GOAL ACCOMPLISHED

etc.

CPM-GOMS

Bonnie E. John and David Kieras describe four different types of GOMS. CMN-GOMS, KLM and NGOMSL assume that all of the operators occur in sequence and do not contain operators that are below the activity level. CPM-GOMS being the fourth method uses operators at the level of Model Human Processor which assumes that operators of the cognitive processor, perceptual processor, and the motor processor can work in parallel to each other. The most important point of CPM-GOMS is the ability to predict skilled behavior from its ability to model overlapping actions. [9] [10]

Shown below is a simple copy and paste example.[11]

GOAL COPY-AND-PASTE-TEXT

GOAL COPY-TEXT
GOAL HIGHLIGH-TEXT
Operator MOVE-CURSOR-TO-BEGINNING
Operator CLICK-MOUSE-BUTTON
Operator MOVE-CURSOR-TO-END
Operator SHIFT-CLICK-MOUSE-BUTTON
Operator VERIFY-HIGHLIGHT
GOAL ISSUE-COPY-COMMAND
Select*:
GOAL USE-MOUSE
Operator MOVE-CURSOR-TO-EDIT-MENU
Operator PRESS-MOUSE-BUTTON
Operator MOVE-CURSOR-TO-COPY-ITEM
Operator VERIFY-HIGHLIGHT
Operator RELEASE-MOUSE-BUTTON
GOAL USE-KEYBOARD
Operator PRESS-KEY-STRG
Operator PRESS-KEY-C
Operator RELEASE-KEYS
GOAL PASTE-TEXT[...]

*Selection rule for GOAL ISSUE-COPY-COMMAND
if HANDS-ARE-ON-KEYBOARD then

select GOAL USE-KEYBOARD

else

select GOAL USE-MOUSE

GOMS and KLM

The biggest difference between GOMS and KLM is how time is assigned to cognitive and perceptual operators when it comes to execution time predictions. Another major difference is that the goal-hierarchy is explicit in GOMS while it was implicit in the KLM. The nature of unobservable operators is another important difference. KLM has a single M operator that precedes each cognitive unit of action. In contrast, GOMS assigns no time to such cognitive overhead. But both models include M-like operators for substantial time-consuming mental actions such as locating information on the screen and verifying entries. Both methods assign roughly the same time to unobservable perceptual and cognitive activities. Also they make different assumptions about unobservable cognitive and perceptual operators and so distribute the time in different ways.[2] [12]

Assumptions and Errors

Importance of Assumptions in GOMS Analysis

Accurate assumptions are vital in GOMS analysis. Before applying the average times for detailed functions, it is very important that an experimenter make sure he or she has accounted for as many variables as possible by using assumptions. Experimenters should design their GOMS analysis for the users who will most likely be using the system which is being analyzed. Consider, for example, an experimenter wishes to determine how long it will take an F22 Raptor pilot to interact with an interface he or she has used for years. It can probably be assumed that the pilot has outstanding vision and is in good physical health. In addition, it can be assumed that the pilot can interact with the interface quickly because of the vast hours of simulation and previous use he or she has endured. All things considered, it is fair to use fastman times in this situation. Contrarily, consider an 80-year-old person with no flight experience attempting to interact with the same F22 Raptor interface. It is fair to say that the two people would have much different skill sets and those skill sets should be accounted for subjectively.

Accounting for Errors

The only way to account for errors in GOMS analysis is to predict where the errors are most likely to occur and measure the time it would take to correct the predicted errors. For example, assume an experimenter thought that in typing the word "the" it was likely that a subject would instead incorrectly type "teh." The experimenter would calculate the time it takes to type the incorrect word, the time it takes to recognize that a mistake has been made, and the time it takes to correct the recognized error.

Applications of GOMS

A successful implementation of CPM-GOMS was in Project Ernestine held by New England Telephone. New ergonomically designed workstations were compared to old workstations in terms of improvement in telephone operators' performance. CPM-GOMS analysis estimated a 3% decrease in productivity. Over the four-month trial 78,240 calls were analysed and it was concluded that the new workstations produced an actual 4% decrease in productivity. As the proposed workstation required less keystrokes than the original it was not clear from the time trials why the decrease occurred. However CPM-GOMS analysis made it apparent that the problem was that the new workstations did not utilize the workers' slack time. Not only did CPM-GOMS give a close estimate, but it provided more information of the situation.[13]

CAD

GOMS models were employed in the redesign of a CAD (computer-aided design) system for industrial ergonomics.[14] An applied GOMS model shows where the interface needs to be redesigned, as well as provides an evaluation of design concepts and ideas. In Richard Gong's example, when GOMS revealed a frequent goal supported by a very inefficient method, he changed the method to a more efficient one. If GOMS showed that there were goals not supported by any method at all, then new methods were added. GOMS also revealed where similar goals are supported by inconsistent methods, a situation in which users are likely to have problems remembering what to do, and showed how to make the methods consistent.[14]

Software Tools

There exist various tools for the creation and analysis of Goms-Models. A selection is listed in the following:

See also

References

  1. 1 2 3 4 Card, Stuart; Thomas P. Moran; Allen Newell (1983). The Psychology of Human Computer Interaction. Lawrence Erlbaum Associates. ISBN 0-89859-859-1.
  2. 1 2 3 4 5 John, Bonnie E.; David E. Kieras (1996). The GOMS Family of User Interface Analysis Techniques: Comparison and Contrast. United States of America: ACM. doi:10.1145/235833.236054. ISSN 1073-0516.
  3. 1 2 3 4 5 Rogers, Yvonne; Helen Sharp; Jenny Preece (2002). Interaction Design. United States of America: John Wiley & Sons. p. 454. ISBN 0-471-49278-7.
  4. ↑ Tonn-Eichstädt, H. (2005). Measuring website usability for visually impaired people – A modified GOMS analysis. In: ACM SIGACCESS Conference on Assistive Technology. New York: ACM Press. pp. 55–62. doi:10.1145/1168987.1168998.
  5. ↑ Schrepp, M. (2006). On the efficiency of keyboard navigation in web sites. Universal Access in the Information Society, Vol. 5, No. 2, pp. 180-188.
  6. 1 2 Card, Stuart; Thomas P. Moran; Allen Newell (1980). The keystroke-level model for user performance time with interactive systems. Lawrence Erlbaum Associates. doi:10.1145/358886.358895. ISBN 0-13-444910-X.
  7. ↑ Rice, Andrew D.; Jonathan W. Lartigue (2014). Touch-level model (TLM): evolving KLM-GOMS for touchscreen and mobile devices. ACM. doi:10.1145/2638404.2638532. ISBN 978-1-4503-2923-1.
  8. ↑ Kieras, David (1994). GOMS modeling of user interfaces using NGOMSL. ACM. doi:10.1145/259963.260467. ISBN 0-89791-651-4.
  9. ↑ John., Bonnie E.; Alonso Vera; Michael Mattesa (2002). Automating CPM-GOMS. ACM. doi:10.1145/503376.503404. ISBN 1-58113-453-3.
  10. ↑ John, Bonnie E; Wayne D. Gray (1995). CPM-GOMS: an analysis method for tasks with parallel activities. ACM. ISBN 0-89791-755-3.
  11. ↑ Voss, David (2010). Analyse, Evaluierung und Optimierung der intraoperativen Mensch-Maschine-Interaktion. Eberhard-Karls-Universität Tübingen. doi:10.1145/223355.223738.
  12. ↑ John, Bonnie E.; David E. Kieras (1996). Using GOMS for User Interface Design and Evaluation: Which Technique?. United States of America: ACM. doi:10.1145/235833.236050. ISSN 1073-0516.
  13. ↑ Gray, Wayne D.; John,Bonnie E.; Atwood, Michael E. (1992). "The Precis of Project Ernestine or an overview of a validation of GOMS". Proceedings of the SIGCHI conference on Human factors in computing systems. doi:10.1145/142750.142821. ISBN 0897915135.
  14. 1 2 Gong, Richard; David Kieras (1994). A Validation of the GOMS Model Methodology in the Development of a Specialized, Commercial Software Application. ACM. doi:10.1145/191666.191782. ISBN 0-89791-650-6. line feed character in |title= at position 100 (help)

A previous version of this article was largely a derivative work of GOMS Analysis Techniques - Final Essay (1997) (see older version and talk page).

Further reading

This article is issued from Wikipedia - version of the Sunday, January 03, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.