David E. Goldschmidt, Ph.D.

» show syllabus

« hide syllabus

course description

CSCI-4210: Discussion of various aspects of computer operating systems design and implementation. Topics include I/O programming, concurrent processes and synchronization problems, process management and scheduling of processes, virtual memory management, device management, file systems, deadlock problems, system calls, and interprocess communication. Programming projects are required.
Prerequisites: CSCI-2300 (Introduction to Algorithms), CSCI-2500 (Computer Organization).

CSCI-6140: Topics include analysis of multiprogramming systems, virtual memory, computer system performance, and queuing theory. The course also discusses tools for synchronization of parallel programs and algorithms for mutual exclusion.
Prerequisites: CSCI-4210 (Operating Systems) or permission of instructor.

learning outcomes

Upon successful completion of this course, students will:

1. Demonstrate the ability to compare, contrast, and apply concepts of both classic and modern operating systems.
2. Analyze operating systems by designing and implementing both analytical and simulation models, the latter via a programming language.
3. Implement specific operating system constructs in C on Unix platforms to create real-world systems-level programs and applications.

course web site

http://www.cs.rpi.edu/~goldsd/fall2014-csci4210.php

required textbook

none

recommended textbooks

Principles of Modern Operating Systems, 2nd ed.
by Garrido, Schlesinger, Hoganson
ISBN 978-1-4496-2634-1

Modern Operating Systems, 3rd ed.
by Tanenbaum
ISBN 987-0-13-601919-0

The C Programming Language, 2nd ed.
by Kernighan and Ritchie
ISBN 0-13-110362-8

required software

We will use a variety of programming languages, all of which should have compilers or interpreters available for free download from the Web. We will also explore a variety of platforms, including Windows, Linux, and Mac. Expect to learn and understand programs in C, C++, Java, and/or Python.

To study operating system concepts, we will focus on C on Ubuntu. A specific version of Ubuntu will be required. All assignments must execute successfully on this Ubuntu version. It is not a valid excuse to state that your code ran successfully on "your" platform.

exams

There will be a midterm exam and a final exam. You may bring one double-sided crib sheet to the midterm exam and two double-sided crib sheets to the final exam.

Midterm exams will be handed back and reviewed in class. Final exams will not be handed back or available for review.

grading criteria

• Homeworks (4) ..... 40%
• Midterm Exam ..... 30%
• Final Exam ..... 30%

announcements

Announcements and other course-related communication will be sent via email to your RPI (@rpi.edu) email. Therefore, please be sure to check your RPI email at least once a day.

grading policies

Grades will be provided throughout the semester to provide an ongoing assessment of your progress. All grades for individual and team-based (if any) assignments are determined by the professor and the TAs.

Students may appeal a grade by contacting the TA who graded it. If necessary, the next step is to contact the professor. A grade can only be appealed within five days of the grade being made available online and announced (via email or in class).

Paper assignments (e.g., paper homeworks, exams) will be handed back and reviewed in class. Such assignments will also be made available outside my office (Lally 209) for a minimum of five days after being handed back in class (then these graded assignments might be recycled).

Final exams will not be handed back or available for review. To ensure no mistakes are made during the grading process, grades for final exams are determined via multiple passes, first by the TAs, then by me.

assignments

Homework assignments are due on the due dates and times specified.

Electronic submissions are due by unknown. Paper homework submissions are due at the beginning of class.

Because it is vital that students apply what they learn, expect frequent homework assignments, projects, and other such exercises. Further, numerous assignments will likely be assigned and reviewed in class, though not all will be collected for credit. Regardless, doing all such assignments will greatly improve your understanding of the course material and therefore your grades on homeworks, projects, and exams.

Instructions for submitting assignments (both on time and late) will be made available for each assignment.

attendance & classroom policies

Please attend class and be prepared to participate in class discussions.

Turn off phones and other non-classroom electronic devices before class begins. Shut your laptops unless you are actively using them to take notes or follow along in class.

Team-based work (if any) requires full cooperation and coordination from each team member. Lack of participation is detrimental and grades suffer accordingly.

students with special needs

Federal law requires all colleges and universities to provide specified types of assistance to students with disabilities. If you have such special assistance, please obtain an authorizing memo from Disability Services for Students by contacting Mark Smith, Dean of Students, in the Dean of Students Office (x6266). Information about a student's special needs will be treated as confidential.

Please submit a copy of your authorizing memo to your professor well in advance of any affected exam or assignment. Failure to do so may result in a lack of special accommodations.

academic integrity

From The Rensselaer Handbook of Student Rights and Responsibilities: Intellectual integrity and credibility are the foundation of all academic work. A violation of Academic Integrity policy is, by definition, considered a flagrant offense to the educational process. It is taken seriously by students, faculty, and Rensselaer and will be addressed in an effective manner.

Individual assignments in this course must be the sole work of each individual student, though your professor, TAs, and fellow classmates may help in figuring out how to solve the given problems. For team-based work (if any), work must be the sole work of the individual team members, though your professor, TAs, and fellow classmates may help in figuring out how to solve the given problems.

You must write your own code. Copying of code from others is strictly forbidden and will not be tolerated. You may certainly use code and examples from the course materials.

Homeworks, projects, and exams in this course must be the sole work of each individual student.

If found in violation of the academic dishonesty policy, you may be subject to three types of penalties: (1) the instructor administers an academic (grade) penalty; (2) the student may be subject to the procedures and penalties of the student judicial system outlined in The Rensselaer Handbook of Student Rights and Responsibilities; and/or (3) the incident is reported to the Head of the Department of Computer Science. Cheating may cause you to be ineligible to mentor for the department, participate in various departmental organizations, etc.