CPS 210, Operating Systems, Duke Univ.

CPS 210

Operating Systems

Spring 1999


Course Vital Statistics

Lecture Time: TH 12:40-1:55
Lecture Location: LSRC D344

Instructor: Carla Ellis
Office: D324 LSRC
Phone: 660-6523
Email: carla@cs
Office Hours: Tuesdays and Thursdays, 10:30-11:30 AM

TA: Ken Yocum
Email: grant@cs.duke.edu
Office: D307
Phone: 660-6599
Office Hours: TBA


Announcements

Check the schedule for assignments.

Assignment Number 3: proj3.ps (also available in proj3.pdf).

Lecture Notes are all available now.

All homework stats can be found here .


Communications

The mailing list and newsgroup are still under construction.


Workload

Base Workload. In addition to the readings, there will be three programming assignments (35%), a midterm exam (20%), and a written final exam (30%). You are expected to program in C, C++, or Java on Unix. In addition, there will be a "final interview" during which we will meet one-on-one and have a conversation about operating systems. The final interview and class participation will be worth 15% of your grade. We try very hard to be fair.

The E-track, Grading, and Quals. This is a two-track class. Assigned work includes mandatory "G-track" components and some optional "E-track" components. The E-track work is necessary if you want to earn a grade of E or E+. You may choose at any time to do any or all of the optional E-track work, but it is not likely to improve your grade much unless you take on the primary E-track requirement, a project on a topic of your choosing (see below). This will demand a significant commitment of time and energy on your part (and ours).

CPS 210 is a "quals course" for CPS graduate students. We assign quals passes based on demonstrated mastery of the quals material, regardless of your grade. In particular, E-track work is not necessary for a quals pass and will not improve your chances of earning a quals pass. The E-track is intended for students with a serious interest in systems or architecture. If you decide to take on E-track work, make sure you also leave yourself enough time to learn the course material and earn your quals pass.

Grades will be assigned by adding your scores on the G-track work and exams, and assigning base grades curved from G- to E-. Undergraduates are graded on a different scale since this course is more advanced than typical undergraduate classes. Your scores for the E-track work are then added and curved to improve your base grade from 0 to 3 notches (e.g., 3 notches advances you from a base grade of G+ to a final grade of E+). We give S grades only for barely satisfactory work, since graduate students cannot receive credit for more than two S grades.

To summarize: if you do an outstanding job on all the G-track work, you'll get an E- and a quals pass; if you do a good job on the G-track work you'll get a G or a G+ and a quals pass; if you do good work in both tracks you'll get an E- or an E and a quals pass. We reserve E+ grades for truly outstanding students.

Project. If you choose to do an optional project, you must discuss your ideas and goals with me prior to February 23 and we must arrive at an agreement on a project no later than March 2. We encourage you to form groups of two or perhaps three students. At the end of the reading period you will post the URL of a web page describing your project, with pointers to your code and related material. Projects and other E-track work are held to a high standard; incomplete or incorrect work will receive little if any extra credit. It is acceptable to combine this project with project work from another course (e.g. CPS 296.2 or CPS 296.3) as long as the topic of the project is appropriate (i.e., has something to do with Operating Systems).


Reading Materials and Other Resources


Policies

On collaboration. Collaboration on recommended problem sets and programming assignments is encouraged. However, your final written work must be your own, and you may be called upon to explain (alone) your choices and answers in more detail. How can you know when you are crossing the line between leaning on your colleagues and learning with your colleagues? Here's the Gilligan's Island Rule: This rule says that you have truly assimilated the knowledge gained by working with fellow students if you can leave the session without a written record of the interactions (electronic or otherwise), then engage in a half hour of mind-numbing activity (like watching an episode of Gilligan's Island), before starting to work on your own. This test assures that you are able to reconstruct what you learned from the meeting, by yourself, using your own brain.

On giving credit where credit is due. You must acknowledge the sources of your words and ideas, when they are not your own, and you should list the names of anyone who helped you with your work. Thus, I acknowledge that much of this web page content comes from Professor Jeff Chase who developed the clever E-track system in previous offerings of CPS 210. The Gilligan's Island Rule is an inspiration of Professor Larry Ruzzo from University of Washington. Failing to give appropriate credit is at best a violation of professional etiquette, and at worst it is plagiarism. Plagiarism, like collaboration on exams, is cheating. Cheating is a very serious offense and I do not expect it to occur in this class.


Previous CPS 210

Spring 1998


Last Updated: 21-April-99

Carla Ellis's HomePage