Draw a UML sequence diagram with the given class diagram of a dental clinic management system and the following use case. The specifications below describe the interaction among system objects when performing one of the systems use cases. This use case explains a patient booking an appointment at a dentist.

Preconditions of this use case: The patient already logged-in and several objects already exist in the system memory. Some of these objects are GUI (an object representing the graphical user interface of the system), patient (instance of Patient), registry (instance of Registry), dentist (instance of Dentist).

1. The patient searches for dentists availability using GUI.
2. GUI calls the patient object to search for a dentist for the given date.
3. The patient object calls the registry object to find the available times.
4. The registry calls all dentist objects to get their availability.
5. The registry returns the list of availabilities to the patient object and the patient object to the GUI.
6. If the returned list is empty, then GUI displays (the patient) no available dentists message.
7. Otherwise, GUI display the available times to the patient.
8. The patient selects one of the available times and dentists on the GUI.
9. GUI calls the patient object to book an appointment.
10. The patient object calls registry to create an appointment for the selected date and time and dentist.
11. The registry object creates a new appointment object and adds this appointment to the dentists schedule.
12. The registry returns the appointment object to the patient object and the patient object to GUI.
13. GUI displays appointment details to the patient.

HINTS:

You can use List notation for your return messages where an object return a list of availabilities.

Please use the names below for the actor name and messages in your diagram:

Patient, search availability, no available dentists, display available times, select a time and dentist, display appointment details

Vangm Registry +getAvailable Times(d: Calendar): List