UML Data modeling

Draw UML diagrams for the following cases

Part 1: A metropolitan library network is building a system to manage its collections.

Each physical library item - book, tape cassette, CD, DVD, etc. could have its own item number. - book, tape cassette, CD, DVD, etc. could have its own item number. The items may be barcoded. The purpose of barcoding is to provide a unique and scannable identifier that links the barcoded physical item to the electronic record in the catalog. A barcode must be physically attached to the item, and the barcode number appears in the electronic record of the item.

Barcodes on library items could be replaced by RFID tags. The RFID tag can contain an item's identifier, title, material type, etc. Its advantage consists in the ability to read it using an RFID reader, without the need to open a book cover or CD/DVD case and scan it with a barcode reader.

Part 2: A company wants to build a system for online shopping management. The system should maintain the customer information including the id, address, phone number and email. Each customer has unique id and is linked to exactly one account. The customer account includes shopping cart and orders information.

Customers could register as a web user to be able to buy items online, but they are not required to be a web user because purchases could also be made by phone or by ordering from catalogs. Web users have login name which also serves as unique id.

Customers can add items to the shopping cart. The shopping cart needs to store the quantities and the unit price of the products added. Each product has a unique id, a name and supplier information. When the customer makes an order, the system will generate the order information including the unique order id, ordered date, estimated ship date, shipping address and the total cost of the order. After an order is made, the customer can then make a payment, and the customer can choose to make a payment of several orders together.