TOPIC: ONLINE AIRTICKET BOOKING SYSTEM

CASE STUDY: LOVE UGANDA SAFARIS

BY

MUTUMBA HAMUZAH

DIT/JAN22/D/1192

SUPERVISOR

MR BAZIGU ALEX

SUBMITTED IN PARTIAL FULFILLMENT FOR THE AWARD OF A DIPLOMA

IN INFORMATION TECHNOLOGY, MAKERERE INSTITUTE OF

TECHNOLOGY EAST AFRICA.

OCTOBER, 2022

1
 DECLARATION
I, Mutumba Hamuzah, hereby declare that all the work included in this proposal is my
original and my own, and it has never been submitted to any academic institute for any
academic award. I hereby abide by the academic integrity policy of Makerere Institute of
Technology East Africa

Signed: ……………………………………….

Mutumba Hamuzah
DIT/JAN22/D/1192
STUDENT

i
 APPROVAL
The following academic supervisor has thoroughly reviewed the proposal and hereby approve
for submission to the research department.

Signed. ………………………………………. Date. ………../………../………………

Mr. BAZIGU ALEX

DEPARTMENT OF INFORMATION TECHNOLOGY

MAKERERE INSTITUTE OF TECHNOLOGY

ii
 TABLE OF CONTENTS
DECLARATION i
APPROVAL..............................................................................................................................ii

LIST OF FIGURES..................................................................................................................iv

CHAPTER ONE........................................................................................................................1

INTRODUCTION......................................................................................................................1

1.0 Introduction.................................................................................................................1

1.1 Background Of The Study...............................................................................................1

1.2 Problem Statement...........................................................................................................1

1.3 Objectives Of The Study..................................................................................................1

1.3.1 Specific Objective.....................................................................................................1

1.4 Research Questions......................................................................................................1

1.5 Signifiance Of The Study.................................................................................................1

1.6 Justisfication Of The Study..........................................................................................1

1.7 Scope Of The Study....................................................................................................1

1.7.1 Geographical Scope..................................................................................................1

1.7.2 Content Scope……………………………………………………………………….1

1.7.3 Time Scope…………………………………………………………………………1

1.8 Definition Of The Key Terms………………………………………………………….1

iii
 LIST OF FIGURES
No table of figures entries found.

iv
 CHAPTER ONE

INTRODUCTION
1.0 Introduction
1.1 BACKGROUND OF THE STUDY

ONLINE AIRTICKET BOOKING SYSTEM

Background of the case study

Love Uganda Safaris & tours Ltd is a registered in bound tour & Travel Company based in
Kampala, Uganda, East Africa. Founded and registered in 2012 & 2014 respectively, Love
Uganda Safaris & Tours has gained experience over the years in the travel & safari business.
It is located on Kireka hill near the Adventist Relief Agency (ADRA) Headquarters.

The agency name, Love Uganda Safaris was then derived from Love Uganda Foundation;
despite the challenges encountered in the course of developing the 2 companies concurrently,
McMillan always ensured that the company offers relatively excellent services to her new
clients with efficiency and effectiveness. Together with his new partner and brother, Mr.
Robert Paul, they managed to establish new partnerships in various countries, including USA,
Canada, Australia, German, Italy, Mexico, France, Spain, Israel, Botswana, Rwanda,
Tanzania, Kenya and DR Congo.
These 2 young and ambitious men ran the 2 companies successfully, while growing the
customer base and continuing to fund the orphanage that now houses over 20 children, until
2016 when death befell our own McMillan and he went to be with the lord, but the
foundation he set up for the 2 organizations is never to be forgotten.

The study seeks to develop an online Air Ticket booking system for booking Air Tickets
online for Love Uganda Safaris. The Online Air Ticket booking system is therefore an
information management system for Air ticket companies to book Air Tickets find the best
flights and vacation locations easily. And also, is a web and mobile based application with
centralized data storage structures that make it easier for the end users, access data from
Smartphone.

1
Travel to any destination of your dream in the world with Uganda’ s travel specialists, Love
Uganda safaris offers air ticketing services to tourists and other travelers with efficiency and
effectiveness.

1.2 Problem Statement

