10. Criteria
• Time
• to learn the application
• to perform task
11. Criteria
• Time
• to learn the application
• to perform task
• that users remember how and what
12. Criteria
• Time
• to learn the application
• to perform task
• that users remember how and what
• Errors
13. Criteria
• Time
• to learn the application
• to perform task
• that users remember how and what
• Errors
• number
14. Criteria
• Time
• to learn the application
• to perform task
• that users remember how and what
• Errors
• number
• kind
15. Criteria
• Time
• to learn the application
• to perform task
• that users remember how and what
• Errors
• number
• kind
• Subjective feeling of satisfaction
16. Criteria
• Time
• to learn the application
• to perform task
• that users remember how and what
• Errors
• number
• kind
• Subjective feeling of satisfaction
Often a compromise - important to make explicit
20. Usability engineering
•‘Think-aloud protocol‘
•Video recording with annotation
•Log, remarks, etc. for analysis
•‘Discount usability engineering’
•Comparative test of user interface
24. By experts
•in HCI or domain
•very effective
•delicate relation with developers
25. By experts
•in HCI or domain
•very effective
•delicate relation with developers
•target
26. By experts
•in HCI or domain
•very effective
•delicate relation with developers
•target
•identify problems
27. By experts
•in HCI or domain
•very effective
•delicate relation with developers
•target
•identify problems
•suggest solutions
28. By experts
•in HCI or domain
•very effective
•delicate relation with developers
•target
•identify problems
•suggest solutions
•through checklist of guidelines
29. Participants
• representative
• computer experience, language, task,
motivation, education, etc.
• gender, age
• have to know they are not being evaluated
• relationship
• colleagues, friends, family, ...