CMPSCI 645: Database Design and Implementation

subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link
subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link
subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link
subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link
subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link
subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link
subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link
subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link

Course Project


Students can form teams of 2 people or work individually. Students are encouraged to propose projects on data management issues related to the course material. They can also contact the instructor for help with the topic selection. Each team should meet with the instructor once every month for technical discussions and progress reports.

Milestones


Form groups (Due Feb 20, before class)

Find a project partner and begin to discuss project ideas.

Project proposal (Due Mar 6, midnight)

Your proposal should explicitly state the following:
  • Problem your project will address.
  • Your project’s goal and motivation.
  • Areas of related work. Your survey of the related work should place a particular focus on how existing work differs from your proposed work and why it is insufficent for solving the problem you propose. Through this survey, you should be able to convince the reader that you are addressing something fundamentally new, either a brand new problem or a novel approach to a known problem.
  • The methodology and plan for your project. Be sure to structure your plan for the project as a set of incremental milestones and include a schedule for meeting them.
  • The resources needed to carry out your project.
Please email your proposal to both the TA and the instructor by midnight on the specified date.

Midterm status report (Due Apr 19, midnight)

Your status report should contain enough implementation, data, and analysis to show that your project is on the right track. You should revise your original proposal to accommodate the instructor's comments, along with any surprising results or changes in direction, schedule, etc. You sometimes also need to have a refined version of the problem statement as well as a more developed related work section.

Again, email your status report to both the TA and the instructor by midnight on the specified date.

Project presentation (Due May 10/15, in class)

A brief presentation should include the proposed problem, state-of-the-art solutions, your proposed solutions including the algorithms and implementation, and evaluation results. The presentation may include a system demo if appropriate.

Project report (Due May 22, 5 pm)

A final report extends your previous writeups to present the research problem, summarize your contributions, survey related work, and include a detailed description of your algorithms, analysis, implementation, evaluation methodology and significant results, and finally present conclusions. For team work, the report should also include a paragraph explaining, for each group member, their contributions and duties in the project.

Email your final report to the TA and the instructor by 5 pm on May 22.