CS 161: Operating Systems (2014)
||David Holland: email@example.com
|Maxwell Dworkin 241
||Office Hours: Friday 3-5 (or mail me), MD 213
||Daniel Margo: firstname.lastname@example.org
||Office Hours: Thursday 2:30-4:30 Maxwell-Dworkin 121
||Kenny Yu: email@example.com
|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)
- Concept Inventory
- Please bring your laptops to class for the first couple of weeks.
- We will be using
for class discussion. Please sign up now!
- Section times are posted above. Mostly we won't run the full two
hours. Go to whichever section fits your schedule better; generally
both will have similar content.
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:
- Explain how operating systems provide the abstractions with which
programmers and users are familiar.
- Work effectively with a partner.
- Design, implement, modify, and analyze complex software systems
- Undertake different types of design projects including: implementing
to a well-defined interface, designing appropriate interfaces to provide
specified functionality, extending an existing body of code.
- Explain through examples how violation of good design
and coding practices lead to security problems.
- Analyze how operating systems problems are addressed in different
systems and understand why particular approaches were taken.
As was done last spring, we will teaching CS161 in a hybrid
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.
- Pre-class work: typically reading and/or video clips on a particular
- Web-work: a short web-based form that will ask you to demonstrate
understanding of the pre-class work.
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
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.
|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
||Assignments 2-5 completed in teams of 2
|Final take-home exam (25%)
||5 total late days for assignments 2-5
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.
- Web Work: These are pre-class assignments due the day of class
and should be completed by individuals without collaboration.
- Homework assignments: Homework assignments are to be completed
by the individual or team whose name(s) appear(s) on the submission.
You are free to discuss the assignment with anyone else in the class,
including design documents, debugging tips, or suggested tools.
When such discussions influence your design or implementation,
you must identify the individuals who influenced you in the written
documents that accompany your assignment.
Similarly, if you get design ideas from a web site, book, or external
piece of code, you should cite those sources as well.
- Exams: No collaboration is allowed.