Description erro
الصح و الغلط جنب بعض
Loss of activation
تضييع الهدف من الحركة
Mode errors
كتابة كوماند بمكان ثاني
Designing for slips
General rules
Prevent slips before they occur
• Detect and correct slips when they do occur • User correction through feedback and undo
Capture error (habit)
occurs when common and rarer actions have same initial sequence
–change clothes for dinner and find oneself in bed (William James, 1
Interlock
• deals with errors by preventing the user from continuing – eg cannot delete an object if none are selected
Warn
• warn people that an unusual situation is occurring
• when overused, becomes an irritant – e.g.,
•audible bell
Teach me
• system asks user what the action was supposed to have meant • action then becomes a legal one
Prevent errors.
• try to make errors “impossible” to make
• modern widgets: only “legal commands” selected,
Help is a replacement for bad design!
False
Usually used when users are in some kind of panic, they will want (and perhaps need) immediate help.
Documentation help
Types of help
Tutorial and/or getting started manuals.
• short guides that people are likely to read when first obtaining their systems
on-line “tours”, exercises, and demos
– demonstrates very basic principles through working examples
Reference manuals.
• used mostly for detailed lookup by experts – rarely introduces concepts
– thematically arranged
• on-line HTML
– search / find
– table of contents – index
– cross-index
ypes of help
Wizards specific to task.
Danger if stack ,
Tips
• provides migration path to learning system features
• also context-specific tips on being more efficient
• must be “smart”, otherwise boring and/or tedious and/or interrupts user’s
work flow (ie: Office Assistant had good and bad elements)
which experts work together to prioritize problems.
Depriefing session
Heuristics for websites
Clarity
• Minimize unnecessary complexity & cognitive load
• Provide users with context
• Promote positive & pleasurable user experience
Focus on ease of learning.
• Designer presents an aspect of the
design & usage scenarios.
• Expert is told the assumptions about user population, context of use, task details.
• One or more experts walk through the design prototype with the scenario.
• Experts are guided by 3 questions.
Analytics example
• Many examples including Google Analytics, Visistat (shown below)
• Times of day & visitor IP addresses
Walkthroughs
For small part
Inspections can be used to evaluate only prototypes, or systems.
False,also requirements, mockups, functional
Zuletzt geändertvor einem Jahr