Carnegie Mellon University
15-721 Database System Design and Implementation
Spring 2003 - C. Faloutsos
Grading scheme for final report
The grade of the final phase of the project will have two components:
-
writeup: there, you would describe the novelties of your approach
and your discoveries/insights/experiments
-
software: packaging, documentation, and portability. The goal is
to provide enough material, so that other people can use it and continue
your work.
A. Grading Scheme
-
Writeup: Each 'bullet' should correspond to a section:
-
[5%] Introduction - Motivation
-
[5%] Survey
-
Proposed method
-
[10%] Intuition - why should it be better than the state of the art?
-
[40%] Description of its algorithms
-
Experiments
-
[5%] Description of your testbed; list of questions your experiments are
designed to answer
-
[25%] Details of the experiments; observations (as many as you can!)
-
[5%] Conclusions
-
Software (testing, packaging and documentation) [5%]
Deviations from the above scheme:
-
In case that your project requires no software, its 5 points go
for 'description of algorithms', making the weight 45%.
-
In the reverse case that the project is mainly on implementation, the 10
points of the 'intuition' would go for 'Software', making its weight 15%.
B. Specifications for packaging:
Please create a tar-file, like this sample
package ( use gunzip ; tar xvf). Exact specifications:
-
after un-tar-ing, the command 'make' should compile your
system, install it if necessary and run a small demo on a sample input
file (included in your package)
-
your programs should run on at least two environments (the one of
your class account, as well as on, say, on your ``andrew'' account), and,
ideally, on as many environments as possible.
-
it should have a README file, corresponding to the `user's manual':
This file should describe the package in a few paragraphs, as well as how
to install it and how to use it.
-
it should have a directory DOC, with your writeup, preferably in
latex
-
`make paper.ps' should create a postscript version of your
writeup (Not applicable, if you use ms-word or open-office)
-
`make clean' should eliminate all the derived files
(*.o, *.aux, etc)
-
`make uu' should create a gzip-ed, uuencoded tar-file into
the UNIX file 'uu', which should be ready for distribution.
-
please make sure that your package includes only the absolutely
necessary set of files!
C. Deadline - check-list of items to hand in:
April 24, 2003, in class, for both the write-up as well as the software.
Please,
-
bring a hard copy of the writeup in class,
-
also bring a (hard copy) of the graded phase-2 report and
-
e-mail me a copy of your uuencoded tar-file before class. The tar-file
should include your report in latex, in the DOC directory.