501
edits
Labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests/Tester 08a: Difference between revisions
Jump to navigation
Jump to search
Labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests/Tester 08a (view source)
Revision as of 19:34, 12 December 2008
, 12 December 2008Added Metrics box
Indolering (talk | contribs) (New page: === Tester 008 === "My idea is that the interface should be so intuitive that one doesn't even have to try, it should just do what you think it should do." === Highlights === # Mistaking...) |
Indolering (talk | contribs) (Added Metrics box) |
||
| Line 17: | Line 17: | ||
====Translate Command==== | ====Translate Command==== | ||
Raskin's 1st law of Interface Design "A computer shall not harm your work or, through inaction, allow your work to come to harm " 22:15 -I believe a single user has guessed to reload the page, after three previous failed attempts. | Raskin's 1st law of Interface Design "A computer shall not harm your work or, through inaction, allow your work to come to harm " 22:15 -I believe a single user has guessed to reload the page, after three previous failed attempts. | ||
====Metrics==== | |||
{| cellspacing="0" border="1" | |||
|- | |||
| <u>Research Questions <br /></u> | |||
| <u>Performance Benchmarks<br /></u> | |||
|- | |||
| How do users try and access Ubiquity | |||
*Number of things they tried before launching Ub. | |||
*Time before launching Ub | |||
*Did the instructor have to directly show them how? | |||
|- | |||
| How do they learn the command syntax? | |||
| | |||
|- | |||
| Do users value Ubiquity? | |||
*Feedback | |||
*Followup studies | |||
|- | |||
| How would we identify problematic commands via statistical analysis? | |||
*look at failed commands & commonalities | |||
**Lack of completion | |||
**High error rates | |||
*User feedback of poor commands, correlate with data | |||
|} | |||
=== Timeline === | === Timeline === | ||