2. What
• Evaluation is something we actually already
do, but without formally saying.
• Example : buy something, then decide good
enough to buy again.
3. Why
• Help us to understand the user experience
with the system and, where there are
difficulties, to find ways to improving it.
– Does the interface meet the usability requirements?
– Why user unable to complete particular task very easily
– Whether the UI that has been developed for novice user is
acceptable to experianced users.
– To find out if the user like a particular design feature
4. When
• Evaluation Early in the life cycle
– Validate the users’ requirements, predict usability, assess
how well the interface meets the users’ need
– Paper-based prototype and mockups
• Evaluation Later in the life cycle
– Assess how well the interface meets the users’ need, check
out the usability and requirements.
– System is more or less ready
– Findings might be used for next version or release
5. How
• Observing the organization and how people
work
• Interviewing, talking, and asking questions
• Making predictions
6. How
• Understanding the User, Tasks, Environment,
and Domain
• Creating an evaluation strategy
• Planning who, what, when, and where
• Deciding how to collect data
• Final preparation for the evaluation
• Analysis and interpretation of user
observation evaluation data