| Course Objectives |
|
The purpose of this course is to teach computer software system structures from a design point of view. We will look at different structuring techniques, and we will examine their usage in both important historical systems and in modern systems. In addition to learning about different system structures and different operating systems, you will learn:
|
| Reading List |
|
We will be reading and discussing two papers each class period according to the following schedule: |
| Class Participation |
|
The structure of this class is unusual in that there are no lectures or presentations during the class period. Instead, we will discuss research papers that we will have all read before each class period. I will lead discussions by asking questions of students at random in class. Note that your answers to these questions form an appreciable portion of your overall grade, so it is important that you both show up to class as well as read the papers carefully. To get you started, I include a question about each paper in the reading list. I'll ask that question in class. Because of the unusual format of this class, I will not grade you on class participation during the first two weeks of class. |
| Project |
|
Revised October 18 You will work on a project for the course. It can be done either by yourself or in a team of two. |
| Exams |
|
There will be a final exam for the course during the university scheduled exam period. Here is the final I gave last year. |
| Grading |
|
(Subject to change)
|