The term project is an important part of this course. Projects will be conducted in teams of size two or three. There are three types of projects that are acceptable in this course:
Successful projects could lead to publishable results. Obviously, publishing is not a requirement, but this is the mindset that you should have.
You will need to form your team and come up with a project idea in the first three weeks of class. I strongly encourage you to come up with your own project ideas. Choose some open question from the papers on the reading list. Or pick a problem that interests you from outside of databases and give it a self-managing database twist. I will try to help by presenting some possible directions for projects during the first two weeks of class.
The project proposal should be one page long in 10 point font. It should include the title of the project, names of the team members, a description of the problem you will work on, why it is important, and how you will attempt to solve it. Try to clearly identify your objectives, methodology, milestones, and metrics for success.
The project report should be written in research paper style. It should motivate your problem, discuss related work, and present your solution in detail including its benefits and limitations. The report should be 10 pages maximum (20 pages for survey projects). It should be formatted in the two-column ACM proceedings format, using one of the ACM SIG Proceedings Templates. The ACM templates include headings for "Categories and Subject Descriptors," "General Terms," and "Keywords." Do not use any of these headings.
Project report in hard copy and PDF.
Source code and scripts required to replicate your solution.
20-30 minute presentation (length of presentation will depend on number of project groups).
Demo if applicable.
You will be evaluated on the depth and novelty of your work, on the quality of your report, and on your research methodology (cleanness of your implementation, experimentation methodology, etc.).