Phase II

You will pick an application area that you find interesting and store its information in a database. We may have several real projects available, on a first-come first-served basis, that involve creating a DB for an actual "client" within the University. We'll let you know more about these opportunities, if they work out, as soon as possible.

To date, we have just one project available, so most of you should start thinking about what you want to model in your database. The available project may be quite challenging, so we encourage you to choose it only if you are very confident in your team's ability to come up with a good solution. A brief description can be found here. Let Bart know if you want to choose this project.

For this phase of the project, you will submit the following, in hardcopy form, by the beginning of class on the due date:

1. One or more paragraphs, in English, describing the application area.
2. A complete E/R diagram for the information that will be stored in the database. As a rough guideline, an E/R diagram with 4 or 5 entities is usually sufficiently complicated, so pick your application area accordingly.
3. A list of any integrity constraints that your data should satisfy that aren't already covered by the E/R diagram (e.g., "nobody named 'Fred' is allowed to make less than $100000 per year").
4. A description of the "application" level of your system: i.e., what functionality will be performed by your web interface, etc. In general, this web-based application level should be able to handle the common tasks of your system: A user should typically not need to manipulate the database directly for any reason once the system is up and running. The DBA, of course, should always be able to do so!