Despite the fact that air travels in Uganda has continued to expand, Love safaris Uganda has
continued to face problems in managing air ticket booking, customers have a hard time
finding the best flight prices, Sometimes the customers are not well updated and miss the best
flight times. It gets hard to travel from one place to another finding the best price. Transport
expenses are high if one is looking for a flight ticket are high. Some fear to speak with the
workers at the companies, Language barrier, pandemic lockdowns, overcrowding of people
and not knowing where the location where to book the air tickets. So, the system will solve
all the above-mentioned problems by Making an online interface which will find the best
flight deals, help keep track of the flight times, Make booking tickets easier with just one
click. It will also be in a variety of languages including English Luganda, Kiswahili,
Runyankole, Arabic and others so that everyone could use. This system will also come in
handy during countrywide lockdowns where movement and gatherings are restricted one will
be able to book tickets online without the need to walk outside. In the system some features
will require stable internet, computer, smartphones to be able to operate the software.

1.3 Main objective of the study

To design and implement a workable system that is going to enable the Online simple
booking of air tickets, keeping track of flight times, finding the best places for vacation with
the best deals ever and giving the user a simple new way of booking Air Tickets.

1.3.1 Specific objectives

 To study the existing system and highlight the outcomings within the system.
 To analyze the current and come up with the recommendations of a new system.
 To design and develop the new system
 To implement and test the system.
 To allow teachers, parents, school community to view reports on students.
 To facilitate attendance and record keeping.

2
1.4 Research Questions

1. What are the measures to be taken when using the Online Air Ticket booking system?
2. What are the problems to be associated when using the Online Air Ticket booking
system?
3. Why is it important to have a Online Air Ticket booking system?

1.5 Significance of the study

1.Once implemented Clive college Kireka will no-longer lose school data, , since the
software will allow recording of the school data .

2. The system will also connect the school and parents directly through improving on
communication.

3. Some of the student functions like admissions, attendances, grading will be managed
easily.

4. Their will be urgent school fees payment like paying of school fees online.

1.6 Justification of the study

I justify that this system is going to implement smoother management of the school
operations such as attendances, admissions, grading etc.

Scope of the study

1.7.1 Geographical scope

The study shall be conducted in Wakiso district, Kireka.

1.7.2 Content scope

The study shall focus on School Management System where a workable system will be
designed basing on the following computer languages.

a. PHP
Is a general-purpose or server-side scripting language geared towards web
development and will be used for making web servers.

3
 b. HTML
Is a standard markup language for document designs to be displayed on a web
browser.
It will be used for designing the structure of the system.
c. CSS
Is a style sheet language used for describing the presentation of a document on the
markup language.

It will be used for beatifying the system.

d. JAVASCRIPT
Is a dynamic programming language that used for web development, in web
application etc.
It will be used for making the system interactive(behavior) and responsiveness of the
system.
e. MYSQL

Is a relational database management system.

It will be used to add, process data stored in the database.

1.7.3 Time scope

The study shall be conducted within 2 months running from October to December
2022

4
 CHAPTER TWO: LITERATURE REVIEW

Introduction

Now a days, information technology leads an important role in the organization where
everything is computerized by reducing paper based manual work. In the new era in Air
traveling also some changes have done by developing and designing an online Air Ticket
booking system.

2.2 Background

For many years, flight reservation was an off-putting, difficult task. As air travel became a
viable transportation option in the early 40s, thousands of people became ticket buyers. With
the growing number of customers, carriers had to overcome numerous challenges to make
booking fast, convenient, and operationally easy. Twenty years or so down the road in the
60s, the whole booking process could be accomplished in minutes – through a travel agent.
Fast forward to today – and previously unimaginable – travelers enjoy fully automated ticket
booking, reserving and paying for flights using smartphones.

In the 1950s, airlines in the USA and Europe experienced the rapid growth of new customers.
Rising demand forced major carriers to seek a solution capable of processing bookings much
quicker than it used to be. At that time, airlines used archaic, manual systems that opened
access to the airlines’ inventory and allowed for booking tickets via phone calls. A single
booking could take about an hour, even more.

Ticketing agents were operating with paper cards stored in a rotating tank, manually checking
flight and seat availability, filling in passenger info by hand. The whole process was clumsy
and slow, making it hard for carriers to process large volumes of bookings.

