KDE TechBase
  • Page
  • Discussion
  • Edit
  • History
KDE TechBase is a Wiki - You can help! Please contribute! Questions?
Please ask development related questions in the KDE Community Forum.

Projects/Usability/Project User Research Template (zh CN)

< Projects | Usability

Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenščina | српски | Українська | 简体中文 | 繁體中文

关于项目用户概要研究模板: 这个模板的目的是提供一个地方,保存应用程序的用户研究内容,以供在开发过程参考研究。最顶层的内容是每个项目成员都应该知道并理解的。以下的一些细节可能会在项目完成时进一步完善和讨论。

Contents

  • 1 项目用户概要研究
    • 1.1 什么人是这个应用程序的用户?
      • 1.1.1 (什么人不是这个应用程序的用户?)
      • 1.1.2 用户概要举例
    • 1.2 他们被用来干什么
      • 1.2.1 (什么样的功能是这个应用程序不支持的)
      • 1.2.2 使用场景和用例
    • 1.3 环境条件和要求
    • 1.4 更多信息

[edit] 项目用户概要研究

Short summary description of the purpose of the application, who it is for, and what those people can do with it.

[edit] 什么人是这个应用程序的用户?

  • 用户和用户列表
  • 用户可以按照某种规则归为一组
  • 有些组可以进一步细分为几个子类别

[edit] (什么人不是这个应用程序的用户?)

  • Sometimes it is easy to identify who the application is not for
  • This can help keep the scope of the project under control

[edit] 用户概要举例

用户概要一: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.

[edit] 他们被用来干什么

  • 列举用户常用功能
  • 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

[edit] (什么样的功能是这个应用程序不支持的)

  • 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

[edit] 使用场景和用例

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.

[edit] 环境条件和要求

  • List of environmental conditions for the user or the application to consider
  • For example, an Internet-capable application would require an Internet connection

[edit] 更多信息

Short introduction to user personas on Usability.gov

In-depth discussion about creating personas on Boxes and Arrows

Retrieved from "http://techbase.kde.org/Projects/Usability/Project_User_Research_Template_(zh_CN)"

Navigation

  • Home
  • Help
  • Recent changes

Sections

  • Getting started
  • Development
  • Schedules
  • Policies
  • Contribute
  • Projects

Toolbox

  • What links here
  • Related changes
  • Special pages
  • Printable version
  • Permanent link

Personal tools

  • 38.107.191.95
  • Talk for this IP
  • Log in / create account
  • Login with OpenID
Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V. | Legal