ACENTRALIZED ONLINE AIR TICKET RESERVATION SYSTEM
CASE STUDY: UGANDA AIRLINE
BY
TUMUSIIME FLORENCE
BIT/10141/81/DU AND
NGABIRANO JOSHUA
BIT/i 0100/81/PU
A GRADUTION PROJECT REPORT, SUBMITTED TO THE FACULTY OF COMPUTER STUDIES, IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FORTHE AWARD OF THE BACHELOR DEGREE IN
INFORMATION TECHNOLOGY, OF
KAMPALA INTERNATIONAL
UNIVERSITY
JUNE, 2011 ACKNOWLEDGEMENT
We would like to take this opportunity to express our gratitude towards all the people who have helped me in various ways, like in the successful completion of our project.
We must convey our gratitude to Ms. Kamulegeya Grace For giving us the constant source of inspiration and help in preparing the project, personally correcting our work and providing encouragement throughout the project.
We also thank all our faculty members for steering us through the tough as well as easy phases of the project in a result oriented manner with concern attention. ABSTRACT
Uganda Airline is a leading travel company offering leisure and business travelers the widest selection of low fares as well as deals on lodging and vacation packages. The system was created to address the need for an unbiased, comprehensive capture and display of fares and rates in a single location for passengers.
Uganda Airline search results are presented in an easy-to-use Matrix that displays a vast array of travel options for you. Uganda Airline is the first and only travel system with an online 24 hours Customer Care
Team that monitors nationwide travel conditions for our travelers around the clock, everyday.
Uganda Airline is a system, which helps the flight travelers. Its mission is to offer flexible leisure travelers a quick and easy way to get better deals on airline tickets. All purchases made on Uganda
Airline are not final and can be cancelled, refunded or changed. If you want, you can also receive your updates by calling Customer Care on toll-free number and using your personalized PIN. When customers prefer a specific travel itinerary, they offer the widest range of flight options and fares. APPROVAL
The Graduation project entitled, “an optimized secure online air ticket reservation system, a case study of Uganda Airline”, is submitted to Kampala International University, school of Computer Studies with the approval of the Supervisor.
SUPERVISOR : MR. KAMULEGEYA GRACE
SIGNATURE : .
DATE DEDICATION
We dedicate this publication to our beloved parents, and family members who endeavored to support us and saw potential in us, and for the love and encouragement and support during our years of education struggle.
May God Bless you all!
V Table of Contents
ACKNOWLEDGEMENT.
ABSTRACT ii DECLARATION iii APPROVAL iv DEDICATION v Table of Contents vi CHAPTER ONE 1 INTRODUCTION 1 1 .0 Introduction 1.1 Background 1 1 .2 Problem statement 2 1.2.1 New system 2 1.3 Scope ofthe study 3 1.3.lSystem scope 3 1.3.2 Geographical scope 3 1.4 Purpose of the study 3 1.4.1 Objectives of the study 3 1.4.2 Main objective 3 1 .4.3 Specific objectives 3 1.4.4 Research Questions 3 1.5 Functional requirements 4 1.6 hardware and software requirements 4 CHAPTER TWO 4 LITERATURE REVIEW 5 2.0 Introduction 5 2.1 Online Ticketing and Functionality of Websites 5 2.2Online Ticketing and Online Marketing 6 2.3 Online Ticketing and Server Capacity of the website 7
vi CHAPTER THREE . 9 METHODOLOGY 9 3.0 Introduction 9 3.1 Data Collection techniques /tools of data collection 9 3.1.1 Questionnaire 9 3.1.2 Observation 9 3.1.3 Interview 9 3.1.4 Internet and reading available Documents 9 3.2 System design 10 3.2.1 Data flow diagram 11 3.2.2 Entity Relationship diagram Error! Bookmark not defined. CHAPTER FOUR 13 SYSTEM ANALYSIS AND DESIGN 13 4.0 Introduction 13 4.1 System analysis 13 4.2 Level 0 Data flow diagram 15 4.3 Level IThe Data Flow Diagram (DFD) serves two purposes~ 16 Database Design 1 8 4.4.1 Entity relationship diagram 18 4.4.2 Screen prints of database Tables 19 Passangers detail 19 Flight information 19 Concession 20 Route fare 20 Ticket reservation 21 Enquiry 21 Cancellation 22 4.5 Algorithms 22 Reservation Algorithm 22 Cancellation 23 Flight 23
vii Concession Algorithm . 23 CHAPTER FIVE 24 SYSTEM TESTING, IMPLEMENTATION AND MAINTENANCE 24 5.1 System testing 24 5.1.1 Unit testing 25 5.1.2 Module level testing 25 5.1.3 Integration & system testing 26 5.1.4 Regression testing 26 5.2 System Implementation 26 5.2.1 Implementation methods~ 26 5.2.2 Implementation plarr 27 5.2.3 Educations and training 27 5.2.4 Post implementation review 28 5.3 Maintenance 28 5.3.1 There are three types of maintenanceS 28 INPUT SCREENSHOTS 29 Figure 5.OThis is a picture of the Login form 29 Figure 5.1 This is a picture of the main menu 29 Figure 5.2 This is a form of passenger detail 30 Figure 5.4 This is a form of flight information 32 Figure 5.5 This is a form of the route fare 33 Figure 5. 6 This is a form of reservation 34 Figure 5.7 This form is enquiry 35 Figure 5.8 This form is passenger’s payment 36 Figure 5.9 This is a cancellation form 37 REPORTS 38 Passengers details report are shown below 38 This is a report of concession form 39 Testing debugging and validation 39
VIII CHAPTER SIX .40 RECOMMENDATIONS AND CONCLUSION 40 6.0 Introduction 40 6.1 System service management 40 6.1.1 Input control and output control 40 6.2 Security control 40 6.2.1 Data security control 40 6.2.2 Software and Hardware control 41 6.3 Recommendation 41 6.3.1 Backup 41 6.3.2 Error recording and analysis 41 6.4 Conclusion 41 REFERENCES 42 APPENDICES 43 Appendix:A 43 Interview questions for internal workers 43 Appendix: B 44 Questionnaire used 44 Appendix C~ 46 Definition of the terms used 46 Appendix D 47 Meaning of the abbreviations used 47
ix CHAPTER ONE
INTRODUCTION
1.0 Introduction This project looked into the factors were influencing the effective management of a centralized online ticketing by airlines in Uganda and suggest effective ways to improve some of them by developing and implementing a sample system. Subsequently, this chapter presents the background to the problem of inefficient management of online air ticket by airline companies in Uganda, statement of the problem, purpose of the study, specific objectives of the study, scope of the study and significance of the study.
1.1 Background The airline reservation system maintains information
o on flights,
o classes of seats,
o personal preferences,
o Prices and bookings. The system allows three classes of users: casual, registered and administrators. These users view flights on particular days and book seats. Before finalizing the booking of a flight, personal information must have been entered. Registered users may go on a waiting list for seats if the desired flight does not have enough free seats. Management of the waiting list was left undefined. Registered users must logon using a user_id and password, and the system maintains personal information for such users. Registered users may view and update their personal information.
The “Air Uganda” helps Airlines serve their passenger by following a tailored version of the organization’s standard process called “The Frequent Flyer Program”. The goal of the Uganda Airline was to ensure that passenger login, view and manage their acquired miles through a beautiful, user friendly front-end. This document records the transactions of the user like all the details of his acquired miles in their airlines. Through this application, the Airlines can automate the process of updating the various details associated with its scheme for frequent passenger; thus, avoiding manual or telephonic overhead involved in providing information and book keeping.
1 The user, by entering his unique user id and password, can login to his account and avail the online services like checking the no. of miles acquired, and the various benefits entitled to him for it. The airlines, on the other hand, can make its announcements on new schemes to be introduced. This kind of application over the internet enhances the chances of attracting new passenger as well as retaining the old ones.
1.2 Problem statement The existing airline reservation system has many shortcomings associated with it. In the existing system airlines used to set flight reservation levels higher than seating capacity to compensate for passenger cancellations and no-shows accounting to overbooking in the system. If a passenger has to make / cancel reservation he has to visit either the airline or travel agent frequently to do so thus wasting time and money for all.
o In the existing system due to non-availability of a central server the airline and the agents suffered unwanted delays in bookings and payments.
o In the current system integration of different airlines on a single platform was not met. With the advent of the online reservation system these flaws can be overcome.
The following were the features of the Existing System
o The transactions are maintained manually.
e There is no separate user to interact with the database in the former system.
o Not very user friendly interface because manual, complexity and logical flow information in the system.
1.2.1 New system The new online reservation system maintains the database centrally giving the clients the information required from anywhere in the world whenever required. This system requires the use of an API (Application Programming Interface) through which the data from central database extracted. The central database monitors all the data changes that are made at the client side to it and updates it automatically.
Through centralized online reservation system, passenger is able to book & purchase the ticket from his home/office conveniently it doesn’t require the passenger to go to the airline or an agent to purchase a ticket thus saving time & money for the passenger and an
2 airline/agent. As the information is stored centrally the passenger never loses his ticket as in the existing system.
1.3 Scope of the study
1.3.lSystem scope
The new system was designed in consideration to all the limitations of manual system. Existing manual system & as per the requirement suggested by user. It is designed in such a way that it hold all the information that they need for data processing & to generate various reports as per requisition.
This project does not include the development of centralized authentication of ticket payments, account password recovery via e-mail, e-mail notification of any events regarding payments and/or seat reservations, any forms of trip planning, and any forms of passenger/member’s loyalty reward system.
1.3.2 Geographical scope The system capture all the information from the clients from anywhere in the world and backup the data in one database from which the daily transactions and programmes of the day are determined in the company, therefore it’s a standalone system that operates on LAN(Local Area Network)
1.4 Purpose of the study
1.4.1 Objectives of the study The study was to achieve the following objectives:
1.4.2 Main objective To provide reliable services to passengers anywhere in the world
1.4.3 Specific objectives 1. To reduce Manual work 2. To save passengers from wasting their time in both moving to respective offices to reserve a ticket and queuing at those branch offices. 3. To Increase speed, storing and accuracy. 4. To decreases manpower and high cost.
1.4.4 Research Questions The study was to answer the following questions:
1. How can a centralized online reservation system reduce manual work?
3 2. Can the new system save passengers from wasting their time in both moving to respective offices to reserve a ticket and queuing at those branch offices?
3. How can increased speed and accuracy be obtained by the new system?
1.5 Functional requirements The study was to discover and minimize the challenges of online airline ticketing in Uganda and the results are beneficial to online ticketing companies since it has exposed the challenges faced in e-ticketing. Importantly, this has helped organizations to improve their online ticketing management, which benefits both the companies and their clients. ICT scholars will also find the study useful because it is conceived from ICT theoretical point of view. Lastly, the study is now a reference for researchers, especially ICT, since it was hoped to follow a basic approach.
1.6 hardware and software requirements
Processor : intel(R) dual core Clock speed 2 GHz System bus 32 or 64 bit Ram : 2GB Hard Disk : 5GB Operating system : windows xp and or windows7 all version Browser internet explorer, firefox, chrome, opera safari Database layer Msql Web server : Wampserver 2.Oa Server side scripting : jsp, PHP, jQuery Client side scripting java script
4 CHAPTER TWO
LITERATURE REVIEW
2.0 Introduction This chapter prevents a review of concepts, variables, issues and concern related to the study. For clarity, they are arranged according to the three concern of the study.
2.1 Online Ticketing and Functionality of Websites It’s very imperative to have a functioning website if online ticketing was to be effective. No matter how good a webs ite is if it’s non functional, it always shunne. The process of webs ite functionality begins at its construction, which means that it was constructed in such a way that it will become difficult for its users to get any information they may need.
Some sites functioning such way that they don’t have any specific purpose. They tend to handle different things at a time. This confusion led to the site being shunned (Black, 2009). Black (2009) further urges that the goal of a website is to sell something, persuade, invite, and attract people to come in and spend some time within its confines. To achieve this goal designer must avoid confusion and unnecessary complex design.
They must not use any element which distracts the user from the basic purpose of the site. A simple and informative site outperforms a complex one anytime. There is so much more to website design than just making a few web pages look pretty if you want to succeed. You need to consider your target audience, underlying message, content, desired responses, visitor impact, and online goals, how you are going to measure the success of the site and more.
Most of the internet users are impatient. If they don’t find quickly what they are looking for, they simply leave the site. A site serves its purpose more effectively if the site is user friendly. If you want to have long term benefits its usability matters and not the design and appearance.
The usability needs of a site partially depend on the nature of the site. For example, a large e commerce site must have an effective search function, logical categorization of products for browsing, a user-friendly shopping cart, etc. A Service provider’s site should list their services in a detailed manner after going through which, the customer should be able to pick the service and contact the concerned person easily. The whole process should be hassle free to encourage repeat visitors.
5 In addition to providing visitors with an easy way to move through the site, navigation is often used by designers to create more visually-appealing websites. Although navigation provides designers with a great opportunity to improve the look of the site, attractiveness should not come at the expense of usability and accessibility.
While developing links web developers should think about which pages are most likely to be visited by visitors and which pages are critical for the purpose of the site. Link location also plays a vital part; we must consider how many clicks it takes a visitor to get from the hornepage to any other specific page.
2.2Online Ticketing and Online Marketing
Online marketing refers to the marketing of the products or services over the internet (www.wikipedia.org). Other than the functionality of websites, however, there is the issue marketing. Here, it’s very important to employ strategies that may win over customers to buy your products. In a one-to-one approach, marketers target a user browsing the Internet alone and so that the marketers messages reach the user personally. This approach is used in search marketing, for which the advertisements are based on search engine keywords entered by the users. This approach usually works under the pay per click (PPC) method.
When appealing to specific interests, marketers place an emphasis on appealing to a specific behavior or interest, rather than reaching out to a broadly defined demographic. These marketers typically segment their markets according to age group, gender, geography, and other general factors. Niche and hyper-niche internet marketing put further emphasis on creating destinations for web users and consumers on specific topics and products.
Niche marketers differ from traditional Internet marketers as they have more specialized topic knowledge. For example, whereas in traditional Internet marketing a website would be created and promoted on a high-level topic such as kitchen appliances, niche marketing would focus on more specific topics such as 4-slice toasters.
Niche marketing provides end users of such sites very targeted information, and allows the creators to establish themselves as authorities on the topic or product. In Internet marketing, geo targeting and geo marketing are the methods of determining the relocation of a website visitor with reallocation software, and delivering different content to that visitor based on his or her location, such as latitude and longitude, country, region or state, city, metro code or zip
6 code, organization, Internet Protocol (IP) address, Internet Service Provider (ISP), and other criteria.
2.3 Online Ticketing and Server Capacity of the website
Even where there is a functioning website as well an effective online marketing strategy, it’s important that the website in place should have a well meaning server capacity. This is because at the end of the day it the capacity of the server of the website that matters a lot. With corporate Web sites getting millions of hits per day, the choice of Web-server software can be critical. Web servers that don’t respond crisply under heavy loads can bog down network connections, deny service for visitors, and cause network failures. For administrators of large sites or others seeking to differentiate among the wide variety of Web-server software packages, the Standard Performance Evaluation Corp.’s SPECweb96 benchmark can in many cases help determine which Web-server software performs best on a particular set of hardware systems and network connections. Though SPEC officially released SPECweb96 1.0 in September, production problems with the Windows NT version delayed release of the CD-ROM software until the end of December. This software can evaluate the performance of Web-server software running on virtually any Unix system or Windows NT platform. Like SPEC’s other benchmarks, SPECweb96 is a standardized performance benchmark created in a spirit of cooperation among competitors. As a non-profit organization, SPEC oversees the development and creation of benchmarks by using the technical resources of member companies. The result is a benchmark that has been examined by all interested parties and is considered a fair test of performance by them. For SPECweb96, companies as diverse as Digital Equipment, Hewlett Packard, IBM, Intel, Netscape Communications, Siemens Nixdorf~ Silicon Graphics, Sun Microsystems, and others helped shape the benchmark. A SPECweb96 test bed consists of a server machine that runs the Web-server software to be tested and a set number of client machines. The client machines use the SPECweb96 software to generate a workload that stresses the server software. The workload is gradually increased until the server software is saturated with hits and the response time degrades significantly. The point at which the server is saturated is the maximum number of HTTP operations per second that the Web-server software can sustain. That maximum number of HTTP operations per second is the SPECweb96 performance metric that is reported. For example, the SPECweb96 performance metric of the sample machine in the table and graph on page 58 is 626 HTTP operations per second.
Although SPECweb96 can do an admirable job of testing Web-server performance, you may not want to rush out and pay $800 for the CD-ROM without first considering what SPECweb96 is testing and what kind of test bed you’ll need. It can take some serious network resources to properly test Web-server software, and your site may not be ready to take on such software configuration responsibility. Also, as with most benchmarks, you’ll need close to-laboratory conditions to make accurate comparisons among systems. CHAPTER THREE
METHODOLOGY
3.0 Introduction This chapter provides a general overview of the data gathering method used to collect data for analyzing of using information systems for online ticket reservation.
3.1 Data Collection techniques / tools of data collection
3.1.1 Questionnaire Using this method, a researcher was used as a printed document to the company which contained standardized questions that were to be answered by the users of the current system and to some of the staff. gather information systems for competitive advantage in airlines.
The method was used because, it enables the respondents to answer the questions in their free time and it gives an opportunity to get accurate information since it was designed in less tense information systems for competitive advantage in airlines. (Jude, 1990)
3.1.2 Observation Using this method, the researcher had to observe important points that will not be revealed by the respondents in interview on analysising the information systems for competitive advantage in airlines.
This method was re-approved the validity of the data collected through interview that could not provide a clear explanation by the respondents.
3.1.3 Interview With this method, the Analyst visited company offices. This will provide the researcher with information regarding how they (Directors) keep the records. From this the researcher was able to analyze the system.
3.1.4 Internet and reading available Documents The growing popularity of the Internet has brought a major shift in Electronic Data Reporting and data collection. The researcher took the advantage of the internet being an ocean of information to study well established organization that uses the federal bureau of investigation Laboratory and other law enforcement agencies began developing programs to examine information systems for competitive advantage in airlines. The researcher also accessed some information systems for competitive advantage in airlines and look at how they are issued which helped in designing of the proposed system and redesigning the forms to suit the information systems for competitive advantage in airlines.
3.2 System design In this phase initially we had designed E-R diagram of the processes, in order to identify various entities and relationship set, entity set, attributers, link attributes .The Diagram of this process as under.
After this step we had tried design the data base for the new system and normalized it
The tables motivated in data dictionaries enclosed as an outcome of this step
The symbol of entities are shown bellow
Entity sets ~io.isl~ipset~
Line 3.2.1 Data flow diagram
Figure 3.2 Data flow diagram
RECEIVE Flight MAINTENANCE, RESERVING, cancellation PASSANGER
PASSENGER
LIST AIRLINE
RESERVATION WAITING LIST
DATA STIRAGE DATAACCESS
Passenger list, Ticket reservation Flight information, Cancellation, Concession 3.2.2 Entity Relationship diagram
Figure 4.2.1: E-R diagram CHAPTER FOUR
SYSTEM ANALYSIS AND DESIGN
4.0 Introduction. This chapter shows how data was collected, analyzed, the system functional requirements and how a system that implements those requirements was designed. In the study, the researcher used questionnaires as the major techniques. After the data was collected, it was analyzed.
4.1 System analysis This was the most important phase of our project life cycle .It had connected our maximum time .The block diagram given bellow depict various fact which were understood by one during the analysis phase.
Figure 4.1 System Architecture
RECEIVE Flight MAINTENANCE, RESERVING, cancellation PASSANGER
PASSENGER
LIST AIRLINE
RESERVATION WAITING LIST
DATA STIRAGE DATA ACCESS
Passenger list, Ticket reservation Flight information, Cancellation, Concession In that phase initially we had observed the system by visiting to Entebbe Airport (domestic terminal) and a few airline reservation agencies. The above block diagram is an implementation of this observation. In the next phase we had various quires in our mind, which we tried to ask from appropriate authorities a sample of our quires are enclosed as: Q.l The features to be included in the new system?
o Enquiry o Reservation o Cancellation o Report e Edit o Other specify
Q2. How the system should be?
o Multi-user • Single user 0 Q3. The reports to be Incorporated from the system?
o List of all passenger o List of all flights o List of passenger(date wise) o List of passenger(flight wise) o Any other
After getting solution our queries we started studying database structure used in the existing system. In this connection we had come to know about various master files as
In passenger list: Passenger ID, name, passport no, Gender, Address, phone, d_o_b, Religion, Email, marital status, Designation. Flight info: flight_code, flight_name, Departure, Arrival, Source, Destination, Miles, fare.
Concession: concession_code , flight_code , class_name , discount , v_o_t , baggage
allowance , fare.
Route Fare: route code, destination place, Via, source place, Departure time, stoppage, Arrival time, Flight code, class_code, Fare.
Reservation: Ticket_no, PNR, flight code, flight_name, destination place, source place, reporting time, departure time arrival time, Class, Fare, number of passenger, Age, sex, Fare, seat_no.
Payments: Ticket_no, flight_code, class, creditCard_no , Account_no, pin_no, Amount,
means of payment, date_Today , payment_date. Enquiry: Passanger ID, Flight_name, Class, seat number, pnr.
Cancellation: Pnr, ticket no, Days left, Basic amount, Cancel amount. Various categories of flight code are display here AF, STF, FAA, CRF and CSF in this process further we had visited the air port again in order to interview people to know more about the system. The main purpose was to analyses the method of calculating daily income reservation cost generation methods, and few concern things
4.2 Level 0 Data flow diagram As information moves through software, it is modified by a series of transformations. A Data Flow Diagram (DFD) is a graphical technique that depicts information flow and the transformations that are applied as data move from input to output. The data flow diagram is known as a data flow graph or a bubble chart.
The Data Flow Diagram are used to representation a system or software at any level of abstraction.
In fact, DFDs were partitioned into levels that represent increasing information flow and functional detail. Therefore, the DFD provides a mechanism for functional modeling as information flow modeling.
Figure 4.1 Level 0 (context level) data flow diagram
REQUEST FOR INFORMATIONFLIGHT/FARE/DISCOUNT
IN FORMATION 4.3 Level iThe Data Flow Diagram (DFD) serves two purposes: 1) To provide an indication of how data are transformed as they move through the system
2) To depict the functions that transforms the data flow. The DFD provides additional information that is used during the analysis of the information domain and serves as a basis for the modeling of function.
A Level 0 DFD also called as fundamental system model or a context model represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows respectively. Additional processes and information flow paths are represented as the level 0 is partitioned to reveal details. Each of the proves represents at level 1 is sub function of the overall system depicted in the context model. Each of the process was refined are layered to depict more detail. Information continuity must be maintained in every layer, that is input and output to each refinement must remain the same
In order to design a better solution. We have designed the DFD for system including all technical processing details is given bellow Figure 4.2 Level 2 DFD of Reservation
PASSENGER SPOT)
BOOKING NOW
CASH BY DATE
DAV~IHKIT ACKNOLEDGE
BOOKING
CHOOSE MODE OF PAVMRMT DEVIT NUMBER
PAY CASH
A Database Design 4.4.1 Entity relationship diagram
Reservation
Ticketn o Name
F ro rn Gender To 1 Nationality fare
Ticketno
Class
Seatno V V Flight Cancellation date
z~t. Ticketno
Class
arrival S eat no
from date 4.4.2 Screen prints of database Tables.
Passangers detail ~ Server: locaihost ~ ~ Data ~ Ta. : passanger 7nnoDB (row 6144kW
~Bro ~ i~SOLl H ~ Export Hf-~Import ~Opera~ons. Empty Drop
••; ~ ~ ~1 pass_Id int(11) No ~ ~ ~ ~fllL4 fflame ~archar(1OO) lalin1~s~ishci flt ~ ~ jP ~XJ ~ ~i El Iname varchar(100) ~ahn1_swed,sh_ci No ~ X ~ I ppUto ~ v~rchar(1OO) i~hn1~wedIsh~ci~ No~ ~‘ X ~ El gender varchar(100) latini_swodish_ci No ~ jP ~dZ varchar(1I e)1_~wedish~ ~ El nationality varchar(100) Iatinl_swedishci No ~ ~Q ~ii~jon varchar(1ii) tahn1~swodIshci ~
El :.,. ~~archar(.1QO)lahn,1_swedish_ci No
El phone~ F~öo~ _se~s~_ci ~ ~ ~ ~ ~‘ ~ ~P ~ El email varchar(100), latini_swedish_ci No ~ ~
El rn~taiz. var~ar(iOO) ~1ahn1swedishci No j~ X ~, ~
El -! varchar(100) lalini_swedish_ci No ~ ~ ~ i~j ~ ~L_ Check All tincheck All With selected
Flight information
~ Server: locaihost ~ ~ Database: R- rvatlon ~ Table: flight ‘lnnoDB free: 6144kW
~~ S ~seri; ~Expo~ ~nport ‘,~Operaflons ~Empty~Drop
~Field ljpe Cdfla~on~ Attributes Null Default Extra Acholi ~1 fllgtld varchar(1II) tahnl_swedisb_ci No X ~ El
~ ‘~ppt~~’~ ~ch~i~i’t~’) Iahi1~swedsh~ci~ ~ “~No~’ ~, ~ ~ fllghtName varchar(100) lahnlswedishc No ~1 ~ X ~ ~
[~]j dep ie1~ varch~r(ffX)) ~tIn1Lsw~1Ist~_ct ~No~ ~ )~ El ~ arrival varchar(100) ~tin1_swedish_ci No ~ j X ~ C from varchar(100) ~~hn1_sw~hci No ~ I )( ~ C to varchar(100) lahnl_swedish_ci No ~I / X ~
C fare ~yarchar(1bU) ~edish_c~ - No - X ~ C session ~rchar(1OO) Iahnlswedislici No ~1 / X ~ L CheckAil UncheckAHi6~thseiected: ~ Concession Server: locaihost ~ ~ Database: Reservation ~ ~ Table: concession ‘InnoDB fv~e: 6144 kB”
~ ~SQL ~Search.i~lflsert~ :.i~Expoit~ ~frnporti ~‘ Op rations ~ Empty ~Drop.
t• ~p .‘~. olation D~ E~fra Aon
P oncJd int(11). ‘No ‘ .~ / .x..~ ~
~‘ pptjio varchar(1 ii) ~hn1_~swedishci No ~- £ ~ l~l filghtcode ~rchar(1 II) Iahnl_swedish_ci 2~. No
I~J dan ~ varchar(~tII) ~ahn1_swedishci No~ / ~ ,~archar(iOO) ~hn1.swed~h~ci ‘No’
l~ bagjll ar(i~m) ~labñ1_swedisli~ci N .~ I’ ~ ~ dlscount varch~r(1OO) Iahnls*edishcI ‘No ~
~ ~... ~rciiar(iOO)~ ,~hñ1~s~iish ci . -, t~ CheckAfi UncheckAlHMthselected: ~
Route fare ~) Server: localhost p ~ : Reservation p (~ Ta. :route7nnoDBfree6144kB~ ~Sáah~1 pal ~Operatiàns ~~Empty.~Drop
~flation ~Atbibutu~.N~ufl ~ ~A~tioñ .~ I~ rt-Id int(11) No ~ I X ~
~lD pptno ~, varchØ1OO)~ Iahnl_sw h’~ci~ No ~ I routecode varchar(100) latinlswedtshci No ~ I X ~ ~
I~J ~m ~archai(1OO) ~ahn1_swedish~ ~‘ ~ N~ ~ / f~ vii varchar(100) lahnlswedishci No ~ ./ ~1~!] ~jo ~yarchar(1~)) ~bn1_~~_~ ~Noc ~ ~) departure varchar(100) Iahnl_swedtshci No ~ I X ~ O~ stopage ~archar(4 ii) IatIn~!edish_cI[ No ~ ~ ~ afTival varchar(100) latinlswedishci No ~) I ~ ~.Yi ~
~‘~[~j ~mghtName varchar(j~I )~ ji1_~q~h~h.~c1, ~ ‘~ N~ I ~ 0 dasa varchar(100) latini Swedish ci No ~ I X ~
El fare~1, ~ varchar(100) ahh1_~~h~h.~ci .. No ~‘ ./ X ~ t Check All Uncheck All With selected: ~ 19 Ticket reservation ~I Server: locaihost ~ ~ Data. : R rvatlon ~ ~ Table: booking InnoDB free: 6144 kB~
~Browse .~Lt~cture SQL~ dSearch -. ert Export Import Empty Drop
Field H Foli~ilc~n~ ~ NuN Defatdt Exfra Action
bkjd iiit(ii) - NO it X ~ T~] ppt~rio har(~10ó5~’ tatini_swedish_ci No ~ it )( ~ I~Z) tickebto varchar(100) tatini_swedish_ci No ~ it X ~
J] pnr ha~) lahnlswedishiici ‘ No it X ~ ~1 fllghtName varchar(100) latin1_swedish~ci No it X ~ class ~ varchar(100)~ lalini_swedish_ci No [~] seatno varchar(l00) latinl_swedish_ci No .1 X ~ ii~ fare varchar(~100) lahnl_swedish_ci No it ~J from varchar(100) latini_swedish_ci No ~ it T via varchar(100) talini_swodish_ci No I~J to varchar(1 00) JatinI_swedish_ci No it X ~
name varchar(100) Iatinlswedishci ~ No it - l!rifloc arciiar(~Ia)latin1_swodish_ci No
varchar(~1 I I) tahn~_swed,sh_ci No it X ~ - t~] tdate varchai(100)- labn1sw~dishci No it
-~‘; varc~ No
Enquiry
~J Server locaihost ~ i-.. : R rvatlon ~ ~jjj Table: equiry 7nnoDB froo 6144kW
~~ro ~ Séarch~ i~E~p~itr.ii&npoét~ Ope . ~Empt Drop
ld: P! ~ ~ ~w Action..
f!1 Id int(1i) ‘- No ~ it )~ ii
~ Lvarchar(100) at~_swed~_ce ~o ., it !!~] name varchar(100) Iahnl_swó,dish_ci No ~ it X rn.!] ~
~ varchar(100) tab~1_swedis~_ci -i No it T ~-seatno -varóhar(100)tatinlswedishci No ~ X ~ El tdate’ ~varchar(100~ tahn~s~,sh_ci No
•varàhar(100) ~1_swedish~ci- No .- . it t Check All I Uncheck AD With selected: ~
Pnnt view ~ Relation ~new ~ Propose table structure ~ ______Add 1 field(s) ~ö) At End of Table o At Beginning of Table ~ After id [~] Cancellation
~j Serv r: locaihost ~. ~ Database: ReservatIon ~ ~ Table: on lnnoDB free: 6144 kB~
: Bro ~ ~ SQL Search ic rt - Export Import Emp~ ~Drop
.J ~. 1~j1eId Type” C~ij~ón. Attilbutes Null Default Exfra Action ~D ca1!~~IJd int(11) .: NO ? X ~ T
~. ~ir~ ~~ ~ i Ii. ticketnö varchar(100) lahnlswed,ci No ~ jP X ~
class ~varchar(~9) I~hn1_swedi~h~ ,,~, N~’ ‘ iP X ~ is seatno varchar(1 is) latmi_swedish_ci No ~ ‘F ~ dleft varchar(100) ~~‘iswedishci No l~ P )( ~ ‘F ~] bamoiint varchar(100) Iahnlswodishci No ~ P X ~ ~ fine’ I varci~fOO) ~ti’n1ts%~Ishci’ ~lo, ~ P 7
[E] bal varchar(100) Iatin1swedi~hci No P X ~ ‘F t_ Check All Uncheck All With selected: ~
4.5 Algorithms In this phase further we designed algorithms for various technical sub problems a few than are enclosed here with. Reservation Algorithm
• A person comes to reserve a ticket. • then he gives his full details • In passengersform those details were written. • then computer check the date what date the person reserved • date wise it checks the flights • if theflight isflying that day • then system justify the spec~/1c flight code • It checks its seat class. • ~f the passenger want to economic class and window side seat • then system checks if there any seat in economic class which is inside the window • Ifseat is empty then system reserved the seat. • Then ticket is generated • The ticket is confirmed • ~f the condition is not applied then it check next sea • andjustified it. • ~fit is not also empty then it check next by next. • ifthere is no seat then system take ticket which is not confirmed • Then it gives waiting list. •End Cancellation
o a passenger come to cancel the ticket o then the system open the delete form o then click shoe command o it display all the passenger list o then select the Ticket number and click delete option o the system show record is deleted.
when passenger come to reserved a ticket then system find out the flight details. system click flight details option then the flight details form open those system are followed. Flight
in flight details we first create a form. o then we made all text box.
e . we create command box..
o . in this form we are use various command box those are o previous, first, next, addNew, update, delete, save o in this form we add new flight record and update ii then the o value go to the database o when we click next, last, previous, first command button e Then it show various thing serially. o a person come to know the timingsfor the flight which is go Source airport to destination airport.
o Then we click show command button.
Concession Algorithm
o First it clicks the concession box. e concession box open o It selects the categories. o Then it is calculate. o And the fare is calculated. e Then finalfare is generating in ticket. CHAPTER FIVE
SYSTEM TESTING, IMPLEMENTATION AND MAINTENANCE
5.1 System testing
System testing is a critical aspect of Software Quality Assurance and represents the ultimate review of specification, design and coding. Testing was a process of executing a program with the intent of finding an error. A good test was one that had a probability of finding an as yet undiscovered error. The purpose of testing was to identify and correct bugs in the developed system. Nothing was complete without testing. Testing was vital to the success of the system.
In the code testing the logic of the developed system was tested. For this every module of the program was executed to find an error. To perform specification test, the examination of the specifications stating what the program should do and how it should perform under various conditions.
Unit testing focuses first on the modules in the proposed system to locate errors. This enables to detect errors in the coding and logic that are contained within that module alone. Those resulting from the interaction between modules are initially avoided. In unit testing step each module has to be checked separately.
System testing does not test the software as a whole, but rather than integration of each module in the system. The primary concern was the compatibility of individual modules. We had to find areas where modules have been designed with different specifications of data lengths, type and data element name.
Testing and validation are the most important steps after the implementation of the developed system. The system testing was performed to ensure that there are no errors in the implemented system. The software must be executed several times in order to find out the errors in the different modules of the system.
Validation refers to the process of using the new software for the developed system in a live environment i.e., new software inside the organization, in order to find out the errors. The validation phase reveals the failures and the bugs in the developed system. It came to be known about the practical difficulties the system faces when operated in the true environment. By testing the code of the implemented software, the logic of the program can be examined. A specification test was conducted to check whether the specifications stating the program are performing under various conditions. Apart from these tests, there are some special tests conducted which are given below: Peak Load Tests: This determines whether the new system was to handle the volume of activities when the system is at the peak of its processing demand. The test has revealed that the new software for the agency is capable of handling the demands at the peak time.
Storage Testing: This determines the capacity of the new system to store transaction data on a disk or on other files. The proposed software has the required storage space available, because of the use of a number of hard disks. Performance Time: Testing this test determines the length of the time used by the system to process transaction data.
In this phase the software developed Testing was to exercise the software to uncover errors and ensure the system meets defined requirements. Testing was done at 4 levels
Unit Level • Module Level Integration & System Regression
5.1.1 Unit testing
A Unit corresponds to a screen form in the package. Unit testing focuses on verification of the corresponding class or Screen. This testing includes testing of control paths, interfaces, local data structures, logical decisions, boundary conditions, and error handling. Unit testing was used Test Drivers, which are control programs to co-ordinate test case inputs and outputs, and Test stubs, which replace low-level modules.
5.1.2 Module level testing Module Testing was done using the test cases prepared earlier. Module was defined during the time of design. 5.1.3 Integration & system testing Integration testing was used to verify the combining of the software modules. Integration testing addresses the issues associated with the dual problems of verification and program construction. System testing was used to verify, whether the developed system meets the requirements.
5.1.4 Regression testing Each modification in software impacts unmodified areas, which results serious injuries to that software. So the process of re~testing for rectification of errors due to modification is known as regression testing.
5.2 System Implementation
Implementation includes all those activities that took place to convert from the old system to the new. The old system consists of manual operations, which operated in a very different manner from the proposed new system. A proper implementation is essential to provide a reliable system to meet the requirements of the organizations. An improper installation may affect the success of the computerized system
5.2.1 Implementation methods:
There are several methods for handling the implementation and the consequent conversion from the old to the new computerized system.
The most secure method for conversion from the old system to the new system was to run the old and new system in parallel. In this approach, a person may operate in the manual older processing system as well as start operating the new computerized system. This method offers high security, because even if there was a flaw in the computerized system, we could still depend on the manual system. However, the cost for maintaining two systems in parallel was very high. This outweighs its benefits.
Another commonly method was a direct cut over from the existing manual system to the computerized system. The change was within a week or within a day. There are no parallel activities. However, there was no remedy in case of a problem. This strategy required careful planning.
A working version of the system was also implemented in one part of the organization and the personnel piloted the system and changes could be made as and when required. But this method was less preferable due to the loss of entirety of the system. 5.2.2 Implementation plan: The implementation plan included a description of all the activities that must occur to implement the new system and to put it into operation. It identifies the personnel responsible for the activities and prepares a time chart for implementing the system. The implementation plan consists of the following steps.
• List all files required for implementation.
o Identify all data required to build new files during the implementation.
o List all new documents and procedures that go into the new system.
The implementation plan should anticipate possible problems and must be able to deal with them. The usual problems was missing documents; mixed data formats between current and files, errors in data translation, missing data etc.
5.2.3 Educations and training
The implementation of the proposed system includes the training of system operators. Training the system operators includes not only instructions in how to use the equipment, but also in how to diagnose malfunctions and in what steps to take when they occur. So proper training should be provided to the system operators. No training was complete without familiarizing users with simple system maintenance activities. Since the proposed system was developed in a GUI, training will be comparatively easy than systems developed in a non-GUI. There are different types of training. We can select off-site to give depth knowledge to the system operators.
Success of the system depends on the way in which it was operated and used. Therefore the quality of training given to the operating person affects the successful implementation of the system. The training must ensure that the person can handle all the possible operations.
Training must also include data entry personnel. They must also be given training for the installation of new hardware, terminals, how to power the system, how to power it down, how to detect the malfunctions, how to solve the problems etc. the operators must also be provided with the knowledge of trouble shooting which involves the determination of the cause of the problem. The proposed system requires trained personnel for operating the system. Data entry jobs must be done utmost carefully to avoid errors. This was to reduce the data entry errors considerably. It was preferable to provide the person with some kind of operating manuals that would explain all the details of the system.
5.2.4 Post implementation review
After the system was implemented, a review should be conducted to determine whether the system is meeting expectations and where improvements are needed. System quality, user confidence and operating systems statistics are accessed through such technique event logging, impact evaluation and attitude surveys. The review not only assesses how well the proposed system is designed and implemented, but also is a valuable source of information that can be applied to a critical evaluation of the system.
The reviews are conducted by the operating personals as well as the software developers in order to determine how well the system was working, how it has been accepted and whether adjustments are needed. The review of the system was highly essential to determine the future enhancements required by the system. The system can be considered successful only if information system has met it objectives. The review analyses the opinion of the employees and identifies the attitudes towards the new computerized system. Only when the merits and demerits of the implemented system are known, one can determine what all additional features it requires are. The following are the issues to be considered in the evaluation of the system.
5.3 Maintenance
Maintenance is making adaptation of the software for external changes (requirements changes or enhancements) and internal changes (fixing bugs). When changes are made during the maintenance phase all preceding steps of the model must be revisited.
5.3.1 There are three types of maintenance:
1. Corrective (Fixing bugs/errors) 2. Adaptive (Updates due to environment changes) 3. Perfective (Enhancements, requirements change INPUT SCREENSHOTS As a last step in design phase I had designed various Input and output inter phase screen The sample format of these screens were enclosed.
Figure 5.OThis is a picture of the Login form.
WEL COME TO U€ANDA AIRUNE RESERVATiON USTEM 1.0 FORM ~ ugandaa~nes
JjserNan,e: waku
flie6et
Figure 5.1 This is a picture of the main menu.
~.mrnu
romn Tw.ket . ...~ - details COM4i TO U DA kIRL1N4~ R4~S~IWAflON ~
sYsTI~M MAIN MENU ..
Enquuy
Comessian . -. .~• ~•_•~•. .
I — ••;çd~1l - - • .- -~-~ •• ‘~— —~ •~z•~•~_i.~=~•__~. — ~ : • ~“ ~ ~
- - - .•—I ~ p A~~XL~ _L_7 - -—-‘-a- •‘~ .~ • .,~ . ~
‘S
.~.. ‘c•I
In this picture there are three parts. Those are system form, ticket, report,
When you click in system form then it show five forms those are passenger Details, concession, Flight info, Route fare and Enquiry . when you click any one of this then the form is Open. Now open each file one by one.
29 Figure 5.2 This is a form of passenger detail PASSANGE DET uganda airlines
~..
assangerjD Add peter Save asspwt_ o 009988778658 Delete -j~\t. px male Update ~ ‘7 ., .~. Os VHbKDI ~ ..rAN~rAWIA ~‘ . — First 4 4)22/2010 — Jaw. ~ — Last t*ust ‘.,. ~W*~% . ~— ~ •1~~ ~ WC~Afl eon kenyan -~ 4— Lievious .e• ~r~n’”-—~-
gaba ——4 “ ;“I~4’Z*~fcflOTLA’MOflL. ~~ft‘ -‘ Next I-fl tk ç~ ~ 99800876
fleporl ~1.:-;%._...;,. -~ .k~~~., .-.~- [email protected] ~ :.- —4—.
married Forward esignation pdice Close
In this form enter the passenger detail. When you enter the new name then you click add button and then update .Then it is automatically update .This is under system file. In this form first button work for show first record ,next button work for show next record. Preview show the just preview record.
30 Figure 5.3 This is a form of concession form
CONC SION ~ORM
7 uganda aIrftne~
•~Code E~fl.
hiCode — [CHOOSE FLIGHT Save
_Name Relete
_O_T 2years llpdate aoqage_Aflowab?e 24kg Fust 29?~ Last aie Pievioug
Rack frnwa,d Pose Report
THE AIRLINE COMPANY WOULD WiSH TO GIVE SOME DISCOUNT TO ITS BABIRAL CUSTOMER IN ASPECIFIFJ) PER OFTIME
In this form there are several concession type are shown.
When we click any one of them the relevant condition are open. In this form when we click category then it show its conditions Figure 5.4 This is a form of flight information AIRLINE UEi*NDA FORMATION 0
light code f
ight_Name viation
aperture 11:44:00 PM Releic
rnval 1 2: 2~ 00 PM update
ource Entebbe Fi~s1
estination Mumbai
Miles 50000000
are 23765000
sack fmwaid flepoit ~lote THE PASSANOERS MAKES CHOOSE OF THE FLIGHT BY FlLLC’~G N THIS FORM
In this form we are watching the flight information .It has several fields those are seen in the screenshot above. In this form we enter the flight detail .When we enter the new flight then we click add button and then update .Then it is automatically update .This is under master file.
In this form first button work for show first record ,next button work for show next record. Preview show the just preview record. Figure 5.5 This is a form of the route fare.
ROUTE FARE
uganda airlines
mite_Code 1
Add ource Destination Save Entebbe nairobi stna
!~eIete -Il Depariwe liptiate
2~43 OftOO 12:33 First
CODE FARE — Last FIIqht_Code Oasajode Fate
JEXP)1 jbuO2 JEXPJ1 ~bse
Previous Next Back Forward Report INDICATE ROUTE. TI1~fE AND THE RIGHT THAT YOU WOULD LIKE TO I. SE FOR YOUR JOURNfl
This is a form of fare in this fare form there are various fields as seen in the screen shot above
In this form we enter the fare detail .When we enter the new fare then we click add button and then update .Then it is automatically update .This is under master file. In this form first button work for show first record ,next button work for show next record.
Preview show the just preview record Figure 5. 6 This is a form of reservation. TICKET RI~SfR ATION ITORM uganda airlines
Add 012 PNR 1z~I4 FARE Ji000ooo save Flight Code JEXPO1 Flight_Name JEXPRESS Pelete
Class IFIRST _j Seat_No 123 update PASSANGER From Via Destination ame First
1000000 fl DUBAI
24
~r:avelhn ~~Je: ay~ ~t: Next
. .— -. . ~ Gender
MALE -~~- 9/6/2011 9/13)2011 No Ut Passanqe[ rorivard
ëpørg~ -~ .epartUv.ini~ rnva •ime Back
4:30:00PM ~8:O0:00 PM ~9/14/2011 H..-~Y1~ FoR RESERVING WITH US
This is reservation form or ticket .PNR number are generated automatically .When click customers’ age then fare is coming by the route based. When you click total button then total fare is shown. When you click on Print command button then the ticket is print. And when we click in exit button then the form is closed. Figure 5.7 This form is enquiry.
aa.aner_ — ~dd FIiuht_ ~ vi8liatpon -
g2 ccrcm.
aat_ a 23 ~eIe~e a 9/13/2011
Se~aian even~ng
ftack fuzt flapait
~rr~ Emw~d Last £Iae
PLEASE SEND YOUR ENQUIRIES ~ND THE FEEDBACK WILL BE SEND BACK TO YOU
If any person come to airport want to know that its seat reserved or not
Then system open the enquiry form and put the value of ticket no and click
confirm box if it is confirmed then it show value of the all concerning data. Figure 5.8 This form is passenger’s payment PASS 6ERS’ P ITO uganda airlines
1 Md
al Save
FIRST 0 Delele 12343 !ipdate Acceunl_ 0 12000000788634 Fint Pm_No 45637 Last 235000000 Lievious Means_Of_Pay nt Next Dale_Today mobile Cath ATM Payment_Date 8/20/2011
Back [ofward ~Iose MAKE PAYMENT TO BE CONFIDENT OF THE RESERVED SEAT OTHERWISE iT CAN BE PAID BY OtHER AND YOt ~ I~ S1TCC~ rww T1~VTTV~
If the passenger wants to pay for the reserved seat number for the flight, the system prompts the user to enter the ticket no, flight code and the class, then it prompts the user to enter the payment details as seen in the form above for security purpose Figure 5.9 This is a cancellation orm. CK~T C TION FORM % ~an~ a~nes \~ ~1- ~
CanceLiD Add icket_No 110008
Class save FiRST
eat_No Delete
aps_Left ‘V update
asic_Amount Fiist CanceLAmount
Last ~AIAN~E ~0°°
- h. Nest Lievious fiepmt
Fozwajd Oose Back THE CANCELLATION (W THE TICKET IS ONLY VALID tJPTO THE TRAVELLING HOUR .4FITR THAT IS 1NVALII
This is a form of cancellation .When a person come to cancel his/her ticket then, in the form the ticket number are put and system show the value of data and refund amount. Then click on the delete command. Then automatically the record is deleted. REPORTS
Passengers details report are shown below. DataReporti L~1_J zIio0%~j
Passanger_ID: 1 Name: wake Pass portj4o~ 1266676u880 Gender: n~1e 91712011 Nationafily: ugandan Retigxon: mos’em Address: gulu Phone: 3332211098 EmaiI wake2AOLCOM M_Status: Saigle Designatiorn doctor
Pages:144’1 ~ 4
38 This is a report of concession form
~ Datafleport2
L~Ii~i Zoom jiOU?~ ~j
Conces_Code: 2102 Fhght_Code Class_Name: business V_O_T; 2years Bsgqage_A!kwa 24kg Discount 29% Fare: 28880000 Conces_Code: 2133 Flight_Code: IMF Clas s_Name: Fbst V_O_T: I month Ba~age_Atbwa 34kg Discount 89% Fare: 123000 Pages 41 4
Testing debugging and validation In these phases we had tried to check all the modules separately for their proper formatting.
After this step we had performed a unit test to check the fhnctionality of the whole system.
Further we had come to know to add certain validation in project as given bellow
1) Table name- passenger details Field name —D_O_B
Data type -Date/Time.
When we enter date in the form then it show empty .Because we forgot to give it the constraints before packaging. And date in the religion, nationality are wrongly placed in different fields in the form.
39 CHAPTER SIX RECOMMENDATIONS AND CONCLUSION 6.0 Introduction
This chapter states the recommendation to the system under study; design and development which includes control measures, hardware and software control management, input and output management.
6.1 System service management
This will initiate the use of computerized system through; Ensuring proper and accurate recording of all the booking passengers
o Recruiting and training of skilled personnel Adequate documentation and recording to prove and service-trial
o Ensure system control over availability of Seats in Class types of the flight. • The general control will be ensured over the environment in which the based system will be installed, maintained and operated. The purpose of general control is ensuring the integrity of data and program files and of safe operations of the computer system.
6.1.1 Input control and output control The data captured should be as result of the passenger reserving a seat online. The documents that are the end result of these activities should be linked to the entries made to the system. These shall be done through a clear and uniform referencing where each entry will contain a unique ID number at the database. All item categories must be communicated to the end users of the system.
6.2 Security control
6.2.1 Data security control o All user logs must be authorized by the general manager/administrators.
o The user should safe guard the output of the system to protect the image of the organization.
o Any unauthorized activities and unusual reactions by the system should be taken under notice. 6.2.2 Software and Hardware control o The systems administrator will have to assign end users with access password to the system to prevent mismanagement and ID must be carefully controlled. Passwords must be confidential • Staff should be aware of the damage that computer virus can do to the record and computers. The anti-virus software should be updated regularly.
6.3 Recommendation
6.3.1 Backup Copies of current data should be kept in more than one media to reduce the risk of loss or corruption. The information officers and the users should backup data outside the main operation. Test on the backups should be performed to ensure that they are not corrupted.
6.3.2 Error recording and analysis Users should always maintain a log of any problems encountered during interaction with the system. The log will give the detail of the activity one was engaged in, and the exact error message (if any). This log should be given to the head of IT department.
6.4 Conclusion Though the system still contains lot of scope of improvement in it, but its overall look and feel gives rough picture of on existing automation system. We have taken Access at backhand but it has a limitation of less than 10 GB size .It over data size approaches this 10 Gb some other database the SQL server ,oracle, Navision and cyber base can be used with OBBC to break this barrier. REFERENCES:
Wikipedia page for ARS: http://en.wikipedia.org/wiki/Airline_Reservation System
Further reading: Winston, Clifford, ‘The Evolution of the Airline Industry”
“The Origins and Development of Airline Control Program/TPF”, http://www.ambriana.com/IT2O1_webs1te/TPF_history.pdf
Sql server2000, Online and Online Help support.
Wrox Professional asp.net
Anulish asp.net
.www.ni it-tech .com
• OurSQL:: OurSQL 5.1 Reference Manual [Online].
Available from World Wide Web: http://dev.oursgI.com/doc/refrnan/5. 1/en/i ndex.htm I
Pankaj Jalote(2004);An integrated approach to Software Engineering;Narosa Publications. APPENDICES
Appendix: A
Interview questions for internal workers 1. What are your roles in the Airport?
2. On estimate how many Passengers book through your office and what major concerns, queries or applications do they present suggest?
3. How quick are they served, get responses and how long does it take?
4. What category of passengers do you receive in your department? Please state the Class and the nationality.
5. Do you have information systems used to collect, store, Analyze and disseminate this information?
6. What Reservation or booking services do you have and how efficient are they? Appendix: B
Questionnaire used Dear respondent,
We kindly request you to fill this questionnaire below to facilitate the research study to a success and helpful to the Airport services and to obtain the objectives of the Company.
o PLEASE feel free and give the important information as required to make the project feasible.
o Your information will be treated and kept with a lot of confidentiality, great care and will be highly appreciated. Much regards:
1) Your occupation
o Administrator I
o Baggage Staff I
o others ______2) Age bracket 15—20 I 120—25 125—30 I land above
3) Gender
o Male I
o Female1 I 4) Your education level
o Masters I I
o Degree I
o Diploma I_____
o Others
5) What are your views about the online reservation system? (please tick where appropriate)
o excellent I I
o good I
e average I I o poor _____I 6) How efficient is the existing system? (Please tick where appropriate)
o good I
o Fair _____
o Poor I I
o don’t know I I 7) Is the company ready to change the existing system? (please tick where appropriate)
o agree I
o Fair I I
o Disagree I
o not decided I I 8) What is the level of computer literacy in the Administration?
o Good
o Average I
o Poor I 9) What do you believe will be the impact of the proposed system on the cost of operation (administration)? (please tick where appropriate)
o Good I I
o Bad I
o Not decided I
Your support is highly appreciated.
Thanks May GOD Almighty Bless You Appendix C:
Definition of the terms used
o Booking — This term refers to the temporary holding of a seat(s) on a flight for a specific period of time. The user incurs no cost for booking a ticket, but must make a decision at least two weeks prior to the date of departure.
o Reservation — Process of changing a ticket from a booked status to a bought status after paying for it.
o Rescheduling — This process means that the user is allowed only to postpone the travel date and he has to pay the difference in fare. No other details can be changed through this process. For example the number of passengers can’t be changed.
o Base Amount — This refers to the maximum price of a ticket, which usually is the price when the purchase is made at the last minute. This is used in arriving at the discounted price which depends on various factors like early booking, concession etc.
o Flight — This refers to a one-way trip made by an aircraft from a particular source to a particular destination at a particular time on a particular weekday.
o Flight code— This uniquely identifies a flight.
o Administrator — Refers to an authorized official of the airline who has the authority to change and update the databases of the ARS. Appendix D:
Meaning of the abbreviations used ISP- Internet Service Provider
IP — internet protocol
PPC- Pay Per Click
DFD — data Flow Diagrams
GUI - Graphical user Interface
PNR- Personal Number Record
AF - Aviation Flight
STF — Seattle Tracon Flight
FAA - Federal Aviation Administration
CRF — Code of Federal Regulation
CSF — Commercial Space Flight
FC — First Class
BC — Business Class
EC — Economy Class