Winthrop University College of Business Administration CSCI 411 - Operating Systems Syllabus Spring 2009 1. Texts: 1. Schaum's Outline of Operating Systems, Harris, McGraw-Hill, 2001, ISBN 0071364358 / 9780071364355 References: Available through the class website at http://cba.winthrop.edu/fosterk/CSCI411/. 2. Prerequisites: 1. A course in computer organization and architecture (CSCI 211) 2. Competency in programming in a high level language, especially C++. 3. Competency in using the Linux systems (CSCI 208 lab) 4. A satisfactory background in mathematics (MATH 201, 261) 3. Instructor: Dr. Kent E. Foster Office: Thurmond 324 Hours: Class: MW 3:30 - 4:45 Office: MW 1:30 – 3:30 (before class) Website: http://cba.winthrop.edu/fosterk/CSCI411/ 4. Schedule (tentative) Week Date Topic (Very Tentative !!!) 1 1/12,14 Introduction; Computer System Review: History of Operating Systems. 2 1/19 MLK Day – no class 1/22 Operating system overview. 3 1/26,28 Processes, interrupts and system calls 4 2/2,4 continued 5 2/9 Test # 1, Monday, February 9th. 2/11 Other process issues: threads, IPC’s, scheduling 6 2/16,18 Threads 7 2/23,25 Interprocess communications and controlling concurrency 8 3/2,4 Concurrency: mutual exclusion and synchronization 9 3/9,11 Concurrency continued Concurrency: deadlock 10 3/15-21 Spring break 11 3/23 3/25 Test # 2, Monday, March 25th. 12 4/30,1 Concurrency: deadlock 13 4/6,8 Memory management 14 4/13,15 Processor scheduling 15 4/20 4/22 Last Class 16 4/28 Study Day 17 5/6 Final exam, 3:00 Friday May 1stCSCI 411 Page 2 5. Assignments: There will be a number of assignments during the semester. Each assignment is due the next class. No assignments will be accepted after the due date. Assignments are to be done by you alone, unless specified otherwise. Duplications or near duplications will be treated as plagiarism. 6. Attendance: Attendance will be taken daily. The attendance policy in this course is that you are completely responsible for everything that occurs in class, regardless of your attendance. It should be understood by you that you will not obtain a satisfactory grade in the course if you do not attend most of the classes. You are not expected to be absent more than a few classes if you expect to earn a C or better. 7. Tests: You are expected to take tests at the scheduled times. If you cannot take a test at the scheduled time, then you must request an alternate time. The instructor will judge the validity of the request, and either disallow it or assign another time. 8. Course grade: Your course grade will be based on the following weights (tentative): Test 1 30% Test 2 30% Final Exam 30% Assignments 10% with at least 70% average for all of the assignments to get a C or better in the course. The course average will be computed by a formula that results in an average of 0 to 100 points. The course grade will be determined by this average according to the table: Grading Scale. Your course grade will be assigned according to the following grading scale. >=91 89-90 87-88 81-86 79-80 77-78 71-76 69-70 67-68 61-66 59-60 <=58 A A- B+ B B- C+ C C- D+ D D- F Catalog Description A survey of the function of an operating system and the concepts necessary for the design of an operating system. Students are required to program a part of a subsystem. Objectives Learn about the following concepts and issues in operating system design: 1. System structures 2. Processes 3. CPU scheduling 4. Process synchronization 5. Memory management 6. Virtual memory 7. File systems and I/O systems Revised January 8,