During the late 50s, this issue was partially solved by IBM’s early computerized systems.
Those systems included primitive semi-automatic devices as Magnetronic Reservisor and
Reserwriter developed by IBM for American Airlines. Both devices represented complicated
mechanical computers that could show seat availability. If an agent needed to book a ticket,
he or she would put a paper card into the device and fill in all the necessary information. So,
the whole process relied heavily on manual input.

The growing number of travelers and analog booking forced American Airlines to modernize
their booking pipeline. As a result, the first computer reservation system (CRS) was born.

5
1957-1964: SABRE is the first booking automation system

In 1957, a meeting of IBM’s salesperson and a former director of American Airlines initiated
the development of an automated reservation tool. It was based on SAGE, a ground-control
environment developed for the US Air Force. Expertise in military equipment allowed IBM
to reuse some of its groundworks for American Airlines and start creating a Semi-automated
Business Research Environment or simply SABRE.

SABRE became the first computerized booking system and it quickly boosted American’s
position in the market. Development was finished in 1964 when SABRE could process over
7,000 bookings per hour with nearly zero error rate. SABRE operated on two IBM
mainframes connected with thousands of terminals allowing American Airlines operators to
check the inventory and book in seconds. Additionally, for the first time, a reservation system
could store passenger information in its memory.

American Airlines spent almost 7 years and $40 million (about $350 million today) on
SABRE development. But instead of bankrupting American, it helped American occupy
leading positions in the market.

1964-1971: Emergence of PARS-based reservation systems

The success of American’s modernization forced other airlines to join the CRS race. Several
US-based carriers contracted IBM to create an alternative to SABRE. As a result, IBM
created PARS (Programmed Airline Reservation System).

At the end of 1971 nearly all major American carriers, and some Northern European ones,
customized PARS to release their own reservation systems. In 1964 IBM built PANAMAC
for Pan American, that offered flight and hotel reservations. Next year, in 1965, Eastern
Airlines launched System One, then Delta Airlines launched DATAS II in 1968. United
Airlines built Apollo reservation system and Trans World Airlines came up with PARS
customization in 1971.

As most systems used PARS to some extent, the capabilities of most CRSs were similar. In
highly competitive conditions, American’s SABRE and United Airlines Apollo got the lion’s
share of the market being to the largest US carriers.

6
1974: Airline Tariff Publishing Company starts providing flight information

Travel agencies got access to CRSs. Seeing the distribution landscape changing, in 1974
Airline Tariff Publishing Company (ATPCO) was formed. ATPCO is one of the most
important third-party players in airline distribution even today. During the 1960s, the
company was providing airline tariffs to travel agencies, following its modernization with the
first IBM computers installed in 1969. By 1974, ATPCO managed to modernize its hardware,
connecting to CRS distribution.

1976: Travel agencies got access to CRSs

At the beginning of the 1970s, nearly all the major carriers in the US launched their
reservation systems. Automated reservations enabled airlines to process giant volumes of
bookings and increase revenues.

The problem arose on the other side of the industry. While airlines were automating the
booking process, travel agencies remained fully-manual, keeping all fare information and
schedules in a written format. To book a flight, a travel agent had to call a ticket agent at the
airline to check seat availability. So, the only way to keep travel agencies updated and
capable of selling more tickets was by setting the direct connection to airlines’ CRSs.

In 1976, United (Apollo) and American Airlines (SABRE) started selling access to their
reservation systems to travel agents. Delta, Trans World, and Eastern joined the movement
soon.

1978-1992: Airline deregulation and GDS emergence

In 1978, due to the economy and the emergence of new types of jets, the US government
decided to deregulate the airline industry. That meant the US government stopped controlling
fares, prices, and routes, as well as market entry. That made the airline industry a free market
new player could enter while existing carriers now could set their own prices and establish
new routes.

1987: major European GDSs, Galileo and Amadeus, are created by airlines

Being cut from the US market, European carriers worked on their own CRSs. Since the
beginning of the 60s, there were two CRSs (CORDA by Dutch KLM and SASCO by
Scandinavian) that operated across Europe. New systems were forming during the late 70s to
the end of the 20th century.

7
1990: Worldspan forms from earlier American CRSs

