LBSC 796/INFM 718R
Information Retrieval Systems
Fall 2007
Final Project Report
The project report should essentially be a written version of what is
in your slides. If you write it in Word, it should be easy to import
graphs and tables from your slides. You do not need to duplicate
information that is already in your batch evaluation report -- just
include that entire report as an appendix, and refer to it as
necessary.
- Describe the problem that you are solving and provide the URL for
your project's Web page (which should have the documents that you
generated along the way along with this report). [~1 page]
- Describe the design of your system, including the interface, the
query-time processing, and the indexing process. Don't get too
carried away here -- you might try to rewrite the entire system in words,
and there is no ned for that. If you want, you can alway spost the
code on the Web for the gory details. [3-4 pages]
- Describe the design of your user study (generally including: what
documents and other system configuration settings you used, what you
asked the users to do, how you organized a session, how you collected
the data, how you analyzed your results, and what you learned. [3-4
pages]
- A summary of what you learned along the way. It might be easiest
to organize this as bullet points, elaborating on what is in your
slides. [~1 page]
- Some appropriate way of ending (e.g., remarks on limitations, one
or more suggestions for future work, etc.) [0.5 page]
- As an appendix, your batch evaluation report (just for
completeness).
- As an appendix, your presentation slides (only necessary if they
contains things that are not convenient to include in your written
report).
The total (excluding appendices) should be 9-10 pages, about 1/3 of
which (or so) will likely be figures and tables.
As with all project components, this report will be separately graded
but the overall proect grade will be holistic (not some formulaic
combination of the graded parts).
Doug Oard
Last modified: Dec 2 2007