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

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Created page with "__NOTOC__ == Purpose == A ''scenarios'' describes the whys and wherefores a persona make use of the application. It illustrates how the use...")
 
(Language edits)
Line 2: Line 2:
  
 
== Purpose ==
 
== Purpose ==
A ''scenarios'' describes the whys and wherefores a [[Projects/Usability/HIG/Persona|persona]] make use of the application. It illustrates how the user achieves the 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 persona, providing together an efficient method applicable it in a wide range of applications.
+
A ''scenario'' describes the whys and wherefores a [[Projects/Usability/HIG/Persona|persona]] makes use of the application. It illustrates how the user achieves 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 ==
* Always create scenarios on ground of empirical data.
+
* Always create scenarios based on empirical data.
 
* Take technical configuration, environmental condition, organizational and social aspects into consideration.
 
* Take technical configuration, environmental condition, organizational and social aspects into consideration.
 
* If available, use real world images to support imagination.
 
* If available, use real world images to support imagination.

Revision as of 19:41, 28 January 2014


Purpose

A scenario describes the whys and wherefores a persona makes use of the application. It illustrates how the user achieves 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.

Best Practice


Content is available under Creative Commons License SA 4.0 unless otherwise noted.