Scenario of use: Difference between revisions
Jump to navigation
Jump to search
m (moved Scenarios of use to Scenario of use: Can't have it right the first time ;)) |
m (→Introduction) |
||
| Line 7: | Line 7: | ||
Scenarios of use describe what a person does with a system from the user's point of view. The opposite analysis is [[use case]], a description of what users can do with a system from the system's point of view. | Scenarios of use describe what a person does with a system from the user's point of view. The opposite analysis is [[use case]], a description of what users can do with a system from the system's point of view. | ||
See also [[Personas]] | See also [[Personas]], since scenarios of use are often integrated with persona files. | ||
== Links == | == Links == | ||
Revision as of 16:19, 27 April 2011
<pageby nominor="false" comments="false"/>
Introduction
Scenarios of use describe what a person does with a system from the user's point of view. The opposite analysis is use case, a description of what users can do with a system from the system's point of view.
See also Personas, since scenarios of use are often integrated with persona files.
Links
- Introductions
- Scenarios at Information & Design, (2011).
- Accessibility in User-Centered Design: Scenarios and Example Scenarios by Shawn Lawton, the author of "Just Ask".
- Create Scenarios at usability.gov
- Special topics
- Scenarios in Practice, by Paul McInerney, Michael J. Muller, IBM Watson Research Center, Summary of a CHI 03 workshop. (abstract/ TR2003-13.pdf PDF Report)
- Collections of links
- Scenarios at Dey Alexander Group