Skip to content

Detailed Use Case Descriptions

raniaouassif edited this page Mar 15, 2021 · 32 revisions

Table of Contents

USE CASE: SIGN IN and LOGIN

Use Case Diagram

Author: Ege Karadibak

Identifier: Req. 1,2,3

Actor: User

Intention: Creating an account, logging into the account

Precondition: The user must have an internet connection.

Steps for the main scenario for Sign up :

  1. The system asks the user for their first name, last name, username, email, password, and optionally the phone number.
  2. The system validates that the user’s information is correct.
  3. User presses the sign-in button.

Alternative scenarios for Sign up:

2a. The system determines that the username is already taken, the system takes the user to step 1.

2b. The system determines that the given email is already associated with an account, the system takes the user to step 1.

3a. The system deletes the user’s account.

Steps for the main scenario for Login:

  1. The system asks for the user’s login information.
  2. The user gives their login information to the system.
  3. The system validates that the user’s information is correct.
  4. The system finds out the type of user from the credentials.
  5. The user logs in to the system.

Alternative scenarios for Login:

1a. The login information of the user is incorrect.

1a.1 The system redirects to step 1 where the user enters the login information.

Post Condition (success): The user has an account on the platform.

Post Condition (success): The user logs in successfully.

Post Condition (failure): The system deletes the user account.

USE CASE: BOOK APPOINTMENT

Use Case Diagram

Author: Rania Ouassif

Identifier: REQ. 3,4,11

Actor: Customer

Intention: Book Appointment

Precondition: The user must have an internet connection and must have an account.

Steps for the main scenario:

  1. The system asks for the user’s login information.

  2. The user gives their login information to the system.

  3. The system validates that the user’s login information is correct.

  4. The user is logged into the system as a customer.

  5. The user selects the book appointment option in the system which is only available to customers.

  6. The system notifies the customer that no more than three services per appointment can be selected.

  7. The user selects up to three services.

  8. The system asks the user to choose the desired date or starting and ending dates for the booking.

  9. The system displays the availabilities with regards to the date(s) and services chosen, by specifying the date, the start time, the end time, and the name of the technician(s) for the appointment.

  10. The user selects one appointment slot.

  11. The system displays the price of each service and then the total.

  12. The user confirms by pressing the book appointment button.

  13. The system directs the customer to the appointments view.

  14. The user receives a confirmation message for the booking.

Alternative scenarios:

1a. The user enters incorrect login information. 1a.1 The system redirects to step 1 where the user enters the login information.

7a. The user chooses more than 3 services. 7a.1 The system displays the error message: "Please, select at most 3 services".

9a. The system determines that no available appointment slot is available for the date(s) or service(s) chosen. 9a.1 The system displays the message: "No available appointment slot for the chosen date. Please select another appointment date".

12a. The user selects the button Book Later 12a.1 the system redirects the customer to the main view.

Post Condition (success): The user books the appointment and can view it on the list of appointments.

Use Case: Create Schedule Of Appointments

Use Case Diagram

Identifier: REQ. 2

Author: Anandamoyi Saha

Actor: Administrative Assistant

Intention: Create a schedule of appointment spots

Precondition: The user must have an internet connection. The user must have an account as an administrative assistant.

Steps for the main scenario:

1.The system asks for the user’s login information.

2.The user gives their login information to the system.

3.The system validates that the user’s login information is correct.

4.The user is logged in to the system as an administrative assistant.

5.The user selects the creation of schedule option in the system which is only available to the administrative assistant.

6.The user requests the system that they would like to create an appointment spot.

7.The system asks the user to select the date, the start time and end time of the appointment.

8.The user chooses, the date, the start time and end time of the appointment.

9.The system shows available technicians to the user.

  1. The user selects the technicians to be assigned to the appointment.

11.The system validates that the right number of technicians is assigned and that the availability of the technicians match the time of the appointment.

12.The appointment spot is created in the system.

13.The user may repeat steps 6 to 12 until there are no more available technicians.

Alternative scenarios:

1a. The login information of the user is incorrect.

1a.1 The system redirects to step 1 where the user enters the login information.

8a. The time of appointment chosen by the user overlaps with another appointment.

8a.1 The system redirects to step 7 and continues the following steps.

9a. There are no available technicians for the selected time of the appointment.

9a.1 The system redirects to step 7 and continues the following steps.

11.a. The right number of technicians has not been assigned.

11.a.1 The system redirects to step 10 and continues the following steps.

Use Case: Make Payment

Use Case Diagram

Author: Venkata Satyanarayana Chivatam

Identifier: Req. 6,7

Actor: User

Intention: Make payment for the appointment booking

Precondition:

1.Success: Thank you! Your payment was successful.

2.Fail: Your Payment failed, Please try again

Steps for the main scenario of make payment :

  1. The System asks the user to enter the login credentials
  2. The User logs into the system as customer with valid credentials
  3. The system re-directs to the Customer home page
  4. The Customer books an appointment with desired service and time slot
  5. The System redirects to the checkout page
  6. The Customer chooses a payment option
  7. The System opens a dialog box with payment credential blanks
  8. The User fills in the required payment credentials
  9. The System processes the payment
  10. The System shows a “successful payment” message box
  11. The System sends a message and an email to the user with the appointment summary and payment Invoice.

Alternative scenarios:

2a. The user logs in with invalid Customer credentials.

2a.1 The System gives an error message and asks to enter login credentials again.

8a. The user leaves a box empty.

8a.1 The System shows a “!” symbol with error message beside the corresponding box.

8b The user fills in invalid payment credentials.

8b.1 The system will give an error message in dialog box.

9a. If the User chosen payment method have insufficient funds.

9a.1 The System gives a “Failed payment’ message and asks.

9a.1.i The System asks the user to choose another payment method.

9a.1.ii The System asks the user to try again with the same payment method.

Use case: System messages

Use Case Diagram

Author: Elie Ruban

Identifier: Req. 12, 13, 14

Actor: Customer, Technician(s)

Intention: Get a confirmation of a booking or a cancellation, send reminders

Precondition: The customer must have an internet connection.

Steps for the main scenario for System messages :

  1. The system sends monthly reminders to customers to book appointments.

  2. The customer books a service at a specific time slot.

  3. The system sends a confirmation message to the customer and the technician(s) with the name of the customer, the date, the time slot, the name of the technician(s) and the service(s) desired.

  4. The system sends a reminder to the customer and the technician(s) on the day of the appointment.

Alternative scenarios for System messages :

3a. The customer cancels the booking.

3a1. The system sends a confirmation message to the customer and the technician(s) with the booking information. The system is redirected to step 1.