Section 2 - 2:00 pm - 3:15 pm, Tuesdays and Thursdays, 103 LOV

Section 3 - 8:00 am - 9:15 am, Tuesdays and Thursdays, 103 LOV

Instructor Mr. Jeff Bauer, 120 MCH,

644-4290 (office), jtbauer@cs.fsu.edu (e-mail)

Office hours Monday and Wednesday from 2-4 PM and by appointment.

Grader Mr. Huilong Wu, harriswu@cs.fsu.edu

Textbook Operating Systems: A Design-Oriented Approach, by Charles Crowley

You will be expected to read most of this. It will be supplemented by the UNIX on-line manual pages (man), and by notes which will be provided as handouts and by electronic mail.

Class Home Page http://www.cs.fsu.edu/~jtbauer/cop4610

You are expected to learn to:

• Explain and use the concepts and terminology of operating systems
• Explain and apply the key implementation techniques of operating systems, including:
• Concurrent programming
• Resource management
• Virtual memory
• File systems
• Use the UNIX operating system, and understand principles of its implementation
• Read and write operating-system-like code, written in C, C++ and Java

A detailed schedule, showing tentative dates of reading assignments, quizzes, and programming assignments will be given on a separate handout.

Assignments & Grading Homework will be assigned on occasion from the textbook or via handouts. In addition, there will be several programming assignments, using the Java language and the UNIX operating system.

All assignments must be sent by electronic mail to cop4610@cs.fsu.edu by 4 PM on the due date. For your insurance against e-mail problems, it is strongly recommended that you keep an email copy.

The programming assignments will (tentatively) consist of five programming projects using SOS, an operating system simulator written in Java.

Programs will be graded according to the following guidelines:

• 0 (F) program not turned in, copied, or too incomplete to determine whether principles behind the assignment were understood.
• 60- 69 (D- to D+) program turned in and indicates some understanding of principles behind assignment, but does not work correctly on public test data supplied by the instructor.
• 70- 79 (C- to C+) program works correctly on public test data, is based on correct algorithms, and shows understanding of most of the principles behind the assignment.
• 80- 89 (B- to B+) program works correctly on public test data as well as other data that may be used by the instructor in grading, and indicates understanding of all the principles behind the assignment.
• 90-100 (A- to A+) program is correct and is also well written, in an economical clear style. (This includes use of economical algorithms and data structures, and adequate documentation explaining the data structures used and the effect of each subprogram in terms of its parameters and any global variables it uses.)

Within these bands, matters such as style and documentation will be reflected. Programs that go beyond the assignment in some respect may occasionally be forgiven a few errors without lowering of grade, but students are cautioned against writing overly ambitious programs, since this grading scheme is harsh on non-working programs.

Programming assignments are to be done individually, unless the assignment specifies otherwise. It is a violation of the Academic Honor Code to take credit for code written by another person. It is also a violation to assist another person in violating the Code. (See the FSU Student Handbook for penalties for violations of the Honor Code.)

Short quizzes will be used to check up on reading and programming assignments. Missed quizzes may not be made up, but may be dropped from the final grade for verifiable excused absences. Homework assignments will also be used to encourage reading.

There will be one midterm (E₁) and one final exam (E₂). Make-up exams will not be given without prior consent of the instructor.

The final grade will be computed as follows:

H = (H₁ + ... + H_m-1 + H_m) / m Homework average

P = (H + P₁ + ... + P_n) / (n + 1) Program average

Q = (Q₁ + Q₂ + ... + Q_k) / k Quiz average

E = max {(Q+E₁+2*E₂)/4, (E₁+2*E₂)/3, E₂} Exam average

if (P < 70) or (E < 70) then

G = min{P,E}

else

G =(E+P)/2 Final grade

This policy rewards those who do well with both programming assignments and traditional classroom testing situations.

The final grade may be raised for exceptional class participation or marked improvement over the term, or in cases where the formula above appears skewed by a few exceptionally low grades or work missed for verifiable excusable reasons.

Attendance Attendance at all class meetings is expected. Although it will not be recorded, attendance and participation will have a strong indirect effect on your grade for the course. You are responsible for all information explained in class, some of which may not be available in written form. I will not feel obligated to repeat announcements of homework, future quizzes, exams, assignments, schedule changes, or hints on programming assignments. If you are forced to miss a class, it is also your responsibility to get good class notes from a friend and check with me for handouts. I will use email extensively to give out assignments and general class information.

Communication You are required to check your electronic mail frequently for information about this course, as well as the class home page. The class home page will contain a copy of the course gradebook, referenced by the last four digits of your Social Security Number. Let me know if you would rather use some other pseudonym for the on-line gradebook or if you would prefer that your grades not be posted at all on the web site. You are also encouraged to use email to ask questions and report problems.

Please advise me at your earliest convenience (minimum 1 week) if you have a disability that will require a reasonable accomodation for the successful completion of this course.

If you are experiencing difficulty or are concerned about your progress, please speak with me immediately.