Princeton University Computer Science Department

Computer Science

What's New? January 3

Click Here for Pre-Midterm Schedule and Resources

Click Here for Post-Midterm Schedule

Click Here for Final Schedule

Course Summary

Design and interfacing of computer input and output systems.
Inputs: Standard (mouse, keyboard, joystick, etc.) and
              new (head trackers, music controllers, gloves, etc.) devices.
Signal processing, feature extraction, and data mapping schemes.
Outputs: Graphics, haptics, music, and 3-D sound.
This year we will emphasize non-speech facial and vocal UI components.
Hands-on laboratories and independent projects.
Prerequisites COS 217 or ELE 318.

Administrative Information

Lectures: -, Room: CS 302

Professor: - CS Building - 258- @cs.princeton.edu

Undergraduate Coordinator: Tina McCoy - 410 CS Building - 258-1746 tmmccoy@cs.princeton.edu

Teaching Assistants: Ananya Misra

Homework Assignments

There will be questions to be answered as part of the labs.
These will go into the overall lab report grades.
Labs are group activities.

Exams

Assignments, Exams, and Grading

The grading in this course will be based on the evaluation of the following:

• Two exams (see Exams and/or Schedule)
• Assignments: All of these must be completed.
• Laboratory Reports, including some homework-like questions to be answered.
  (Read here what a good lab report should have)
• Final Project (also includes proposals and progress reports)

Final Project

The goal of this course is for the students, working in teams, to propose a new human computer interface, or an improvement to an existing interface, to solve a particular problem. Inter-Disciplinary teams are encouraged. Applications include interfaces for persons with disabilities, musical or other artistic controllers/systems, sports monitors and improved interfaces, interfaces for virtual environments, and new means for identifying and authenticating individual computer system users. It is expected that the projects will lead to a completed (though rough in most cases) prototype. Testing (not just for functionality, but for "betterness" by some metric) of the device/system should be conducted and included in the report.

Final written reports will be due on Dean's Date, January 11, 2005, and a demonstration of the system must be completed by Friday, January 14, 2005.

References

• Mark W. Lansdale and Thomas C. Ormerod. Understanding Interfaces: A Handbook of Human-Computer Dialogue. Computers and People Series, edited by B.R. Gaines and A. Monk. Academic Press, San Diego, CA. 1994 289 pp.
  
  
• William H. Cushman and Daniel J. Rosenberg. Human Factors in Product Design. Series: Advances in Human Factors/Ergonomics, edited by Gavriel Salvendy. Elseview, Amsterdam Holland. 1991. 340 pp.
  
  
• Jenny Preece, ed. Human-Computer Interaction. Addison-Wesley, Menlo Park, CA. 775 pp.
  
  
• Ben Shneiderman. Designing the User Interface: Strategies for Effective Human-Computer Interaction, Second Edition. Addison-Wesley, Menlo Park, CA. 573 pp.

Schedule of Lectures, Labs, Assignments