CS 354: Operating Systems (3 credits, fall 2016)

Instructor

Prof. Mathias Payer (LWSN 3154M, office hours: Mon, 1500--1600)

Teaching Assistants

Bader AlBassam

Derek Schatzlein

Prashast Srivastava

Web site, Piazza, and Blackboard

The course home page is at: http://www.cs.purdue.edu/homes/cs354.

Discussions related to the class (especially labs) will take place on Piazza. It will also be the primary medium for communication between the TAs and the students (use a private post if you wish). Most handouts, including lecture notes, lab specifications, and supplementary materials will be posted on Piazza.

Grades will be posted on Blackboard Learn.

Meeting places/times

Lectures will be in KRAN G016, Monday and Wednesday (4:30 PM - 5:45 PM).

PSO sessions are scheduled at the locations given in myPurdue on: Tuesdays, Wednesdays, and Fridays. You are strongly recommended to attend one PSO session a week. There will be no PSOs the first week of class. Here are the PSO locations from myPurdue:

P01; CRN: 11462; Fridays 1530-1720; HAAS 257

P02; CRN: 13243; Fridays 1130-1320; HAAS 257

P03; CRN: 60236; Fridays 930-1120; HAAS 257

P04; CRN: 52686; Tuesdays 930-1120; HAAS 257

P05; CRN: 12381; Tuesdays 1330-1520; HAAS 257

P06; CRN: 62132; Wednesdays 930-1120; HAAS 257

Labs

Prerequisites

CS 250, CS 251, CS 252, and fluency in C.

Course Material

The required textbook for the course is: Operating System Design, The Xinu Approach (Second Edition), by Douglas Comer, published by the CRC Press (2015).

Alternate recommended textbooks are: (1) Operating Systems: Three Easy Pieces by Remzi H. Arpaci-Dusseau and Andrea C. Arpaci-Dusseau, (2) Computer Systems: A programmer's Perspective by Randal E. Bryant and David R. O'Hallaron, or (3) Modern Operating Systems, Third Edition, by Andrew Tanenbaum.

Late policy

All deadlines are hard and no late submission will be accepted. If you submit late, you will receive 0 points.

Exams

There will be one midterm exam and one final exam. The midterm will cover material until (and including) the lecture right before the exam. The midterm will be held on TBA.

The final exam will be held on 12/13 from 7:00p to 9:00p in STEW 130. The exam will include material covered during the entire semester.

If you have a conflict with the midterm or final exam time, you must contact the Professor in writing at least one week before the exam. Except for medical emergencies, no further requests will be granted.

Grading

Labs: 50%, Midterm: 20%, Final: 30%, and unannounced quizzes: 3% bonus.

Regrade requests

If you feel that you have been unfairly graded on a project, quiz, or exam, you should petition the appropriate TA or Professor in writing within one week of distribution of the graded work. After one week, no regrade requests will be honored. For labs, you are allowed to change a few lines of code, but there will be a penalty per change.

Academic integrity policies on projects and exams

All work that you submit in this course must be your own; unauthorized group efforts are considered academic dishonesty. See the brochure Academic Integrity: A Guide for Students (available on-line) for definitions and sanctions. Academic dishonesty is a serious matter, which may result in suspension or expulsion from the University. In addition to any other action taken, such as suspension or expulsion, a grade of F will normally be recorded on the transcripts of students found responsible for acts of academic dishonesty. You are encouraged to report academic dishonesty to the instructors or TAs directly, or to the Office of the Dean of Students. You may discuss project assignments in a general way with other students, but you may not consult any one else's code, including online code on the Internet, or code from a former student.

We will be using MOSS to detect similarity among submitted labs, including any similar online code, and code from earlier semesters.