Riya

The Travel Expert

704, 7th floor, Leela Business Park,
Andheri Kurla road,
Mumbai- 400059

Airline Flight Booking System

Version 0.1

30th March 2020

General Objective:

The main goal of the proposed system is to make online the processes of the air ticket
reservation and cancelation system.

Specific Objectives:

Some of the Specific Objectives of the system are listed below:

❖ To create a distributed system that will be used by customers.

❖ To ensure that ticket reservation is easy and user friendly for customers.
❖ To satisfy customers' needs by reaching them at their place.
❖ Provide a large number of ticket reservation and cancelation services in a few time.
1.1 FUNCTIONAL REQUIREMENTS:
The functional requirements of the Airline Reservation System are divided among the Customer
and the administrator of the application.

These functional requirements can be explained in detail as follows:

USER CASE MODULE

1.1 Use Case name: User Registration

Description: This use case describes the scenario where the user registers with the application
by providing all the necessary details, in order to make reservations or bookings for flights,
hotels, special packages.

Actor: User or the Customer

Input: The user or the customer will have to provide all the necessary details present in the
customer registration form of the application.

Output: All the details entered in the customer registration page will be verified and accepted by
the system into the database.

1.2 Use Case name: User Login

Description: This use case describes the scenario where the user logs into the application, with
the username and password he has provided while registering with the system.

Actor: User or the Customer

Input: The user or the customer creates a username and password at the time of registering with
the system. He then uses them to logon to the system and make reservations or view any
information.

Output: The application then verifies the authenticity of the username and password that the
customer has provided and allows the user to view the information available on the system, if the
username and password are valid.

1.3 Use Case name: Contact for Support

Description: This use case describes the scenario where the user contacts the support system
(contact Us) for any information.

Actor: User or the Customer

Input: The customer can contact the airline customer support, requesting them for any
information he needs.

Output: The application verifies their queries that the customer has provided and helps them
with reliable information..
1.4 User Case name: Booking Instructions

Description: This use case describes the scenario where the user views the instructions for
booking flights, packages, or Hotels.

Actor: User or the Customer

Input: After the customer logs onto the application with his username and password, he can look
up the instructions posted for booking flights, packages or Hotels.

Output: The application displays the how to book instructions page.

1.5 Use Case name: Book Flights

Description: This use case describes the scenario where the user books airline tickets.

Actor: User or the Customer

Input: After logging into the application, the customer looks up the information related to various
airlines and checks the availability of seats on flights. If a user finds that there are any available
tickets, he then purchases them or books them.

Output: The application displays information related to various flights to the customer.

1.6 Use Case name: Book Hotel

Description: This use case describes the scenario where the user books hotels at the time of
airline ticket reservation

Actor: Customer or the user

Input: After logging onto the application, the customer looks up the information for all the
available hotels at his destination.

Output: The application displays information pertaining to various hotels at the customer’s
destination.
1.7 Use Case name: Booking Packages

Description: This use case describes the scenario where the user books different touring
packages at the airline ticket reservation

Actor: Customer or the user

Input: The customer looks up information regarding various touring packages available at his
destination at the time of airline ticket reservation.

Output: The application displays information of various touring packages available at customer’s
choice of place.
ADMINISTRATOR CASE MODULE
 The administrator activities use cases will be described here:

1.8 Use Case name: Login/Logout

Description: This use case describes the scenario where the administrator of the application,
logs into the system and logs out after the work is done.

Actor: Administrator

Input: The administrator logs into the application with the username and password provided to
him.

Output: The application verifies the authenticity and displays the home page of the
administrator.

1.9 Use Case name: Add/Delete or Modify Customer information

Description: This use case describes the scenario where the administrator adds, deletes or
modifies customer information in the system database

Actor: Administrator

Input: The administrator of the applications logs onto the system with his username and
password.

Output: The application authenticates the administrator, and then displays the page where the
administrator can add new customers to the database, or delete existing customers or modify
details of customers in the database.

1.10 Use Case name: Add/Delete or Modify flight information

Description: This use case describes the scenario where the administrator adds, deletes or
modifies flight information in the application database

Actor: Administrator

Input: The administrator logs onto the system with the username and password provided to him.
Output: The application authenticates the administrator, then the application displays the page
where the administrator can add new flights to the database, delete the flights that have been
cancelled or modify information for the flights.

1.11 Use Case name: Cancellation of Reservations

