Document the existing internal control structure based on your current design. You may refer to some controls we discussed in Chapter 13. You need to specify at least TWO threats and explain related controls your team can provide to mitigate each of them. For example, the threat to the database could be entering an invalid suppliei when an employee enters the purchase order. To control the threat, we can apply the validity check by comparing the supplier ID which the employee enters with the purchase order with the supplier ID in the supplier mater file to verify that the account exists. (Please do not use this example in your submission) REA Diagram Employee(CEO) Employee (Purchasing Clerk) Flower Inventory Order Inventory Vendor Employee Warehouse Clerk) Receive Order Employee (CEO) Employee (A/P Clerk) Cash Make Payment Vendor Page Notmalized Tables Other Attributes Table Name Primary Key Forcign Key PreparedEmployeeNo, AuthorizedEmployccNo, VendorNo PurchaseOrderNo PODate OrderInventory EmployeeNo, VendorNo, ReceiptDate PaymentNo, PurchaseOrderNo ReceiveOrder ReceiptNo PreparedEmployecNo, AuthorizedEmployeeNo, VendorNo, AccountNo, MakePayment PaymentNo PaymentDate, PaymentAmount, FlowerInventory ProductNo Description, QtyOnHand, ListPrice Cash AccountNo AccountType, Bank, AccountBalance Vendor VendorNo VendorName, VendorAddress, Balance Employee EmployeeNo EmployeeName, EmployecAddress, DateStarted, JobTitle, Phone FlowerInventory- PurchaseOrderNo, OrderInventory QtyOrdered, OrderPrice ProductNo FlowerInventory- ProductNo, ReceiveOrder ProductCondition ReceiptNo 2. Note: For Orderlnventory table, we do not need to have ProductNo as a forcign key to link FlowerInventory table. Instead, Flowerlnventory-OrderInvetory table will link the OrderInventory table and Flowerlnventory table together. For RecciveOrder table, we do not need to have ProductNo as a foreign key to link FlowerInventory table. Instead, FlowerInventory-ReceiveOrder table will link the ReceiveOrder table and FlowerInventory table together.