User:Seele/Sample Project User Research Profile: Difference between revisions
No edit summary |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This is a | This is a work in progress. Feel free to fill in the blanks. | ||
= | This is a sample Project User Profile based on the [[User:Seele/Project_User_Research_Template|Project User Profile Template]] | ||
= Kivio User Profile = | |||
Kivio is an easy to use diagramming and flowcharting application with tight integration to the other KOffice applications. It enables you to create network diagrams, organisation charts, flowcharts and more. | Kivio is an easy to use diagramming and flowcharting application with tight integration to the other KOffice applications. It enables you to create network diagrams, organisation charts, flowcharts and more. | ||
== Who is | == Who is Kivio for? == | ||
* List of types (groups) of users | * List of types (groups) of users | ||
| Line 11: | Line 13: | ||
* Some groups may be broken down in to sub groups | * Some groups may be broken down in to sub groups | ||
=== (Who is | === (Who is Kivio not for) === | ||
* Sometimes it is easy to identify who the application is '''not''' for | * Sometimes it is easy to identify who the application is '''not''' for | ||
| Line 34: | Line 36: | ||
=== Sample Use Scenarios and Cases === | === Sample Use Scenarios and Cases === | ||
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 | 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. | ||
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. | 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. | ||
| Line 46: | Line 48: | ||
http://www.koffice.org/kivio/ | http://www.koffice.org/kivio/ | ||
http://wiki.openusability.org/kivio/index.php/Personas | http://wiki.openusability.org/kivio/index.php/Personas | ||
http://wiki.openusability.org/kivio/index.php/Use_Cases | http://wiki.openusability.org/kivio/index.php/Use_Cases | ||
http://wiki.openusability.org/kivio/index.php/Survey_Results | http://wiki.openusability.org/kivio/index.php/Survey_Results | ||
http://wiki.openusability.org/kivio/index.php/Feature_Priorities | http://wiki.openusability.org/kivio/index.php/Feature_Priorities | ||
Latest revision as of 01:58, 19 March 2008
This is a work in progress. Feel free to fill in the blanks.
This is a sample Project User Profile based on the Project User Profile Template
Kivio User Profile
Kivio is an easy to use diagramming and flowcharting application with tight integration to the other KOffice applications. It enables you to create network diagrams, organisation charts, flowcharts and more.
Who is Kivio for?
- List of types (groups) of users
- User groups can be organized based on any type of dimension
- Some groups may be broken down in to sub groups
(Who is Kivio not for)
- Sometimes it is easy to identify who the application is not for
- This can help keep the scope of the project under control
Sample User Profiles
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.
What kinds of tasks will they complete
- List of common tasks users will complete
- This does not have to be a complete functional specification, but major tasks and specialty tasks should be listed
- Include functionality that is planned but not yet implemented to help keep the future in focus
(What kinds of functionality will the application not support)
- List tasks or functionality the application will not address
- Sometimes it is useful to list this unintended functionality to help keep the scope of the application
- 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
Sample Use Scenarios and Cases
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.
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.
Environment Conditions & Requirements
- List of environmental conditions for the user or the application to consider
- For example, an Internet-capable application would require an Internet connection
More Information
http://wiki.openusability.org/kivio/index.php/Personas
http://wiki.openusability.org/kivio/index.php/Use_Cases
http://wiki.openusability.org/kivio/index.php/Survey_Results
http://wiki.openusability.org/kivio/index.php/Feature_Priorities