1.

Login
1.1 Use case diagram:

1.2 Use case specification:

Use Case Name Login

Scenario Users attempt to access the system by entering their credentials.
Trigger Event The users open the login page and enters their information and password.
Brief Description Users logging into the system using their personal information and password. Upon
successful login, the system authenticates the user and grants them access to their
specific functionalities based on their role.
Actors Traveler, Employee, Admin.

Skateholders System Administrator (maintains user accounts and system security)

System Users (Traveler, Employees, and Admin)
Pre-Conditions The system is up and running.
The user has a valid user account with the system.
 The device needs to connect to the Internet.
Post-Conditions If logged in successfully, the user will be redirected to the home page based on their
role.
Flow of Events Actor System
1. User navigates to the login page 1.1 System displays the login page
with input fields.
2. Enters their information and password in the 2.1 System validates the entered
designated field and submit. credentials:
2.1.1 If the information filled in has
blank fields, the system will prompt
the user to re-enter login
information.
2.1.2 If the information filled in has

no blank fields, the system starts

checking the validity of the
information.
2.2 Queries the user database to find
a record matching the entered
information.
2.3 The system notifies success and
redirects the user to their homepage
based on their role.
Exception If there are technical issues or errors during the login process, the system notifies the
Conditions user and advises them to try again later.
1.3 Sequence:

1.4 Activity:
 2. Logout
2.1. UCD

2.2 Use case specification:

Use Case Name Logout
Scenario Users want to log out of their account and end their session on the website..
Trigger Event Users accessing the website and deciding to sign out of their account.
Brief Description Allow users to terminate their session and securely log out of their account on the
website.
Actors Traveler, Employee, Admin.

Skateholders
System Administrator (maintains user accounts and system security).

Pre-Conditions The system is up and running.

The user is currently logged in to their account on the website.
The device needs to connect to the Internet.
Post-Conditions The user's session is terminated, and they are logged out of their account.
The user is redirected to the login page or a homepage upon successful sign-out.
Flow of Events Actor System
1. The user presses the "Log out" button on the 1.1 System receives the Logout
system interface. request from the user.
1.2 The system displays a
confirmation message about the
logout request.
2. Press the confirmation button 2.1 The system receives the
command and securely terminates
the user's session and logs them out
of their account.
2.2 The system redirects users to the
login page.
Exception If the user is not logged in, the system may ignore the logout request.
Conditions

2.3 Sequence:
2.4 Activity:

3. Register
3.1 UCD
 3.2 Use case specification:
Use Case Name Register
Scenario A new customer wants to create an account on the system to access its features and
functionalities.
Trigger Event The customer accesses the registration page and begins entering their information.
Brief Description The customer registering for a new account on the system. The customer enters their
personal information, sets a password, and confirms it by re-entering it in a separate
field. The system validates the entered information and creates a new account upon
successful registration.
Actors Customer.

Skateholders
System Administrator (maintains user accounts and system security).

Pre-Conditions The system is up and running.

The device needs to connect to the Internet.
The customer has an unused email address registered on the system.
Post-Conditions If successful, the system creates a new customer account with the provided
information.
The customer receives a message notifying them of successful registration.
The customer is redirected to a login page.
Flow of Events Actor System
1. User navigates to the register page. 1.1 System displays the register
page with input fields.
2. Enters their information and password in the
designated field, and confirms the password by
re-entering it in a separate field.

3. Clicks a "Register" button to submit the 3.1 The system validates entered
registration information. login information:
3.1.1 If the information is left blank,
the system will prompt the user to
re-enter registration information.
3.1.2 Check the password re-enter
field is the same as the password
field.
3.1.2.1 If there is no match, display
an error message
3.1.2.2 If it matches, continue to
confirm the information
3.1.2 If there are no blank cells left
in the information filled in, the
system starts checking the validity
of the information.
3.2 Query the user database to find
duplicate records with the entered
information.
3.2.1 If user information is not
duplicated, send notification of
 successful account registration.
3.2.1 If user information already
exists in system data, display an
error message.
3.3 Redirect users to the login page.
Exception System unavailable: The system displays an error message indicating the system is
Conditions unavailable and the customer should try again later.

3.3 Sequence:

3.4 Activity:
4. Reset Password
4.1 UCD

4.2 Use case specification:

Use Case Name Reset Password
Scenario Travelers forgets their password and needs to reset it to regain access to their account.
Trigger Event The travelers access the "Reset Password" on the account page.
Brief Description Travelers request to reset their forgotten password. The system validates the request
and sends them a new password entry form. Travelers enter a new password and log in
again to use their account
Actors Traveler.

Skateholders
System Administrator (maintains user accounts and system security)

Pre-Conditions The system is up and running.

The traveler is in a login session on the system.
The device needs to connect to the Internet.
Post-Conditions If successful, the system will reset the traveler's password with the new password
provided.
Travelers receive a confirmation message indicating their password has been reset.
Travelers will automatically log out of the current session and need to log back in with
a new password to continue using.
Flow of Events Actor System
1. Traveler clicks on "Reset Password" on the 1.1 The system displays a form with
account page. a new password input field along
with password confirmation
2. Enter the new password with password 2.1 Entered password authentication
confirmation and press the confirm button. system:
2.1.1 If the information is left blank
or the password confirmation field is
incorrect, the system will prompt the
user to re-enter.
2.1.2 If the information is valid, the
 system starts changing the password
