Goals This course introduces basic principles of operating system design. The course has the following goals:

• Introduce basic operating system concepts such as processes, input/output, memory mangement, file systems, and mechanisms for control and abstraction.
• Introduce fundamental operating system language paradigms, including procedural (block-structured), object-oriented, functional, and relational paradigms.
• Provide practical exposure to the operating system subsystems in reading assignments and programming exercises.
• Give students experience thinking and reasoning about why existing operating systems are designed the way they are and how they might be improved.
• Demonstrate how the implementation of operating systems influences their design and use.
• Provide the necessary concepts and implementaiton idioms so that learning a new operating system should be relatively easy for students completing the course.

This course will require three distinct types of learning from the students:

• Students will be required to read and assimilate the material presented in the textbooks and the material covered in class.
• Programming assignments will require creative synthesis of the topics discussed in lecture and will complement the textbook readings and lectures.
• Finally, in written homeworks and on exams, students will be asked to reason about what they have learned. For example, a homework assignment might ask why the Unix OS contains  a particular feature. This critical evaluation requires that you offer your own understanding of the significance of what you have learned.

Academic Integrity Students are encouraged to discuss the materials, homework, and projects together. However, all written assignments and programs must be done individually or in assigned groups. Academic dishonesty includes, but is not limited to: plagiarism, cheating in exams, unauthorized collaboration and falsifying academic records. Violation of any of these may result in a grade penalty on assignments, an "F" in the course, dismissal from an academic unit, revocation of admission, suspension from the University , etc.

Communication The major forms of communication between students and instructors in this course will be office hours, e-mail, and the class Web page. The mailing list cgantz@regis.edu will be for announcements made by the instructor, TA's,  and for any discussion related to the class. The Web page for the class is http://www.cs.du.edu/~cag/courses/CS/Regis/cs430. It will contain most information about the course including a syllabus, all assignments and grades.

Office hours provide an important opportunity to interact with the instructor and TA (if applicable) in a one-on-one setting. Because the class will be large, it may be difficult to follow up on all questions asked by students in class. Office hours provide an ideal, and often underutilized, setting for in-depth discussion of questions you have about the course material.

If you need to see the instructor or TA and cannot make it to office hours, please request an appointment by e-mail (preferred) or phone.

The course newsgroups and the class Web page provide a mechanism whereby we can communicate important information to you about homework and assignments outside the class hours. To keep up with current course information, we ask that you check the Web page and newsgroups approximately once per day. If you have a question involving grades or some matter you do not want widely distributed, send it to us by e-mail. Questions about assignments mailed or posted less than 24 hours before the assignment is due will probably not be answered. Keeping this in mind, please start working on the assignments as early as you can. Questions sent by e-mail that are of general interest to the class may be posted to the newsgroup with the response. If you do not want a question posted in this manner, please indicate this prominently in your message.

Grading: Exams, Programs, and Assignments

In general, you can discuss homework and programming assignment problems with each other, but copying is considered cheating. In other words, talk about the problems with each other as much as you like, but each person is responsible for writing and debugging their own program or problem solution.

Any time text is copied verbatim from another source I expect the source to be correctly referenced. Verbatim copying from unaccredited sources is plagiarism. If a case of plagiarism or other form of academic dishonesty is discovered, the guilty parties will receive a 0 score for the assignment and the matter will be referred to the Dean's office.

Your final grade for the course will be determined from the following sources:

• Exams -- all exams will be in-class, closed-book exams. Makeup exams will not be given unless there are circumstances clearly beyond your control (accident, illness, etc.). Exams will cover material from the textbook, homework and lectures.
• Mid-term exam -- 25%

One mid-term will be given during class (1 hour and 30 minutes). Tentatively, this exams is scheduled for February 13th. Please do not count on this date, however, as they are subject to change. The exam will focus to a greater degree on material covered since the time of the initial class.
• Final exam -- 25%

1 hour and 50 minutes, Wednesday November 18th, 5:00-6:50pm (Rm 105 Olin Hall).
• Programming Assignments -- 20%

There will be approximately 4-6 programming assignments(PA). A new PA will be assigned roughly every two to three weeks.

PAs will be graded on a scale of 1--100. Your submitted code must compile and execute to be considered for any points. All programming assignments must be submitted electronically.

All programming assignments will have a precise due date and time. Late programming assignments will be accepted up to 24 hours after the time they are due with a 20% penalty. No submissions will be accepted more than 24 hours after they are due.

• Homeworks -- 30%

Homeworks are designed to assist you in understanding the material presented in the lectures and texts, and to prepare for the exams.

Homeworks will be due at the beginning of class on the day they are due. Because solutions to the assignments will be made available after the homework is due and we may discuss them in class, late homeworks will not be accepted. At all.