锁定老帖子 主题:10条UI设计评估规则
精华帖 (0) :: 良好帖 (0) :: 新手帖 (0) :: 隐藏帖 (0)
|
|||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
作者 | 正文 | ||||||||||
发表时间:2008-10-20
最后修改:2008-11-12
The following are nine heuristics listed in Nielsen (1993) and one (the last one) is from Nielsen and Mack (1994).
Visibility of System Status (可视化原则
)
|
|||||||||||
返回顶楼 | |||||||||||
发表时间:2008-10-21
都是武汉的 打个招呼 支持下
|
|||||||||||
返回顶楼 | |||||||||||
发表时间:2008-10-21
最后修改:2008-11-12
554949699 写道 都是武汉的 打个招呼 支持下 谢谢! 关于以上的十条规则,我们更多的会在软件界面设计方面用到。 但是很多时候,我们可以将其作为我们前期开发设计的基本标准,并且我们应当将主要精力放在UI设计这一块。毕竟我们设计的是软件而不是在做一个自己用的小程序。在经历了很多软件比赛后,我的感受比较深刻,软件的后期包装、外观设计是更主要的。至于底层实现,使用者是不会太在意的(因为很多使用者不是专家)。 |
|||||||||||
返回顶楼 | |||||||||||
发表时间:2008-11-12
HE: Consistency and Standards(一致性与标准化的设计规范)Don’t Frustrate the User(不要迷惑用户)Users become accustomed to certain actions and sequences, and they are likely to become confused or frustrated when they encounter unexpected behavior. When one screen requires a specific series of actions, users will expect the same series of actions to be required under similar conditions. The qualities of familiarity and predictability in an interface reduce the stress involved in using an application. 系统的返回信息需要明确,需要让用户能够在看到系统的反应时不会诧异和意外。 Maintain Platform Consistency(系统设计需要符合平常的使用惯例)Products should conform to the conventions of the platform for which they are built.
Maintain Application Consistency(整个系统需要统一)Consistency within an application is also important. One kind of consistency is location consistency-that is, commands should not move around between menus, sometimes appearing on one menu and sometimes on another. Also, commands should not appear and disappear from menus-disappearing or moving menu items leave users unsure of where and when they last saw or used a particular item. Instead, menu items that aren’t available to the user at a given moment should be dimmed (or shaded) instead of being removed from the menu. Other areas where consistency is important are
系统上面的显示和使用控件需要在系统的始末都保持一致,举个简单的例子:一个button在有的时候不能点击,这个时候我们最好使它的属性变成不可使用而不是直接删除。 这方面(一致性)涉及到其它的一些控件和事件:
下面用一个UAR来作为一个具体实例进行解释: Date/Time Control Panel Applications of this HeuristicExample UAR: Aspect 1 - Button Labels Are GoodUAR IdentifierHE5-Good Feature Succinct description:"OK", "Cancel", and "Apply" button labels follow Windows standards. Evidence for the aspect:Heuristic: Consistency and standards (in particular, the "standards" part of this heuristic) Interface aspect: The buttons at the bottom of the screen are labeled "OK", "Cancel", and "Apply"-as shown in the picture below. In the online MSDN Library Visual Studio 6.0 (see Books/The Windows Interface Guidelines for Software Design/ Chapter 8 Secondary Windows/Property Sheets and Inspectors/Property Sheet Commands), it lists the following standard ways to close the property sheet:
Explanation of the aspect:All the standard ways to close the property sheet are present and work as described. Benefit of the good feature:Users will be able to use their prior knowledge of Microsoft products with this control panel. Solution:I cannot think of any drawbacks to using the standard button labels and actions at this time. Relationship to other UARs:None when this UAR was originally written.
Example UAR: Aspect 2 - Button Names Are Very SimilarAt the same time that the "OK" and "Apply" button labels conform to the standards part of the consistency and standards heuristic, those words are so similar in meaning that they may violate the "consistency" part of the same heuristic. That is, when very similar words are used to describe different actions, the user is likely to become confused. First, we'll write up this UAR and then discuss the problem of what to do when heuristics give conflicting design advice. UAR IdentifierHE6-Problem Succinct description:The difference between "OK" and "Apply" is not obvious. Evidence for the aspect:Heuristic: Consistency and standards (in particular, the "consistency" part of this heuristic) Interface aspect: The button labels "OK" and "Apply" have very similar definitions in lay English. Definition of "OK" in Webster's New Collegiate Dictionary: approve, authorize.In the context of just making changes to something, the changes are the things that are approved or authorized. Definition of "apply" in Webster's New Collegiate Dictionary: To put
into effect. Explanation of the aspect:The difference between "OK" and "Apply" is not obvious to the user. From common definitions of the words, it would seem that they do the same thing: make the changes that the user just indicated in the control panel. Since the words are different, the actions should also be different according to the consistency and standards heuristic, but the difference between the actions should be reflected in the words used to label them. According to the Design Guide passage quoted above, both buttons apply the changes the user made to the property sheet. The only difference is that the Apply button leaves the property sheet open and the OK button closes the property sheet. Unfortunately, this difference is not inherent in the meanings of the labels. Severity of the problem:The users will probably learn the difference between these buttons pretty quickly, especially if they use other Windows products. Solution:Change the labels to reflect the real difference in the actions. Perhaps use "Apply" and "Apply & Close". However, following this solution will violate the Windows Design Guide conventions and, therefore, will violate the standards part of the same heuristic. The buttons "OK" and "Cancel" were standardized long before dialog boxes that needed "Apply" were in use. Therefore, the terms have been "inherited" with a lot of users knowing what they mean. It will not be easy to change away from the "OK" label. Relationship to other UARs:UAR# HE5 – Good Feature:"OK", "Cancel," and "Apply" button labels follow Windows standards. This heuristic seems to give conflicting advice. Perhaps we'll have to do user testing-or at least conduct a survey or some interviews-to see if our users will really have problems with "Apply" and "OK". |
|||||||||||
返回顶楼 | |||||||||||
发表时间:2008-11-12
HE: User Control and Freedom(用户具有良好的控制权与较高的自由度)Let the User Be in Control(让用户具有控制权)The sense of "who's in charge" strongly affects how a user feels about an application. Users get frustrated when they don’t feel in control of the computer, and for this reason, users should initiate actions, not the computer. Also, carefully consider the wording of messages; their tone should suggest that the computer is ready and compliant, not commanding or threatening, and that the user, not the computer, is in charge. 交谈之中,听者为大。软件生产,客户为大。软件运行,用户为大。软件始终需要灌输一个思想:用户是软件运行的主导,他需要具有很好的软件控制权。 Provide an Undo Mechanism(提供撤销操作)The user should be able to reverse the steps in a process and retreat back to a previous state. Some of the ways applications implement undo are listed below:
人人都会犯错,软件使用者亦不例外。我们需要给用户提供良好的用户体验。提供Redo和Undo.这一点我非常佩服Google,人家让WEB应用也如此的人性化了。在这里略微谈下原理:利用栈结构。 Require Confirmation(在重要操作时,需要给用户提供确认操作)The user should be warned when an irreversible action is about to be initiated. An application should require an explicit confirmation before allowing an irreversible step to be set in motion. Provide an Escape Route(提供及时退出功能)Users should be able to halt processes. A typical way to provide for this is to offer a Cancel button at all times. However, when canceling a process may leave the computer in an unstable state - such as canceling an install process when only a subset of the necessary files have been transferred - the user should be warned that canceling could have negative consequences and should be advised of an alternative way to halt or reverse the process.
下面给出一个UAR: Date/Time Control Panel Applications of this HeuristicExample UAR: Aspect 1 — Cancel Button Is GoodUAR IdentifierHE7 - Good Feature Succinct description:"Cancel" button provides an "emergency exit." Evidence for the aspect:Heuristic: User control and freedom Interface aspect: There is a Cancel button at the bottom of the screen, as shown in
the picture below: In the online MSDN Library Visual Studio 6.0 (see section Books/The Windows Interface Guidelines for Software Design/ Chapter 8 Secondary Windows/Property Sheets and Inspectors/Closing a Property Sheet), it lists the following specification of the Cancel button's action:
Explanation of the aspect:If users setsthe time and then change their minds, they can cancel all the changes by clicking the Cancel button. The button is prominent and is the standard way to undo a sequence of changes made in a property box. Benefit of the good feature:Users will be able change their mind and undo a series of changes with just one button click. Solution:Although the Cancel button discards all the changes that have not been applied and closes the window, if the Apply button was clicked prior to clicking the Cancel button, no changes will be undone, though the window will be closed. See UAR #HE8 for more discussion of this control panel operation. Relationship to other UARs:UAR# HE8 Cancel doesn't give feedback when it doesn't cancel anything. Example UAR: Aspect 2 — UARs Sometimes Lead to More UARsIt is quite possible that as you write up one UAR about a good feature or problem, you will discover other usability aspects that warrant their own UARs. When this happens, just record in the first UAR that another UAR is connected; then write the second UAR. For example, while writing UAR# HE7 above, we discovered that the Cancel button doesn't always cancel something, and when it does not, it doesn't indicate that fact. We discovered this when we were thinking about trade-offs and writing in the Solution slot. Therefore, we put a note in that slot referring readers to the next UAR, UAR# HE8. Likewise, we listed UAR# HE8 in UAR# HE7's Relationship to other UARs slot. UAR IdentifierHE8 - Problem Succinct description:Cancel doesn't give feedback when it doesn't cancel anything Evidence for the aspect:Heuristic: Visibility of system status Interface aspect: There is a Cancel button at the bottom of the screen, as shown in
the picture below: In the online MSDN Library Visual Studio 6.0 (see section Books/The Windows Interface Guidelines for Software Design/ Chapter 8 Secondary Windows/Property Sheets and Inspectors/Closing a Property Sheet), it lists the following specification of the Cancel button's action:
As specified in the Design Guide, if changes are made in the property box and then the Apply button is pressed, those changes are made permanent and cannot be discarded by clicking the Cancel button. However, there is no visual indication that these changes are not available to be canceled; the Cancel button still looks active. In effect, if the Cancel button is clicked right after the Apply button is clicked, the Cancel button will behave exactly like the OK button: it will simply close the window (because the changes have already been applied). Explanation of the aspect:The Windows Design Guide does not seem to give advice about whether the standard buttons should be available (black) or unavailable (gray) at any particular time. However, this Date/Time control panel tab (labeled "Date & Time") makes the Apply button unavailable (gray) when there are no changes to be applied, and it will have no effect. The Cancel button is not grayed out when there are no changes to cancel, presumably because it will still have an effect (i.e., closing the window), but it will NOT have the effect it was labeled for (i.e., canceling something) if the changes have been applied. Severity of the problem:This can be a rather severe problem if there is no way the user can check the status of the property box once it is closed - or even if the information is on the screen but difficult to see. In this case, many users will have the clock in very small font down in the bottom right corner where they may never have occasion to look. This is severe because users may think they've canceled changes when they haven't: in reality, the changes have been applied to the system clock. This change will affect the dating of files and e-mail messages and, therefore, can have wide-reaching consequences. Solution:Make the Cancel button unavailable (gray) when there are no changes to cancel. Thus, the Apply and Cancel buttons will either be available (black) or unavailable (gray) at the same time - depending on whether or not there are changes to apply or cancel. When there are no unapplied changes, only the OK button will be available (black), and it will close the window. Note that this train of thought could continue to the point of reconsidering if the OK button should also be gray when there are no unapplied changes made. The window could always be closed with the Close button (labeled with an "x") in the top right corner of the window. A complete analysis of this issue would generate at least one more UAR to discuss the OK button, links between all these UARs, and a group UAR to discuss them all as a group (to be discussed in a later section of the course). The Windows Design Guide seems to be silent on the issue of active/inactive Property Sheet command buttons, so graying the Cancel button would not violate an explicit platform standard. However, we might want to look at several other applications with property boxes to see if there is a de facto standard, or see if people in user tests are confused by the Cancel button becoming unavailable (gray).Relationship to other UARs:UAR# HE7 - Good Feature:"Cancel" button provides an "emergency exit."
|
|||||||||||
返回顶楼 | |||||||||||
发表时间:2008-11-12
HE: Flexibility and Efficiency of Use(提供灵活和高效的使用方式)Provide Keyboard Shortcuts(需要提供快捷键)Keyboard shortcuts provide alternative ways of issuing commands, and in most cases, using a keyboard shortcut is faster than using the mouse. Using the mouse requires moving the hand from the keyboard to the mouse, moving the mouse to the target, clicking the target, and then moving the hand back to the keyboard. In contrast, when a user uses a keyboard shortcut, their hands need not leave the keyboard. Examples of keyboard shortcuts:
Allow for Customization(为专家级用户提供定制功能)Giving users control over how their computer looks and behaves allows users to tailor their environment to suit their preferences. This gives users a sense of being in charge that has an overall positive effect on their experience. It also allows users with special needs to adapt their computing environment to meet their needs. For example, a user with difficulty using their left hand can move important keyboard shortcuts to the right side of the keyboard. Some other examples are
Example UAR: Button Accelerators ExistUAR IdentifierHE9 - Good Feature Succinct description:"OK" and "Apply" buttons have keyboard shortcuts. Evidence for the aspect:Heuristic: Flexibility and efficiency of use: keyboard accelerators. Interface aspect: The buttons at the bottom of the screen labeled "OK" and "Apply"
have keyboard accelerators, as shown in the picture below. The "OK"
button is in focus, so pressing the ENTER key will activate that
command. And, notice that the "Apply" button has a keyboard shortcut:
typing ALT-A (as indicated by the underlined "A" in "Apply")
will activate that command. Explanation of the aspect:OK and Apply are the actions the users will most frequently want to take (assuming that Cancel is used only for undoing errors and changing courses of action - both of which should be relatively rare in comparison to other actions people choose and carry out.) The OK button is the default, indicated in the standard way (with a bold outline). The Apply button can be activated by typing ALT-A, also indicated in the standard way: by underlining the "A" in "Apply". Both of these interaction techniques can be found in the Design Guide. (See the following sections in Chapter 8: "Characteristics of Secondary Windows/Default Buttons" and "Characteristics of Secondary Windows/Navigation in Secondary Windows" respectively.) Benefit of the good feature:Users who are skilled at using Windows will be able to operate these two commands without their hands leaving the keyboard (which is faster than using the mouse - see "1.1.3 Basic Psychology Needed for Interface Design"). Since the commands are indicated visually in standard ways, skilled users will see these indications and know them for what they are - clues to the keyboard shortcuts. Solution/Discussion:I cannot think of any drawbacks to using the standard button labels and actions at this time. Relationship to other UARs:None when this UAR was originally written. |
|||||||||||
返回顶楼 | |||||||||||
浏览 5474 次