Description
A modelling notation that describes each interaction context with a standard set of abstract components before any concrete visual or interaction design.
Canonical abstract prototypes belong to Constantine and Lockwood's usage-centred design. Content models derived from essential task cases describe what each interaction context (a screen, window or panel) must contain and how it is organised, using a standard vocabulary of abstract components: containers for information, actions or operations, and active materials that combine both. A navigation map then links the contexts. Only after the abstract structure is resolved does concrete layout and visual design begin. The rigour lies in separating what must be present from how it will look, and in tracing every component to a task case. The Persona Lifecycle chapter only sketches the notation and points to Constantine's own references for the full component set.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Extinct
- Stage
- Design
- Data
- Analytical / expert
- Effort
- Days
Steps
- Derive the content of each interaction context from essential task cases.
- Express each context with canonical abstract components: containers, actions and active materials.
- Resolve the organisation and grouping of components within each context.
- Draw a navigation map linking the contexts.
- Check that every component traces to a task case and every task case is supported.
- Proceed to concrete visual and interaction design from the abstract prototypes.
Sources
- The Persona Lifecycle (Pruitt & Adlin, 2006)
Also known as
- Content model
- Abstract prototype
Categories
- Design
- Design & Product Practice