The requirements below partially describe a garage management system that is used for managing day to day activities of garages (of a company). The system keeps track of customers, vehicles, bookings,...

Draw a UML class diagrams with the following requirements.

Extracted text: The requirements below partially describe a garage management system that is used for managing day to day activities of garages (of a company). The system keeps track of customers, vehicles, bookings, payments and employees. Draw a UML class diagram describing an object- oriented system using the list of requirements below. 1. The system must support two types of customers: individual and company. 2. The system must be able to store multiple contact details for each customer. 3. The system must allow customers to own multiple vehicles. 4. The system must support two types of employees: staff and mechanic. 5. Each garage has at least one employee. 6. The system must allow customers to book a service for a vehicle. 7. Each booking must be made for a single garage. 8. The system must not allow an employee to work in more than one garage. 9. The system must assign only one mechanic to each booking. 10. The system must create one bill for each booking. 11. A bill consists of at least one service and car parts. 12. The system must allow each garage to offer several services. 13. The system must be able to ack payments. 14. Each payment is made to pay a bill. 15. The system must support these payment methods: card, cash and check. 16. Each payment must be made with one of the supported payment methods. 17. The system must track the staff who received the payment.