Model-Based Evaluations
Get introduced to the GOMS and KLM model used in model-based evaluations.
We'll cover the following
Introduction
Another expert-based evaluation technique is the model-based evaluation. This approach uses cognitive and design models. These models help to identify project specifications along with design evaluation. In this lesson, we are going to study two models: the GOMS model and the Keystroke-level model.
The GOMS model
GOMS stands for Goals, Operations, Methods, and Selection.
-
Goals: This describes user goals, i.e. what the user wants to achieve. For example, “Close a tab in Safari,” is a goal.
-
Operations: The set of basic actions that users can perform to interact with the system and achieve a goal. For example, “press key X,” and “mouse click,” are operations.
-
Methods: These are the different ways of achieving the same goal. Method X will have a different set of subgoals from method Y. Both methods can be used to achieve the goal. For example, a tab in Safari can be closed either by selecting the “close tab” option from the menu, by clicking the “cross icon” on the tab, or by using the key shortcut “command+W”. There are three methods to achieve this goal.
-
Selection: These are the conditions and situations that predict which method will be used. Selection basically depends on three things:
- Particular users
- System state
- Goal details
For example, an expert user will prefer either the “cross icon” method or the “command+W” shortcut. In contrast, a novice user may not know about the shortcut and chooses to close the tab using the menu option or clicking the “cross icon.”
GOMS example
Here is an example of a task to move the word “cute” before the word “baby” in the following sentence.
“What a baby she is cute!”
GOMS | Description |
Top-level goal | Move the word "cute" before the word "baby". |
Subgoals |
|
Operators |
|
Methods | For the highlight text subgoal
For the edit text subgoal:
|
Selection rules |
The Keystroke-level model
The Keystroke-level model, abbreviated as KLM, is a model that predicts user performance on the basis of a deep understanding of the human motor system. It focuses on the time taken by the user to perform basic unit tasks of simple functions. For example, it can be used to evaluate individual unit tasks performed for functions like changing font size, searching and replacing. Complex functions such as making a graph or a diagram will be divided into subtasks with subgoals just like in the GOMS model and then these subtasks can be evaluated using KLM. KLM assumes that the user has decided and established how to perform a task in the mind before initiating actions. It divides the task execution into seven operators. Out of all of them, one is a mental operator, five are physical operators, and one is a system response operator. The mental operator is a slight recall of the action that the user is going to perform. These operators are:
Operators | Description |
K | Striking keys. |
B | Pressing the mouse buttons. |
P | Pointing at a specific position on screen. |
H | Switching the hand from mouse to keyboard and vice versa, i.e., homing. |
D | Using the mouse to draw lines. |
M | Getting prepared mentally for the physical action. |
R | The system response. |
Example
Consider a task to close a tab in Safari. The user will point at the “cross sign” on the tab and click it to close the tab. This task can be divided into KLM operators as follows:
Tasks | Operators |
Reach the mouse | H [Mouse] |
Position mouse on the cross tab icon | M P |
Click on the cross icon | B [LEFT] |
The operators have some explanations as well in the square brackets. For example, homing the mouse or keyboard, which mouse key is pressed, and which keyboard key is pressed in case of a K operator, etc.
Calculating time
The KLM represents the time taken by each operator as where is the specific operator. If there are multiple occurrences of an operator, for example, multiple keystrokes, then time taken by each keystroke is summed to calculate .
The total time taken by the user in the above example can be calculated as:
Have a look at this table. These are the common and widely accepted times for each operator.
Operators | Remarks | Times (s) |
K | Key press
| 0.12 0.28 1.20 |
B | Mouse button press
| 0.10 0.20 |
P | Point with mouse | 1.10 |
H | Homing | 0.40 |
D | Drawing a line or grid | Domain dependent |
M | Mental preparation | 1.35 |
R | System response | Domain dependent |
🤔 Point to ponder
Shouldn’t we use the mental operator M before every action? Clearly, humans recall before initiating an action. In the example about closing a Safari tab, why did we use M before P?