HCI 360 User-Centered Evaluation

Spring 2006

Instructor

Dr. Craig Miller
Office: 830 CTI Building, 312-362-5085
Email: cmiller@cs.depaul.edu
Web page: http://facweb.cs.depaul.edu/cmiller
Office Hours: Announced on Web page

Course Meeting

Thursday 5:45-9:00
Lewis 1506, Loop Campus

Required Texts

Handbook of Usability Testing, by Jeffrey Rubin. ISBN 0-471-59403-2.

Task-Centered User Interface Design, by Clayton Lewis and John Rieman. Online text.

Recommended Texts

Usability Testing and Research, by Carol M Barnum. ISBN 0-205-31519-4.

Usability Inspection Methods, edited by Jakob Nielsen and Robert L. Mack. ISBN 0-471-01877-5.

Prerequisites

HCI 210.

Overview

This course surveys user research and usability evaluation methods. Working as teams, students choose a working computer application and practice course methods on it throughout the term. Students first learn to conduct user research to determine user needs and core tasks for the chosen application. User research results are presented in the form of user profiles (aka personas) and task scenarios. The results of user research are then used to guide usability evaluation methods including heuristic evaluation, walkthroughs and usability tests.

Goals

Certainly, a primary goal is to learn how to conduct various methods for conducting user research and evaluating user interfaces. However, the course also practices skills with broader application. These include:

Projects

  1. User Research
  2. Heuristic Evaluation and Cognitive Walkthrough
  3. Preparation for Usability Test
  4. Usability Test and Results

Grade Determination

40% (80 points) 4 Projects (20 points each)
5% (10 points) Quiz
20% (40 points) Test
25% (50 points) Final Exam
10% (20 points) Participation

Students receiving more than 90% of possible points are guaranteed at least an A-, more than 80% at least a B-, more than 70% at least a C-, and more than 60% at least a D.

Policies

Students are expected to attend all classes and participate in in-class exercises. Class will start promptly at 5:45. Students are individually responsible for material they may have missed due to absence or tardiness. Furthermore, since some group work will occur during class, a student who misses class will jeopardize their standing with the group.

The participation score is based on a variety of indications including group participation in class, contribution summaries in reports, and student feedback at the end of the quarter. This form will be used to solicit student feedback. Scores of 16 through 18 (out of 20) signify a solid contribution. Scores of 19 or 20 will be reserved for students who made an extraordinary contribution to their team.

All projects will be completed in groups of three or four. While students will have some control on group selection, the instructor reserves the right to modify groups in order to meet course objectives. While the group may assign a primary role to each group member, all group members are jointly responsible for the entire assignment. Generally, each group member will receive the same grade. However, in some cases, additional credit may go to those who make an exceptional contribution to a project and reduced credit to those who contribute little to a project. Such adjustment of credit would be made in addition to the grade awarded for group participation.

Exams can only be made up with a serious documented excuse (e.g. illness, death in the family). A make-up exam must be arranged as soon as possible and always before the student attends the next class meeting. Arrangements involving other excuses require prior permission from the instructor.

Late projects will be accepted without penalty until 2pm the day following the due date. Projects turned in later than 2pm the day following the due date will not be accepted.

School policies on instructor evaluation, email, plagiarism and incompletes.

Tentative Schedule

Week Topic Text Reading Exam or Due Project
Mar 30 Course overview, usability principles, user research Rubin ch. 1, Lewis and Rieman ch. 1 Establish project groups
Apr 6 Learning about users; Personas and scenarios Lewis and Rieman ch. 2; Class links and notes  
Apr 13 Heuristic evaluation Rubin ch. 1, Lewis and Rieman ch. 1, Lewis and Rieman section 4.3 Quiz
Apr 20 More inspection methods; Intro to Usability Testing Lewis and Rieman section 4.1, Rubin ch. 2-4 Project 1
Apr 27 Work on projects after test (as time permits)   Midterm Test
May 4 Prep for usability testing, Testing materials, Conducting the Test Rubin ch. 5-7 Project 2
May 11 Creating the Report, Comparison Tests Rubin ch. 10 and class notes  
May 18 Pilot usability testing   Project 3
May 25 User modeling Class notes  
Jun 1 Presentations, overview, additional techniques Class notes Project 4
Jun 8     Final Exam