Final Project

The purpose of this project is to step through both the design and implementation phases of creating a database and appropriate applications. The subject of your database should be of your own choosing, either fictional or intended for actual use.

Defaults: It is assumed that

• you will work on your own
• you will use the departmental database server provided for class use
• applications will be coded using Java servlets or JSP on an Apache Tomcat web server or other web designs students may prefer.

Deliverables:

1. Title page
2. Table of contents
3. URL Tell us where to find the project.
4. Summary - This is a high level, English description of the mini-world to be modeled. This should include an informal discussion of the kinds of data to be stored and the application programs desired.
5. Logical Design - A description if the inter-relationships of the data items, including an E-R diagram.
6. Physical database design - A description of all tables and attributes. This step should discuss functional dependencies and normalization issues.
7. Physical application design - A description of all the desired applications, which tables each effect, and the I/O behavior of each.
8. User's guide - How to use what you have implemented. We will look at each project, and you need to be present for a demo.
9. Table contents - A list of your tables and the contents of each.
10. Implementation code - You do not need to implement all applications that you propose. For example, an application package may need 15 applications, while you need only implement 5 or 6. (Alternatively, instead of providing hardcopy of your code, you can provide a link from your website to a page with the code.)
11. Conclusion Describe what you have done and what you would do if you had more time.

Mechanism and dates:

• Part One - due Thursday, November 16

  This should include a hardcopy report of the summary, logical design (ER diagram), physical database design (relational tables), and an outline of the (proposed) physical application design. (This is essentially steps 4-7 above.) You do not need to have created any tables or written any code.

• Part Two - due Friday, December 8

  Send the full report by email to dou@cs.uoregon.edu. Please arrange to provide a demo to the GTF (451) and the instructor (551) before you submit your final report. (Students in CIS 551 are expected to do something extra. Students in CIS 451 are encouraged to do it for extra credit.)

• Warnings
  • Be sure that you have given access permission to the people that will be grading the project. The simplest way to do this is by a GRANT CONNECT TO PUBLIC statement.
  • Please do not incorporate a login mechanism with password protection, or anything of the sort.
  • Provide sample input data if you feel that it would make testing your project simpler.