GENERAL USER INTERFACE DESIGN GUIDELINES

R.L. Magyar, Ph.D., CHFP PSY 410: Human Factors Holt Business School, Rollins College
A.

Visual Clarity Information displayed on a screen should be clear, well organized, unambiguous and easy to read. The interface should be as direct and intuitive as possible. All text, including field labels and messages should be concise and unambiguous. Related fields and items should be grouped together. Icons should be instantly "meaningful, recognizable and discriminitively different from each other."

B. Terminology Relates closely to task domain Computer-related terms are used appropriately Terms are precise and not ambiguous Abbreviations are clear Terminology must be consistent in use C. Instructions describing tasks are Clear and consistent in position, grammar, & tone Available & clear for commands or choices, correcting errors, and getting help D. Structure Explicitness -The way a system works & is structured should be clear to the user E. Navigation - Standards for navigation are based on the observation that "users learn by trial and error...they often make mistakes, which must be anticipated and dealt with." The system should allow for user exploration without causing user frustration. This includes allowing for a "graceful exit" from any function inadvertently entered. Also included under navigation would be errors resulting from inherent faults within the system. The system should not require the user to duplicate entries or other efforts: An example of this type of fault would be to ask a user to input a name and social security number twice for one entry. The system should be comprehensive in that it should contain as much information as is necessary for the user to accomplish the job, but it should not include excessive and/or irrelevant information; i.e., asking for information that is not

used or giving the user choices that do not aid in completing the task. 1. Sequence of displays Next screen is in a predictable sequence It is easy to maintain a sense of position It is easy to go back to the previous display Beginnings, middles, and ends of tasks are marked clearly 2. Exploration Is encouraged Are destructive operations protected? Are prompts meaningful? Is it easy to learn new features? 3. System Logic Does it do what is expected by users, in a logical manner? 4. Flexibility and Control The interface should be sufficiently flexible in structure, in the way information is presented and in terms of what the user can do, to suit the needs and requirements of all users, and to allow them to feel in control of the system F. Feedback : Users should be given clear, informative feedback on where they are in the system, what actions they have taken, whether these actions have been successful and what actions should be taken next. Feedback must: Be appropriate and informative (visual, tactile, or audible?) Link operations with results Be user-controlled or acceptable to the user Be adequate (not too much or too little) An effective user interface is designed so that feedback is always provided on what has been accomplished and what the computer is doing or has done. Feedback should be in the form of "simple, direct, explicit and active messages". Specific solutions to incorrect or inadvertent choices should be suggested where possible. G. Error Prevention and Control - The system should be designed to minimize the possibility of user error, with built-in facilities for detecting and handling those which do occur. Users should be able to check their inputs and to correct errors or potential error situations before the input is processed. The best design is to anticipate errors before they occur and eliminate their occurrence. 1. Error Messages Clarify the problem Indicate actions to be taken Are messages specific 2. Error Correction (Editing) Typos or complex slips --- simple or complex?

Going back to change values --- simple or complex? Undoing operations --- simple or complex? H. User Guidance and Support - Help screens and Documentation are an important part of a software system. Inadequate help can lead to confusion, errors, and reduced efficiency interaction as well as to user frustration. Informative, easy-to-use and relevant guidance and support should be provided, both on the computer (online help) or in hard copy document form, to help the user understand and use the system. 1. Online Help a. Accessing online help b. Organization c. Contents 2. Documentation 3. Training I. Consistency: The way the system looks and works should be compatible with user conventions and expectations. Standards for consistency are based on the observation that "effective user interfaces will look, act, and feel the same throughout the application," and "in a similar manner as other applications the user is likely to use." Consistency reduces uncertainty and ensures that the user will understand the nature and form of what is required at a given point in the application. Consistency may be evaluated in terms of the following: 1. Terminology 2. Data Input 3. Field Population 4. Field Values 5. Structure

J. Aesthetics - Refers to the purposeful combination of functionality with visual appeal. Interfaces should be designed to be clean, orderly, and clutter-free. The principle of Aesthetics refers to the "purposeful combination of functionality with visual appeal". "Interfaces should be designed to be clean, orderly, and clutter-free. Information should be grouped meaningfully, and controls should be spatially grouped. When this principle is ignored, the user is often presented a cluttered and visually disturbing interface which will likely lead to confusion, errors, and reduced efficiency in system interaction." An interface designed according to the principle of Aesthetics ensures that information can be rapidly and accurately retrieved. K. Means of evaluating system in terms of functions within a category: 1. 2. Lists Field Population

3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14.

Search Feature Required Entry Invalid Functions Field Values Data Input Incomplete Information Editing Duplicate Functioning Function Meaning Command Line Message prompts Terminology

References: HRISO Human Factors Design Team (1993). GUIDES - Graphical User Interface Design Standards. Johnson, G. I., Clegg, C. W., & Ravden, S. J. (1989). Towards a practical method of user interface evaluation. Applied Ergonomics, 255-260. Scneiderman, B. (1978). Iterative design, testing and evaluation. In Designing the User Interface: Strategies for Effective Human-Computer Interaction (pp. 390-418). Reading, MA: Addison-Wesley Publishing Company, Inc.