COP5615 Syllabus Spring 2007 Title: Operating System Principles Time: 8th and 9th periods (3:00 - 4:55 pm) on Tuesday, 9th period (4:05 - 4:55 pm) on Thursday Classroom: CSE-107 Instructor: Professor Richard Newman (nemo@cise.ufl.edu) 346 CSE, (352) 392-1488 TAs: Zhan Zhang (zzhan@cise.ufl.edu), CSE-E309; 352-392-5770 Textbooks: Required: Distributed Operating Systems and Algorithms, Chow & Johnson, Addison/Wesley Reference: Distributed Systems: Principles and Paradigms, Tanenbaum & Steen, Prentice Hall Class websites: www.cise.ufl.edu/class/cop5615sp07 www.cise.ufl.edu/~nemo/cop5615/ Office hours: Newman: W 3:00-4:00 pm, R 1:30-11:30 am and 2:00 pm - 3:00 pm, and by appointment Zhang: TBA Course objective: To study design principles and computing paradigms for modern distributed systems and their underlying distributed and network operating systems. Topic Outline: 1. Fundamental OS concepts 1 week 2. Network and Distributed OS 2 weeks 3. Threads and client/server models 1 week 4. Group communication and naming 3 weeks 5. Distributed Processing 2 weeks 6. Distributed File Systems 2 weeks 7. Distributed Shared Memory 2 weeks 8. Security 2 weeks 9. Review 1 week Grading: 1. Examinations (8th and 15th weeks) 30% and 30% 2. Projects (3) 30% (we will use Java and Unix) 3. Quizzes (10) 10% Homeworks will not be graded, but will be assigned for your benefit. There will be one quiz per week to test your preparation level. Exam policy: Exams will be closed book, closed notes, but you will be permitted one 8.5"x11" crib sheet (two sides) per exam. Academic Honesty: * UF Honor Code: We, the members of the University of Florida community, pledge to hold ourselves and our peers to the highest standards of honesty and integrity. * Plagiarism will not be tolerated. ADA: Students requesting classroom accommodation must first register with the Dean of Students Office. The Dean of Students Office will provide documentation to the student who must then provide this documentation to the Instructor when requesting accommodation. General Policies Attendance: Attendance is required, but tapes are available for viewing through EDGE. Late arrivals are expected to enter discretely and avoid interfering with the cameras. Cell phones and pagers must be silent during class. Communication: Students are required to check the class web pages at least three times a week (MWF) for announcements/updates. While we will not check that you do this, the web pages are the authoritative source of information for the class, and to obtain this information in a timely manner, you will want to visit often. Questions: Questions are encouraged - raise your hand to be recognized. Try to formulate the question before asking it, and wait to see if it is answered in a few minutes so we can maintain flow. Lengthy discussions will be deferred to office hours. Program Grading: Programs will be graded based on documentation, good programming practice, functionality, and performance. You must provide design and test documentation and interface specifications for your components, document your programs and give test results. Collaborative work: you may work on registered teams for programming, but the exams must be your own work. You are encouraged to discuss operating systems outside of class with your fellow students. Late submissions: Projects will be due at 4:59 pm on the date on which they are due. Late submissions will be discounted 10% per day for up to five days. Regrade requests: we grade carefully the first time, but if you find an error in grading or believe that you deserve more credit for an answer, you must submit a regrade request via email to the TAs and to me justifying your request within two weeks from the time that the graded material was returned to the class. The email must include the specific part(s) that you desire to have regraded and why you believe your answer deserves more credit.