General comments

What you will turn in:

These are both due at the project deadline.

The report

Assume the reader has taken the course (but not seen your presentation). It is up to you how to decide how to organize the report, but the reader should be able to answer the following questions:

Your report should be roughly 4-8 pages (not including references and appendices). For inspiration (good and bad examples), you can consult shared task system papers, e.g. at a SemEval workshop. Your report should start with an abstract (a few sentences) that advertises/summarizes the main achievements.

Final presentations

You will have 15 minutes to present your project to the class. The presentation should describe the project motivation and goals; what was challenging about the task; what approach was taken, what aspects of the approach were new, and what the most interesting findings were. You need not (and probably should not) try to present every detail that is in your writeup—think of the talk as an advertisement that should motivate people to read the report. You can decide how to share time in the presentation (e.g., each person could present for 3-4 minutes). If you have a live demo, that should be part of the 15 minutes. There will be 5 minutes for questions afterwards.

Peer evaluations

After the presentations, each of you will be asked to give private feedback on your teammates. If the team functions smoothly and everyone has contributed a reasonable share to the project, everyone on the team will get the same grade. However, if somebody has been an especially strong contributor or an especially weak contributor, we will adjust individual scores to take that into account.