Database Design and Normalization: A Case Study of UPS Company, Study Guides, Projects, Research of Management Information Systems

UPS company prides itself on having up-to-date information on the processing and current location of each shipped item. To do this, UPS relies on a company-wide information system. Shipped items are the heart of the UPS product tracking information system. Shipped items can be characterized by item number (unique), weight, dimensions, insurance amount, destination, and final delivery date. Shipped items are received into the UPS system at a single retail center. Retail centers are characterized by their type, uniqueID, and address. Shipped items make their way to their destination via one or more standard UPS transportation events (i.e., flights, truck deliveries). These transportation events are characterized by a unique scheduleNumber, a type (e.g, flight, truck), and a deliveryRoute.

Typology: Study Guides, Projects, Research

2022/2023

Uploaded on 07/21/2023

sandaruwan-m-herath
sandaruwan-m-herath 🇱🇰

5 documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1. Create an Entity Relationship diagram that captures this information about the UPS company.
Be certain to indicate identifiers and cardinality constraints.
The "Shipped Items" entity represents the shipped items, with "ItemNumber" as the primary key
(PK). It has a one-to-many (1..*) relationship with the "Retail Centers" entity, indicated by the
line with crow's foot at the "Shipped Items" side.
The "Retail Centers" entity represents the retail centers, with "UniqueID" as the primary key
(PK).
The "Transportation Events" entity represents the transportation events, with
"ScheduleNumber" as the primary key (PK).
There is a one-to-many (1..*) relationship between "Retail Centers" and "Transportation
Events," indicated by the line with crow's foot at the "Transportation Events" side.
Shipped Items
Retail Centers
Transportation Events
1
1
1
pf3
pf4
pf5

Partial preview of the text

Download Database Design and Normalization: A Case Study of UPS Company and more Study Guides, Projects, Research Management Information Systems in PDF only on Docsity!

1. Create an Entity Relationship diagram that captures this information about the UPS company. Be certain to indicate identifiers and cardinality constraints.

 The "Shipped Items" entity represents the shipped items, with "ItemNumber" as the primary key (PK). It has a one-to-many (1..) relationship with the "Retail Centers" entity, indicated by the line with crow's foot at the "Shipped Items" side.  The "Retail Centers" entity represents the retail centers, with "UniqueID" as the primary key (PK).  The "Transportation Events" entity represents the transportation events, with "ScheduleNumber" as the primary key (PK).  There is a one-to-many (1..) relationship between "Retail Centers" and "Transportation Events," indicated by the line with crow's foot at the "Transportation Events" side.

Shipped Items Retail Centers

Transportation Events

2. Normalize all the relations extracted from the above Entity Relationship diagram in Part 1.

First Normal Form (1NF):

  1. Shipped Items (ItemNumber, Weight, Dimensions, InsuranceAmount, Destination, FinalDeliveryDate)
  2. Retail Centers (UniqueID, Type, Address)
  3. Transportation Events (ScheduleNumber, Type, DeliveryRoute)

Second Normal Form (2NF):

No partial dependencies exist in the relations, so they already satisfy 2NF.

Third Normal Form (3NF):

No transitive dependencies exist in the relations, so they already satisfy 3NF.

The normalized relations are as follows:

 Shipped Items (ItemNumber, Weight, Dimensions, InsuranceAmount, Destination, FinalDeliveryDate)  Retail Centers (UniqueID, Type, Address)  Transportation Events (ScheduleNumber, Type, DeliveryRoute)

  1. Save the "Retail Centers" table.
  2. Create the "Transportation Events" table with the following fields:  ScheduleNumber (Primary Key): Text data type.  Type: Text data type.  DeliveryRoute: Text data type.
  3. Save the "Transportation Events" table.
  4. Close the table design view.
  5. Click on the "Database Tools" tab and select "Database Relationships."
  1. Drag and drop the "ItemNumber" field from the "Shipped Items" table to the "UniqueID" field in the "Retail Centers" table to create a relationship between them.
  2. Drag and drop the "UniqueID" field from the "Retail Centers" table to the "ScheduleNumber" field in the "Transportation Events" table to create a relationship between them.
  3. Set the relationship options, such as referential integrity and cascade update/delete, according to your requirements.
  4. Save the database.