Projects/Usability/HIG/Scenario: Difference between revisions
(Language edits) |
No edit summary |
||
| Line 2: | Line 2: | ||
== Purpose == | == Purpose == | ||
A ''scenario'' describes the whys and wherefores a [[Projects/Usability/HIG/Persona|persona]] makes use of the application. It illustrates how the | A ''scenario'' describes the whys and wherefores a [[Projects/Usability/HIG/Persona|persona]] makes use of the application. It illustrates how the users achieve their goals by means of a task-orientated example. In contrast to ''use cases'' known from requirements engineering a scenario is more descriptive. It is supplementary to a persona, providing together an efficient method applicable in a wide range of applications. | ||
== Guidelines == | == Guidelines == | ||
Revision as of 12:16, 29 January 2014
Purpose
A scenario describes the whys and wherefores a persona makes use of the application. It illustrates how the users achieve their goals by means of a task-orientated example. In contrast to use cases known from requirements engineering a scenario is more descriptive. It is supplementary to a persona, providing together an efficient method applicable in a wide range of applications.
Guidelines
- Always create scenarios based on empirical data.
- Take technical configuration, environmental condition, organizational and social aspects into consideration.
- If available, use real world images to support imagination.
- Try to include problem situations that will test the system concept, not just straightforward scenarios.