• Spring 2011
• Tuesdays (lecture/discussion): 11:30-1:20 EE 236
• Thursdays (lab/project): 11:30-1:20 LWSN B160
• http://www.bikmort.com/dokuwiki/hci_issues_and_implementation

• Tim Korb
• Office: LWSN 3144
• Phone: 765-494-6184
• Email: jtk@purdue.edu
• Office Hours: By appointment
• http://www.cs.purdue.edu/people/jtk
• (There is no teaching assistant.)

This course is an introduction to Human-Computer Interaction (HCI). Students read, and report on in class, research papers, book chapters, and other sources of information on HCI. There are no (or very few) lectures. The course also includes a weekly lab (and associated significant project) to reinforce HCI concepts.

Permission of instructor is required. The project requires solid programming experience (e.g., in Java, C/C++, and/or Python), understanding of dynamic data structures, familiarity with operating system intefaces, and ability to use a variety of software development tools (e.g., Eclipse and Git or SVN). Android experience a plus.

1. Learn the concepts and vocabulary of Human-Computer Interaction (HCI).
2. Gain experience in applying HCI principles to the design of software systems.

1. Create, as a team, a body of HCI knowledge encountered during the course.
2. Create, as a team, a large project using HCI principles (among others).

• Each student will identify three papers to use as course readings (book chapters may be used instead of papers). All reading choices require instructor approval.
• With these papers, each student will
  • create a review (summary plus critique) on the class wiki site,
  • lead a class discussion on the paper, and
  • update the review based on class feedback.
• All students will read all papers and provide feedback to the student reviewer (in class and on the wiki site).
• With 10 students in the class, there will be 30 papers covered during the semester.

• Students will participate in the design and development of a large software project, applying HCI principles.
• For spring 2011:
  • The project is a control system for the Harris video wall in the Lawson Commons.
  • Students will be responsible for a presentation at the CS Corporate Partners meeting, April 4-5, 2011.

There are no required texts. Reading materials will be drawn from publicly available sources, where possible.

• Class participation is a component of the grade: Full credit given each day for being on time, staying the full period, and actively participating.
• Email (jtk@purdue.edu) is the best way to reach me. You are welcome to stop by my office at any time for a brief question, although I do have frequent meetings, or you may schedule an appointment.

Students who participate fully in class, provide good reviews of their chosen papers, and actively contribute to the project, will receive A grades.

Purdue prohibits “dishonesty in connection with any University activity. Cheating, plagiarism, or knowingly furnishing false information to the University are examples of dishonesty.” [Part 5, Section III-B-2-a, University Regulations] Furthermore, the University Senate has stipulated that “the commitment of acts of cheating, lying, and deceit in any of their diverse forms (such as the use of substitutes for taking examinations, the use of illegal cribs, plagiarism, and copying during examinations) is dishonest and must not be tolerated. Moreover, knowingly to aid and abet, directly or indirectly, other parties in committing dishonest acts is in itself dishonest.” [University Senate Document 72-18, December 15, 1972]

For more information, see the Purdue Academic Integrity: A Guide for Students.

• When reviewing papers for this class, be sure to use quotations and references as necessary to properly credit the original authors. Text that is attributable to you must be in your own words.
• The project is a team one, but to the extent that code and other artifacts are identified by an author, the authorship must be accurate.

Students are expected to be present for every meeting of the classes in which they are enrolled.

The dean of students has a Class Attendance and Absence Reporting Policy.

• Full attendance is required at all weekly class and lab sessions.
• If you must miss a session for any reason, notify the instructor in advance or as soon as practically possible. Be prepared to document the reason for any missed sessions.

Include your policy on late or missed assignments (e.g., homework, labs, exams). Define clear expectations and consequences. Also include your policy on making-up missed assignments (e.g., homework, tests, labs).

Purdue University is required to respond to the needs of the students with disabilities as outlined in both the Rehabilitation Act of 1973 and the Americans with Disabilities Act of 1990 through the provision of auxiliary aids and services that allow a student with a disability to fully access and participate in the programs, services, and activities at Purdue University.

Add your personal timeline and procedure for being notified by a student (sample below).

If you have a disability that requires special academic accommodation, please make an appointment to speak with me within the first three (3) weeks of the semester in order to discuss any adjustments. It is important that we talk about this at the beginning of the semester. It is the student's responsibility to notify the Disability Resource Center (http://www.purdue.edu/drc) of an impairment/condition that may require accommodations and/or classroom modifications.

Add your personal policy for health emergencies and other emergencies. Define procedures for communicating with the students and submitting asignments. Below is Purdue's plate for addressing such emergencies.

In the event of a major campus emergency, course requirements, deadlines and grading percentages are subject to changes that may be necessitated by a revised semester calendar or other circumstances beyond the instructor’s control. Relevant changes to this course will be posted onto the course website or can be obtained by contacting the instructors or TAs via email or phone. You are expected to read your @purdue.edu email on a frequent basis.

Purdue University is committed to maintaining a community which recognizes and values the inherent worth and dignity of every person; fosters tolerance, sensitivity, understanding, and mutual respect among its members; and encourages each individual to strive to reach his or her own potential. In pursuit of its goal of academic excellence, the University seeks to develop and nurture diversity. The University believes that diversity among its many members strengthens the institution, stimulates creativity, promotes the exchange of ideas, and enriches campus life.

Purdue University prohibits discrimination against any member of the University community on the basis of race, religion, color, sex, age, national origin or ancestry, marital status, parental status, sexual orientation, disability, or status as a veteran. The University will conduct its programs, services and activities consistent with applicable federal, state and local laws, regulations and orders and in conformance with the procedures and limitations as set forth in Executive Memorandum No. D-1, which provides specific contractual rights and remedies.

Provide an outline of the content of the course with dates for readings, assignments, midterms, quizzes, labs, exams, etc. Be clear about the topics that will be covered each day in class and what the students should do in advance of class.

This syllabus is subject to change.