Link Search Menu Expand Document
CS6400

Project Demo and Code Submission

DUE MONDAY DEC 9 AT 11:59PM.

Table of contents

Part 1: Project Demo (Dec 6)

  1. Sign up for a 15min slot on Zoom: sign up link. All team members should attend the demo session
  2. During your group’s time slot, start with a demonstration of your final project outcome. Your demo should be concise (no more than 5 minutes) to allow time for questions. Here are some suggestions for the demo:
    • Application: Give a live demo of what you have built. Try to show in the best possible way what you have implemented and how. Go over what you consider to be the main highlighting features that will give us a good idea of the effort you have put into the project.
    • Benchmark: Present your analysis in detail. Be specific about the experiment setup, the methods/systems in comparison, and results and interpretation.
    • DB system/component: Demonstrate the component’s functionality or performance improvements. Walk through implementation details that could highlight technical challenges.
  3. Be prepared to answer questions based on your live demo and project presentation. You may need to walk us through specific sections of your code.

Part 2: Code Submission

Upload all project code to Canvas using either a zip file or a link to your GitHub repository (make sure the course staff has access).

In your repo, include a detailed README file with instructions to setup and run the project. We should be able to reproduce the demo following the instructions provided. Considering including the following information:

Project Setup

  • Specify the database system(s) and version(s) used, along with installation instructions (a link to official documentation will be enough).
  • If you are benchmarking different database systems, detail any configuration modifications made.
  • Dependencies: List required third-party libraries and installation instructions (e.g., through a requirements.txt file).

Data Preparation

  • Data source: describe how to obtain/generate project data. Consider including one of the following: 1) sample dataset (< 5MB), 2) data generation scripts (for synthetic data), and 3) download/scraping scripts.
  • Include instructions for data loading and preprocessing to transform data into expected format.

Running the Project

  • Provide execution instructions for running your project, and describe expected results from the execution.
  • If applicable, explain how to run the GUI or the plotting scripts for your main results.

References

  • Provide links to any code used from GitHub or other sources. Note that using online code without appropriate citation/ credits would be considered plagiarism.
  • Documentation of modifications to referenced code. For example, this could be a list of Github commits.

Part 3: Complete the Team Dynamics Assessment Form

Generally, teams work constructively together to complete projects. It’s important for us to know whether this is the case in your project. In the case of substantially imbalanced contribution, we will adjust participation grades to compensate.

So we can understand this, each member of the team needs to fill out the team feedback form. We will not return grades to your team until every team member has submitted the form.

Fill out the form here.

Submission and Grading

Submit the zip file/repo link along with the instruction file on canvas. Note that your code will NOT be graded, but the instructions would help us reproduce your project in the scenario we wish to confirm something.

In addition, all team members must individually submit the team dynamics assessment form.

The project deliverables count for 10% of your grade. We will grade the project using the following criteria:

  • the amount of effort you put in
  • how complete you were in terms of what you set out to do
  • overall quality of your work
  • how creative/exploratory/innovative/pro-active/ambitious you were in trying out things.