Time left 1:47 Type: External Relationships: Association: Patient Include: Make Payment Arrangements Create New Patient Extend: Generalization: Normal Flow of Events: 1. The Patient contacts the office regarding an appointment. 2. The Patient provides the Receptionist with his or her name and address. 3. The Receptionist validates that the Patient exists in the Patient database. 4. The Receptionist executes the Make Payment Arrangements use case. 3. The Receptionist asks Patient if he or she would like to make a new appointment, cancel an existing appointment, or change an existing appointment. If the patient wants to make a new appointment, the S-1: new appointment subflow is performed. If the patient wants to cancel an existing appointment, the S-2: cancel appointment subflow is performed. If the patient wants to change an existing appointment, the S-3: change appointment subflow is performed. 6. The Receptionist provides the results of the transaction to the Patient. Subflows: S-1: New Appointment 1. The Receptionist asks the Patient for possible appointment times. 2. The Receptionist matches the Patient's desired appointment times with available dates and times and schedules the new appointment. S-2: Cancel Appointment 1. The Receptionist asks the Patient for the old appointment time. 2. The Receptionist finds the current appointment in the appointment file and cancels it. S-3: Change Appointment 1. The Receptionist performs the S-2: cancel appointment subflow. 2. The Receptionist performs the S-1: new appointment subflow. Alternate/Exceptional Flows: 3a The Receptionist executes the Create New Patient use case. S-1.2a1: The Receptionist proposes some alternative appointment times based on what is available in the appointment schedule. 4-1, 2a2: The Patient chooses one of the proposed times or decides not to make an appointment. Q1.R3. Stat the use of Use-Case Name, Primary Actor, Trigger, and Relationships items in the process of Verifying and Validating the analysis models