Unformatted text preview:

1. Visibility of System StatusThe system should always keep user informed about what is going on, through appropriate feedback within reasonable time.2. Match Between System and the Real WorldThe system should speak the user’s language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.3. User Control and FreedomUsers should be free to select and sequence tasks (when appropriate), rather than having the system do this for them. Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Users should make their own decisions (with clear information) regarding the costs of exiting current work. The system should support undo and redo.4. Consistency and StandardsUsers should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.5. Help Users Recognize, Diagnose, and Recover From ErrorsError messages should be expressed in plain language(NO CODES).6. Error PreventionEven better than good error messages is a careful design which prevents a problem from occurring in the first place.7. Recognition Rather Than RecallMake objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.8. Fexibility and Minimalist DesignAccelerators-unseen by the novice user-may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. Provide alternative means of access and operation for users who differ from the “average” user (e.g., physical or cognitive ability, culture, language, etc.)9. Aesthetic and Minimalist DesignDialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.10. Help and DocumentationEven though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.11. SkillsThe system should support, extend, supplement, or enhance the user’s skills, background knowledge, and expertise ----not replace them.12. Pleasurable and Respectful Interaction with the UserThe user’s interactions with the system should enhance the quality of her or his work-life. The user should be treated with respect. The design should be aesthetically pleasing- with artistic as well as functional value.13. PrivacyThe system should help the user to protect personal or private information- belonging to the user or the his/her clients.Heuristic Evalualtion - A System Checklist1. Visibility of System StatusThe system should always keep user informed about what is going on, through appropriate feedback within reasonable time.# Review Checklist Yes No N/A Comments1.1 Does every display begin with a title or header that describes screen contents? O O O1.2 Is there a consistent icon design scheme and stylistic treatment across the system? O O O1.3 Is a single, selected icon clearly visible when surrounded by unselected icons? O O O1.4 Do menu instructions, prompts, and error messages appear in the same place(s) on each menu? O O O1.5 In multipage data entry screens, is each page labeled to show its relation to others? O O O1.6 If overtype and insert mode are both available, is there a visible indication of which one the user is in?O O O1.7 If pop-up windows are used to display error messages, do they allow the user to see the field in error?O O O1.8 Is there some form of system feedback for every operator action? O O O1.9 After the user completes an action (or group of actions), does the feedback indicate that the nextgroup of actions can be started?O O O1.10 Is there visual feedback in menus or dialog boxes about which choices are selectable? O O O1.11 Is there visual feedback in menus or dialog boxes about which choice the cursor is on now? O O O1.12 If multiple options can be selected in a menu or dialog box, is there visual feedback about whichoptions are already selected?O O O1.13 Is there visual feedback when objects are selected or moved? O O O1.14 Is the current status of an icon clearly indicated? O O OPage 1 © Usability Analysis & Design, Xerox Corporation, 1995# Review Checklist Yes No N/A Comments1.15 Is there feedback when function keys are pressed? O O O1.16 If there are observable delays (greater than fifteen seconds) in the system’s response time, is theuser kept informed of the system's progress?O O O1.17 Are response times appropriate to the task? O O O1.18 Typing, cursor motion, mouse selection: 50-1 50 milliseconds O O O1.19 Simple, frequent tasks: less than 1 second O O O1.20 Common tasks: 2-4 seconds O O O1.21 Complex tasks: 8-12 seconds O O O1.22 Are response times appropriate to the user's cognitive processing? O O O1.23 Continuity of thinking is required and information must be remembered throughout several responses: less than two seconds.O O O1.24 High levels of concentration aren't necessary and remembering information is not required: two to fifteen seconds.O O O1.25 Is the menu-naming terminology consistent with the user's task domain? O O O1.26 Does the system provide visibility: that is, by looking, can the user tell the state of the system andthe alternatives for action?O O O1.27 Do GUI menus make obvious which item has been selected? O O O1.28 Do GUI menus make obvious whether deselection is possible? O O O1.29 If users must navigate between multiple screens, does the system use context labels, menu maps,and place markers as navigational aids?O O OPage 2 © Usability Analysis & Design, Xerox Corporation, 19952. Match Between System and the Real WorldThe system should speak the user’s language, with words, phrases and concepts familiar


View Full Document
Download Visibility of System Status
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Visibility of System Status and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Visibility of System Status 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?