PHASE 1:

REQUIREMENTS
DETERMINATION

1
PROJECT DESCRIPTION

The DestiniGo Airline Reservation System is a web-based application to

book/reserve airline tickets online. This website provides an option for a customer
to view different flights available and book/reserve their airline tickers via online.
The main objective of the application is to improve the issuing airline tickets, at
present tickets, are issuing only in at select outlets. This can be enabled to make
available online so that each customer can book/reserve airline tickets at his or her
place.

PROJECT SCOPE AND LIMITATIONS

The name of the software is “DESTINIGO AIRLINE RESERVATION

SYSTEM”. This software provides options for viewing different flights available
with different timings for a particular date and provides customers with the facility
to book a ticket, modify or cancel a particular reservation but it does not provide
the customers with details of cost of the ticket and it does not allow the customer
to modify a particular part of his reservation and he/she can modify all his details.

The system allows the airline passenger to search for flights that are
available between the two travel cities, namely the “Departure city” and “Arrival
city” for a particular departure and arrival dates. The system displays all the flight
details such as flight no, name, price and duration of the journey, etc.

After a search, the system displays a list of available flights and allows the
customer to choose a particular flight. Then the system checks for the availability
of seats on the flight. If the seats are available then the system allows the passenger
to book a seat. Otherwise, it asks the user to choose another flight.

2
 To book a flight the system asks the customer to enter his details such as
name, address, city, state, and contact number. Then it checks the validity of the
card and book the flight and updates the airline database and user database. The
system also allows the customer to cancel his/her reservation if any problem occurs.

The main purpose of this software is to reduce the manual errors involved in
the airline reservation process and make it convenient for the customers to book the
flights as when they require such that they can utilize this software to make
reservations, modify reservations or cancel a particular reservation.

Hardware and Software Specification

 Hardware Specification

 Processor: Pentium III @ 1.2 GHz or Above

 RAM: 2 GB or Above
 Hard Disk: 40 GB or Above

 Software Specification

 Operating System: Windows, macOS

 Browser: Chrome, Mozilla Firefox, Internet Explorer

3
FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS

Functional requirements

3.1 Reservation

3.1.1 – The system displays the four (4) process of the reservation as user
guidelines.

3.1.2 – The itinerary phase, the system allow the user to search for the
available flight with the detail of types of an airline, flight number, date and
time of travel and the origin city and destination city.

3.1.3 – The accommodation phase, the system allow the user to choose how
many passenger and select what types of accommodation such as sitting,
economy, tourist, cabin and deluxe.

3.1.4 – The passenger info phase, the system allow the user to enter the
information of the booker (name, contact number, address) and the
passenger (full name, age, gender).

3.1.5 – The payment info phase, the system shows all the information given
from the previous phase.

3.2 Payment/Blocking/Confirmation

3.2.1 - The system will now ask the user if he wishes to block/accept the
reservation.

4
 3.2.2 - the system compares the departure date with the system date. If the
departure date falls within 2 weeks of the system date, the system informs
the user that he has no option to block the ticket and asks him if he would
like to buy it.

3.4 Cancellation

3.4.1 – The system shall also give the user an option to cancel a confirmed
ticket or a blocked ticket.

3.4.2 – The system generates a cancellation number and displays it for the
user to note down.

3.5 Ticket Status

3.5.1 – The system sends information via SMS about the reservation to a
user about his trip.

3.6 Reservation refund

3.6.1 – The system shall allow the user to refund its reservation with a
deduction of the service fee.

3.7 User Accounts

3.7.1 – The system will manage the user accounts such as

user/employee/staff/admin and the passenger/guest.

5
Non-functional requirements

1. Operational

1.1 The system should run in both mobile and PCs to be used by the
user/staff/admin.

1.2 The system should interface with the airline ticketing reservation
system.
1.3 The system should notify the user via SMS.

2. Performance

2.1 The system should support a sales staff of 10 salespeople.

2.2 The system should be updated with the availability of the ticket every
minute.

3. Security

3.1 Only the administrator and staff may approve the customer purchase.

3.2 The use of each PC should be restricted to the staff/salesperson to

whom it is assigned.

4. Cultural and Political

4.1 Customer/Guest personal information is protected in compliance with

the Data Protection Act.

6
USE CASE ANALYSIS
Use case Name: Reservation ID: UC-01 Priority: High
Actor: Staff, Guest/Customer
Description: It is for the user to provide all the necessary details, in order to make
reservations or bookings for flights.
Trigger: Staff or Guest/Customer reserve for a flight ticket.
Type: External
Precondition:
1. The Staff or Guest/Customer has all the information requirements for input
and submission.
Normal Course:
1. The staff or guest/customer reserve for a flight.
1.1 The Staff or Guest/Customer click the reservation button and redirects
to a reservation page.
1.2 The system allows the staff or guest/customer to select the flight before
clicking the “Next’ button.
1.3 The staff or guest/customer choose the type of accommodation and enter
how many passenger before clicking the “Next’ button.
1.4 The staff or guest/customer provides the required data before clicking
the “Submit’ button.
Postcondition:
1. The system shows the successful reservation transaction with information
such as the payment information and passenger information.
Exception:
1. Reservation failed.
1.1 The system highlights the required fields with missing information in
the reservation form. The staff or guest/customer is prompted to fill in
the missing information.
1.2 The system starts the Normal Course once more and prompts the staff
or guest/customer to click the “Next” and “Submit’ button.

