An easy ER diagram and database with following requirements

The company needs to keep track of the following information about parts:

- partNo unique (PK)

- partName

- partDescription

- currentPrice

- qty quantity of a part in stock (also referred to as Quantity On Hand (QOH))

Information that needs to be known about clients:

- clientCompId ID of the client comp

- clientCompName

- clientCity

- clientCompPassword

- moneyOwed

Information about purchase orders (POs)

- poNo

- clientCompID ID of the client comp.

- datePO date of the purchse order

- status

Each Purchase Order (PO) has a number of lines, each one denoting an order for a number of units of one part. Thus, for each part, the part number and its price need to be stored together with the quantity on order. Lines are assigned unique numbers starting at one for the first line, 2 for the second and so on. As prices for parts are subjects to change, the purchase price for each part on an order line must be stored in the DB also.

Draw the ER diagram and create the database