http://techbase.kde.org/index.php?title=Projects/Plasma/PURP&feed=atom&action=history 2013-05-22T00:46:24Z Revision history for this page on the wiki MediaWiki 1.20.2 http://techbase.kde.org/index.php?title=Projects/Plasma/PURP&diff=22320&oldid=prev 2008-03-19T20:13:43Z

<p>New page: = Plasma User Research Profile = Short summary description of the purpose of the application, who it is for, and what those people can do with it. == Who is the application for? == * Li...</p> <p><b>New page</b></p><div>= Plasma User Research Profile =<br /> <br /> Short summary description of the purpose of the application, who it is for, and what those people can do with it.<br /> <br /> == Who is the application for? ==<br /> <br /> * List of types (groups) of users<br /> * User groups can be organized based on any type of dimension<br /> * Some groups may be broken down in to sub groups<br /> <br /> === (Who is the application ''not'' for) ===<br /> <br /> * Sometimes it is easy to identify who the application is '''not''' for<br /> * This can help keep the scope of the project under control<br /> <br /> === Sample User Profiles ===<br /> <br /> User Profile 1: For each group of users identified (or primary groups, or particularly special groups if many groups are defined), write a description of that user's characteristics based on a real user you know.<br /> <br /> == What kinds of tasks will they complete ==<br /> <br /> * List of common tasks users will complete <br /> * This does not have to be a complete functional specification, but major tasks and specialty tasks should be listed<br /> * Include functionality that is planned but not yet implemented to help keep the future in focus<br /> <br /> === (What kinds of functionality will the application ''not'' support) ===<br /> <br /> * List tasks or functionality the application will not address<br /> * Sometimes it is useful to list this unintended functionality to help keep the scope of the application<br /> * For example, a certain functionality may not be implemented because it is out of scope with the primary goals of the project, another application with a different focus does it better, or it is an extreme edge case for a user type which is not primary<br /> <br /> === Sample Use Scenarios and Cases ===<br /> <br /> Use Scenario 1: For each task identified (or major tasks, or particularly special tasks if many tasks are defined), write a description of how that user would accomplish the task ''independent'' of how they would complete it within the application.<br /> <br /> Use Case 1: If a use scenario has been implemented, include a matching use case which describes how the task use scenario can be completed in the application. There may be branching or multiple ways to complete the task, and this is a good way to document it.<br /> <br /> == Environment Conditions &amp; Requirements ==<br /> <br /> * List of environmental conditions for the user or the application to consider<br /> * For example, an Internet-capable application would require an Internet connection</div>

Aseigo