Part 1. Data Model for Shipping Ticke A. The following figure shows a shipping ticket sent to a customer. Prepare an entity-relationship diagram (ERD) reflecting the data contained in the shipping ticket. TIM Press Shipping Ticket Sold to Customer Name: Clint Eastwood Street Address: 8808 N. Campside Dr City, State, Zip: Richardson, TX 75088 Phone Number 972-884-0000 Customer ID 1930M31 ecipient Name: Harry Callahan Street Address: 2414 W. Seashore Blvd City, State, Zip: Virginia Town, VA 23450 Phone Number: Recipient ID: 1971D23 20100214AQ May 14, 2013 16, 2013 Order ID: Sales Manager: Don Siegel Book ID Author(s) Order Date: Shipping Date Sales ID: 1912026 Title Quantity Unit Price LR7792 W2231 WR2232 Luce, Raiffa Games and Decisions Whinston Whinston, Rays Companion Guide to Operations Research $79.95 $115.95 $25.99 Introduction to Operations Research 2 Total: $247.88 Carrier: United Parcel Service Tracking Number: 201002147787283 Carrier Contact No: 800-008-0008 Note: The ERD must have Customer (Customer ID as the PK), Recipient (Recipient ID as the PK), Author (Author ID as the PK), Carrier (Carrier Name as the PK), and many other entities. Assume that there is only one customer, one recipient, and one sales manager for each order; further all items of an order are carried by only one carrier. The ERD must include not only entities and relationships with cardinalities but also all attributes available in the shipping ticket. Underline or clearly mark the primary key of every entity. Enter all foreign keys in the ERD. There must be no many-to-many relationships and no multi-valued 1B. Convert the above ERD into a relational model