Meanwhile, in 1990, three major US airlines, Northwest, Delta, and Trans World, founded an
international GDS system named Worldspan. CRS of Worldspan was a combination of two
earlier systems, DATAS II and PARS. Operating across Europe, US territory, and part of
Asia, owning a part of Asian GDS Abacus, Worldspan soon became the third major European
GDS, along with Amadeus and Galileo.

1992-2000: Distribution regulations and growth of GDS monopolization

So, at the beginning of the 90s, GDSs were nothing new. The American market was
dominated by SABRE, with other US-based and international systems. Regulations set in
1984 didn’t affect the monopolization of the market.

2009-2019: Mobile booking, Expedia, Inc. acquisitions, and social networks

Online booking became a reliable alternative to phone sales for nearly all the airlines and
travel agencies in the early 2000s. Technology providers, GDSs, and airlines started to create
the first travel APIs in the second part of the 2000s. These were used to source flights and
any kind of travel data. One of the first travel APIs traces back to 2006, the XML API by
AirKiosk.

2011: Google launches its own flight booking platform – Google Flights

Google announced its plans to acquire ITA software company in 2011. ITA was a travel
technology company that developed a pricing system QPX. It was used by numerous
companies like American, Delta, US Airways, KAYAK, and Orbitz.

2012-2019: Airlines start utilizing social networks

With the rise of mobile internet, social networks have also occupied a tangible part of the
travel market. An exceptional example of using social networks in online booking is Meet &
Seat by KLM. KLM managed to integrate social networking with the seat allocation process.
Sharing the link of your Facebook or LinkedIn profile, KLM allows you to see who will sit
next to you, and choose the place based on social profiles.

CHAPTER THREE

RESEARCH METHODOLOGY

8
3.1 Introduction

This chapter consists of a description of details of the systematic methods that we intend to
use to accomplished the objectives of this research project.

The structure plan of the research project that will acknowledge the tasks need to achieve in
the design of School Management System. In preparation the first task will include the
challenges in the existing system.

3.2 Research Approach

The study shall use descriptive surveying in order to gather a wide range of information for
the research goals to be accomplished. Surveys shall be needed because they will provide
information for drawing generalization. Other awards interviews are very important tools in
conducting a qualitative research. Interviews shall be used to gather first-hand information
from different departments of the Air ticket booking company regarding of the existing
system used in the company, challenges of the existing system and suggestions for any
improvement. The method is to be used following the interviews and the information
gathered from the interviews will be analyzed and used to reach the final conclusion.

3.3 Target population

The research shall be conducted in Kireka Wakiso district, Uganda and the population size
will involve a total of 40 participants selected from the school and the people within the area.

These people will include the Pilots, Air hostess, customers, workers and other people within
the area and the Census approach will be used because the population is not big.

3.4 Sampling techniques

The research understudy will involve using the simple random sampling method which
ensures accuracy and permitted generation from the selected sample of the population it
represents. This method is realistically economical, convenient, and ease the process of
obtaining reliable and valid responses from the selected study population since the sampling
size of the organization under study is small. Using this method, each expected participants in
the selected areas of study will have the same chance of being selected for the sample.

3.5 Sample size

9
The study will be conducted in Kampala. A sample of 40 people is targeted and will be
generated using the formula to find the final sample size of this research.

Table 1: Sample Selection and Categories [Participants] of respondents involved.

Categories [Participants] Expected Sample Percentage

Pilots 5 12.5%
Air hostess 5 12.5%
IT Person ells 10 25%
Customers 20 50%
Total 40 100%

3.6 System Implementation

The system will be implemented using numerous tools that include the following.

a) HTML

This will be used to develop an Automated Agricultural Stores Management System.

Hyper Text markup Language is being used in web designing because of its ability to be
interpreted by all available web browsers and makes the directory accessible.

b) JavaScript

This is a scripting language used to enable programmatic access to objects within other
applications. It is primarily used in the form of client-side JavaScript for the development of
dynamic website. With the different frameworks and libraries being developed like React.js,
node.js and Express, it becomes possible for full stack development using the JavaScript
libraries.

c) Cascading Style Sheets

CSS provides the means to control and change presentation of HTML documents. Style
sheets allow you to impose a standard style on a whole document. It will be used to control
the color of the text, the style of fonts, the spacing between paragraphs, how columns are
sized and laid out, what background images or colors are used, as well as a variety of other
effects.

