Draw a Collaboration diagram for the Written Use Case description of a Purchase process in a bookstore, as provided below: Use Case Title: Primary Actor: Level: Stakeholders: Preconditions: Minimal Guarantee: Success Guarantee: 10. Main success scenario: 1. Customer selects book 2. 3. 4. 5. 6. 7. 8. 9. 2a) 5a) Hint: Extensions: O Purchase Books Customer O Kite (high, more general) Customer, Shop assistant Customer has selected book Customer is informed if the book cannot be bought Customer pays for and receives their book Shop Assistant checks stock for book Discount is calculated Tax is calculated Total amount due is calculated Shop Assistant informs customer of the Total price Customer confirms order, pays with Credit card Customer's Credit card is debited with the amount due Inventory is adjusted (decremented) Assistant gives the customer the ordered product and receipt The item is unavailable --- Inform customer Credit card will not accept charge - transaction is cancelled. Use only the Main Success scenario to draw the diagram. The Customer Actor interacts with the system through a Shop Assistant boundary object. Also, consider one Control object (e.g. Store Control), and two entity objects: Inventory, containing available book items' data, and CustomerCredit Card, containing Customer's Credit Card data). Consider all calculations to be performed by the Control class on itself. (11 marks) (b) Convert the Collaboration Diagram you have prepared in the previous task (a) into Analysis Class Diagram. Hint: O Consider that all messages presented on the Collaboration diagram become responsibilities of the receiver object class (i.e. they become methods of that class). Also, consider that each book instance of the inventory class has a unique identifier Item No, and attributes like Title, Description, and Price. The unique identifier of the Customer Credit Card class is Card Number, and attributes are name, expiration, and CVV.