How to Write a Usability Aspect Report (UAR)
- UAR Identifier — <Problem or Good Feature>
- Succinct description of the usability aspect
- Evidence for the aspect
- Explanation of the aspect
- Severity of the problem or benefit of the good feature
- Possible solution and potential trade-offs (if the aspect is a problem)
- Relationship to other usability aspects (if any)
=========================================
Heuristic Evaluation
一个更好的帖子请猛击这里。
启发性评估是在开发早期阶段的一种用来分析界面设计的可用性的技术。
启发性评估的基本流程是：提出一个用户界面设计方案，然后让几个人检测这个设计是否违反了启发法的任何一条。
设计的启发性评估可以在产品开发的任意阶段进行。不过，可用性的困难被发现的越早，修正它们的代价就越小。所以在雏形阶段的时候使用启发性评估很可能是它最有价值的时候。
代表性地，一些评估者将会做一份启发性评估的综述，因为研究发现不同的人会发现不同的问题。对于一个简单的系统来说（比如ATM，只有6种功能可供人们使用），可能四五个评估者就足够发现绝大部分的可用性问题。对于更复杂的系统，则需要更多的评估者。然而，由于这种评估技术简单易学易用，所以找到能够展示这些功能的开发团队成员并不困难。并且，就算只有一两个人来做启发性评估，发现的问题如果被修正，也能够增加你正在设计的系统的可用性。
当你理解了启发法的时候，你会发现当你做设计的时候，你会不自觉的使用启发法。因此，这些启发法能够启迪一些用户设计的细节，同时，当一个设计已经被构想出后，启发法也能作为一种评估技术。
Visibility of System Status
Match Between System and the Real World
User Control and Freedom
Consistency and Standards
Error Prevention
Recognition Rather Than Recall
Flexibility and Efficiency of Use
Aesthetics and Minimalist Design
Help Users Recognize, Diagnose, and Recover from Errors
Help and Documentation
Visibility of System Status系统数据的可见性
即：电脑应该让用户知道正在进行着什么，电脑接收了输入的什么，现在正在走哪步进程，这些进程的结果是什么。
电脑应该通过显示或者声音向用户提供信息，不然用户将不会有必须的信息来了解发生了什么。
Match Between System and the Real World系统与现实相一致
用户设计应该使用用户熟悉的概念、语言和现实惯例。也就是说，开发者需要从用户的角度明白系统正要完成什么任务。
这也意味着当系统将被全球运行的时候，文化相关的问题也要被考虑在内。
界面中熟悉的概念、语言和实际惯例能够通过用户的长期记忆来进行修正，因为用户的使用地域不同是跟计算机无关的。
User Control and Freedom 用户的控制权和*度
Brief explanation of the heuristic. Allow the user to have control of the interaction. Users should be able to undo their actions easily, exit from any interaction quickly at any time, and not be forced into a series of actions controlled by the computer.
Relationship to the information-processing model of a user. Users will make errors, and, therefore, they will need easy ways to recover from them.
Consistency and Standards一致性和标准化
Brief explanation of the heuristic. Information that is the same should appear to be the same (same words, icons, and positions on the screen). Information that is different should be expressed differently. This consistency should be maintained within a single application and within a platform. Developers therefore need to know platform conventions.
Relationship to the information-processing model of a user. As with the Match Between System and the Real World heuristic, this heuristic makes use of a user’s prior knowledge and experience with other parts of the same application as well as with other applications on the same platform.
Error Prevention阻止错误
Brief explanation of the heuristic. As much as possible, prevent errors from happening in the first place. For instance, if there are a limited number of legal actions at some point in the application, then help users select from among these legal actions—rather than allowing them to perform any action and telling them after the fact when they've made an error. This could be considered a subset of the first heuristic, visibility of system status (what input the computer system is ready to accept), but it is so important and so often violated that it warrants its own heuristic.
Relationship to the information-processing model of a user. Errors can come about because users make mistakes in perception, lack knowledge about what to do next, recall the gist of a command rather than the exact details, or slip when they type or point. Some of these mistakes can be prevented by showing only those actions that are acceptable at that particular point in an interaction (e.g., graying out inappropriate buttons) or caught as soon as the user performs them (e.g., not accepting an incorrect abbreviation of a US state in an address form).
Recognition Rather Than Recall让用户认出而不是回忆
Brief explanation of the heuristic. Show all objects and actions available to the user. Do not require them to remember information from one screen of the application to another.
Relationship to the information-processing model of a user. This heuristic is a direct application of theories of human memory. It is much easier for someone to recognize that they know what to do if there are cues in the environment coming into working memory through perception as well as knowledge in long-term memory of what to do.
Flexibility and Efficiency of Use使用的灵活性和高效性
Brief explanation of the heuristic. The design should have accelerators (keyboard shortcuts) to allow skilled users to speed up their interaction (as opposed to always using menus or icons with the mouse). Skilled users should also be able to tailor their interface to speed up frequent actions.
Relationship to the information-processing model of a user. The value of accelerators comes primarily from the motor processes of the user. Typing single keys is typically faster than continually switching the hand between the keyboard and the mouse and pointing to things on the screen. Furthermore, skilled users will develop plans of action, which they will want to execute frequently, so tailoring can capture these plans in the interface itself.
Aesthetics and Minimalist Design美学和抽象的设计 清除无关的屏幕上的杂物
Relationship to the information-processing model of a user. This heuristic relates to the visual search aspect of perception and also to memory. The more clutter, the more information the eyes must search through to find the desired information. In addition, the more information coming in through perception as the visual search proceeds, the more this information interferes with the retrieval from long-term memory of the information that is actually relevant to the task at hand.
Help Users Recognize, Diagnose, and Recover from Errors帮助用户认出、确认和从错误中恢复
Brief explanation of the heuristic. Error messages should be written in plain language, tell the user what the problem is, and give constructive advice about how to recover from the error. Again, this could be considered a subset of the first heuristic, visibility of system status, but it is so important and so often violated that it warrants its own heuristic.
Relationship to the information-processing model of a user. This is simply an admonition to give the user sufficient information to understand the situation.
Help and Documentation帮助文档
Brief explanation of the heuristic. If the system is not an extremely simple, walk-up-and-use application, it is going to need help and documentation. This should be always available, easily searchable, and give concrete advice applicable to users’ tasks.
Relationship to the information-processing model of a user. This is again an admonition to give the user sufficient information to understand the application. The search feature should allow information to be found by asking for the gist of the meaning, rather than only the exactly right keyword, because people will remember only the gist, not the exact words (if they ever knew them).
=============================================
TA=Think-Aloud
=============================================
附件是两个HE的UAR 一个good feature 一个problem 还有一个TA的UAR 是个problem