CS 161: Operating Systems (2014)

Tuesday/Thursday 1:00-2:30

Pierce 301

Home Syllabus Assignments Resources Piazza

Professor Teaching Fellows
Margo Seltzer David Holland: dholland@eecs.harvard.edu
Maxwell Dworkin 241 Office Hours: Friday 3-5 (or mail me), MD 213
margo@eecs.harvard.edu Daniel Margo: dmargo@eecs.harvard.edu
http://www.eecs.harvard.edu/margo Office Hours: Thursday 2:30-4:30 Maxwell-Dworkin 121
617-496-5663 Kenny Yu: kennyyu@college.harvard.edu
Office hours: Monday 3:00-5:00 Office Hours: Wednesday 8-10pm, Quincy Dining Hall
Monday 3-5, MD 2nd floor lounge  
Tuesday 2:30-4:30pm, Cruft 403 (the IACS conference room)  



Computer Science 61 or permission of instructor.


Doeppner: Operating Systems in depth (required)


This course is an introduction to operating systems. After completing this course, you should be able to:

As was done last spring, we will teaching CS161 in a hybrid flipped and conventional classroom. On days we are officially flipped, class attendance is mandatory. Such days will be clearly marked on the syllabus. Each one will (almost always) have:

On these days, attendance is mandatory and you should have completed both the pre-class work and the web work before coming to class. I check the web work before class so that we can discuss issues that were not clear from the pre-class work. While we do not expect that you will be writing the majority of OS161 code during these flipped sessions, we will use them to help you become familiar with the code base you'll be using this semester, select and use appropriate synchronization primitives, and evaluate and improve design documents.

Classes that are not flipped will frequently still have interactive in-class work, but will not require any pre-class preparationp These more conventional classes will frequently take place while you are working on the three heavy assignments for the course. Although I will not take attendance for those classes, attendance is strongly encouraged.

Although we flipped the classroom in 2013, the precise structure of the classes continues to be a work in progress. We always welcome feedback -- tell us what is working for you and what is not working for you. You can read about last year's experience at my blog.

Course Requirements Course Policies
Class participation (10%) In lieu of class participation, students may send comments/questions (regularly) via email.
Six homework assignments (50%) No late days for assignments 0 and 1
Midterm (15%) Assignments 2-5 completed in teams of 2
Final take-home exam (25%) 5 total late days for assignments 2-5

Collaboration Policy

There are three types of work associated with this course and each has its own specific policy for collaboration. We encourage students to talk to each other about the course. In particular, you can always discuss technical details about software used in the course. You can share design information, help each other debug, brainstorm ideas, talk about CS161 over dinner, shout out breakthroughs in your sleep, etc. Academic integrity requires that when you submit work, you make it clear who contributed to the work and from where ideas came.