Projects/Usability/HIG/Scenario

From KDE TechBase
< Projects‎ | Usability‎ | HIG
Revision as of 14:52, 28 January 2014 by Htietze (talk | contribs) (Created page with "__NOTOC__ == Purpose == A ''scenarios'' describes the whys and wherefores a persona make use of the application. It illustrates how the use...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Purpose

A scenarios describes the whys and wherefores a 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.

Guidelines

  • Always create scenarios on ground 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