[kde-guidelines] Styleguide: Scenario

[Heiko Tietze]

Structure > Task flow
* Define a scenario where persona(s) interact with your application.

http://techbase.kde.org/Projects/Usability/HIG/Scenario

== 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.

== 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 ==

[[Category:Usability]][[Category:Structure]][[Category:Task_Flow]]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-guidelines/attachments/20140128/3d6490f9/attachment.html>