CSS 430: Operating Systems
Winter 2014
M/W 3:30-5:30pm
Room: UW2-131
Prof. Kelvin Sung

---

Professor:

Kelvin Sung <ksung@u.washington.edu>, room UW1-339, phone 352-5420, office hours: Wednesday 1:00-3:00 pm (or by appointment).

Course Description:

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.

Prerequisites:

CSS343.

Work Load and Grading:

Course Work	Percentage
Assignment 1	8%
Assignment 2	8%
Assignment 3	8%
Final Project	14%
Class Participation	2%
Weekly Quiz	10% (Weekly on the Web)
Midterm Exam	25%
Final Exam	25%

Textbooks:

1. Operating Systems Concepts With Java Eighth edition, Abraham Silberschatz, Peter Galvin, and Greg Gagne, Addison-Wesley, 2009.
2. A Java book of your choice.

Some Java Books:

• Absolute Java, 4^th Edition, Walter Savitch, Addison-Wesley, 2009.
• Java How to Program, 9^th Edition, Deitel & Deitel, Prentice Hall, 2011.

References:

• Advanced Programming in the Unix Environment, 2nd Ed, W. Richard Stevens, Addison Wesley, 2005
• Understanding the Linux Kernel, Daniel P. Bovet and Marco Cesati, O'Reilly, 2000
• Java Threads, 3rd Edition, Scott Oaks and Henry Wong, O'Reilly, 2004
• The Design of the Unix Operating Sytem, Marice J. Bach, Prentice Hall, 1987

Policies:

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 for both its hardcopy and softcopy on the due date. Both copies must be submitted. The submission may be postponed only in emergencies such as accidents, sickness, sudden business trips, and family emergencies, in which case you may turn in your homework late with a written proof. No make-up exams will be given except under exceptional circumstances. Barring emergencies, I must be informed before the exam.

To request academic accommodations due to a disability, please contact Disability Resources for Students (DRS) UW1-175, (email: drs@uwb.edu, 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.

Course Goals:

The overall goal of CSS 430 is to learn fundamental 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/de-allocates 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 is allowed) which are essential to have the 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.

Assignments:

• Assignments are due at the beginning of lecture for both your hardcopy and softcopy on the specified date. No late programs will be accepted unless you provide me with a proof showing that you have been under an emergency circumstance. No matter the circumstances, it is always best to turn in something.
• Click here to know the details of the programming environments, the assignment specifications, the submission procedure (for both hardcopy and softcopy), and the grading criteria.

Topics covered and tentative 430 spring schedule:

Note that this is an approximate ordering of topics. Chapters will take about the allotted time and not all sections in all chapters are covered.

Week	Date	Topics	Chapters	Assignment
1	Jan 6	Introduction	1	Program 1 assigned
	Jan 8	OS Structures	2
2	Jan 13	Process Management	3
	Jan 15	Threads	4	Program 1 due Program 2 assigned
3	Jan 20	MLK Day	no class
	Jan 22	CPU Scheduling	5
4	Jan 27
	Jan 29	Process Synchronization	6	Program 2 due Program 3 assigned
5	Feb 3	Study day Kelvin at IEEE Editorial Board	no class
	Feb 5	Midterm exam in class	Chap: 1-6
6	Feb 10	Deadlocks	7
	Feb 12	File-System Interface	10
7	Feb 17	Presidents Day	no class
	Feb 19
8	Feb 24	File-System Implementation	11	Program 3 due Project assigned
	Feb 26	Final Project Explanation		Program 3 due Project assigned
9	Mar 3	Main Memory	8
	Mar 5
10	Mar 10	Virtual Memory	9
	Mar 12			Final Project Due
11	Mar 17	Final exam in class	Chap: 7 – 11

Acknowledgment

The materials (including lecture notes and assignments) used in this course are based on the contents developed by Professor Munehiro Fukuda.