CIS 345 Operating Systems Principles CIS 545 Architecture & Operating Systems Instructor: Timothy Arndt Office location: BU 331 Office Phone: (216) 687-4779 Office hours: MW 2:00pm-3pm, 6pm-7pm E-Mail: email@example.com Home Page: http://cis.csuohio.edu/~arndt Meeting time : MW 8pm-9:50pm Meeting place: BU 106 Credit: 4 credits Prerequisite: CIS 265/506 and CIS 340/540 Drop Dates Friday September 5; Friday October 31 (with W on transcript) Course Description Basic principles of modern operating systems. Processes and threads, memory management, file systems, security, deadlocks, etc. Examination of implementation in such operating systems as Linux and Windows. Programming assignments in C/Linux. Laboratory BU 004 is the laboratory assigned for this class. Textbooks Required: Modern Operating Systems, Tanenbaum, Pearson Prentice-Hall, 2nd or 3rd edition. Linux for Programmers and Users, Glass and Ables, Pearson Prentice-Hall, 2006. Grading Programs and other assignments 40%; Exams (3) 60%;. I reserve the right to change the weighting of assignments. The following grading scale will be used to calculate final grades (subject to curving if class grades on exams are substantially below expected): CIS 345 Total percentage earned Total percentage earned 93 - 100% A 80 - 82% B- 90 - 92% A- 77 – 79% C+ 87 - 89% B+ 70 – 76% C 83 - 86% B 60 – 69% D 59% and under F CIS 545 Total percentage earned Total percentage earned 93 - 100% A 80 - 82% B- 90 - 92% A- 70 – 79% C 87 - 89% B+ 69% and under F 83 - 86% B Grading Criteria No extra credit will be given. Students registered for CIS 545 will be asked to complete additional assignments and/or questions on exams. For programming assignments, in order to receive a grade of 100, the program must be extensively commented, well formatted, and must meet all program requirements as stated in the assignment. A document containing (as a minimum) the name of the programmer, complete instructions for running the program (including any assumptions about the test environment), any limitations of the program, and a test procedure. This document must be formatted as text (not Word) unless explicit permission is given. Any test data needed for testing (e.g. media files) must be provided as well. Deductions will be made for violations of any of the above criteria. A program that does not run at all will not receive a grade above 70. A program that always fails to produce correct results will not receive a grade above 80. Programs that work on some (but not all) test cases (both those provided by the student and those provided by the instructor) will have a maximum grade of between 81 and 95, depending on the number of cases in which the program produces incorrect results. For exams, problems will be multiple choice/true false/short answer as well as problem solving and descriptive problems. For problem solving type questions, mistakes in arithmetic will result in only small deductions while failure to use the correct technique will result in a larger deduction. Any assumptions that you make in answering these types of questions should be written as part of the answer to the question. A small deduction will be made if your answer is very hard to read, so be neat. Illegible answers will receive no credit. For descriptive type questions, if you describe some other entity rather than one asked for, you will receive no credit. Course policy (1) Class participation and preparation Class participation and regular attendance are expected. If a student misses a class, the student is responsible for bringing herself/himself up-to-date on class material and assignments. All students are expected to read the assigned chapters prior to coming to class. All cell phones and pagers must be turned off during class. Notebook computers may be used only for taking notes and for no other purpose. Abuse of this privilege will cause all students to lose the privilege. Chatting is not allowed during class periods. If you have a question about material being presented in class, please ask the instructor. (2) Exams Exams will be based on the combination of: material covered in lectures, the assigned reading from the textbooks, material covered in the notes, and lab practice. All exams are closed books and closed notes. No makeup exams will be given! (3) Homework assignments All homework assignments are due at the beginning of class on the specified date. An assignment turned in one day late will get a 10% penalty, two days late will get a 20% penalty, etc. Assignments turned in after the beginning of class on the due date will be counted as one day late and will receive a 10% penalty. All assignments must be individually and independently completed. Should two or more students turn in substantially the same solution or program, in the judgment of the instructor, the solution will be considered a group effort. All involved in a group effort homework will receive a zero grade for that assignment. No late assignment will be accepted after the assignment is graded and returned. See the CSU student conduct code for further information. (5) Class cancellation: If I need to cancel class for any reason, I will try to put an announcement on the course web page as early as possible. (6) Grading mistakes All grading mistakes must be corrected within one week of the return of the assignment or quiz. No exceptions. It is your responsibility to verify that your exams/assignments have been graded correctly. Tentative Course Schedule Week Topics covered Reading (Tanenbaum 3rd edition) Week 1 Course introduction; Introduction to Lab; Linux Chapter 1 review. Week 2 Linux review. Monday September 1, Labor Day, no class. Week 3 Processes and threads. Chapter 2 Week 4 Memory management. Chapter 3 Week 5 File systems Chapter 4 Week 6 Exam 1. Input/Output Chapter 5 Week 7 Deadlocks Chapter 6 Week 8 Multimedia Operating Systems. Monday October Chapter 7 13, Columbus Day, no class. Week 9 Multiple Processor Systems. Chapter 8 Week Security Chapter 9 10 Week Security (ctd.) Exam #2 11 Week Case study: Linux Chapter 10 12 Week Case study: Windows Chapter 11 13 Week Case study: Symbian OS Chapter 12 14 Week Operating System Design Chapter 13 15 Final Exam Monday December 8, 8pm-10pm Student Conduct: Students are expected to do their own work. Academic misconduct, student misconduct, cheating and plagiarism will not be tolerated. Violations will be subject to disciplinary action as specified in the CSU Student Conduct Code. A copy can be obtained on the web page at: http://www.csuohio.edu/student-life/student_handbook/index.html or by contacting Valerie Hinton Hannah, Judicial Affairs Officer in the Department of Student Life.
Pages to are hidden for
"Graduate Seminar in Computer and Information Science"Please download to view full document