7
Use case Name: Blocking/Confirmation ID: UC-02 Priority: High
Actor: Staff
Description: It is for the staff/admin to decide to block or accept the reservation.

Trigger: Staff
Type: External
Precondition:
1. The Staff verifies the reservation of the guest/customer in the system.

Normal Course:
1. The staff decides to block or accept the reservation.
1.1 The system asks the staff to accept the entry reservation.
1.1.1 The system asks the staff for the discount before clicking the
“Compute” button.
1.1.2 The staff clicks the “Accept Payment” button to reserve the
flight.
1.2 The system asks the staff to cancel the entry reservation.
1.2.1 The system asks the staff if he/she will confirm or decline the
cancelation of the entry reservation.
Postcondition:
1. The system shows the successful transaction either accepted or canceled
flight reservations.
Exception:

8
Use case Name: Reschedule Ticket ID: UC-03 Priority: Medium
Actor: Guest/Customer
Description: It is for the guest/customer to reschedule the confirmed ticket.

Trigger: Guest/Customer re-scheduling confirmed reservation/ticket.

Type: External
Precondition:
1. The Guest/Customer must have a reservation in the system.

Normal Course:
1. The Guest/Customer search for his/her reservation number.
Postcondition:
2. The system shows the successful transaction either accepted or canceled
flight reservations.
Exception:

Use case Name: Cancellation ID: UC-04 Priority: Medium

Actor: Staff
Description: It is for the staff/admin to cancel the reservation.

Trigger: Staff
Type: External
Precondition:
1. The Staff verifies the reservation of the guest/customer in the system.

Normal Course:
1. The system asks the staff to cancel the entry reservation.
1.1 The system asks the staff if he/she will confirm or decline the
cancelation of the entry reservation.

9
Postcondition:
1. The system shows the successful cancellation of canceled flight
reservations.
Exception:

Use case Name: Reservation Refund ID: UC-05 Priority: Medium

Actor: Staff
Description: It is for the staff/admin to refund the reservation of the user.

Trigger: Staff
Type: External
Precondition:
1. The Staff verifies the confirmed reservation of the guest/customer in the
system.
Normal Course:
1. The system allows the staff to refund the confirmed reservation by clicking
the “10%” or “20%” button. The percentage corresponded to the service
fee in refunding the tickets/reservation.
Postcondition:
1. The system shows the successful transaction of refunding the flight
tickets/reservations.
2. The system shows all the refunded tickets/reservations.
Exception:

10
 PHASE 2:
ANALYSIS PHASE – PROCESS
MODELLING AND DATABASE
DESIGN

11
12
 PHASE 3:
DESIGN PHASE – ARCHITECTURE
AND USER INTERFACE DESIGN

13
USER/CUSTOMER GRAPHICAL USER INTERFACE

Figure 1

Figure 1 shows the home page of the system. It is where customer/passenger

can reserve and read the services offered by the system, view a contact number and
read the description of the system.

Figure 2

Figure 2 show the first step in booking/reserving a fligh. It is where

customer/passenger can choose flight available in the system such as travel date,
destination and type of airline.

14
 Figure 2.1

Figure 2.1 shows the information of the availability of the flight such as the
travel date, travel time, destination and the airline.

Figure 3

Figure 3 shows the accomodation type where the user/customer choose

what type of accomodation and show the remaining slots and its fare.

15
 Figure 4

Figure 4 shows the passenger information. It is where the user/customer

input their information such as whom booked by, its contact number and address.
Also the information about the passenger

Figure 5

Figure 5 shows the payment information. It is where the customer/

passenger viewed inputted data from the previous transaction. It will serve as a
registration record.

16
STAFF/ADMIN GRAPHICAL USER INTERFACE

Figure 6

Figure 6 shows the home page of the system. It is where the admin/staff can
reserve and read the services offered by the system, view a contact number and read
the description of the system.

Figure 7

Figure 7 show the login form of the admin/staff. It where the admin/staff
can login to the system using RFID.

17
 Figure 8

Figure 8 show the login form of the admin/staff. It where the admin/staff
can login to the system with a regular process such as inputting username and
password.

Figure 9

Figure 9 shows the passenger list and payment. It is where the admin/staff
view the list of who are already booked/reserved in the system. It shows also the
payment transaction where the admin/staff can choose if the passengers are
qualified for the discount price.

18
 Figure 10

Figure 10 shows the payed transaction in the system. It where the

admin/staff view all the payed transaction in the system and can select the refund it
the passenger want to rebook or cancelled a flight.

Figure 11

Figure 11 shows the reports recoreded in the system. It show the transaction
reports in the system day by day.

19
 PHASE 4:
IMPLEMENTATION AND TESTING

20
21