User Interface Design and Ergonomics - National Open University of ...

More documents

Recommendations

Info

There are two important reasons for the clustering principle. First, it helps users search for the command they need. If you're looking for the "Print setup" menu, it's easier to find if it's in a box or menu with the label "Printer" then if it's one of hundreds of command buttons randomly distributed on the top of the screen. Second, grouping commands together helps the user acquire a conceptual organization for facts about the program. It's useful to know, for example, that Bold, Italic, and Outline are all one kind of font modification, while Times Roman, Palatino, and Courier are another kind. (That distinction, common to most PC-based word processors, doesn't hold for many typesetting systems, where users have to acquire a different conceptual organization.) b. The Visibility Reflects Usefulness Principle: Make frequently used controls obvious, visible, and easy to access; conversely, hide or shrink controls that are used less often. This is a principle that WIMP systems implement with dialog boxes and, in many recent systems, with "toolbars" of icons for frequently used functions. The reasoning behind this principle is that users can quickly search a small set of controls, and if that set contains the most frequently used items, they'll be able to find and use those controls quickly. A more extended search, through dialog boxes, for example, is justified for controls that are used infrequently. c. The Intelligent Consistency Principle: Use similar screens for similar functions. This is similar to intelligent borrowing, but in this case you're borrowing from one part of your design and applying it to another part. The reasoning should be obvious: Once users learn where the controls are on one screen (the "Help" button, for example), they should be able to apply that knowledge to other screens within the same system. This approach lets you make a concentrated effort to design just a few attractive, workable screens, then modify those slightly for use in other parts of the application. Be careful to use consistency in a meaningful way, however. Screens shouldn't look alike if they actually do significantly different things. A critical error warning in a real-time system should produce a display that's very different from a help screen or an informational message. d. The Color As a Supplement Principle: Don't rely on color to carry information; use it sparingly to emphasize information provided through other means. Color is much easier to misuse than to use well. Different colors mean different things to different people, and that relationship varies greatly from culture to culture. Red, for example, means danger in the U.S., death in Egypt, and life in India. An additional problem is that some users can't distinguish colors: about 7 percent of all adults have some form of color vision deficiency. A good principle for most interfaces is to design them in black and white, make sure they are workable, then add minimal color to the final design. Color is certainly useful when a warning or informational message needs to stand out, but be sure to provide additional cues to users who can't perceive the color change. 106
Unless you are an experienced graphic designer, minimal color is also the best design principle for producing an attractive interface. Try to stick with grays for most of the system, with a small amount of bright color in a logo or a label field to distinguish your product. Remember that many users can -- and frequently do -- revise the color of their windows, highlighting, and other system parameters. Build a product that will work with that user input, not one that fights it. e. The Reduced Clutter Principle: Don't put "too much" on the screen. This loosely defined principle is a good checkpoint to confirm that your design reflects the other principles listed above. If only the most highly used controls are visible, and if controls are grouped into a small number of visual clusters, and if you've used minimal color, then the screen should be graphically attractive. This is also a good principle to apply for issues that we haven't dealt with specifically. Type size and font, for example: the Reduced Clutter Principle would suggest that one or two type styles are sufficient. Don't try to distinguish each menu by its own font, or work with a large range of sizes. Users typically won't notice the distinction, but they will notice the clutter. 4.0 CONCLUSION In this unit, you were introduced to different Interaction Styles and Graphic Design Principles. 5.0 SUMMARY The following are the summary of what were discussed in this unit:- Introduction to Interaction Styles which refers to all the ways the user can communicate or otherwise interact with the computer system. The advantages and disadvantages of various styles like Command language and form fillin. Graphics design principles like the Clustering Principle, The Visibility Reflects Usefulness Principle, and e.t.c. 6.0 TUTOR MARKED ASSIGNMENT a. Explain any two Interaction Styles. b. Write a short note on any of the Graphic Design Principle. 7.0 FURTHER READING AND OTHER RESOURCES Crandall, B., Klein, G., and Hoffman, R. (2006). Working minds: A practitioner's guide to cognitive task analysis. MIT Press. Hackos, JoAnn T. and Redish, Janice C. (1998). User and Task Analysis for Interface Design. Wiley. 107
Page 1:
] NATIONAL OPEN UNIVERSITY OF NIGER
Page 4 and 5:
National Open University of Nigeria
Page 6 and 7:
Summary ...........................
Page 8 and 9:
UNIT 3 - GRAPHICAL USER INTERFACE (
Page 10 and 11:
Assignments File Tutor-Marked Assig
Page 12 and 13:
2 DESIGN and DESIGNING GOOD USER IN
Page 14 and 15:
need both the study unit you are wo
Page 16 and 17:
CIT 711: USER INTERFACE DESIGN AND
Page 18 and 19:
UNIT 1 FUNDAMENTALS OF USER INTERFA
Page 20 and 21:
3.3 TYPES OF USER INTERFACES Curren
Page 22 and 23:
3.5 USER INTERFACE MODALITIES AND M
Page 24 and 25:
Table of Contents 1.0 Introduction
Page 26 and 27:
3.1.1 DESIGNING A GOOD USER INTERFA
Page 28 and 29:
widgets properly is to read and und
Page 30 and 31:
Figure 1:- Showing that alignment o
Page 32 and 33:
6.0 TUTOR MARKED ASSIGNMENT a. How
Page 34 and 35:
A graphical user interface is a typ
Page 36 and 37:
Operating System. It is easy for a
Page 38 and 39:
A list of items from which to selec
Page 40 and 41:
collaborative work. For example, sc
Page 42 and 43:
MODULE 1 UNIT 4 HUMAN COMPUTER INTE
Page 44 and 45:
3.3 DIFFERNCES WITH RELATED FIELDS
Page 46 and 47:
window blinds to automobile braking
Page 48 and 49:
Wickens, Christopher D., John D. Le
Page 50 and 51:
The International Ergonomics Associ
Page 52 and 53:
approach, the Gilbreths reduced the
Page 54 and 55:
3.6 BENEFITS OF ERGONOMICS The thre
Page 56 and 57: Another key to reducing lumbar disc
Page 58 and 59: MODULE 2 - USER INTERFACE DESIGN TE
Page 60 and 61: methods include inspection methods,
Page 62 and 63: Determine time of each operation (b
Page 64 and 65: unable to understand new informatio
Page 66 and 67: M cones, or, misleadingly, green co
Page 68 and 69: Motor skill which is a learned seri
Page 70 and 71: MODULE 2 UNIT 2 UNDERSTANDING USERS
Page 72 and 73: The users of a system must be ident
Page 74 and 75: This example brings up an important
Page 76 and 77: whether you want to have a palette
Page 78 and 79: Task analysis which includes identi
Page 80 and 81: MODULE 2 UNIT 3 USER CENTERED DESIG
Page 82 and 83: or small body text is also hard to
Page 84 and 85: Introduction to User-centered desig
Page 86 and 87: organizations themselves. Interacti
Page 88 and 89: After thorough analysis using vario
Page 90 and 91: Interaction design which is the dis
Page 92 and 93: In human-computer interaction and c
Page 94 and 95: The preferred method for ensuring u
Page 96 and 97: 3.4 ISO STANDARDS FOR USABILITY ISO
Page 98 and 99: In this unit, you have been introdu
Page 100 and 101: affect the way the command is execu
Page 102 and 103: • Guides the user via the predefi
Page 104 and 105: The term direct manipulation was in
Page 108 and 109: 108
Page 110 and 111: UNIT 1 PROTOTYPING Table of Content
Page 112 and 113: Figure 12: The iterative steps of p
Page 114 and 115: select print Figure 13: An interfac
Page 116 and 117: Ambler, S.W. & Constantine, L.L. (2
Page 118 and 119: 3.2 LOW-FIDELITY PROTOTYPES Low-fid
Page 120 and 121: Figure 14:- Example of Sketching II
Page 122 and 123: Much more important for features th
Page 124 and 125: DENIM, an extension of SILK, is a t
Page 126 and 127: • Encourage menu & forms style, r
Page 128 and 129: Another problem is that native widg
Page 130 and 131: interfaces, so that a realistic sim
Page 132 and 133: UNIT 3 INPUT AND OUTPUT MODELS Tabl
Page 134 and 135: Recall that perceptual fusion means
Page 136 and 137: 3.2 OUTPUT MODEL There are basicall
Page 138 and 139: directly-mapped pixel image will no
Page 140 and 141: Most stroke models also include som
Page 142 and 143: UNIT 4 MODEL VIEW-CONTROLLER (MVC)
Page 144 and 145: 3.3.2 AS A DESIGN PATTERN MVC enco
Page 146 and 147: The Views are XForms controls for s
Page 148 and 149: UNIT 5 LAYOUTS AND CONSTRAINTS Tabl
Page 150 and 151: 3.5 CONSTRAINTS Constraints are rel
Page 152 and 153: 152
Page 154 and 155: MODULE 4 UNIT 1 TECHNIQUES FOR EVAL
Page 156 and 157:
a. Card Sorting Card sorting is a w
Page 158 and 159:
Rapid prototyping is a method used
Page 160 and 161:
3.2.1 THE USE OF PROTOTYPES It is o
Page 162 and 163:
Dumas, J.S. and Redish, J.C. (1999)
Page 164 and 165:
the users' respect for you as a pro
Page 166 and 167:
the users will be and what kind of
Page 168 and 169:
speed whenever the average load was
Page 170 and 171:
Table 4:- Table: Average times for
Page 172 and 173:
phases: list the actions, and then
Page 174 and 175:
Nielsen and Molich used their own e
Page 176 and 177:
7.0 REFERENCES AND FURTHER READING
Page 178 and 179:
users. If you do not, you can be ba
Page 180 and 181:
If you are led to develop more and
Page 182 and 183:
It's very easy to shape the comment
Page 184 and 185:
a. Analyzing the Bottom-Line Number
Page 186 and 187:
you use. But then you need some way
Page 188 and 189:
ecruit test users with more similar
Page 190 and 191:
MODULE 4 UNIT 4 OTHER EVALUATION IS
Page 192 and 193:
3.2 CURRENT ISSUES CONCERNING EVALU
Page 194 and 195:
2.0 OBJECTIVES By the end this unit
Page 196 and 197:
It provides a real focal point for
Page 198 and 199:
3.3.4 CONDUCTING THE TEST Having co
Page 200:
The stages involved in usability te
show all

User Interface Design and Ergonomics - National Open University of ...

Create successful ePaper yourself

Delete template?

Save as template?