DAT 380 TEAM Week 2 – Fine Diamond Database Design Options

19 May No Comments

DETAIL STORE

Store ID – PK CustomerID – FK Address

City

State Zip

INVENTORY

InventoryID – PK

Cost Price Carat Cut Clarity Color

DIAMOND CLARITY

ClarityID – PK InventoryID – FK IF

VVS1 VVS2 VS1 VS2 SI1 SI2 I1

I2

I3

DIAMOND CUT CutID – PK

InventoryID – FK

Excellent Good Very Good

DIAMOND COLOR

ColorID – PK InventoryID – FK Colorless D,E,F

Near Colorless G,H,I,J,K Faint Yellow K,L, and M

CARAT

CaratID – PK InventoryID – FK Weight

ORDER

OrderID – PK InventoryID – PK FK CustomerID – PK FK

OrderDate ShippedDate Quantity

CUSTOMERS

CustomerID – PK

Customer Name

Address City State Phone#

Our team has selected the relational model because each table within the database has a unique primary key that contains specific data information and each table within the database is linked together allowing each department to view the data that is only needed. By allowing workstations to access,

/

update, and share

information




Click following link to download this document

DAT 380 TEAM Week 2 - Fine Diamond Database Design Options.docx