in the database.
2.2 Query the user database to
change the account password.
2.3 The system notifies success and
redirects the user to login page.
Exception System unavailable: The system displays an error message indicating the system is
Conditions unavailable and the traveler should try again later.
The user is not logged in so cannot request a password reset.

4.3 Sequence:

4.4 Activity:
5. View Travel Package:
5.1 UCD
 5.2 Use case specification:
Use Case Name View Travel Package
Scenario A user wants to view the available travel packages offered by the system.
Trigger Event The user accesses the "Travel Packages" section in travel page.
Brief Description User wants to see detailed information about travel packages provided by the system.
The system allows browsing packages based on various criteria, viewing detailed
information about each package, and exploring individual components such as tours,
hotels, and tickets included in the package.
Actors Traveler, Customer.

Skateholders
Manager (maintains and updates travel package information).

Pre-Conditions The system is up and running.

Travel packages are created and stored within the system.
The device needs to connect to the Internet.
Post-Conditions
User gains a better understanding of the available travel packages and their
 components.
Flow of Events Actor System
1. Select "View Travel Packages" section in the 1.1 System displays available tours.
travel page.
2. Click on an available travel package. 2.1 The system receives the travel
package code and starts searching
for information about the tour.
2.2 Query the database to find
records that match the received
travel package information.
2.3 The system returns tour
information of the selected travel
package as complete information
with hotel and ticket viewing
functions.
2.1.1 User selects hotel view function. 2.1.1.1 The system receives the
travel package code and starts
searching for information about the
corresponding hotel.
2.1.1.2 Query the database to find
records that match the received
travel package information.
2.1.1.3 The system returns hotel
information of the travel package
along with ticket viewing functions.
2..1.2.1 The system receives the
2.1.2 User selects ticket view function. travel package code and starts
searching for information about the
 corresponding ticket.
2.1.2.2 Query the database to find
records that match the received
travel package information.
2.1.2.3 The system returns ticket
information of the travel package
along with hotel viewing functions.
Exception System unavailable: The system displays an error message indicating the system is
Conditions unavailable and the customer or traveler should try again later.
No travel packages available: If no travel packages currently exist in the system, the
system displays a message informing the user and suggesting they revisit later.

5.3 Sequence:
 5.4 Activity:

6. Search Travel Package:

6.1 UCD

6.2 Use case specification:

Use Case Name Search Travel Package
Scenario A traveler wants to find and book a travel package that meets their specific needs and
preferences.
Trigger Event Traveler accesses the travel package search function in the system on the travel page.
Brief Description This use case describes the process by which a traveler searches for a suitable travel
package, views the package details and can book the travel package as well as cancel
the tour booking and request a refund. The system allows filtering based on
destination, date or keywords related to travel packages offered by tourists. Visitors
can explore tour details and, if interested, proceed with booking and payment.
Actors Traveler.

Skateholders Booking System Employee (ensures the booking process and payment function goes
smoothly, as well as the refund process if the customer requests to cancel the booking).
Pre-Conditions The system is up and running.
Travel packages are created and stored in the system.
The traveler has a valid account with the system (logged in).
Travelers have payment methods available for booking.
The device needs to connect to the Internet.
Post-Conditions If the booking is successful, guests will receive a confirmation message on the system
interface
Send confirmation emails or notifications to travelers with booking and itinerary
details.
Flow of Events Actor System
1. Accesses the travel search functionality 1.1 The system displays the
within the system. destination and date selection, along
with a keyword input field (if
necessary).
2. Select destination, departure date and press 2.1 The system sends the
submit. information the customer has
entered.
 2.2 Query the database to find
records that match the received
information.
2.3 The system returns travel
package data that matches the input
3. Choose an available travel package. information.
3.1.1 Select the detailed tour view function. 3.1 Displays available functions.
3.1.1.1 The system receives the
travel package code and starts
searching for information about the
tour.
3.1.1.2 Query the database to find
records that match the received
travel package information.
3.1.1.3 The system returns tour
information of the selected travel
package as complete information
with Book tour function.
3.1.2 Select the tour booking function. 3.1.2.1 The system displays a form
to fill in payment information.
4. Enter personal payment information. 4.1 Check payment information and
create new payment order in the
database.
4.2 Confirm the information and
send payment information to the
user.
5. The user pays according to the request and 5.1 The system checks the payment
clicks to confirm successful payment. status and updates payment order
 code information in the database.
5.2 Returns a successful notification
confirmation message and sends a
payment code notification along
with information related to the travel
package via email.
6. User requests to cancel booking. 6.1 The system displays a
confirmation request.
7. User confirms. 7.1 The system searches the
payment information database.
7.2 Return the results and start
filtering for a refund.
7.3 Execute refund and display
result message.
Exception System unavailable: The system displays an error message indicating the system is
Conditions unavailable and the customer or traveler should try again later.
The system checks the status of unsuccessful payment and will notify the user.

6.3 Sequence:
6.4 Activity: