Suppose that you have designed a database for Morgan Importing that has the following tables:

EMPLOYEE (EmployeeID, LastName, FirstName, Department, Phone, Fax, EmailAddress)

STORE (StoreName, City, Country, Phone, Fax, EmailAddress, Contact)

ITEM (ItemID, StoreName, PurchasingAgentID, PurchaseDate, ItemDescription, Category, PriceUSD)

SHIPPER (ShipperID, ShipperName, Phone, Fax, EmailAddress, Contact)

SHIPMENT (ShipmentID, ShipperID, PurchasingAgentID, ShipperInvoiceNumber, Origin, Destination, ScheduledDepartureDate, ActualDepartureDate, EstimatedArrivalDate)

SHIPMENT_ITEM (ShipmentID, ShipmentItemID, ItemID, InsuredValue)

SHIPMENT_RECEIPT (ReceiptNumber, ShipmentID, ItemID, ReceivingAgentID, ReceiptDate, ReceiptTime, ReceiptQuantity, isReceivedUndamaged, DamageNotes)

1. Do you think STORE should have a surrogate key? If so, create it and make required adjustments in the design. If not, explain why not or make other adjustments to STORE and other tables that you think are appropriate.

2.Specify NULL/NOT NULL constraints for each table column.

3.Specify alternate keys, if any

4.State relationships as implied by foreign keys and specify the maximum and minimum cardinality of each relationship. Justify your choices.

5.Explain how you will enforce the minimum cardinalities in your answer to question 4. Use referential integrity actions for required parents, if any. Refer to your book diagram as a boilerplate for required children, if any.