Data ase Desig Ter Proje t Note: This project must consist of your own work completed during this semester. Requirments Analysis Overview of Company and Product(s): Due 6:00 p.m. Friday Week 3 1. Provide a one page document entitles "Company Overview" that identifies: a. Your name & student number b. Your company c. Type of company (wholesaler or retailer) d. Short description of the company e. Product i. Identify at least 6 characteristics (attributes), such as id or code, type, description, size, color, price, and so on ii. Company and product cannot be related to music, phones, games, or computers 2. Submit to TP_Week3 drop box Customer Sales Invoice: Due 6:00 p.m. Friday Week 4 1. Modify the sample Customer Sales Invoice so that it reflects your company and the company's product. Although the company (and website) can advertise several products, the invoice must be based on only one product 2. Submit to TP_Week4 drop box Entity & Attribute Identification: Due 6:00 p.m. Friday Week 4 1. Identify the following from the Customer Sales Invoice : a. Entities b. Attributes i. Name ii. Data type (optional) iii. Length (optional) c. Unique Identifier (UID) 2. Submit to TP_Week4 drop box 1 Conceptual Design ER Diagram: Due 6:00 p.m. Friday Week 5 1. Create an ER diagram based on the customer invoice. Only nclude the entities identified in the entity & attribute identification: a. Entities b. Attributes i. Name ii. Data type (optional) iii. Size (optional) c. Unique Identifiers d. Named Relationships e. Optionality and Cardinality f. Foreign Keys g. Relationship Strength h. ERD language for the relationships 2. Create a second ER diagram that resolves many-to-many relationships 3. Submit to TP_Week5 drop box Logical Model Normalization & Relational Schema: Due 6:00 p.m. Friday Week 6 1. Create a document called "Database Normalization" a. Normalize your database to 3NF b. Modify the ER diagram if necessary 2. Include a relationsal schema for each entity 3. Submit weekly document to TP_Week6 drop box Physical Model Physical Table Representation: Due 6:00 p.m. Friday Week 6 1. Convert the logical model to a physical model using a table format a. Create a table for each physical database table b. Include key type, optionality, column name, data type, length Implementation of Physical Model Create Database Tables: Due 6:00 p.m. Friday Week 7 1. 2. 3. 4. Construct CREATE statements for each table Include IDENTITY and SEQUENCE columns (optional) Construct INSERT statements and populate each table with at least 10 rows Submit to TP_Week7 drop box 2 Identify Business Rules/Database Constraints: Due 6:00 p.m. Friday Week 8 1. Create a document called "Business Rules/Database Constraints" a. List the physical database rules/constraints for:  NOT NULL  DEFAULT  Primary keys  Unique keys  Foreign keys  Check constraints a. List at least 3 business rules that must be programmed 2. Implement the constraints into the database creation statements 3. Submit to TP_Week8 drop box Constraint Testing: Due 6:00 p.m. Friday Week 9 1. Create a document called "Constraint Testing." Test each constraint and provide documentation that each constraint works 2. Submit to TP_Week9 drop box Project Submission: Due 6:00 p.m. Friday Week 10 1. Create a PDF document that contains: a. Table of Contents b. Requirements Analysis i. Overview of company and product(s) ii. Customer sales invoice iii. Entity & attribute identification c. Conceptual Model i. ER Diagram based on customer sales invoice ii. ER Diagram with many-to-many relationships resolved d. Logical Model i. Database normalized to 3NF ii. Relationsal schema for each entity e. Physical Model i. Database creation ii. Identify business rules/database constraints iii. Implement database constraints into database DDL iv. Constraint testing 2. Create a PDF document called c99999_TP, where c99999 is your student number. The PDF document will be a database proposal developed for the Vice President of IT. Submit your PDF document into the "TP_Week10" drop box 3