(Move notice)
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{Note|This page is outdated, please refer to [[https://hig.kde.org/ https://hig.kde.org/]]}}
== Purpose ==
== Purpose ==

Latest revision as of 18:30, 5 February 2019

This page is outdated, please refer to [https://hig.kde.org/]


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.


  • 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

This page was last edited on 5 February 2019, at 18:30. Content is available under Creative Commons License SA 4.0 unless otherwise noted.