CPSC 304, Project Information

Quick Jumps

Goals
Oracle Information
JDBC/PHP Troubleshooting
JDBC/Oracle
PHP
MySQL Info
Schedule
Talking to the TAs vs. submitting to the directories

Project Description

Students in teams of 4 are required to select an application that would benefit from a database and build a database application from start to finish.

Philosophy

Building a full database application from scratch allows you to control the process; instead of having the pieces decided for you, you must make all of the decisions by yourself. Part of this process is that you will see how design decisions made at the beginning will effect your final project. We'll have some practice of some of the skills that you'll need in tutorial, but this will allow you to get some more in depth practice and a feel for what it's like when you make all of the decisions for an application.

Goals

Deciding on an application are for which database systems would be required
Modeling the domain of the application, and defining the application functionalities
Designing and implementing the schema
Populating the database (this should not be the main focus of the project)
Writing the code needed to embed the database system in the application (again, the focus should be on the database aspects, not the GUI)

Oracle Information

SQLPlus - how to connect to your oracle account through the command line.
Oracle Reference
Oracle Date Functions
How to get more help Including troubleshooting
A free, legal, limited version of Oracle for home can be found here

So you are having problems with JDBC/PHP ...

Check out our troubleshooting page

JDBC/Oracle

PHP

Getting started with PHP

MySQL Information

MySQL Installation Instructions for Windows (done by yourself, not discussed in the lab)
MySQL Installation Instructions for Mac (done by yourself, not discussed in the lab)

You may also find the department's information about sharing files and CVS version control to be helpful, along with the SVN offered by the CVSS.

Schedule

There are a number of intermediate deadlines that you must meet in order to ensure a successful project. Descriptions for each of the required checkpoints will be described on separate pages. To get an idea of an appropriately sized project, the one from a previous term is about right.

The cover page to be turned in with all assignments. For every due date below, the deadline is 11:59 pm.

Monday, January 16: Project proposals due
Monday, February 13: E/R Diagram and Schemas
Monday, February 27: Formal specification
Friday, March 31: Completed Project
Demos: Monday, April 3 and Wednesday, April 5: Sign up for demos

Talking to the TAs vs. submitting to the directories

As mentioned in class, it is recommended that you go over your milestone with the TA in tutorial who is assigned to look at projects, and the TA can give you feedback and check off your checkpoint there. If you do so, please turn in the files as well, so that we have a record in case something goes wrong. You may also talk to the TAs during their office hours. It is recommended to talk to the same TA throughout the term, but it is not required.