Database Systems

CS-377: Spring 2004

Database Population

DATABASE POPULATION MILESTONE:

Deadline: Friday, April 9th, in class, turn in your project notebook

After the proposal divider:

	any revised proposal, if required, clearly marked with a Last modified: date,
	any intervening proposal modifications,
	your original proposal, including my comments and annotations, along with all prior proposals with annotations.

After the model divider:

	your revised model, if required, clearly marked with a Last modified: date,
	any intervening model modifications,
	your original model, including my comments and annotations.

Make sure that your latest model included here corresponds with the design given in the next section as well as the newly created contents section. In other words, I expect the topmost current proposal, model, design, and contents to be up to date and self consistent.

After the design divider

	your revised design, if required, clearly marked with a Last modified: date,
	any intervening design modifications,
	your original design, including my comments and annotations.
	In addition to the materials in this section from before, I expect you to use your set of functional dependencies and to argue BCNF for your set of relations. If any of your relations is not in BCNF, then perform the appropriate decomposition to bring it into BCNF. If any relation can be normalized to 3NF but not BCNF, see me so that I can verify.

After the (newly created and inserted) contents divider

Recall that each logical item in the contents section should have a last modified date.

I require a dated printout of the results of a SELECT * for every table in your final design. Each table's select statement should be preceeded by a prompt command including the name of the table.

Please use a monospaced font for these.

It is your responsibility to make sure that rows are readable and do not run on across more than one line each. To achieve this you may have to do one or more of the following:

Use a small font size

Print using landscape instead of portrait orientation

Break a single table into multiple select queries with subsets of the attributes

In SQL*Plus, there is a COLUMN command that allows you to specify truncation during the display of very wide text columns (i.e. even though an attribute may be NVARCHAR2(256), only display the first 20 characters)

If using SQL*Loader, include printouts of your raw data file and your control file as well.

In terms of how much data you should include per table, the main idea is that you should include enough to make your project at least a non-trivial, demonstrable prototype. Trying to give some firmer guidelines, have at least 12 rows per table, in general, with additional rows as needed to make your database a reasonable prototype. (Fictitious data is fine.) As mentioned in class, I would expect at least one of your tables to grow substantially larger than this to support the set of queries and reports in a meaningful way.

Home | Syllabus | Schedule | Projects | Contact Information

All rights reserved, Thomas C. Bressoud and Denison University.
For problems or questions regarding this web contact bressoud@denison.edu.
Last updated: 01/30/04.