Paper summary guidelines

An important component of 712 is critical reading of the assigned papers and coming to class ready to discuss them. To help you in this process, we require that you hand in a short review of each paper at the beginning of the class during which we will discuss the paper.

Your summaries should:

• State the 3 most important things the paper says. These should be some combination of their motivations, observations, interesting parts of the design, or clever parts of their implementation .
• Describe the paper's single most glaring deficiency. Every paper has some fault. Perhaps an experiment was poorly designed or the main idea had a narrow scope or applicability. Being able to assess weaknesses as well as strengths is an important skill for this course and beyond.
• Describe what conclusion you draw from the paper as to how to build systems in the future. Most of the assigned papers are have been significant to the systems community and have had some lasting impact on the area.

We do not want a book report or a repeat of the paper's abstract. Rather, we want your considered opinions about the key points indicated above. Of course, if you have an insight that doesn't fit the above format, please include it as well.

We want the reviews to be short, between 1/4 and 1/2 a page. Reviews must not be hand written, and plain text is preferred over some document formating input or output.

All reviews will be counted, and a random sample of the reviews will be graded. Do not skip class or come late just to finish a review -- we expect that everyone will miss a few, though skipping more than 10% will have a negative impact on your grade.

How to submit.