d) Bootstrap

10
This is a sleek, intuitive, and powerful, mobile first front-end framework for faster and easier
web development. It provides a clean and uniform solution for building an interface. It also
provides web-based customization.

f) MySQL

It is preferred because it is efficient in developing database driven websites, an open source

database and is the most popular database systems in use today for relational databases. A
language called Structured Query Language.

g) PHP

It is preferred because it is compatible with MySQL, fast search engine and PHP is a server-
side scripting language. PHP is important when establishing a connection to the database. h)
Sublime Text Editor

This will be used to perform the coding in developing the system. Any other code editor
could be used but Sublime is a very light text editor that have additional dependencies
installed to increase its functionality.

3.7 System documentation.

The system documentation stage will involve drafting the overall systems’ report, final
project remarks and the implementation of the system

3.8 Methods of Data collection.

These are methods of data collection used during the process of carrying out research. These
are a few mentioned below.

3.8.1 Observation Method.

This method involves using the eye to see the probable information required to meet the
needs of the problem statement. This will require carrying out approximately 3 hours of
observation while systematically noting and recording of the way in which the different
stakeholders utilize and manage their current system.

3.8.2 Interview Method.

11
This requires the asking of questions to different people in order to obtain or data required by
the research problem. One prepares guiding questions both closed and open which both are
used to ensure sufficient data collection.

3.8.2 Questionnaires.

Questionnaires will also be used as one of the main sources of information from stakeholders
and users of the current system. These will be used because through them we are able to get
first-hand information and responses from a large number of people. Questionnaires will as
well be used in a situation where interviews could not be conducted especially during the
times where the stakeholders are busy with their work.

12
 REFERENCES

I am MUTUMBA HAMUZAH a student of Makerere institute of technology pursuing a Diploma in

Information Technology and lam here carrying out a research “ONLINE AIRTICKET BOOKING
SYSTEM”.

Kindly help me to fill in the questionnaire by either ticking the right answer and the information
given shall be kept confidential.

13
 APPENDICES

APPENDIX 1: WORKPLAN

No Activity Planned Jan Feb Mar Apr May June

1 Planning

2 Requirement
Collection
3 System Design

4 Evaluation and
implementation
5 System testing and
Documentation

RESEARCH WORK PLAN

PLANNED JA FE MA AP MA JU JU AU SEP OC NO DE JA FE MA
ACTIVITIE N B R R Y N L G T T V C N B R

21
S
Getting a
Research
topic.
Submitting
a Research
topic to our
supervisors.
Submitting
your topic
on the
system to
be approved
Meeting the
supervisors
Designing
concept
paper and
objectives
Writing a
Research
proposal
Meeting the
supervisors
Designing
Research
questioners
Designing
the table of
Approach
Defending a
research
22
proposal
Data
collection
using
questioners
Designing a
workable
system
Writing a
system
report
Meeting
supervisors
Submission
of reports

23
 APPENDIX: PROPOSED BUDGET

The whole system design, development, implementation and report drafting is estimated to take UGX 191,000
only and the table below stipulates each item and its costs.

# ITEMS UNIT PRICE (UGX) AMOUNT (UGX)

1 Transport 1,000 60,000
2 Meals 3,000 90,000
3 Books and pens 4,000 4,000
4 Printing 2,000 2,000
5 Consulting services 20,000
6 Internet and research 15,000
TOTAL (UGX) 191,000

24
 CHAPTER SYSTEM IMPLEMENTATION

4.1 Screenshot for homepage

4.2 Screenshot of e-books from user.

4.3 Screenshot of login for admin

4.4 Screenshot of e-book from admin

5.1 MODULE DESCRIPTION

For Online Airticket Booking Management System it is divided into the following Modules:

25
 System flow chart.

Login

Register/save/Check user credentials

Are all
no
credenti
als true

yes

Book a flight Ticket

stop

26
14. Database Design

4.1.1 System Interfaces

Software will work on Windows OS. The database used will be an open-source database like
MySQL and the system will work on JVM.

4.1.2 System Specification

Software requirements
Operating System: we have chosen windows operating system for its best support and user
friendliness.

Database: to save the records of the applicants and their details, SQL database is used.

Hardware requirements

