Overview
|
Course Summary
Examines recent developments in operating systems. Also covers multiprogramming, parallel programming, time sharing, scheduling and resource allocation, and selected topics.
A detailed list of a lecture by lecture contents, assignments, and due dates (subject to change as semester evolves) is available on the course schedule.
Required Textbook
The course readings will come from the following required textbook (available online):
Additional paper readings will be assigned on the course schedule web page.
Grading
The course will be graded on programming projects, quizzes, paper reviews, exams, and class participation in the following proportions:
| 20% | Programming Projects (3) |
| 10% | Quizzes (4) |
| 10% | Paper Reviews |
| 25% | Midterm Exam |
| 30% | Final Exam |
| 5% | Class Participation |
Projects
During this course, students perform programming projects examining multiple aspects of operating systems. The projects will require deep knowledge of the C programming language and runtime. Knowledge of the debugger will be very helpful. The projects will be performed in teams of two - same team for each project.
Grades will be based on the factors specific to each project.
Quizzes
To prepare for the exams, there will be four quizzes given at the test center. There will be 3-4 questions per quiz.
Reviews
Students will be produce one-page reviews of the research papers during the course. There will be up to six reviews during the quarter. We will provide information on the format of reviews.
Exams
This course will have midterm and final exams. The midterm will be given in class. The final exam will be comprehensive.
Class Participation
Class participation includes participation in lectures. Lectures are augmented by various readings, which are expected to be read prior to class (note: reading materials twice - once before and once after the lecture worked for my comprehension). During the lecture, we will discuss the readings, and students are required to participate in discussions during each lecture. Ultimately, the students' ability to exhibit comprehension of readings is essential to a good grade on exams.
Lateness Policy
You have 4 days of slack from deadlines for homeworks or projects for the semester. There is a 2% bonus (total course points) if you do not use any - all or nothing. No further credit for late projects, so use these days judiciously.
Course Outline
A rough outline of the class is as follows:
|
Academic Integrity Policy
Academic integrity is the pursuit of scholarly activity in an open, honest and responsible manner. Academic integrity is a basic guiding principle for all academic activity at the University of California, and all members of the University community are expected to act in accordance with this principle. Consistent with this expectation, all course activities should be performed in compliance with the University’s Academic Integrity Polices & Procedures.
The course projects are to be carried out individually (i.e., within the project team). Students are explicitly not allowed to share information, source code, or even discuss the contents of the projects. Any violation of this policy will be considered cheating and will result in the student receiving an 'F' grade for the project and a full letter grade off the final grade for the course. Students with more than one violation may face stronger penalties per the university policy.
Students are forbidden from copying code, makefiles, or any other material from the Internet (such as publicly available Github repos). Plagiarism will be strictly enforced through in-depth reviews of your submissions. Any violation in the letter or spirit of this policy will also be considered cheating, and handled as described above. Note that any publication of the assignments (e.g., via github or other system) is considered a violation of the above policy.
