Unit5 - Balancing - Function Final 1
Unit5 - Balancing - Function Final 1
UNIT 5
INTRODUCTION
⯈ User experiences play a critical role in influencing software
acceptance
⯈ Conversational messages have their limits
⯈ Design needs to be comprehensible, predictable, and
controllable
⯈ Information layout is important
⯈ Multi window coordination
⯈ Large, fast, high-resolution color displays have potential
⯈ Recognition of the creative challenge of balancing function and
fashion may lead to designers even working even harder.
2
INTRODUCTION
⮚ “This chapter deals with design matters that are
functional issues with varying styles/solutions to suite a
variety of users.”
⮚ Error messages
⮚ Display design
⮚ Web page design
⮚ Window design
⮚ Colour 3
ERROR MESSAGES
⮚ Overview
⮚User experience with computer-system prompts,
explanations, error diagnostics, and warnings is crucial
in influencing acceptance of SW systems
⮚ Why do errors occur?
⮚ Lack of knowledge, incorrect understanding, inadequate slips
⮚ What is a solution?
⮚Make error messages as user-friendly as possible; this is especially important
for novice users as they commonly have a lack of knowledge, confidence, and
are sometimes easily frustrated or discouraged 4
ERROR MESSAGES
⮚ Product
⮚ Be as specific and precise as possible
⮚ Be constructive: Indicate what the user needs to do
⮚ Use a positive tone: Avoid condemnation
⮚ Choose user centred phrasing
⮚ Consider multiple levels of messages
⮚ Maintain consistent grammatical forms, terminology, and
abbreviations
⮚ Maintain consistent visual format and placement
⮚ Process
⮚ Increase attention to message design
⮚ Establish quality control
⮚ Develop guidelines
⮚ Carry out usability tests 6
⮚ Record the frequency of occurrence for each message
ERROR MESSAGES
⮚ Rules to follow:
1. Specificity
⮚ Avoid being too general (e.g., “Syntax Error”)
⮚ This makes it difficult to understand what went wrong and how it can be
fixed
Poor Better
Resource Conflict Bus: 00 Device: 03 Remove your compact flash card and
Function: 01 restart
Network connection refused. Your password was not recognized.
8 Please date
Drop-off retype.
must come after pickup
ERROR MESSAGES
⮚ Good example
⮚ We’re sorry, but we are unable to complete your
call as dialed
⮚ Please hang up, check your number, or consult the operator
for assistance
⮚ Bad example
⮚ Illegal telephone number
⮚ Call aborted
⮚ Error number 583-2R6.9
Consult your user manual for further information 9
DISPLAY DESIGN
Overview
⮚ Deals with layout of information on the display
⮚ Goal: Avoid clutter, reduce search time, increase
subjective satisfaction
⮚ Task performance goes up!
⮚For most interactive systems the display is key component of
successful design
⮚General rule: Always start with task analysis without
consideration of display size
⮚ Consider:
⮚ Provide all necessary data in a proper sequence to carry out the
task
⮚ Meaningful grouping of items (with labels suitable to users’
knowledge)
⮚ Use consistent sequences of groups and orderly 22
formats
DISPLAY DESIGN
Overview:
⯈ Effective display designs must provide all the necessary data in the
proper sequence to carry out the task
⯈ Mullet and Sano proposed six categories of principles that reveal the
complexity of designer’s task.
23
DISPLAY DESIGN
⯈ Field layout
⯈ Blank spaces and separate lines can distinguish fields.
26
DISPLAY DESIGN
⯈ Field layout
⯈ Names in chronological order, alignment of dates, familiar date
separators.
27
DISPLAY DESIGN
⯈ Field layout
⯈ Labels are helpful for all but frequent users.
28
DISPLAY DESIGN
⯈ Field layout
⯈ Distinguish labels from data with case, boldfacing, etc.
29
DISPLAY DESIGN
⯈ Field layout
⯈ Ifboxes are available they can be used to make a more appealing
display, but they consume screen space.
30
DISPLAY DESIGN
Empirical results
⯈ Structured form superior to narrative form
⯈ Improving data labels, clustering related information, using
appropriate indentation and underlining, aligning numeric values,
and eliminating extraneous characters improves performance
⯈ Performance times improve with fewer, denser displays for expert
users
⯈ Screen contents should contain only task-relevant information
⯈ Consistent location, structure, and terminology across displays
important
⯈ Sequences of displays should be similar throughout the system for
similar tasks 32
WEB PAGE DESIGN
⯈ User performance
⯈ Visual layout has a strong impact on (human) performance and is a critical
factor in web page design.
⯈ Some specific patterns of performance with web pages reflect differences
between web page and traditional GUI design.
⯈ User performance test based on layout and language
⯈ Layout factors: Quantity of links, alignment, grouping indications, and density
⯈ Languages: Hebrew (right-to-left) and English (left-to-right)
⯈ Measurement: Search times and eye movement
⯈ Conclusion:
⯈ Performance patterns were similar between languages
⯈ Poor performance in pages with many links and variable densities
⯈ But improved with the presence of uniform density
Also...
⮚ Guidelines documents are numerous
46
BALANCING FUNCTION AND FASHION
⮚ Error messages
⮚ Display design
⮚ Web page design
⮚ Color
47
COLOR
49
COLOR
⯈ Color Guidelines
⯈ Use color conservatively
- too much color can confuse and mislead users.
⯈ Limit the Number of Colors
- Too many colors may confuse novice users.
⮚ Recognize the power of color as a coding technique
- Ex Red means stop, overdue tasks. Green means go, completed
tasks.
⯈ Ensure that color coding supports the tasks
- Ex. Wrong data is highlighted for search task
50
COLOR
⯈ Color Guidelines
⯈ Have color coding appear with minimal user effort
- Color coding should in general be automatic when users perform a task
⯈ Place color coding under user control
– Users should be able to turn off or correct color coding
⯈ Design for monochrome first
- Layout data in a logical manner first, before colouring (universal usability,
black\white monitors, colour blind users)
⯈ Consider the needs of color-deficient users
- Readability, universal usability issue
⯈ Use color to help in Formatting
- Useful for densely packed
51
displays
COLOR
⯈ Color Guidelines
⯈ Be consistent in color coding
- don't use different colors for messages i.e some red and some
yellow
⯈ Be alert to common expectations about color codes
- Ex. Red – danger, stop, etc.
⯈ Be alert to problems with color pairings
- Ex. Red and Blue
⯈ User color changes to indicate status changes
- To gain attention of user
⯈ Use color in graphic displays for greater information density
- Example Graphs with multiple plots
52
User Documentation
Purpose: Information visualization aims to present data in ways that are both
visually engaging and easy to understand. This can help users make
decisions based on the data presented.
Process: It involves the transformation of abstract data into visual
representations like graphs, charts, and maps. This process requires an
understanding of the data, the context in which it will be used, and the target
audience.
Principles: Effective information visualization adheres to principles that
enhance the user’s ability to perceive patterns and trends. These include
clarity, consistency, and the use of visual hierarchies to direct attention.
Interactivity: Modern information visualization often includes interactive
elements that allow users to manipulate the visualization and explore the
data in different ways.
ANY QUESTIONS???
7
0