1. Utah School of Computing HCI Validation Richard F. Riesenfeld University of Utah Fall 2004

2. Utah School of Computing slide 2 Student Name Server Fall 2003 Major Considerations - 1 Stage of design -Conceptual, preliminary, detail Novelty of project -Do we know what we are doing? Number of expected users -How important is this? -How amenable to change will it be?

3. Utah School of Computing slide 3 Student Name Server Fall 2003 Major Considerations - 2 Criticality of the interface -Are lives at stake if there are problems? Cost of product -Allocation for testing Time available for testing Experience of designers and evaluators

4. Utah School of Computing slide 4 Student Name Server Fall 2003 Expert Review methods - 1 Heuristic evaluation -Experts critique it wrt established criteria Guidelines review -Does it meet “spec” -Can be an overwhelming list -Bureaucratic approach

5. Utah School of Computing slide 5 Student Name Server Fall 2003 Expert Review methods - 2 Consistency inspection -Experts check of style, function, form, etc. Cognitive walkthrough -Experts perform role of users -Try to assess its success from experience

6. Utah School of Computing slide 6 Student Name Server Fall 2003 Expert Review methods - 3 Formal usability inspection -Moot court -Countervailing opinions -Can be unwieldy

7. Utah School of Computing slide 7 Student Name Server Fall 2003 Comparative Evaluations - 1 Different experts see different issues -Can get caught with conflicting advice* -Limit the number of experts Get a “bird’s-eye” view in the beginning -Throw images on a wall, etc. * “ * “ For every PhD, there is an equal and opposite PhD”

8. Utah School of Computing slide 8 Student Name Server Fall 2003 Comparative Evaluations - 2 Formal (statistical) methods -Form a hypothesis -Determine dependent variables -Identify independent variables * “

9. Utah School of Computing slide 9 Student Name Server Fall 2003 Usability Labs, etc Hard to employ because of time and money constraints in product development -Development cycle schedule -Budgets -Corporate/Cultural Attitude

10. Utah School of Computing slide 10 Student Name Server Fall 2003 Controlled Experients Statistical testing -Establish level of statistical significance -At the 95% confidence level we know… Usability testing -Find flaws in the interface through more informal (inconclusive) methods -Empirical methods

11. Utah School of Computing slide 11 Student Name Server Fall 2003 Human Subjects -1 Careful, “This isn’t Kansas anymore!” Many new dimensions need attention Human respect and dignity -Voice generated check outs violated privacy  Military has NO privacy  Other cultures treat matters differently

12. Utah School of Computing slide 12 Student Name Server Fall 2003 Human Subjects -2 Real LEGAL issues, so get it right! -Informed consent -Understand your liability -Get it in writing, copy to each party Government, or institutional rules -We are not accustomed to this -Need cognizant approvals  IRBs, etc.  Research proposals, etc

13. Utah School of Computing slide 13 Student Name Server Fall 2003 Observations methods Have subjects “think aloud” -Will subjects be honest, etc. Use video recording Field tests -Study the successes/failures of the interface -Getting access -Reliance on memories  “How is it going?” (We tend to react to most recent)

14. Utah School of Computing slide 14 Student Name Server Fall 2003 Destructive Testing Hey, can you break this? Good for security Good for games Durability testing appropriate for some environments -ATM in high crime area -Military -Students, they can’t resist a challenge

15. Utah School of Computing slide 15 Student Name Server Fall 2003 Competitive Testing -1 Consumers Union, Road & Track, style -Take several into lab and have a “shoot out” Expensive Takes skill (like a movie review) -Depends on the criteria -Depends on good and representative judgment

16. Utah School of Computing slide 16 Student Name Server Fall 2003 Competitive Testing -2 Major Limitations -Limited coverage of features -Depends on initial user experiences

17. Utah School of Computing slide 17 Student Name Server Fall 2003 Surveys Tricky business, can lead to nearly any conclusion -Population selection -Question choices -Size -Leading questions, other bias Negative bias – users with complaints

18. Utah School of Computing slide 18 Student Name Server Fall 2003 Online Surveys More issues…

19. Utah School of Computing slide 19 Student Name Server Fall 2003 Conclusions HCI is a new game Not exact science Old methods not entirely applicable Need newer, faster, light weight, flexible, informal, subjective, intelligent approaches

20. Utah School of Computing slide 20 Student Name Server Fall 2003 Recommendations Use good judgment Trust good judgment -Yours -Others, whom you trust Be open to criticism and suggestion

21. Utah School of Computing slide 21 Student Name Server Fall 2003 Interpretation What is being said? What is the real issue? What is the real fix? RSI is a problem -Pain -Keyboard or mouse? -Need different devices, or speech, or simply a better mouse and keyboard?

22. Utah School of Computing slide 22 Student Name Server Fall 2003 acm.org/~perlman/question.cgi Please rate the usability of the system. Try to respond to all the items. For items that are not applicable, use: NA Make sure these fields are filled in: System: Email to: Add a comment about an item by clicking on its icon, or add comment fields for all items by clicking on Comment All. List the most negative aspect(s): 3.List the most positive aspect(s): 4. Top of Form Top of Form

23. Utah School of Computing slide 23 Student Name Server Fall 2003 acm.org/~perlman/question.cgi To mail in your results, click on: Mail Data System: Email to: Optionally provide comments and your email address in the box. List the most negative aspect(s): 3.List the most positive aspect(s): 4. Top of Form Top of Form

24. Utah School of Computing slide 24 Student Name Server Fall 2003 acm.org/~perlman/question.cgi 1234567 NA 1.Overall, I am satisfied with how easy it is to use this system strongly disagreestrongly agree 2.It was simple to use this system strongly disagreestrongly agree 3.I can effectively complete my work using this system strongly disagreestrongly agree 4.I am able to complete my work quickly using this system strongly disagreestrongly agree 5.I am able to efficiently complete my work using this system strongly disagreestrongly agree 6.I feel comfortable using this system strongly disagreestrongly agree List the most negative aspect(s): 3.List the most positive aspect(s): 4. Top of Form Top of Form

25. Utah School of Computing slide 25 Student Name Server Fall 2003 RHS of Each Row 1234567 NA 1. strongly disagree strongly agree

26. Utah School of Computing slide 26 Student Name Server Fall 2003 acm.org/~perlman/question.cgi 7.It was easy to learn to use this system 8.I believe I became productive quickly using this system 9.The system gives error messages that clearly tell me how to fix problems 10.Whenever I make a mistake using the system, I recover easily and quickly 11.The information (such as online help, on-screen messages, and other documentation) provided with this system is clear 12.It is easy to find the information I needed

27. Utah School of Computing slide 27 Student Name Server Fall 2003 acm.org/~perlman/question.cgi 13.The information provided for the system is easy to understand 14.The information is effective in helping me complete the tasks and scenarios 15.The organization of information on the system screens is clear 16.The interface of this system is pleasant 17.I like using the interface of this system 18.This system has all the functions and capabilities I expect it to have 19.Overall, I am satisfied with this system List the most negative aspect(s): 3.List the most positive aspect(s): 4. Top of Form Top of Form

28. Utah School of Computing slide 28 Student Name Server Fall 2003 acm.org/~perlman/question.cgi List the most negative aspect(s): 3.List the most positive aspect(s): 4. Top of Form Top of Form List the most negative aspect(s): 3.List the most positive aspect(s): 4. Top of Form Top of Form

29. Utah School of Computing END HCI Validation