Reference
Glossary of usage-centered design terms.
Short definitions for the terms used across this guide. Treat them as working definitions for design discussion, not as replacements for the book's fuller treatment.
Terms
| Term | Working definition |
|---|---|
| Abstract prototype | A low-detail representation of interface structure used to test work organization before visual design is finalized. |
| Essential model | A model that describes what is meaningful in the work without prescribing a particular interface or implementation. |
| Essential use case | A compact task description organized around user intentions and system responsibilities. |
| Interaction architecture | The structural organization of workspaces, objects, commands, navigation, and feedback in an interface. |
| Role map | A model showing the user roles that participate in the system and their relationships to the work. |
| Role profile | A concise description of a role's purpose, responsibilities, tasks, frequency, skill assumptions, and failure sensitivity. |
| Task case | A meaningful unit of work that a role needs the system to support. |
| Task model | An organized view of task cases, including sequence, priority, variants, exceptions, and handoffs. |
| Usage-centered design | A design approach that focuses on user intentions, usage patterns, and abstract models as the basis for interface design. |
| User role | A recurring pattern of participation, responsibility, and intention in relation to the system. |
Common Distinctions
User role vs persona
A role defines participation in use. A persona describes an archetypal person. Both can be useful, but they answer different questions.
Essential vs concrete
Essential descriptions state purpose and responsibility. Concrete descriptions state a particular interaction mechanism.
Task model vs sitemap
A task model describes work structure. A sitemap describes page organization. The second should be informed by the first.
Prototype vs specification
A prototype tests design assumptions. A specification records agreed behavior. The same artifact should not be forced to do both jobs too early.
Sources
- Larry Constantine and Lucy Lockwood, Software for Use: A Practical Guide to the Essential Models and Methods of Usage-Centered Design, Addison-Wesley, 1999.
- Usage-centered design overview.
- Larry Constantine biography and publication list.