Difference between revisions of "Projects/Usability/HIG/Scenario"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Guidelines)
(HIG moved to community)
 
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

This page is now on the community wiki.


This page was last modified on 4 August 2016, at 12:09. Content is available under Creative Commons License SA 4.0 unless otherwise noted.