|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| __NOTOC__
| | {{ Moved To Community | KDE_Visual_Design_Group/HIG/Scenario }} |
| | |
| == Purpose ==
| |
| 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 ==
| |
| * Always create scenarios based on empirical data. Feel free to ask the KDE user experience team (kde-usability at kde.org) for
| |
| assistance with the collection of 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.
| |
| | |
| == Best Practice ==
| |
| | |
| [[Category:Usability]][[Category:Structure]][[Category:Task_Flow]]
| |
Latest revision as of 12:09, 4 August 2016
