UML Diagrams for a simple Hotel Management System in Java with Design Patterns and MVC, and a simple documentation

I need only the UML Diagrams for a simple Hotel Management System in Java. IMPORTANT: the system must be designed with MCV architecture and use of Design Patterns (at least 6-8 in total, at least 1 design pattern for all type of design pattern (creational, structural, behavioral)) The Hotel Management System should be a basic one, whit this requiriments: The users of the management system consist of hotel guests and receptionist. Only people with this authority can log in to the system and perform the operations defined to them. Hotel customers' authority over the system is only to book a room at the hotel and to cancel this room reservation. The authority of the hotel receptionist on the system is to make room reservation, cancel the room reservations, make check-in and check-out, reserve the rooms and send the invoice to the customers. Customer information: -Name -Surname -Telephone number -Email -Specify whether the customer is a loyal customer, based on the number of bookings he has made in the past Room information -Room number -Room type and base price (editable by the user) -Extra services for the room (like wi-fi, breakfast, room service) -Internal Telephone number -Specify if the room is booked, free or reserved (the user can determine if the room is reserved. The room is booked if it has been booked in the reservations menu) Bookings -Date in and out -Amount due by the customer, which also depends on the extra services. The import may vary according to the season, in a percentage determined by the user. A loyal customer can receive an extra discount. -Function for print and send the invoice to the customer I need only the UML diagrams for this project. This are the UML diagrams i need: Class Diagrams which show all classes and their relationships 2 Sequence Diagrams, 1 for receptionist and 1 for customer some Use Cases VERY IMPORTANT: i need a UML diagram showing the implementation of MVC Architecture, and 1 UML diagram FOR EACH Design Pattern involved, showing all the classes involved in that Design Patterns. Finally: a little doumentation that motivates the choices of Design Patterns.