< KDE Visual Design Group | HIG Revision as of 16:42, 2 February 2014 (view source)Htietze (talk | contribs) (→Guidelines)← Older edit Revision as of 12:21, 30 March 2016 (view source) Ochurlaud (talk | contribs) m (5 revisions imported)Newer edit → (No difference) Revision as of 12:21, 30 March 2016 Purpose 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. 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 Retrieved from "https://community.kde.org/index.php?title=KDE_Visual_Design_Group/HIG/Scenario&oldid=59286" Categories: UsabilityStructureTask Flow Content is available under Creative Commons License SA 4.0 unless otherwise noted.