HCI 210 Introduction to Human Computer Interaction

Fall 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

Wednesday 5:45-9:00 and Distance Learning
CS&TC 200, Loop Campus

Required Text

User-Centered Website Development: A Human-Computer Interaction Approach, by D. D. McCracken and R. J. Wolfe, ISBN 0-13-041161-2.

Prerequisites

Sophomore standing.

Overview

This course examines the practical and theoretical issues of how people interact with computers. Students draw upon theoretical principles, observations and self-reflection as they practice methods for designing interactive systems to improve their usability. A principal goal of the course is for students to develop an awareness and sensitivity for user needs and abilities as they interact with computer applications, websites and other interactive devices. By the end of the term, students will be able to:

Projects

Projects for this course include two individual assignments and a multi-stage team project.

For the first individual assignment, students will choose an interactive system or device and reflect on their ability to use it. They will contrast their ability with that of users different from themselves.

For the second individual assignment, students will analyze a task and reflect on required abilities and mental models to successfully complete each step.

For the the multi-stage team project, students will design an interactive system employing methods comprising the user-centered design (UCD) process. Student teams will prepare a report for each stage. The stages include the following:

Grade Determination

15% (30 points) Two individual assignments (15 points each)
30% (60 points) Multi-stage team project (20 points each stage)
20% (40 points) Midterm exam
10% (20 points) Individual contribution to class and team projects
25% (50 points) Final exam

The score for individual contribution to class and team projects is based on contributions to class activities, documented contributions in team reports, observed team activities (in class, email or group message boards) and team member reports at the end of the quarter.

At the end of the quarter every student is expected to submit a completed evaluation form for each member in their team.

Team presentations occur in the last week of class. Distance Learning students will create an online presentation.

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

All students are expected to attend or view all classes and participate in class activities, either in-class or remotely through the DL program.

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.

Team projects will generally be completed in groups of three or four. Team composition will be determined by the instructor based on meeting preferences and shared interests. All group members are jointly responsible for the entire assignment, although the group may assign primary roles to each group member. Generally, each group member will receive the same score on each project. 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. Any adjustement will be based on a variety of indications including group participation in class, contribution summaries in reports, and student feedback at the end of the quarter.

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

The individual assignments and exams must be individual efforts. When re-using materials, citing examples or using quotes, it should always be clear to the instructor when relying on the work or results of others. If in doubt, be explicit in your assignments and reports.

No opportunities for extra credit will be offered. If you find that you have low scores on tests or assignments, your best strategy is to focus on the remaining assignments and tests in the course.

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

Tentative Schedule

Week Topic Text Reading Exam or Due Project
Sep 6 Importance of computer usability and accessibility; overview of user-centered design process; Academic disciplines for HCI Chapter 1 Discuss possible projects
Sep 13 Human capabilities and limitations Chapter 2 Form project teams
Sep 20 Analysis for UCD Chapter 3 Individual assignment 1
Sep 27 Conceptual Design Chapters 4, 6 and course notes  
Oct 4     Midterm Exam
Oct 11 Visual organization, presentation principles Chapters 5 Team project 1
Oct 18 Prototyping and Evaluation Chapters 7, 8 Individual assignment 2
Oct 25 Testing demo, Accessibility Chapters 8, 12, Rettig article Team project 2
Nov 1 Globalization and Usability testing Chapter 13 Usability testing (in class)
Nov 8 Presentations, Personalization and Trust Chapter 14 Team project 3
Nov 15     Final Exam