To gain real world experience in database design, teams of students will work with a local organization (small company, university department, campus organization, etc.) on a semester-length Database Design Project (DP). The DP starts with analysis of the organization's current methodology and needs, and proceeds through data modelling, design, and implementation of a prototype Relational Database, including queries, forms, and reports. Your design should not be limited by the current needs of the organization (feel free to add features/relations that your contact may feel are unnecessary). Teams should emphasize the structure of their design and richness of their queries rather than the user interface. Extra credit will be given for mathematical analysis involving IEOR methods. The organization must understand that your prototype is not a fully operational system (and that you will not provice maintainance and customer support after the class is over!).

• Contact Report: (1pg, every student) Find one organization who is interested in participating in the DP. Give a short description of the organization, their data, number of employees, your contact person and how you found him or her, existing database support (if any), current or future availability of PC platform to run MS Access, and your estimate of their level of enthusiasm (on a scale of 0-10, 10 is very enthusiastic).

• Proposal: (2pg, team, written) A detailed version of above for the organization selected and confirmed by the team. Contact Person at Organization and phone number. Current system. Availability of MS Access and PC/Windows. Estimates of Data size (number of records). Proposed benefits. Resources needed. Team member responsibilities. NOTE: All Team reports must include: Team number, Design Project Title, and date, as well as all team member names.

• DP Review I: (oral, <10 mins using Powerpoint) Project summary, textual summary of database requirements (similar to p. 44,45 of textbook). Simplified EER diagram (omitting most attributes, but including relationships and cardinality constraints) with at least 10 entities and 10 relationships. Project schedule. Turn in: 1 page Simplified EER Diagram.

• DP Review II: (oral, <10 mins using Powerpoint) Revised version of PR I plus: Revised EER diagram, Relational Design (schema), 5 "interesting'' queries in plain English (describe, do not implement them yet!) Interesting queries should be intuitively helpful to your client and incorporate IEOR methods, for example: ranking employees by some productivity metric, ranking products by profitability, fitting stochastic models for expected demand, scheduling employees or transportation, locating events (to minimize travel time), looking at seasonal trends, setting discount levels, computing correlations, setting warranty periods based on Mean Time Between Failures. Your Queries should demonstrate the the power of your database using the breadth of SQL. Each query must be justified in terms of organizational needs and described in plain text (not SQL yet!).

• DP Review III: (<=4pg, written) Executive Summary must include (in this order): project title, team number, team member names, client description, EER, screencapture of relational design in Access Relationship View, and 5 interesting queries in algebra or SQL. Note that the 4 page limit is firm. No cover pages or appendices!

• Final Presentations (oral, <10 mins using Powerpoint): Overall summary of PR I, II, III, and demonstration of Access implementation of your database design using screencaptures (there's not enough time to run Access live during the presentation: you are on the honor system not to doctor the screencaptures). Demonstration should be based on realistic examples of 5-10 tuples for the relations involved (please don't use joke names or data).

• Final Report: (<=20pg, written: submit 2 copies!). Revised 4 page Executive Summary. The other 16 pages is an expanded version including: Introduction describing client, previous approach and goals. 5 Queries: plain text, algebra (where possible), SQL. Access screen shots of at least 2 forms and 2 reports. Normalization analysis for your design: Indicate Functional Dependencies for 5 relations, at least one in 2NF, one in 3NF, and one in BCNF, explaining why they are not fully normalized why and how they might be normalized. 1 page signed letter providing client feedback: This can be faxed directly to me by the deadline at (510) 642-1403. Team members contributions. Discussion and Future work.