Recent Changes - Search:

Instructor

  • who: Michael Swift
  • where: Room 7369
  • when: Thurs. 1:30-2:30
  • email: swift 'at' cs.wisc.edu

TA

  • who: Ceyhun Alp
  • where: 1306
  • when: Wednesday 1:15-2:15
  • email: e.ceyhun.alp 'at' gmail.com

Lecture:

  • when: Tues./Thur. 11:00 -- 12:15
  • where: Computer Sciences 1325
  • list: compsci736-1-s16 'at' lists.wisc.edu

HomePage

Resources

edit SideBar

Reading

Writeup

Before 9:00 am on day of class, please post your review to the blog at:

Your posting should contain:

  1. A one or two sentence summary of the paper
  2. A description of the problem they were trying to solve
  3. A summary of the contributions of the paper
  4. What did the paper evaluate and was it appropriate
  5. One thing you were confused about from the paper

Here is a template you can use

 <b> 1. summary</b>
 <b> 2. Problem</b>
 <b> 3. Contributions </b> 
 <b> 4. Evaluation </b>
 <b> 5. Confusion </b>

The writeup should not be more than a page in length. Late write-ups will receive a zero grade.

Advice

The reading schedule for this course will be intense. The readings are grouped into four major categories: complexity, performance, reliability, and security. Within each category, we will read papers that address that issue in the context of different portions of an operating system.

You should form a discussion group for talking about the papers. You should have three or four people in your group, and discuss each paper sometime before class meets. It is up to you if you want to meet just once a week or twice a week before each class, but you should discuss each paper. When you have formed a group, please send me email with a list of group members.

When discussing each paper, you are encouraged to consider the following questions: As you read, here are some questions you should consider:

  1. What problem are the authors trying to solve?
    • Why was the problem important?
    • Why was the problem not solved by earlier work?
  2. What is the authors solution to the problem?
    • How does their approach solve the problem?
    • How is the solution unique and innovative?
    • What are the details of their solution?
  3. How do the authors evaluate their solution?
    • What specific questions do they answer?
    • What simplifying assumptions do they make?
    • What is their methodology?
    • What are the strengths and weaknesses of their solution?
    • What is left unknown?
  4. What do you think?
    • Is the problem still important?
    • Did the authors solve the stated problem?
    • Did the authors adequately demonstrate that they solved the problem?
    • What future work does this research point to?

You should be prepared to discuss these questions in class. For each paper I will ask for a volunteer to summarize and address a few of these questions in class.

Here are a few links to advice on reading papers:

Responsibilities

For every lecture, you will be reading one or two research papers. For each paper, you have four responsibilities:

  1. Read the paper
  2. Discuss the paper with your group
  3. Submit a short writeup about the paper
  4. Prepare to summarize the paper in class

Each class, one group will be chosen to present a brief summary of the day's papers.

Writeup Grading

What I’m looking for:

  • Does the review include all sections (summary, problem, contributions, flaws, topic question)
  • Are all assertions backed up (e.g. “X is a bad idea” is not acceptable, but “X is a bad idea because Y”) is acceptable
  • Is the review concise? The summary should be a few sentences and give the essence of the design in the paper, not the problem. (E.g., “This paper is about how to build a multiprocessor operating system” is not acceptable, but “This paper is about building a multiprocessor operating system by layering abstractions that mask the existence of multiple processors” is acceptable)
  • Did the student understand the material? Are there factual flaws in the review? For example, if the paper defines a term, does the student use it appropriately? As another example, if students state that a paper is relevant because modern operating systems do things the same way, is that true?
  • Did the student consider whether the evaluation is sufficient? Does it show that the work doesn't harm regular programs, even if it works well for some programs? Do they evaluate all the goals for the system?

Assigning grades:

  • If the review does an excellent job on all four considerations, and provides genuinely insightful comments about the problem, contributions (going beyond what the paper claims are contributions), evaluation, confusions, it should receive a check plus
  • If two or more of the four criteria are not met, the review should receive a check minus
  • Otherwise, it should receive a check.

A check plus is worth 1 point, a check is 3/4 point, a check minus is 1/2 point, and not turning a review in is worth zero points.

Edit - History - Print - Recent Changes - Search
Page last modified on February 01, 2016, at 04:46 PM