StatusCompleted April 2008 by Erin Yu and Daphne Ogle SummaryHigh-level summary to be added after testing has been completed. NotesGoals Wiki Markup |
---|
For File Uploader user test we want to consider ease of use for uploading files to Sakai \[to start with\]. <ac:structured-macro ac:name="excerpt" ac:schema-version="1" ac:macro-id="fe43cbf6d5985a4c-5850edef-41f8411e-bfa6a51d-1eb1b028e46ee5de316a20e7"><ac:parameter ac:name="atlassian-macro-output-type">INLINE</ac:parameter><ac:rich-text-body><p>Research questions/goals include:</p>
<ul>
<li>Do users realize they can upload files? Do they realize they can upload multiple files?</li>
<li>Are users successful at uploading a file in general? A single file from their computer? Multiple files from their computer?</li>
<li>Can a user find a particular file easily?</li>
<li>Do users recognize and understand intuitively how to upload files?</li>
<li>Is pause/resume upload understandable or does this confuse them</li>
<li>Does the user understand that you cannot "cancel" the upload until you first "pause" the upload? Is differentiating between paused and not paused states understandable to users?</li>
<li>Are visual affordances meaningful and helpful to users?</li>
</ul>
</ac:rich-text-body></ac:structured-macro> |
Success CriteriaA successful design has been achieved when: - 80-90% of users can successfully upload a file from their desktop.
ProtocolMethod and test coordinator script. UsersThe File Uploader will be used by a wide cross-section of students and faculty in higher educational institutions. We'd like to include keyboard-only users in the user test if possible (can prototype handle keyboard nav?). Wiki Markup |
---|
Our access to participants is limited primarily to students over faculty. We will try and include a few faculty. We want to test a range of non-technical and more tech savvy students as well as faculty members of the University of Toronto and UC Berkeley. For our user test with working prototype we will have 5-7 users \[combination of students and faculty, but primarily students\]. |
** If doing: For earlier paper-prototyping sessions we will work with a smaller number of participants. Interaction DesignUnderlying design patterns and description of component behavior. Test EnvironmentTest EnvironmentLocation and version of the environment that was used. Attach a screenshot of the environment at the time of testing if the environment will change over time. ResultsFull notes and analysis of the user tests. Excerpt Include |
---|
| Infusion13:Uploader User Testing - Round 1 Results |
---|
| Infusion13:Uploader User Testing - Round 1 Results |
---|
nopanel | true |
---|
|
More... |