This document describes what is expected of a final project and proposes some possible project ideas.
What is Expected
Good class projects can vary dramatically in complexity, scope, and topic. The topic should be something related to databases and/or analysis of data. It should have some programmatic component, e.g., doing analysis using Excel does not count. You will have to write some scripts that process the data.
You can use what you have used in DS 200, but, you have to have something new you did in this class. For example, a design and compare different database options to select a good backend for your application may be acceptable. Simply using a project from another course is not allowed. You can reuse code, but you have to clearly identify what you are doing new in this class.
What to Hand In
There are two written deliverables: a proposal due on Sep 28, midway report including a project proposal, due on Nov 1, and a final report, due on the last day of class.
Project Proposal: The proposal should consist of 1-2 pages describing the problem you plan to solve, outlining how you plan to solve it, and describing what you will "deliver" for the final project. In the project proposal, you need to clearly identify the non-trivial use of databases and data analytic techniques you will use.
Final Report: You should prepare a report on your project with maximum length of 15 pages (10 pt font or larger, one or two columns, 1 inch margins, single or double spaced -- more is not better.) Your report should introduce and motivate the problem your project addresses, describe related work in the area, discuss the elements of your solution, and present results that measure the behavior, performance, or functionality of your system (with comparisons to other related systems as appropriate.)
Because this report is the primary deliverable upon which you will be graded, do not treat it as an afterthought. Plan to leave at least a few days to do the writing, and make sure your proofread and edit carefully!