Assume you have determined the follow tables for the database: EMPLOYEE (EmployeeID, LastName, FirstName, Department, Position, Supervisor, OfficePhone, Office Fax, EmailAddress) STORE (StoreName, City, Country, Phone, Fax, EmailAddress, Contact) PURCHASE ITEM (PurchaseItemID, StoreName, Purchasing AgentID, Purchase Date, Item Description, Category, PriceUSD) SHIPPER (ShipperID, ShipperName, Phone, Fax, EmailAddress, Contact) SHIPMENT (ShipmentID, ShipperID, Purchasing AgentID, ShipperInvoiceNumber, Origin, Destination, Scheduled DepartureDate, ActualDepartureDate, EstimatedArrivalDate) SHIPMENT_ITEM (ShipmentID, ShipmentItemID, PurchaseItemID, Insured Value) SHIPMENT_RECEIPT (ReceiptNumber, ShipmentID, PurchaseItemID, Receiving AgentID, ReceiptDate, ReceiptTime, Receipt Quantity, isReceivedUndamaged, DamageNotes) TO DO:
Create a MySQL Workbench Design.

When making changes to optimize part of a processor, it is often the case that speeding up one type of instruction comes at the cost of slowing down something else. for example, if we put in a complicated fast floating-point unit, that takes space, and something might have to be moved farther away from the middle to accommodate it, adding an extra cycle in delay to reach that unit. the basic amdahl's law equation does not take into account this trade-off. a. if the new fast floating-point unit speeds up floating-point operations by, on average, 2ă—, and floating-point operations take 20% of the original program's execution time, what is the overall speedup (ignoring the penalty to any other instructions)? b. now assume that speeding up the floating-point unit slowed down data cache accesses, resulting in a 1.5ă— slowdown (or 2/3 speedup). data cache accesses consume 10% of the execution time. what is the overall speedup now? c. after implementing the new floating-point operations, what percentage of execution time is spent on floating-point operations? what percentage is spent on data cache accesses?