Project Stage 5
Due date: When you demo
A sign-up sheet is available at the door of the TA office, so that
on-campus teams can sign up for demo. Pick one time slot that works
for your team-- Not all members are required to be present. One or
more representatives will work. We expect that you will use one of
PCs in the TA office. (Alternatively, you can bring your own machine
The demo for each group is expected to last about 10 minutes. When
you demo, please bring a hard copy of your final report.
Your final report should include:
briefly describes what the project
states if everything goes
according to the plan and the designed specifications, if not, then
describes the final division of
labor (who did what),
and any other strengths you would like to bring to our
attention while grading your project.
WHAT ARE WE LOOKING FOR AT THE DEMOS: In essence, we are
looking to see your application "in action", and to check
that you have done a reasonable job on implementing various database
functionalities (inputing the data, querying data, updating, etc.).
We will also take a look at your cool feature.
Applications that do not function fully during the presentation but at least have a partial demonstration in stage 4 (or are made to work during or afterwards) will receive a Marginal score (see below).
Basic functionality (60%)
Demonstrate the ability to insert records into the database (Pass=20%/Marginal=10%/Fail=0%)
Demonstrate the ability to delete records from the database (as above)
Demonstrate the ability to list record(s) in the database (as above)
Demonstrate two of the following (or equivalent advanced feature) 2x(Pass=10%,Marginal=5%,Fail=0%):
Additional 'cool' user feature that goes beyond the basic functionality above
Superior user interface design
Error checking on field data or other security feature
Additional administrative interface or role-based interface.
Batch loads from other datasets (please describe this in your final report).
Any advanced SQL that goes beyond simple insert,delete,select-from-one-table
Written Report (20%)
The written report should include a clear explanation of the basic functionality of the project and how to start it (e.g. URL or executable name, and login name).
The written report describe your two advanced features (see above).
The written report should document and briefly explain one concrete example simple SQL call that the application performs. Include a screen shot or other description of the user action associated with this SQL. Then list and briefly explain the dataflow i.e. all of the steps that occur between a user entering the data on the screen and the final SQL update that occurs in the database. (Your list should include more than 5 items but less than 15)
The report should describe whether the website attempts to prevent SQL injection. Provide an example SQL injection attempt from the user side and the corresponding SQL that would be executed if the injection attempt is successful. Describe whether it is prevented (and if so how).
The written report should describe one technical challenge that the team encountered (one-two paragraphs). This should be sufficiently detailed such that another future team could use this as helpful advice if they were to start a similar project or were to maintain your project.
The written report should be about printed 2-3 page sides. Please bring a stapled copy with you at your demonstration. Please include your team name and netids on the final report. You may include additional information and screenshots in an appendix.
Remote teams may email their report as a pdf to Tao (tcheng3 [at] uiuc.edu), please include additional screen shots of your application in your report.