Conceptual Model Design (Objects and Operations)

Description

Turn user and task research into an explicit, interface-free model of the objects, attributes, operations and relationships an application exposes, with vocabulary and task mappings, tested before UI design.

A conceptual model describes an application in task terms: its purpose, every concept users meet (objects, attributes with value types, operations) and their relationships (specialisation, containment, whole and part, source and result), plus a mapping of domain tasks onto those concepts as task scenarios. It is distinct from users' mental models, metaphors, the UI and the implementation. The aims are simplicity, the fewest concepts that deliver the function, and task focus, concepts that map directly onto the domain. Draft concepts come from research transcripts (nouns suggest objects, verbs operations), then modelling rules are applied: every operation belongs to an object, implementation concepts are excluded, near-identical objects share a type attribute. The model, with a vocabulary and an issues log, acts as a contract: the UI may expose only what the model contains. It takes a team one week to a month. Object-oriented UX (OOUX) is a current revival under a new name.

Attributes

Loss type
Renamed
Effort
Weeks

Steps

  1. Gather user profiles and task analysis (use cases, task hierarchy, task sequences) from observing and interviewing people at work.
  2. Write the application's purpose and high-level functionality.
  3. Draft objects, operations and attributes from transcripts (nouns as objects, verbs as operations, adjectives as attribute values) and correct mis-voiced concepts.
  4. Build the objects/operations analysis, applying the rules: every operation belongs to an object; exclude implementation concepts; admit new concepts sparingly; settle containment and inheritance.
  5. Compile the vocabulary list with agreed user-visible names and definitions.
  6. Write task scenarios using only model terms and redesign if common tasks need complex plans.
  7. Log resolved and open conceptual issues; one person drives drafts, the whole team reviews, and any change is a team decision.
  8. Test the model early with users or domain experts through concept and terminology sessions or low-fidelity prototypes, and keep it current through releases.

Sources

  • Conceptual Models (Johnson & Henderson, 2011)
  • Just Enough Research (Hall, 2013)
  • Designing Interfaces (Tidwell, 2010)

Also known as

  • Conceptual design
  • Objects/operations analysis
  • Object/action analysis
  • Conceptual model document
  • Task-to-tool mapping

Categories

  • Design
  • Design & Product Practice