← Projects/Usability/HIG/Scenario You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. __NOTOC__ == Purpose == A ''scenario'' describes the whys and wherefores a [[Projects/Usability/HIG/Persona|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 == [[Category:Usability]][[Category:Structure]][[Category:Task_Flow]] Template used on this page: Template:Moved To Community (view source) Return to Projects/Usability/HIG/Scenario. Retrieved from "https://techbase.kde.org/Projects/Usability/HIG/Scenario"