You turn in a document which looks like a completed research paper, which is ready to be submitted to a conference.
You incorporate the feedback you received on M3 in class (plus you write the text for the Empirical Evaluation section
that you presented at M3), and add new sections:
- By now you should have a working solution. Take your previous document from Milestone 1, and add 2-3 pages describing:
This is the time when you make sure that the whole paper reads like it's written by one author,
so you will need to smoothen the transition between the previously written sections, etc.
Due on Finals Week (exact time TBA) each team sends one PDF document with
the final project report. Your email should be entitled "CS561
Final Project" and it should contain a PDF file whose name should
include the last names of the people in the team.
This should be punchy, intriguing, and stirring the interest of the reader to read the whole paper.
You can achieve these goals by following the
This should be a 1-2 page summary of the whole paper. It contains:
- the higher-level motivation for the work (e.g., the importance and urgency of the problem you are trying to solve),
- a brief description of the state-of-the-practice and state-of-the-art, the challenges that your solution must address.
- a brief description of your solution
- a brief description of the empirical evaluation and its main results
- an explicit list of the contributions
We require at least 10 references. You need to compare and
contrast your work to previous work.
This is a brief summary, but also contains the most surprising
findings, implications, directions for future research.