UC-005: Book Activity

by ADMIN 22 views

Overview

The Book Activity use case is a crucial part of the overall system, allowing travelers to book activities with ease. This use case is designed to provide a seamless experience for travelers, ensuring that they can book activities that meet their needs and preferences.

Actors

  • Traveler: The user who is interacting with the system to book an activity.

Related User Stories

  • UC-001: Searching and Booking Activities
  • UC-002: Searching and Booking Activities Details

Related Diagrams

Preconditions

Before the Book Activity use case can begin, the following preconditions must be met:

  • The traveler is on a screen that displays one or more activities.
  • The traveler has selected an action to book one displayed activity.
  • The traveler wants to finish booking the activity.

Basic Flow

The basic flow of the Book Activity use case is as follows:

  1. The system shows the details of the activity: The system displays the details of the activity that the traveler has selected.
  2. The system shows 3 available dates and times for booking the activity: The system displays 3 available dates and times for booking the activity at and around the known date and time for which the traveler wants to book it.
  3. The traveler chooses one of the available dates and times: The traveler selects one of the available dates and times for booking the activity.
  4. The traveler enters the number of people for whom they want to book the activity: The traveler enters the number of people for whom they want to book the activity.
  5. The system shows the chosen details for the booking: The system displays the chosen details for the booking, including the date and time, number of people, and any other relevant information.
  6. The system confirms the details: The system confirms the details of the booking with the traveler.
  7. The system creates the booking: The system creates the booking and sends a confirmation to the traveler.
  8. The system informs the traveler that they will be notified after the booking is confirmed by the guide: The system informs the traveler that they will be notified after the booking is confirmed by the guide.

Alternative Flows

There are several alternative flows that can occur during the Book Activity use case:

  • 2a. The date and time for which the traveler wants to book the activity are unknown from the previous interaction: If the date and time for which the traveler wants to book the activity are unknown from the previous interaction, the system will prompt the traveler to specify the date and time. The system will then repeat step 2.
  • 3a. The traveler is unsatisfied with the available date and time options and wants more options: If the traveler is unsatisfied with the available date and time options and wants more options, the traveler can choose the option to load more available dates and times for the activity. The system will extend the available dates and times with 3 additional options and repeat step 2 with the extended availabilities.
  • 3b. The traveler is unsatisfied with the available date and time options and does not want to make the booking: If the traveler is unsatisfied with the available date and time options and does not want to make the booking, the traveler can choose the leave the booking option. The system will cancel the booking in progress and the interaction will end with no booking.
  • 6a. The traveler does not confirm the booking because they want to change something: If the traveler does not confirm the booking because they want to change something, the traveler can return back to any of the previous booking steps.
  • 6b. The traveler does not confirm the booking because they want to cancel the booking in progress: If the traveler does not confirm the booking because they want to cancel the booking in progress, the traveler can choose the leave the booking option. The system will cancel the booking in progress and the interaction will end with no booking.

Postconditions

The postconditions of the Book Activity use case are as follows:

  • The booking is created as required by the traveler.
  • If the user cancels the booking in progress, no booking is created.

Frequently Asked Questions

In this section, we will answer some of the most frequently asked questions related to the Book Activity use case.

Q: What is the purpose of the Book Activity use case?

A: The purpose of the Book Activity use case is to allow travelers to book activities with ease, ensuring that they can book activities that meet their needs and preferences.

Q: Who is the actor in the Book Activity use case?

A: The actor in the Book Activity use case is the traveler, who is interacting with the system to book an activity.

Q: What are the preconditions for the Book Activity use case?

A: The preconditions for the Book Activity use case are:

  • The traveler is on a screen that displays one or more activities.
  • The traveler has selected an action to book one displayed activity.
  • The traveler wants to finish booking the activity.

Q: What is the basic flow of the Book Activity use case?

A: The basic flow of the Book Activity use case is as follows:

  1. The system shows the details of the activity: The system displays the details of the activity that the traveler has selected.
  2. The system shows 3 available dates and times for booking the activity: The system displays 3 available dates and times for booking the activity at and around the known date and time for which the traveler wants to book it.
  3. The traveler chooses one of the available dates and times: The traveler selects one of the available dates and times for booking the activity.
  4. The traveler enters the number of people for whom they want to book the activity: The traveler enters the number of people for whom they want to book the activity.
  5. The system shows the chosen details for the booking: The system displays the chosen details for the booking, including the date and time, number of people, and any other relevant information.
  6. The system confirms the details: The system confirms the details of the booking with the traveler.
  7. The system creates the booking: The system creates the booking and sends a confirmation to the traveler.
  8. The system informs the traveler that they will be notified after the booking is confirmed by the guide: The system informs the traveler that they will be notified after the booking is confirmed by the guide.

Q: What are the alternative flows of the Book Activity use case?

A: There are several alternative flows that can occur during the Book Activity use case, including:

  • 2a. The date and time for which the traveler wants to book the activity are unknown from the previous interaction: If the date and time for which the traveler wants to book the activity are unknown from the previous interaction, the system will prompt the traveler to specify the date and time. The system will then repeat step 2.
  • 3a. The traveler is unsatisfied with the available date and time options and wants more options: If the traveler is unsatisfied with the available date and time options and wants more options, the traveler can choose the option to load more available dates and times for the activity. The system will extend the available dates and times with 3 additional options and repeat step 2 with the extended availabilities.
  • 3b. The traveler is unsatisfied with the available date and time options and does not want to make the booking: If the traveler is unsatisfied with the available date and time options and does not want to make the booking, the traveler can choose the leave the booking option. The system will cancel the booking in progress and the interaction will end with no booking.
  • 6a. The traveler does not confirm the booking because they want to change something: If the traveler does not confirm the booking because they want to change something, the traveler can return back to any of the previous booking steps.
  • 6b. The traveler does not confirm the booking because they want to cancel the booking in progress: If the traveler does not confirm the booking because they want to cancel the booking in progress, the traveler can choose the leave the booking option. The system will cancel the booking in progress and the interaction will end with no booking.

Q: What are the postconditions of the Book Activity use case?

A: The postconditions of the Book Activity use case are as follows:

  • The booking is created as required by the traveler.
  • If the user cancels the booking in progress, no booking is created.

Q: How does the Book Activity use case ensure that travelers can book activities with ease?

A: The Book Activity use case ensures that travelers can book activities with ease by providing a seamless and efficient booking process. The system displays the details of the activity, shows available dates and times, and allows the traveler to choose their preferred options. The system also confirms the details of the booking with the traveler and creates the booking.

Q: What are the benefits of the Book Activity use case?

A: The benefits of the Book Activity use case include:

  • Travelers can book activities with ease and efficiency.
  • The system provides a seamless and efficient booking process.
  • Travelers can choose their preferred options for dates and times.
  • The system confirms the details of the booking with the traveler and creates the booking.

By following the basic flow and alternative flows outlined in this use case, the system can ensure that travelers can book activities with ease and that the booking process is seamless and efficient.