Monday, December 11 - 8:00am:
Final report due. Your final project report is
due, along with a group evaluation for those working in groups (see below). The final report must be a full-length (10-14 page single column)
conference-style paper discussing your project. You should model your
paper on some of the papers we've read this term. Either PDF by e-mail or a
hard copy in my box is fine. If you give a hard copy, I'd appreciate
an e-mail letting me know that you've turned it in.
The goal of saying "conference style paper" is that I want
you to include things like:
Note that some of you won't actually create a solution, but just
explore the literature, which is fine. In this case, your job is to
explore the strengths and weaknesses of the approaches, and, if you
feel like there's an obvious choice, say what you would do if you were
going to implement a solution to the problem. Note that I do not care
about the layout.
- Motivate the problem that you're working on
- Provide an example of a scenario where you'd use your solution
- Tell me about the solution that you've created, this includes telling me about what makes the problem interesting
hard. If you'd like, you can interpret this as telling me what
problems you ran into.
- Relate it to related work
- Tell me about potential future work - even if you have no
intension of ever doing it. Just like in a real conference paper, the
goal is for you to show that you know what some of the flaws are with
your system, even if you have no intension of solving them. ;)
In addition to the report, I want each person who is working
on a project in a group to SEPARATELY turn in a report on how they
felt that all of the group members (yourself included) contributed to
the project. Useful information is: what parts of the project you did
(e.g., if you divided the work by sections, who did what section), how
many hours you estimated that you worked, and how well you feel like
you and the other people in the project did.