2ReferencesRitter, D.J. LabVIEW GUI Essential Techniques. McGraw Hill, 2002.- Quotations from Page 10/11, Page 22 Figure 2-5, and Appendix BMullet, K. & Sano, D. Designing Visual Interfaces – Communication Oriented Techniques. Prentice Hall, 1995.LabVIEW Style Guide
3What goes into a GUI  The look (10%) Aesthetic quality of organization and layoutColor choicesFont choicesGraphic elementsOverall visual impressionConsistency
4What goes into a GUI  The feel (30%) GUI object choices – Does behavior match functionalityGUI object location, proximity – Affect on task flowAccess to critical and frequently used itemsNavigation and freedom of movementAppropriate feedback for each user actionInterface text: button, menu, and dialog labels and messages
5What goes into a GUI  Conceptual elements (60%) System metaphors Ease of useThe power of each GUI actionDepth of GUIFlexibility and capacity for growth and change
6The Software Development Process Process expertsUsersProgrammers
7Successful Software: Avoiding Unpleasantly Surprised Users Early GUIPrototypesUser interactionWatch users interacting with the programGood understanding of the usage modelUser buy-in
17GUI Design Checklist  The GUI reflects the user’s mental model rather than the implementation modelProgram features and functions support only required user goals.No superfluous features have been added simply because they are easy to implement or as a result of the personal biases of the programmers
18GUI Design Checklist  The GUI design reflects the expected characteristics and abilities of the user populationVisual, physical, and cognitive abilitiesCultural and technical backgroundDomain experienceEducation levelEtc..
19GUI Design Checklist  The GUI design reflects any unusual characteristics of the user’s environmentDangerous or hazardous work areasExcessive noiseBright or dim lightingEtc..
20GUI Design Checklist  The design is optimized for human perception and information processing abilitiesShort term memory considerationsRecognition over recall
21GUI Design Checklist  All user classes are adequately represented and the potentially diverse needs of user classes are balanced appropriatelyAll GUI items are prioritized. Critical and frequently accessed items are prominent and more easily accessed than less important items
22GUI Design Checklist  All unnecessary GUI controls and indicators have been eliminatedThe GUI heirarchy geometry is optimized to reduce panel clutter and to minimize the total number of clicks required to access each function
23GUI Design Checklist  Panel layouts and GUI object placement logically reflect user tasks sequencesThe user is never required to jump between panels or applications to complete a single taskWhere possible, all necessary controls for each task are accessible from a single panel
24GUI Design Checklist  The user is not required to manually copy information displayed on one panel into a control on another panel.The program automatically transfers shared information between panels and eliminates unnecessary busywork for users
25GUI Design Checklist  Tedious, mundane, and predictable tasks are automated to improve user efficiency, but not at the expense of adequate user controlQualified users are permitted to modify or bypass automation as necessary
26GUI Design Checklist  Tool tips, control descriptions, and keyboard shortcuts have been included for power usersUser actions and task sequences lead naturally from one to the next
27GUI Design Checklist  The function of all GUI items is visually apparent and all objects including custom controls behave as expected.GUI buttons look and respond like real buttons from the physical world and don’t produce unexpected outcomes
28GUI Design Checklist  GUI metaphors, visual or otherwise, are natural and consistent with their real-world counterpartsThe GUI adheres as necessary to applicable standards documents and company wide style guides.
29GUI Design Checklist  Direct user feedback has been collected and all design shortcomings have been (or will be) addressed in subsequent iterative cycles.Documentation and help files have been created with the same level of enthusiasm and attention to detail as the software.
30GUI Design Checklist  Panels appear immediately uncluttered and organized.The style and mood of the GUI design are appropriate for the application and its expected usersThe design style is consistent from one panel to the next, and all panel look as though they belong to the same application.
31GUI Design Checklist  A limited number of unique design elements – control and indicator types, colors, fonts, proportions, and so forth – are used consistently and thematically thereby creating a sense of application-wide unityLimited color palettes have been selected and applied consistently to enhance both aesthetics and mental model development.Bright colors are used sparingly to attract the user’s attention.
32GUI Design Checklist  The layout of each panel creates a visual hierarchy, drawing the users’ eyes to the most important items first.GUI items are arranged and ordered to reflect natural visual scanning patterns (left to right, top to bottom in Western cultures). Task sequences are mapped directly to the natural scanning patterns to improve user productivity.
33GUI Design Checklist  Positive and negative space have been used effectively to make panel design appear balanced and uncluttered.GUI text, control labels, and menu text is clear, descriptive and concise.Controls have been grouped to permit the elimination of redundant label text.Error messages are brief, informative, and designed to help users locate and overcome difficulties.Unnecessary technical jargon has been eliminated from panels and dialog boxes.
34GUI Design Checklist  The selected font style, size, and color combinations provide adequate readability for users with common visual deficiencies.Where panel resizing is permitted, panels have been designed to resize gracefully.Bitmapped graphics have been avoided on resizing panels and the number of decoration elements have been kept to a minimum.
35GUI Design Checklist  GUI panels targeted for cross-platform deployment have been verified visually on all target platforms.Panels have been designed to provide a pleasing visual presentation, but form always follows function.