The following tables and attributes exist in a relational database of Rapid Stream Inc.

1. Draw a complete UML Class diagram for this database. Ignore cardinalities (not required). Use Word, Visio, or Draw.IO to draw the UML Class diagram.

   a. You will not get any credit if your diagram is not an UML class diagram.

   b. You must indicate PK and FK in your diagram.

   c. Identify any errors or potential problems you see in the database design (such as missing tables, missing FK, etc.). You need to provide solution to the problem. Type your answers in the Word file.

   d. Important hints:

   1. Identify each table as R, E, A or a relationship table can speed up your thought process.

   2. You also need to think about business processes to list the Event tables in correct sequence.

   3. If you have time, check multiplicities. With multiplicities, you may find more issues with the

      database design.

2. Email your file to your section GA: (1) write A333-UML-your name for the subject line, (2) name your file RS-UML by your name, and (3) make sure your name are on the UML Class diagram (e.g., as the header of the Word file or use a textbox for Draw.IO).

Table Name

Receive goods Order goods Receive Inventory Inventory

Cash Request goods Pay for goods Request Inventory Order Inventory Employee Order Receive V endor

Attributes

InvReceipt#, date, condition of goods, receiving clerk#, carrier, vendor# PO#, date, expected receiving date, total amount, vendor#, purchasing clerk# InvReceipt#, item#, quantity Item#, description, standard unit cost, list price account#, balance Requisition#, date, date needed, vendor#, PO#, supervisor#, purchasing clerk# check#, date, amount, vendor#, account#, InvReceipt#, cashier# Requisition#, item#, quantity PO#, Item#, actual unit cost, quantity Employee#, name, address, phone, SSN#, position title PO#, InvReceipt# vendor#, name, address, contact person, phone, fax, email