CIS 370: Design of Operating Systems, Fall 2009

Home    Lectures  Survey  Announcements

Instructor Information

Instructor: Vinod M. Vokkarane

Office: Dion 307A

Office Hours: Tue and Thu 2:30 - 4:30pm; By appointment: Fri 2:00-3:00pm

Phone: (508) 910-6692

Email: vvokkarane at umassd.edu

Homepage: www.cis.umassd.edu/~vvokkarane

Teaching Assistant, Grader, and Tutor Information

Name: Rajesh Bikram

Email: rrc@umassd.edu
Location: Dion 305
Website: http://www.cis.umassd.edu/~rrc/370/
Office Hours: Tuesday and Thursday 2-3 PM

Lecture Meeting

Tue and Thu 11:00-12:15pm, DION 101

Lab Hours

Section 01: Thu 3:30-5:30pm, DION 305

Section 02: Tue 3:30-5:30pm, DION 305

Prerequisites

C or better in CIS 272

C or better in CIS 273

Ability to program in C and familiarity with UNIX

Course Textbooks

Operating System Concepts, 8e Binder Ready Version, Silberschatz, Galvin and Gagne, J Wiley Publishing, ISBN 9780470279939

Unix System Programming, Haviland and Gray, Prentice Hall

Course Homepage

www.cis.umassd.edu/~vvokkarane/courses/cis370/f09

Course Description

Principles of modern operating systems and their design. Scientific principles and engineering rules of operating systems are explored. Process and storage management subsystems are analyzed in detail. Protection and security are taken into account in design. An introduction to distributed operating systems is also presented. This is a design and project based course with a laboratory component.

Course Goals

Course Outcomes

Having successfully completed this course, the student will be able to:

Course Outline

Weeks

Chapter

Part 1: Overview

1-2

1. Introduction

1

2. Operating-System Structures

Part 2: Process Management

1

3. Processes

1

4. Threads

1-2

5. CPU Scheduling

1-2

6. Process Synchronization

1

7. Deadlocks

Part 3: Memory Management

1

8. Main Memory

1-2

9. Virtual Memory

Part 3: Storage Management

1

10. File-System Interface

1

13. I/O Systems

Part 5: Protection and Security

1/2

14. Protection

1/2

15. Security

Part 8: Case Studies

1-2

The Linux System, Windows XP, BSD UNIX, The Mach System, Windows 2000

Important Dates and Grading

The tentative examination schedule is as follows: (closed book, closed notes, in class)

Midterm Exam 1: 11:00-12:15pm, Thursday, October 8, 2009
Midterm Exam 2: 11:00-12:15pm, Tuesday, November 10, 2009
Final Exam: 11:30am - 2:30pm, Friday, December 18, 2009

Your numerical scores will be based upon the following contributions:

Assignments (HW, projects)
30%
Quizzes (class participation)
10%
Labs
10%
Paper
10%
Midterm exams (2)
20%
Final exam (comprehensive)
20%

90-100
A- , A , A+
80-89
B- , B , B+
70-79
C- , C , C+
60-69
D- , D , D+
Below 60

F

Important Dates

n
Wednesday, September 9  - Last day to Add/Drop
Tuesday, October 13         - Follow Monday's schedule (No Class)
Thursday, November 12    - Last day to withdraw from a class
Tuesday, December 15      - Fall classes end

Course Requirements

·  For this course, regular attendance is necessary for you to achieve the necessary progress needed to learn the course concepts. Attendance will be taken at each class. You must give me, in advance, a legitimate-written excuse for missing any class. Consistent-unexcused failure to attend the class could result in getting a grade of “F”.

·  You are responsible for all announcements and for all material presented in the lecture sessions. In this course, students will have the opportunity to access its material through the course web site. You should be prepared to access the site regularly in order to access the course material and to check any announcements that will be regularly posted.

·   There are several homework assignments and projects during the course. Please make sure that your programs are properly documented and indented. All programming assignments and project deliverables must be submitted through the Learning Portal.

·  Quizzes will be in-class and closed book. Quizzes will not be announced. Any quiz that is missed will receive zero credit - no exceptions.

·  For projects, you are not to copy or distribute code from any other sources. In particular, you are not to share or copy code from other students or code from projects submitted in past semesters. Plagiarism detection software will be employed to detect copying of code on projects. If you are in doubt regarding the use of certain code, ask the instructor.

·  No make-up exam will be given to any missed exam. Any assignment (e.g. homework or project) must be submitted on or before its due date and time. Solutions must be turned in as a clearly legible hardcopy, typeset or neatly hand-written. All pages must be stapled together. Late homework will incur a penalty of 33% per day late up to a maximum of three days. No incomplete grade will be awarded. Exceptions to these rules will be made only under exceptional circumstances (e.g. a note from a medical doctor). No extra credit assignments will be given to individual students for the explicit purpose of passing this course without justifiable reasons. Please see the course webpage for all the details of course outline, test dates and other important information.

Academic Honesty

I expect that you are taking this course to learn and to do the required work by yourself. Plagiarism is not acceptable and is not tolerated under any circumstances. All work turned in must be your own work (no collaboration is allowed unless explicitly stated). Students who violate this rule may get a penalty of getting an “F” as the course grade. Also, the student who offers his/her work to another student will get the same penalty. The UMass Dartmouth Academic Ethical Standards and Student Judicial Code apply to your conduct in this course. Please refer to the following materials for details. Special Needs

If you have particular needs in order to complete this course, such as special seating, note taking, or examination conditions, please let me know as soon as possible so that appropriate accommodations can be made.