LMS uses standard java classes and databases. The database should have backup capabilities.

4.1.3 Communication interfaces

No additional specific communication interfaces are needed during the operation of LMS.

4.1.4 Memory constraints

The system is expected to have a memory of 56 MB and disk space of 200 MB. But it is
recommended that the system has memory capacity of 1 GB and disk space of 1GB.

4.1.5 Operations

The basic operations of the ‘Online Airticket Booking And Management System’ are described as
follows:

 The staff member first has to register him/herself before using the system.

 The staff member can then login into the system with his/her username and password.

 The staff member can then add, delete or update the flight ticket records, and users within the
system.

 The staff member can issue tickets when requesting by the members and then update the
27
 flight record too.
 The system will generate the fine slip according to the returned date when ticket is
returned by the member.
 The staff member will update the flight issue and return records into the Airticket
Booking And Management System.
 The member can search for a specific flight and destination by entering flight information.

 The staff member can update member records within the system.

4.1.6 Site Adaption Requirements

The system was installed on to an application server for the runtime components and a database
for storage. The system will run on select popular application servers and use select popular
database for data storage.

4.2 Product Functions

There are two different users who will be using this product:
 Travel Ggents who would be acting as the administrator.
 Users who can also use product for search operations.

The features that are available to the Travel Agent are:

 Can view different categories of flights available.
 Can update flights and destinations.
 Add flight tickets and their information to the database
 Edit the information of the existing flights.
 Can check the report of the issued flights.
 Can access all the accounts of the users.

The features available to the users are:

 Can view the different flight tickets available.

 Can view the List of places available to travel.
 Can search for a particular flight.
28
4.3 User characteristics

User1: Staff- Staff will add, delete or update flights records within the system. He/she will issue
the tickets as per requested by the member. Staff needs to have complete understanding of
functionalities and internal processing of the system.

User2: user- user will request for ticket issue and then will book the ticket. They can search for a
specific flight. The user does not need to have complete understanding of complex functionalities
and internal processing of the system.

4.4 Assumptions and Dependencies

The assumptions are:

29
  The coding should be error free.

 The system should be user-friendly so that it is easy to use for the users.

 The information of all users, places and tickets must be stored in a database.

 The system should have more storage capacity and provide fast access to the database.
The dependencies are:
 On the basis of listing requirements and specifications the project will be developed.

 The end users should have proper understanding of the product.

 The information of all users must be stored in a database that is accessible by the LMS.

 Any update regarding the is to be recorded to the database and the data entered should
be correct.

4.5 SPECIFIC REQUIREMENTS

4.5.1 External Interfaces

User Interface
Various GUI elements like forms, images and standard buttons will be included in the User Interface.

4.5.1 Functional Requirements

 Login:
Description: Staff member will login to the system. The user must be registered in the
system before login.
Input: Enter the username and password.
Output: Staff will be able to use the features of software.
Processing: Username and password will be checked by the system. If they are incorrect a
message will be displayed.
 Add/Remove flights:
Description: The staff can add or remove flights by entering
details. Input: Enter the flight detail you want to remove or add
within the stock.
30
 Output: Confirmation of addition or deletion and update list of flights available.
Processing: The details of flight must be right in order to add them else there will be problems in future.
 Search:
Description: The users can search a flight by entering flight details such as author’s name,
flight name etc.
Input: Enter the details you know about the flight.

31
 Output: The list of available flights is displayed.
Processing: A message is displayed if the flight related to the entered details is not available.

 Issues ticket:
Description: The staff member checks the availability of flight which the member want to
get issued.
Input: Enter flight name.
Output: Confirmation for flight or apology for failure in issue.
Processing: If selected flight is available then the ticket will be issued and the record
is updated else error will be displayed.
 Cancel Flight:
Description: The member wants to cancel the book.
Input: cancel flight.
Output: The record will be updated.

4.5.2 Logical Database Requirements

Proposed database was intended to store, retrieve, update and manipulate information related to
college which include:
 Tickets availability
 Staff information
 user details

4.5.3 Design Constraints

Software Constraints: The application shall meet the general standards of web applications.
Hardware Constraints: There is no hardware constraints identified at this point.
Acceptance Constraints:

To validate the system, the developers must complete the following:

32
1. Demonstrate the working system and any features upon request.

