|
|
|
|
|
Guidelines for final reports:
Be sure that your writeup contains:
- Team and member names (one report per group).
- Your goals for the project
- Your system design and algorithmic choices
- Sample screens of typical usage scenarios
- Experiments and results that show how effective your system
is, and
where it could be improved. For example, you might show a precision /
recall curve for different types of extraction algorithms. Graphs (if
informative) are better than large tables of numbers. See some of the
papers in the reading. The
Kylin paper is not particularly unusual in this respect, but may
give you ideas.
- Anything you considered suprising or that you learned. What would
you do differently if you could?
- Conclusions and ideas for future work
- Appendicies:
- Which people did what parts of the work? Were there problematic
dynamics in your group?
- What externally-written code (if any) was used in your project?
- Instructions on how to start and use your project (including OS
or browser requirements, pointer to a README file (or include that
inline). Is there a website to visit?
There is no limit on length, but we appreciate good organization and tight,
precise writing. Points off for rambling and repetition.
What to Hand In:
- By the start of the final presentation period, please hand in a hard-copy of your
report as well as an electronic version of both the report and the
code. We will supply details on the electronic hand-in process via the
class mailing list.
- Late submissions for the final project and writeup will not be
accepted, as it will be the end of the quarter. Sorry! (But happy
holidays).
|
CSE Home 
About Us
