Here are the list of entities and attributes that i have started with. below these are the instructions to create a improved database and edit these and add some others.



customer_t
customerid (pk)
customername
customerstreet
customercity
customerstate
customerzip
creditlimit
salesrepid (fk) of employee_t

order_t
orderid (pk)
customerid (fk) of customer_t
customerponumber
orderdate
duedate
shipdate

order_line_t
orderid composite (pk), (fk) of order_t
productid composite (pk), (fk) of product_t
orderquantity

product_t
productid (pk)
productdescription
unitprice
stockquantity

fabricated_t
productid composite (pk), (fk) of product_t. productid
partid composite(pk), (fk) of product_t. productid
partquantity quantity of partid that goes into productid (example, 2 tires
in one bicycle)

product_supplier_t
producid composite (pk), (fk) of product_t
supplierid composite (pk), (fk) of supplier_t
vendorpartid this is the id the vendor (i. e., supplier) uses in their system), similar to
customerponumber in the order_t.
productcost
purchasedquantity

supplier_t
supplierid (pk)
suppliername
supplierstreet
suppliercity
supplierstate
supplierzip

employee_t
employeeid (pk)
employeename
employeestreet
employeecity
employeestate
employeezip
managerid (fk) unary

employee_course_t
employeeid combination (pk), (fk) of employee_t
courseid combination (pk), (fk) of course_t
completiondate

course_t
courseid (pk)
coursedescription

sales_commission_rate_t
employeeid (pk), (fk) of employee_t
commissionrate



using erwin, provide an erd diagram that adds the capability of tracking price changes to the database required for project 3. for example, products’ unit prices will change over time; therefore, for each productid, a given unit price will have a beginning date and an ending date. include both the printed erwin screenshot and the electronic version. think about the wording of the above paragraph carefully. since each the unitprice for each productid will change over time, and we need to store and maintain this information, unitprice then becomes a multi-valued attribute, and we know that this is unacceptable in 3rd normal form (3nf). since we must maintain 3nf, we must refer to the rules for handling a multi-valued attribute. in summary, you must create a new entity (i suggest the name price_history) that has a one-to-many relationship with product. unitprice must be removed from the product entity. price_history will have attributes of productid, startdate, enddate, and unitprice. since each productid will have multiple records in price_history, you must create a composite primary key for price_history based on two attributes (hint: unitprice is not one of