Introduction to Operating Systems
Dean Hougen, DEH 242, 405-325-3150, hougen@ou.edu
Mohammad Dibay Moghadam, DEH 210, m.dibay@ou.edu
Tuesday, Thursday 1:30-2:45, Felgar Hall 304
The primary means of transmitting class information to the students will be through announcements during class time and web pages. You are responsible for announcements made through either or both of these means. The URL for the course homepage is http://www.cs.ou.edu/~hougen/classes/Fall-2012/cs3113/ This page will contain links to the directory of class materials and announcements, and other important information. Some information may be posted through Desire2Learn.
Occasionally, urgent information may be sent via email. You must ensure that the email address the University has on file for you is valid and is monitored by you. A test of the email addresses provided by the University will be made during the second week of class. You are responsible for notifying the instructor if you do not receive this test email.
The best way for students to communicate with the teaching staff is to come to scheduled office hours. If you cannot attend office hours in person, phone calls can be accepted but students present in the office will get priority. Email can also be used but a quick or detailed personal response is unlikely as we get a lot of email and responding to email can be very time consuming. Students should use the email addresses listed above. Again, note that we get a lot of email. Do not expect a reply in minutes; one or two days is more likely in most cases. If you have not heard back within five days, please resend your message, if it is still relevant.
One way for students to communicate with one another is through the Desire2Learn web site for the class.
The prerequisites for this course are CS 2413 - Data Structures and CS 2613 - Computer Organization (or ECE 3223). (If you have not taken these courses, you will need instructor permission to take 3113.) You are expected to have a working knowledge of C and C++, including a familiarity with its basic data types and control structures, and an understanding of basic computer organization. This course will introduce students to operating systems theory and cover the principles of systems programming. For topics covered, see the schedule.
An ability to design, implement, and evaluate a computer-based system, process, component, or program to meet desired needs.
An understanding of security issues and responsibilities.
An ability to apply mathematical foundations, algorithmic principles, and computer science theory in the modeling and design of computer-based systems in a way that demonstrates comprehension of the tradeoffs involved in design choices.
All students in this class should have a CS account. This will be used for writing programs and sending and receiving materials electronically. All code written for this course MUST run using the compilers or interpreters that will be specified for the assignments. You may do your development work on whatever system you choose but it is your responsibility to ensure that your code runs on the school systems.
The graded assignments and their contribution to a student's grade are given in the table below. (Subject to change.)
|
|
|
|
|
Project 2 Project 3 Project 4 Exam 1 Exam 2 Final Exam |
Processes File System IPC First 1/3 Second 1/3 Last 1/3 |
15% 15% 15% 15% 15% 15% |
All exams in this course are to be done ALONE; the work submitted by a student MUST be the student's own. Group work is REQUIRED for the projects. Students may work in groups of two or more. The more people in the group, the harsher the grading will be.
You are responsible for the material covered during the lecture sessions, whether or not it is also found in your textbooks or other assigned reading materials. Similarly, you are responsible for the material found in your textbooks and other assigned reading materials, whether or not it is also covered during the lecture sessions. In other words, you are responsible for the UNION of these sources of knowledge, as depicted by the shaded region of the Venn diagram below, not merely their intersection.
You may write your programs from scratch or may start from programs for which the source code is freely available on the web or through other sources (such as friends or student organizations). If you do not start from scratch, you must give a complete and accurate accounting of where all of your code came from and indicate which parts are original, which are changed, and which you got from which other source. Failure to give credit where credit is due is academic fraud and will be dealt with accordingly.
All work in projects must properly cite sources. For example, if you quote a source in your project, you must include the quotation in quotation marks and clearly indicate the source of the quotation.
You will be turning in electronic and paper copies of all assignments. Electronic copies of assignments are due 1/2 hour before class time (at 1:00 pm) on the due date. Paper copies of assignments are due at the beginning of lecture (at 1:30 pm) on the due date. Late assignments will be penalized 20% per day late. (All parts of days will be rounded up.) After five days, you will not be able to turn in that assignment for credit. If you are worried about turning in the assignment late and losing points, turn in the assignment ahead of time. The paper copy may be submitted in class or turned in during office hours or by slipping it under my office door.
Each group will turn in ONE version of each project (one paper copy and one electronic copy of the same project). The version submitted will be mutually agreed upon by the group members. The scores assigned to the members of the group will reflect their contributions to the version of the project submitted. Note that students are required to contribute equally to each project to the extent possible, so the scores assigned to each group member will typically all be the same. However, if all members of the group do not contribute equally to a project for some reason, the scores assigned to group members may be quite different.
Note that the policy of having each group submit one version of each project for grading is in stark contrast to having each member of each group submit his or her own version of the project for individual grading. As stated above, group work is REQUIRED for the projects. Working as a group does not mean having a chat now and then with another class member then going off to work on your own on the project. It means actively working together with the other members of your group to create a single product (a joint creation).
All exams will be open book/open notes. NO electronic devices will be permitted in the testing area.
Copying another's work, or possession of electronic computing or communication devices in the testing area, is cheating and grounds for penalties in accordance with school policies.
Please see OU’s academic integrity website.
Any student with a disability should contact the instructor so that reasonable accommodations may be made for that student.
Students who do not attend the first week of class may be dropped from the course to make room for additional students to enroll.
It is the policy of the University to excuse the absences of students that result from religious observances and to provide without penalty for the rescheduling of examinations and additional required class work that may fall on religious holidays.
Students should also read the related documents on Replacement Assignments or Extensions and Discussions of Scores and Grades.