CSCE 311 - Operating Systems - Spring 2003

Dr. Duncan A. Buell
3A01 Swearingen, 777-2880
email ID is "buell" in domain "cse.sc.edu"

Meeting time: MW 2:30-3:45, SWR 2A15

Office hours: MW 1:00-2:30, SWR 3A01

This URL is www.cse.sc.edu/~buell/csce311/csce311spring03.html

The URL for section 2 of CSCE 311 is at www.cse.sc.edu/~zheng2

The graduate assistant for both sections of CSCE 311 is Seang Chan Ryu, whose office is 1D49 Swearingen, 576-6355, and whose office hours are Tuesday and Thursday, 2pm-3pm.

---

Texts:

Other references:

Outline, Prerequisites, and Expectations:

To the best of our abilities, the two sections of CSCE 311 will be taught at the same pace and in very similar ways.

The Silberschatz et al. book will be the main text for the content of this course. The OSP book will be the reference for the programming assignments.

Prerequisites for this course are CSCE 212 and CSCE 245. Those courses themselves have prerequisites that become prerequisites for this course. This also includes an assumption that you are able to program. The department reserves the right to execute an administrative drop at any time during the semester for anyone found not to have the prerequisites.

All programming in this course will be done in C. If you are unsure of your ability to program in C, you might consider consulting one or more of the references listed above. The K and R book is The Book on the C language. Kochan is my personal preference for a book on C.

If you are knowledgeable only in C++ and are inexperienced in C you are expected to become sufficiently familiar with C to be able to succeed. This familiarization process is your responsibility.

You can also try the C self-tests one and two .

Tests and assignments

There will be one midterm and one final exam during the semester. The midterm will be on 19 Feb 2003, timed so that you can get back your exams just before the deadline to drop.

The final exam is scheduled for Saturday, 3 May 2003, at 2:00 pm.

Both the midterm and the final exam will be closed book exams.

The quiz/participation grades will be done as follows. You are expected to read the scheduled material prior to coming to class. You are expected to come to class on time. At random intervals, I will either assign short quizzes at the beginning of class or will call upon an individual. I will arrange the class roll so that everyone on the roll will be called upon at least once during the course of the semester. If I call upon you, and you are not there or are late for class that day, you will lose that fraction of the potential quiz/participation grade. A quiz will not be given to students who are not present at the time I begin to hand it out.

Assignment 1, due 29 January 2003: Questions 4.1, 4.5, 4.7

Assignment 2, due 5 February 2003: Questions 5.1, 5.2, and 5.6. In the first two, you must be reasonably specific and explain why your answer is correct, not just state what you claim is correct.

Assignment 3, due 17 March 2003: Questions 8.1, 8.2, 8.5, 8.8, and 8.10.

Assignment 4, due 26 Mar 2003: Questions 9.5, 9.8, 9.10, 9.12, and 9.16.

Assignment 5, due x x 2003:

Programming project 1 doc, pdf, due 17 February 2003.

Programming project 2 doc, pdf, due 17 March 2003.

Some help for project 2: program_hints, io.h, makefile, makefile_annotated, z.c, zz.c,

Programming project 3 doc, pdf, due 2 April 2003.

Programming project 4 doc, pdf, due 18 April 2003.

Programming project 5 doc, ps, pdf, due 30 April 2003.

Grading scheme

The final grade will be computed on the basis of the weighted average of the scores for

• quizzes and participation (5%),
• the midterm exam (25%),
• the homework assignments (15%),
• the programming assignments (30%),
• the final exam (25%).

The final grades will almost certainly be curved, but you should expect no lower a grade than you would receive under the usual 90/80/70/60/50 scheme.

Lecture notes, slides, and pointers

• Slides: Ch01 Ch02 Ch03 Ch04 Ch05 Ch06 Ch07 Ch08 Ch09 Ch10 Ch11 Ch12 Ch13 Ch14 Ch15 Ch16 Ch17 Ch18 Ch19 Ch20 Ch21 AppA
• Chapter 6 scheduling anomaly slides
• Notes 1: Postscript, pdf

Deadlines

Homework and programming assignments will have due dates and will be turned in at or by the beginning of the class period on the due date. Late assignments will not be accepted without prior arrangement to accommodate truly extraordinary circumstances.

Academic Honesty

Assignments and examination work are expected to be the sole effort of the student submitting the work. Students are expected to follow the Code of Student Academic Responsibility. Every instance of a suspected violation will be reported. Students found guilty of violations of the Code will be subject to academic penalities under the Code in addition to whatever disciplinary sanctions are applied.

Proper Use of Computing Resources

Students are expected to be aware of the university policy on use of computing resources, including the Student Guidelines for Responsible Computing, as well as the college and departmental policies on proper use of computing resources. Every instance of a suspected violation will be reported.

Spring 2003 CSCE 311: Operating Systems
Class Schedule, Reading Assignments, Projects

Last Update: 12/04/02