2. Prove that all the significant functional requirements are met.

3. Provide sufficient test cases to show that the system is complete and correct.

The system must be designed to allow web usability. That is, the system must be designed in
such a way that will be easy to use and visible on most of the browsers.

3.6 Software System Attributes

Reliability:

The application would efficiently store all the information related to the various processes in the
system and output the relevant information.

Availability:
The application would be available to all the employees of the organizations with an authorized
access to the workstations and those who are subject to the authorization permissions.

Security:
The system would have adequate security checking through the authentication of the users. The
reports would only be available to the employees of the travel company as per their specific
requirements.

Maintainability:
The software should not require any additional maintenance. If any errors occur, the user should
be able to login again with his credentials. The system shall be flexible enough to add new
modules and upgrade the existing modules

33
 CHAPTER 5 SYSTEM TESTING

The aim of the system testing process was to determine all defects in the project. The program
was subjected to a set of test inputs and various observations were made and based on these
observations it will be decided whether the program behaves as expected or not. Our Project
went through two levels of testing

1. Unittesting

2.integration
testing
Unit testing is undertaken when a module has been created and successfully reviewed. In order to
test a single module, we need to provide a complete environment i.e. besides the module we
would require

 The procedures belonging to other modules that the module under test calls

 Non local data structures that module accesses

 A procedure to call the functions of the module under test with appropriate parameters Unit
testing was done on each and every module that is described under module description of
chapter 4

1. Test For the admin module

 Testing admin login form-This form is used for log in of administrator of the system. In
this we enter the username and password if both are correct administration page will
open otherwise if any of data is wrong it will get redirected back to the login page and
again ask for username and password

 User account addition- In this section the admin can verify user details from and then only
add user details to main library database it contains add and delete buttons if user click add
button data will be added to user database and if he clicks delete button the student data will
be deleted

 Ticket Addition- Admin can enter details of flight and can add the details to the main
booking table also he can view the flight requests.

34
2. Test for user login module

 Test for user login Form-This form is used for log in of user. In this we enter the user id,
username and password if all these are correct user login page will open otherwise if any
of data is wrong it will get redirected back to the login page and again ask for library id,
username and password.
 Test for account creation- This form is used for new account creation when user does
not fill the form completely it asks again to fill the whole form when he fills the form
fully it gets redirected to page which show waiting for conformation message as his data
will be only added by administrator after verification.

integration testing

In this type of testing, we test various integration of the project module by providing the input.
The primary objective is to test the module interfaces in order to ensure that no errors are
occurring when one module invokes the other module.

35
 APPENDIX I
QUESTIONNAIRE

Dear Respondent,

36
Am MUTUMBA HAMUZAH, a student of MAKERERE INSTITUTE OF TECHNOLOGY

EAST AFRICA pursuing a Diploma in Information Technology carrying out research about

“ONLINE AIRTICKET BOOKING SYSTEM’’. Kindly I request you to answer my

questionnaire by either ticking in alternative or filling in the right answering the space provided
and everything given will be kept confidential. Tick appropriately with a


SECTION A

BIODATA

Sex of the respondent

1. Gender

a) Female

b) Male

2. Age Group

a) 18-22

b) 25-30

c) 35-40

d) Above 50

3. Marital Status

a) Married
37
 b) Single

c) Divorced

4. Education Status

a) Attending School

b) Ever Attended School

c) Never Attended School

5. Education Level

a) Secondary Level

b) Diploma

c) Degree

d) Masters

6. Religious Status

a) Protestant

b) Muslim

c) Catholic

d) Born Again

e) Adventist

38
 SECTION B

1. Do travel conpanies use online Airticket booking Management System?

a) Yes

b) No

2. What are the problems associated with online Airticket booking Management System?

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

3. What are the benefits of online Airticket booking Management System?

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

4. Have you ever used Airticket booking Management System?

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

5. Suggest ways we can improve the existing system?

………………………………………………………………………………………………

39
………………………………………………………………………………………………

………………………………………………………………………………………………

6. Have you used any Airticket Booking system before? Yes/ No. If not give a reason why

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

7. Any other comments?

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

THANK YOU SO MUCH RESPONDENT FOR YOUR TIME,

MAY ALLAH BLESS YOU

40