Assignments -- Fall 2007

• Assignments generally are given out on Friday in lecture and are due within one week.
• Homeworks may require an implementation or simply a write-up with pencil and paper.
• If you want to typeset your answers, we recommend proof.sty, a collection of LaTeX macros for type-setting deductions.
• Emphasis is on correctness and elegance.
• Written homeworks are to be handed in at the beginning of lecture on the due date.
• We will try our best to return graded homework during the lecture following the due date.
  
• Electronic handin instructions:
  All code files must be electronically submitted before class on the day when the assignment is due.
  Files are to be submitted using the 'handin' facility. Please submit the files for an assignment in the correct subdirectory.
  For example, for homework 1: handin cs426 ass01 ass01.tut

  Please refer to the 'handin' instructions page if you have never used 'handin' before.

Homeworks and Solutions

• Homework 5 (pdf, ps, ass05.req) Solution: HW5 sol

• Homework 4 (pdf, ps, ass04.tut) Solution: q1 and q2, q3

• Homework 3 (pdf, ps) Solution: HW3-proof, HW3-part 2

• Homework 2 (pdf, ps) Solution: HW2 sol

• Homework 1 (pdf, ps, tut) Solution: HW1 sol

Projects

You should suggest a project based on some ideas handed out in class by Nov 2. You are required to meet with me and discuss your project two-times during the semester, once before the project proposal is due and once before the presentation.

The project consists of three parts:

• Project proposal (6%) : Briefly outline the motivation of your project, and describe what you intend to do. Inlcude a brief time line which outlines the milestones you intend to achieve each week.
• Project milestone (4%) : Your milestone should give an outline of your project and project report, and concretely list the problem you will attempt to solve and what you have done already. Ideally, it will include an updated time line.
• Project presentation (10%) : In the last week, you are expected to give a 20min project presentation which explains why your project is interesting, what you have done so far, and what you intend to do in the remaining 2 weeks. A good presentation includes examples to motivate your project, discusses briefly the benefits and mentions related work (if any).

  You should have some slides prepared for the presentation. Your slides should be well-structured, and easily readible and understandable. This is much more important than choosing powerpoint or handwritten slides. If you want feedback on them, send a version to me via email

• Project report (10%) : You project report is due Dec 14. It should be approximately 10 - 12 pages. A good outline of the report is : Introduction and Motivation, Background (if necessary), What you have done, Related work and conclusion, Future work.

What does it mean to give a good talk? What does it mean to write a good paper?

Here is some advice other computer scientists have given.

• "How to present a paper in theoretical computer science: a speaker's guide to students", Ian Parberry, (ps)
• "How to give a good research talk", Simon L Peyton Jones, John Hughes, John Launchbury, SIGPLAN Notices 28(11), Nov 1993 (ps)
• "A guide for new referees in theoretical computer science", Ian Parberry (ps)
• "What it's like to be a POPL Referee, or How to write an extended abstract so that it is more likely to be accepted", Mark N. Wegman, SIGPLAN Notices 21(5), May 1986,91-95.

More advice on how to write a paper, present a talk, get into graduate school, etc. can be found here.