CS160 is an upper division course, and one of few where you will work extensively on one significant programming project. To participate fully in this course, you are required to have taken CS61B or have equivalent knowledge. We will assume that you are familiar with Java and are comfortable coding a large-scale project.

In Spring 2016 we will be aiming accommodate around 200 students (it may be slightly more or less depending on several factors). It will be held M+W 2:30-4pm. There will be sections as well once a week. There will be a midterm. There will not be a final exam (ignore any conflicts you have with final exams). We will have a final critique during RRR week (date and time TBD). You must attend the final critique.

Enrollment will use the standard policy for computer science upper division courses and will not use a separate application process. This means that waitlist position will matter and students declared as LSCS or EECS who want to prioritize enrollment into this class should consider using phase I of telebears to sign up for CS160. We will take people off the waitlist in waitlist order shortly before the first day of class in January. You must attend the first class or you will be dropped. This means you need to arrange to come back from any trip or vacation in time for the first day of class on Jan 20th 2016 @ 2:30pm. Please do not email us with requests to miss this first class. If you cannot make this first class, please do not enroll.

During the first half of the semester class time will be used for lectures and workshops focusing on core HCI techniques and material. A midterm will be held. During the second half of the semester, students will break into smaller groups (roughly 5-6 students) across three studios within Jacobs Hall. I will be assigning the groups. Within these smaller teams, students will work on a larger scale design project using the three hour studio time as worksessions, critique time, and for direct interaction with faculty and teaching staff. Students will be expected to attend these studio times. A final project critique and public showcase will replace a final exam.

Once enrolled, you will be expected to actively participate in lectures, complete readings ahead of time, complete a number of small programming assignments, and, most importantly, participate 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.

Note that the majority of the work in this course is conducted in the form of a semester-long group project. Unlike other courses, dropping the course before the end of the semester has negative consequences for your other group members. So once you have joined a group please make sure you are committed to staying in the course.

You are expected to read the assigned readings and post a substantive reading response before class. Late comments will NOT be accepted. There will be plenty of opportunities in class to apply that knowledge and in-class participation will be part of your grade.

There will be two types of assignments: programming assignments and project assignments. Programming assignments will be individual exercises; their main goal is to teach you the skills needed to successfully execute on your project. Project assignments will be done in groups.

You will be expected to turn in written documentation at each stage of your project. You will also turn in working code. Each group member will help to give an oral presentation about your project.

There will be a midterm exam.

Most assignments will be turned in online through bCourses.

Project assignments may not be turned in late. Programming assignments will lose 10% at one day late, 20% for two days, and 40% for 3 days.

You not are required to own an Android phone. However….At least one member in each group (to be set in week 4) will need to own an Android phone running at least Android version 5.0 (lollipop) that can be used for development, deployment, documentation, and evaluation of your team’s work. You cannot use a Tablet running Android. Check withe the GSIs and on Piazza if you are unsure.

You are required to own an Android phone running at least Android version 5.0+ (Lollipop) that can be used for development, deployment, documentation, and evaluation of your work. Use Android API 21.

Each group is responsible for making sure that all members are participating. As part of the project reports, you are required to describe the effort put in by each member, both on specific tasks and as a fraction of the group’s effort. Make sure you discuss this regularly, to make sure your group is in agreement about the work breakdown.

If a group member is not participating, the entire group must meet with the teaching staff. Effective group work (which entails some amount of conflict resolution) is a key skill for success in industry. We would like you to work through conflicts if at all possible, and we will devote some class time to this topic.

If you have a question about a grade, you should meet with the GSI. You can come to the professor if the issue cannot be resolved with the GSI’s help.

Cheating will not be tolerated, and will get you an F in the class. Please take time to view the UC Berkeley Student Code of Conduct

We expect all students and teaching staff to conduct themselves according to the UC Berkeley Honor Code

This lectures, format and syllabus of this class are based on HCI classes taught by Bjoern Hartmann, Jodi Forlizzi, John Zimmerman, Haakon Faste, Ben Bederson, John Canny, Maneesh Agrawala, Scott Klemmer, Francois Guimbretiere, Marti Hearst, and James Landay. These authors have kindly provided access to their lecture slides and my own slides borrow from their earlier work.