Home | Lectures | Sections | Assignments | Projects | Reference | News & Chat

User Interface Design, Prototyping, and Evaluation
CS 160 - Spring 2005

Lecture: Tuesday and Thursday, 11 - 12:30, 306 Soda
Discussion: Wednesday 10-11am & 11am-12pm, 320 Soda
Lab: Thursday 2-3pm, 330 Soda

Class Home Page: http://inst.eecs.berkeley.edu/~cs160/sp05/
Class Newsgroup: ucb.class.cs160

Recent Messages


  • Tara will hold extra office hours Tuesday 5/17, 1:30 - 3 pm in 256/360 Hearst Mining.
  • Everyone received full credit (15 / 15 points) on I3, Presentation Reviews.


  • All students need to bring bluebooks to the final. Do not write in the bluebooks before the exam. We will collect them at the beginning of the exam, shuffle them, and hand them back out.


  • You are required to hand in a completed Team Evaluation (word, pdf) during your project evaluation session.


  • Each group needs to schedule a 30 minutes project evaluation session with Prof. Arnold and me. The days/times for these sessions are:
    Tuesday, 5/10, 1 - 5 pm;     Wednesday, 5/11, 10 am - 2 pm
    Please send Tara an email indicating all of the times your group is available within these days/times.


  • The CS 160 project Poster Session will be Thursday, 5/12/05, from 11 am - 12:30 pm in the 6th floor alcoves (611 and 651) and atrium of Soda Hall.

View Message Archive


Instructor: Stephen Arnold
(510) 642-9827
Email: cs160 at imail dot eecs dot berkeley dot edu
Office Hours: Tuesdays 2 - 4 pm (329 Soda), and by appointment
Head TA: Tara Matthews
Email: tmatthew at cs dot berkeley dot edu
Office Hours: Thursday 12:30 - 2:30 pm (356 Hearst Mining; knock if locked)
Required Textbook:
  1. Designing the User Interface: Strategies for Effective Human-Computer Interaction, Edition 4 (2004)
    Ben Shneiderman and Catherine Plaisant
    Addison-Wesley (publishers), ISBN: 0-321-19786-0
  2. Task-Centered User Interface Design
    Clayton Lewis and John Rieman
    Available online and in PDF
CS160: previous years

Course Description

CS 160, or Human Computer Interaction, is a class where you will learn to prototype, evaluate, and design a user interface. You will be expected to work with a group of four to five other students in this project-based course. Throughout the course of this project, you will work closely with users.

Aims and Objectives

When you complete this class, you will be equipped to assess the utility of an interface using one of several different evaluation techniques. You will understand the phases of the design life cycle, and what development and evaluation tools are appropriate to each phase.


CS160 is concerned with the design, evaluation, a use of applications. In contrast, most of the other classes in Berkeley CS focus on the inner workings of technology. You will make use of technology to develop your applications, but you will not learn about technology in particular. The skills you develop, while not directly relevant to other computer science courses, will be useful wherever you go after Cal.

You will be expected to actively participate in lectures, complete readings ahead of time, and, most importantly, participate equally and fully in your group project. The teaching staff will promptly return graded homework to you, and will be available to provide feedback and help with problems.


CS160 includes both group and individual assignments. Much of the grading in this class is qualitative, including assessments of the quality of your design process, the quality of your designs, evaluations, and prototypes. Grading will be done by the instructor, TA and readers.

The breakdown of grading will be:

Individual Work
Midterm 15%  
Final 15%  
Individual assignments 15% 4 assignments at 5% each, keep the best 3
Class participation 5%  
Team Project
Project proposal 0% Must be approved before starting next steps
Task & user analysis & usability goals 8%  
Paper prototype 8%  
Testing without users 8%  
User testing on paper prototype 8%  
Design iteration & presentation 8%  
Implementation 8%  
Team evaluations 2%  
Assessment Guidelines
  • You will be expected to read the assigned material before class, and to come to class with prepared answers to discussion questions.
  • You will be expected to turn in written documentation at each stage of your group project.
  • Assignments may not be turned in late. Individual assignments will lose one grade point per day they are late.
  • You will be asked to evaluate your teammates twice during the term. If there is a serious problem with the participation of a team member, it is your responsible to discuss it with that team member. If you are not able to resolve the problem, discuss the issue with either the TA or instructor.
  • If you have a question about a grade, you should meet with the TA. You may come to the professor if the issue cannot be resolved with the TA's help.
  • Cheating will not be tolerated, and will get you an F in the class

Other Materials

This class has an implement project. You are allowed to use any software or hardware platform. The university will provide you with an account if you need one. The software available with the class account is sufficient to support your project. If you decide to use other software or hardware, it is your responsibility to obtain it.