Description: This use case describes the scenario where the administrator handles the
cancellation of reservations by the customers.

Actor: Administrator

Input: The administrator logs onto the system with the given username and password.

Output: The application authenticates the administrator and then displays the page where the
administrator looks up the id of the customer who has requested cancellation of reservation.
After canceling the reservation, the administrator then sends a confirmation e-mail to the
customer.

1.12 Use Case name: Email confirmations

Description: This use case describes the scenario where the administrator sends email
confirmations to the customers of the application.

Actor: Administrator

Input: The administrator logs onto the application with the username and password provided.

Output: The application then authenticates the administrator and displays the page where the
administrator can send email confirmations to the customer. These email confirmations may be
sent in cases where the customer has cancelled a reservation or changed the personal
information.

1.13 Use Case name: Modifying details of Application

Description: This use case describes the scenario where the administrator logs onto the
application to modify the details of the airline.

Actor: Administrator
Input: The administrator logs onto the application with the username and password provided to
him.

Output: The application allows the administrator to login. The administrators can then browse
through the website and change the details of any webpage in the Airline Reservation system
application.

1.14 Use Case name: Add/Delete or Modify Motel information

Description: This use case describes the scenario where the administrator adds, deletes or
modifies motel information in the database.

Actor: Administrator

Input: The administrator logs onto the system with the username and password provided to him.

Output: The application authenticates the administrator, by verifying the username and
password. Then the application displays the page where the administrator can add new hotels to
the database, delete a specific hotel from the list of hotels, since there are no more available
rooms there. He can even update the price per room of each hotel. To make it easier, the
administrator might assign a unique id for each hotel.

1.15 Use Case name: Add/Delete or Modify package information

Description: This use case describes the scenario where the administrator adds, deletes or
modifies package information in the application database

Actor: Administrator

Input: The administrator logs onto the system with the username and password provided to him.

Output: The application displays the page where the administrator can add new packages to the
database, delete the packages that are no longer available or modify information for any
particular package.
2.0 System models Scenarios

2.1 The Register Profile is as follows:

❖ The customer should register himself in order to proceed to book ticket service.
❖ The customer needs to input all the required particular details during the registration
process. The web service will perform validation checks on customer input and length
constraints.
❖ Upon successful login, the customer will be registered officially to the web service and he
can login using his username and password.
❖ The guest is only permitted to check flight availability.
❖

2.2 The Update Profile is as follows:

❖ The customer should login by himself in order to perform update profile process.
❖ The customer will only change those fields that need to be updated.
❖ Then, any changes will be updated respectively.

2.3 The Check Flight is as follows:

❖ The customer is permitted to search available flights based on the origin city, destination
city, departure date and return date.
❖ The web service will display any matching records based on the search criteria entered.
❖ The web service will notify the customer about the flight availability.
❖ If the searched flights are available, then web service will display flights which are within a
week. Otherwise, the web service will prompt to ask the user to re-enter new searching
criteria.

2.4 The Book Ticket is as follows:

❖ From the Check Flight, the customer is required to log in and the web service will prompt
the customer to confirm the flights.
❖ The web service will then ask the customer whether to update his profile details or not.
❖ Subsequently, the customer will be asked to purchase and confirm the selected flights.
2. 5 The Cancel Ticket is as follows:

❖ The customer is required to be logged in before he has the privilege to cancel his
confirmed tickets.
❖ The customer will select which ticket to be cancelled in the booking history.
❖ Once the confirmed ticket has been selected then the web service will delete the data off
from the database.
❖ The customer is given a cancellation ID upon successful transaction.
❖ There may or may not be cancellation charges that are applicable to customers
accordingly.

2.6 The View Booking Status is as follows:

❖ The customer will select details in the booking history to view booking status.
❖ Flight information that matches input criteria. The user will provide:
a. A flight number and Date
OR
b. Departing/Arriving Cities and Date.
❖ The system will display matching flight information including the following fields:
a. Flight Number
b. Departure City
c. Arrival City
d. Status (one of the following)
• In Flight
• At the Gate
• Delayed
• On Time
❖ In case of cancellation users can also view its current status with all its attachable
information.

2.7 The Pay Ticket is as follows:

❖ After Book Ticket, the web service will generate payment ID upon successful transaction
is made.
❖ Once it has been confirmed, the web service will generate booking id to the customer
and require the customer to print out the mini itinerary receipt..