Syllabus

• Description & Goals
• Administrivia
• Textbooks
• Assignments and Grading
• Policies
• Tentative Schedule

Description & Goals

This course examines the logical design and programming aspects of operating systems and network communication. Topics covered include processes, threads, synchronization, deadlocks, memory management, virtual memory, file systems, and client-server network programming.

Goals

The overall goal of CSS 503, "Systems Programming" includes:

• design & develop multi-process/multithreaded applications
• analyze & simulate different process/thread synchronization approaches
• analyze different memory management strategies
• examine various file system interfaces and implementations
• examine network/distributed system infrastructure
• design and develop a multithreaded TCP-based client-server program

Prerequisite: 2.7 or better in CSS 502

Administrivia

Location & Time

• Time: Monday & Thursday 6:00 pm to 7:40 pm
• Location: SSG CNSVTRY (Sarah Simonds Green Conservatory)
  Tue Apr 1 18:58:08 2014: Relocated to UW2 040

Professor: Morris Bernstein

• Office: Linux lab UW1 320
• Phone: N/A
• Email: morrisb9@u.washington.edu
• Office Hours: after class, Sunday afternoons from aproximately 1 pm, or by appointment

Textbooks

Operating System Concepts with Java, 8th edition, Avi Silberschatz, Peter Galvin, and Greg Gagne

Assignments and Grading

Final grades may be adjusted at the instructor's discretion.

Assignments

Programming assignments should be turned in using catalyst. Submit a zip file (or gzipped tarball) containing:

• program file(s)
• sample input
• expected output
• optional README file with any relevant notes

Assignments are to be handed in by 11:30 pm on the due date. Acceptance of late assignments will be determined on a case-by-case basis.

If a grade is egregiously out of whack with your expectation feel free to ask for another look; with the time limitation on grading, overlooking something is easy to do. Just be aware that reevaluation may cause the grade could go up or down.

Policies

Live lectures are inherently interactive. Questions during class are encouraged. Please raise your hand to get the instructor's attention. At the instructor's discretion, answers may be tabled until the end of class if they are too far off topic.

Limit computer use during class to note-taking so as to not distract or disturb your classmates or your instructor. Since a large part of the presentation involves diagrams, it may be more convenient to turn off the computer and take notes the old fashioned way. Quill pens are optional.

Flash photography is not permitted. Non-flash photography to capture the white board will be permitted as long as it is not disruptive or distracting. Don't even think about video.

Silence your cell phones.

If you arrive late or have to leave in the middle of class, do so quietly without causing disruption.

The assignments and project are to be done independently unless otherwise indicated. Their purpose is to help you understand technical material. By all means, do discuss the problem statement with each other and help debug, but do your own design and coding. See the student honor code.

If collusion or other forms of plagiarism is suspected, I will discuss it with the indivdual(s) first, but paperwork has be filed. Please don't force me to have to deal with that kind of crap; they really don't pay me enough.

Simple email questions may get a response. Complex questions are best saved for office hours.

Special-needs students:

To request academic accommodations due to a disability, please contact Disabled Student Services (DSS) at 425.352.5307, 425.352.5303 TDD, 425.352.5455 FAX, or at dss@uwb.edu. You will need to provide documentation of your disability as part of the review process prior to receiving any accommodations (by the third week of the quarter).

Tentative Schedule

Subject to change as the quarter progresses.