Out: 24 February 2009
Due: 18 March 2009, 5:20pm, one per team

You must have a partner in order to complete this assignment. No assignment will be accepted if not completed as a team of two. If you do not have a teammate, email me immediately or let me know in class. Thank you for your cooperation.

Design E-R and relational models for the database supporting your on-line stock trading system. Your E-R and relational models should conform to the specification and requirements given in the Project Specification Document. All work should be in Word, Visio, or some other approriate document-preparation software. Hand in a hardcopy of your assignment in class on March 18. Make sure your documents are stapled together and your names are clearly indicated on the first page.

You must work in teams of two on all project assignments. Let me know if you do not yet have a partner and I will find you one.

Your document is required to contain the following information:

• The name of your team (i.e. this should also be the name of your online trading system)
• The names and e-mail addresses of the two team members
• E-R diagram capturing the conceptual design of your database system. Your E-R diagram should look like the ones in the course textbook. That is, rectangle shapes should be used for entity types, diamond shapes should be used for relationship types, etc.
• Brief rationale (in English) for your E-R model
• Relational model of your database system, based on your E-R design. Your relational model should be given in the form of SQL 92 or SQL 99 CREATE TABLE|VIEW|INDEX etc. statements. Try to use those features and only those features of SQL supported by Sybase or MySQL.
• The SQL description of your relational model should include as many integrity constraints as possible, including domain, key, and referential integrity constraints.
• A list of functional dependencies of the form X -> Y (where X and Y are sets of attributes) capturing any additional integrity constraints on your database system. (Do not, for example, include functional dependencies that express key constraints.)
• Brief rational (in English) for your relational model.