You run a small antique store that sells antique furniture to local customers. All your records are on paper, and you have been maintaining a simple spreadsheet to keep track of your orders as well. The spreadsheet looks like the one below. However, the business is expanding and the spreadsheet is getting unmanageable. Currently, there is considerable redundant data, and more redundant data will be added with every new customer order. So the first step is for you to normalize the data in the spreadsheet (In other words, identify different themes in this spreadsheet and break it down to several tables). You will need to set up a well-designed database to effectively keep track of the information.
Deliverable:
In a text/word file, write out the “Model” (i.e., relation schema) of your database based on the normalization process covered in class, i.e., break the list down to smaller, well-formed tables with each table only covering a single theme. You might want to add extra fields to make your database make more sense.
The relationship schema should use the following format:
YourInitials_TABLE_NAME (Primary Key, other Elements, etc.) (if there is a foreign key, italicize it)
Prefix each attribute (including PKs and FKs) with your initials (10 points will be deducted from your grade if without your initials prefixed for each table name and each attribute name).
Denote Primary Key, Foreign Key, and relationships. For each relationship, draw a directional arrow pointing from foreign key attribute towards its “parent” primary key.