Syllabus

6.823 Computer System Architecture 
Spring 2002

Course Information

6.001 and 6.004 or equivalent.

Two sessions / week
1.5 hours / session (optional)

Computer Architecture: A Quantitative Approach: 2nd Edition by J. L. Hennessy and D. A. Patterson is the main textbook used in this course. Supplemental readings from selected papers may also be assigned; in which case, there may be a nominal photocopying charge.

You may also want to refer to Computer Organization & Design: The Hardware/Software Interface by D. A. Patterson and J. L. Hennessy to review the basic material.

There will be a midterm exam covering the material from the lectures, assigned readings, and class notes. A final exam will cover the entire course but will emphasize the latter half. Review sessions will be scheduled for both the midterm and the final exam.

There will be 6-7 problem sets. Problem sets are due at the beginning of class on the due date. Students are strongly encouraged to work in groups of two or three. Each student is expected to work on all problems. However, only one write-up should be turned-in per group. Groups need not remain the same throughout the course. We only need to know the people who worked on a particular problem set submission together. To facilitate grading, each problem must be stapled separately. Solutions will be provided for each problem set. It is the students' responsibility to review the solutions.

The course policy on collaboration and the use of past course materials is as follows:

1. For problem sets (with the exception of problem set #0, which must be done individually), students may work in groups of up to 3 students. Although only one write-up should be turned in per group, each student must work on all problems. Students in different groups are not allowed to collaborate on a problem set.
2. Collaboration amongst students to understand the course material and the statement of problem sets is always encouraged.
3. Referring to course bibles (e.g. old problem sets and solutions) is strictly forbidden. Normal ethics dictate that, if you have been exposed to an old solution inadvertently, you should explicitly state this fact on the first page of an affected problem set submission.

If you have any questions about the above policy, please consult one of the TAs.

Grades will be based 30% on problem sets, 30% on the midterm exam and 40% on the final exam. In addition, we have instituted the requirement that every student must help grade at least one problem set over the course of the semester. Failure to assist in grading will result in up to half a grade deduction (e.g. B to B-).

In past years, as the size of the class has gotten very large, we have had trouble returning the graded problem sets in a timely manner. To alleviate this problem, we ask students to assist in grading problem sets. From our previous experience, this peer-grading requirement is very enjoyable and helpful in re-enforcing understanding of the course material. Each student will be expected to help out in grading one problem set. Unless explicitly excused by the instructor, every student will be required to grade once. Failure to assist in grading will result in up to half a grade deduction (e.g. B to B-).

Grading will be done in a scheduled group sessions supervised by the TA. Sign-up sheets for the grading session for a particular problem set will be handed out during lecture the day the problem set is due. If not enough students sign up for a given grading session, the TAs may pick additional students from the set that have not yet graded.

Food and drinks will be provided during each grading session. We hope these sessions will be fun and interesting, and provide an opportunity for additional interaction among students and the TAs.