Skip to content

GOMS

A human–computer interaction modeling family representing skilled task performance through goals, operators, methods and selection rules.

Version
v1 · 2026-09-08 · History
Domain-specific #
4752
Origin domain
human computer interaction
Subdomain
human computer interaction

Core Idea

KLM, CMN-GOMS, NGOMSL and CPM-GOMS make different assumptions about cognition, learning and parallel activity; models best predict routine expert behavior rather than discovery or error-rich work. An analyst decomposes a user goal into alternative methods, primitive perceptual, cognitive and motor operators and rules selecting a method, then derives qualitative structure or predicted execution time. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

GOMS belongs to human computer interaction and is useful where the analyst can specify the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit. The scope is broad within that domain but bounded by the need for the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name GOMS can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to GOMS. GOMS compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of human computer interaction because they reuse the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, An analyst decomposes a user goal into alternative methods, primitive perceptual, cognitive and motor operators and rules selecting a method, then derives qualitative structure or predicted execution time., and type the carrier, state every parameter and convention in the definition, test that the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for GOMSParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.GOMSDOMAINPrime abstraction: Decomposition — is a kind ofDecompositionPRIME

Current abstraction GOMS Domain-specific

Parents (1) — more general patterns this builds on

  • GOMS is a kind of Decomposition Prime

    The proposed strict upward parent is prime:decomposition.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

GOMS sits in a crowded region of the domain-specific corpus (12th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Human–Computer Interaction & Interface Design (24 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08