Computing & Software Systems
CSS430: Operating Systems
Fall 2015 Syllabus
MW 3:30-5:30pm Classroom UW2-005
This course introduces the logical design of operating systems, especially focusing on the design in Java. Topics covered include processes, threads, CPU scheduling, synchronization, deadlocks, memory management, virtual memory, file systems, I/O systems, protection, and security used in the popular desktop and real-time operating systems.
Canvas Learning Management System (LMS) will be used for announcements, discussion forums, assignment posting and submissions, and individual grades. Please visit the Canvas Site to access the Canvas page for this class.
For any direct/individual communication with your instructor please use email (do not use Canvas messaging/mail).
For more detailed information on the course and tentative schedule, please refer to the electronic notebook (OneNote document) accessible through the Canvas Site.
|Class Discussions and Participation||8%||80|
All grades will be listed as percentages in the Canvas LMS. The conversion table below will help you determine your final grade. For example, if you earn 950 points (or 95%) you will get a 4.0. If you earn 750 points (or 75%) you will earn a 2.0.
|A - 100%-90%||B - 89%-80%||C - 79%-70%||D - 69%-62%||E - 61%-below|
100%–95% = 4.0
89% = 3.4
79% = 2.4
69% = 1.4
= .6 (Failing)
Total of 1000 points available
All programs except the final project are to be done independently. Any collaboration of work will result in severe penalty. You may discuss the problem statement and any clarification with each other, but any actual work to be turned in, must be done without collaboration.
The final project may be done by a team of two, (or three students if you cannot find a single partner), in which case each student must achieve an equally amount of work. (If you work with other two students, you must explain the reasons in your report, otherwise you will receive only 2/3 of the full score.) For the detailed instructions, see the project assignment sheet.
Any homework is due at the beginning of class on its due date. Please submit homework and programs via the Canvas LMS assignment upload facilities. Submissions may be postponed only in exceptional events such as accidents, sickness, sudden business trips, and family emergencies. You may turn in your homework late by coordinating with me (which may require written proof). No make-up exams will be given except under exceptional circumstances. Barring emergencies, I must be informed before the exam if you plan to be absent.
Students assume full responsibility for the content and integrity of the academic work they submit. The guiding principle of academic integrity shall be that a student's submitted work, examinations, reports, and projects must be that of the student's own work. Students shall be guilty of violating the honor code if they:
To request academic accommodations due to a disability, please contact Disability Resources for Students (DRS) UW1-175, (email: email@example.com, TDD: 425-352-5303, and FAX: 425-352-3581). If you have a documented disability on file with the DSS office, please have your DRS counselor contact me and we can discuss accommodations.
The overall goal of CSS 430 is to learn fundamemtal concepts that are used in and applicable to a variety of operating systems. The course consists of three major concepts: (1) process management that schedules, executes, synchronizes with events, and terminates your application programs, (2) memory management that loads your programs in memory and allocates/deallocates memory space they requested dynamically, and (3) file system that provides the mechanism for on-line storage of and access to both data and programs residing on the disks. The course also covers protection, (and security if time allows) which are essential to have modern operating systems work in the Internet computing world. Through the course, we will use Java to illustrate many operating-system concepts. Using Java, you will implement each concept of process management, memory management, and file system. As with most technical courses, besides ability and motivation, it takes time to learn and master the subject. Expect to spend an additional 10 to 15 hours a week outside of class time on the average.
Each chapter has its own lecture slides in a ppt file that includes one or more discussion topics and non-turn-in exercises. The class is divided into groups of 4 or 5 students, each discussing about a different topic for several minutes and presenting the dicussion summary in the class. We are planning to have eight or more class discussions through the quarter, although not having scheduled specific discussion dates yet. Your participation in each discussion counts 0.5% of your entire grade, which ends up with 4% by attending minimum eight discussions. If we eventually have more than eight dicussions and you attend all of them, you will receive extra credits.
A discussion group will be dynamically formed in the class. For instance, students sitting closer or on the same desk can form a group. I will give each group a piece of scratch paper or transparency. You should summarize your discussions, write down the names of all group members, and turn it in to me. Each group should elect a group representative who will give a short presentation in the class.