Final Project Submission
The goal of the final project is to build on what you have
accomplished in the other project checkpoints. This document will
show both what you are expected to turn in, and what functionality you
should have for your project to be successful.
There are two components to the final project:
Please read the
following carefully to make sure that you don't miss anything.
One piece of advice: start early; it is hard to imagine that
you will be able to pull this off if you start only a few days before
the deadline. Do one operation at a time and use the interactive SQL
interface to first make sure that you have the right SQL
query. Finally, you can implement the embedded SQL part with the
GUI.
Note that while you can see what we expect you to show us at the demo
in the notes below, it is not enough to hard code the
application to just run that set of specific queries - we will be
looking at your files as well to show that you've implemented the
whole application that you have said that you have.
The files
One person from each project team must turn the following into the
handin directory "project-final" - the full command is "handin cs304
project-final", which assumes that the files that you are
submitting are in a directory called ~/cs304/project-final.
To do so, you'll need
to get
an account on the CS ugrad machines.
- A cover page
- All the code used in the application
- A script that could be used to create all tables and data in the database
such as the one here
- A short description of what the project accomplished
- A description of how your final schema differed from the schema
you turned in. If the final schema differed, why? Note that
turning in a final schema that's different from what you planned is
fine, we just want to know what changed and why.
- A list of the SQL queries used
-
List all functional dependencies that are applicable to the table
(including the ones involving the primary key). For each functional dependency, briefly describe its meaning in English.
The individual reports
By the due date, each group member must submit their own individual
report using the handin directory
"individual-project-reports". The full command is "handin cs304
individual-project-reports", which assumes that the files that you are
submitting are in a directory called ~/cs304/individual-project-reports.
To do so, you'll need
to get
an account on the CS ugrad machines.
Please note that this is
not group work, and must be done individually. please put
your name and your group's name on the top of everything that you
submit. Please also submit this report in plain text. The
project report should contain the answers to the following questions:
- Your assessment of the group's final achievement: Did you fall short
of expectations? Did you exceed your initial predictions? How well did
you work together? What areas could have been improved? Were group
roles and responsibilities clearly defined?
- Individual Assessment: what were your contributions in terms of
code, design, group moral, etc. Specifically, what did you do for the
group and for yourself? What aspects, if any, of your effort and and
work are you most proud of? What aspects, if any, are most in need of
improvement? What do you think your fellow teammembers will say about
your achievements and efforts?
- Assessment of Individuals: for each group member, evaluate
performance, effort, accomplishments on a scale of 1-5 where 1 is "met
them once, I think, they weren't around" and 5 is "captain, CEO,
chief-architect, cheer-leader, all around good person and the project
would have been significantly less without them". It's possible that
everyone in the group could get a 5, or that everyone could get a
1. Please be sure to justify, briefly, your assessment/evaluation. Be
sure to assess/evaluate yourself too. This assessment will be confidential
- Assessment of the project:
- Roughly how much time did you spend on the project?
- What did you like the best about the project?
- What did you like the least about the project?
- What helped you learn the best in the project?
- If you could change the way that the project was organized, what
would you change?