INTERFACE SOFTWARE BPUT UNIVERSITY BIJUPATNAIK UNIVERSITY OF TECHNOLOGY A Project Report on AIRLINE RESERVATION SYSTEM Carried out at INTERFACE SOFTWARE BHUBANESWAR Submitted By: Khitish Kumar Das Registration No:-0805266064 The project is submitted for The Partial Fulfillment of The Requirement for the degree of MASTER IN COMPUTER APPLICATION (MCA) Trident Academy of Creative Technology AIRLINE RESERVATION SYSTEM 1
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
INTERFACE SOFTWARE BPUT UNIVERSITY
BIJUPATNAIK UNIVERSITY OF TECHNOLOGY
A Project Report on
AIRLINE RESERVATION SYSTEM
Carried out at
INTERFACE SOFTWARE
BHUBANESWAR
Submitted By:
Khitish Kumar DasRegistration No:-0805266064
The project is submitted for The Partial Fulfillment of The Requirement for the degree of
MASTER IN COMPUTER APPLICATION (MCA)
Trident Academy of
Creative Technology
Under the guidance of
PARTHASARATHI DAS
PROJECT GUIDER OF INTERFACE SOFTWARE.
.
AIRLINE RESERVATION SYSTEM 1
INTERFACE SOFTWARE BPUT UNIVERSITY
ACKNOWLEDGEMENT
No project reaches its destination with individual effort, similarly in my case
I have been able to complete my project because of the support I have received
from different avenues.
This project would not have seen the light of day without the guidance of
my external guide
I extend my heartfelt thanks to him for offering his valued guidance in completing
the project and also thankful for his valuable suggestion and efficient supervision in
spite of having arduous schedule. The project would have ended in a prenatal stage
if not for this perseverance and firm belief in my potential. This project is certainly
a success because of his all around help and concern; any word of thanks would be
insufficient for the assistance imparted to me.
I am also immensely thankful to our internal guide Mr. Kartik Rana faculty
of MCA Department of “ TRIDENT ACADEMY OF CREATIVE TECHNOLOGY ”.
I would also like to extend our thanks to Mr.P.K Dixit for his help and also
whole Interface family whose support has made our project a memorable success.
I would like to express my gratitude to Archana Panda and Niranjan Nayak,
for their valuable technical assistance, and Mr. Ashish Das , Mr Raghunath Rana
for their help.
Truly every day has been a learning experience for me due to the presence of all the
people who have helped me to frame a better life.
AIRLINE RESERVATION SYSTEM 2
INTERFACE SOFTWARE BPUT UNIVERSITY
ABSTRACT
The first and foremost objective of the project is to give a better service to the customer at the time of reserving the ticket of airline and eradicate the problems faced by the customer to some extent . The Airline Reservation System (ARS) was one of the earliest changes to improve efficiency. ARS eventually evolved into the Computer Reservation System (CRS)A Computer Reservation System is used for the reservation of a particular airline and interfaces with a Global Distribution System (GDS) which supports travel agencies and other distribution channels in making reservations for the most major airlines in a single system .Airline Reservation System contain airline schedule, fare traffics, passenger reservations and ticket records. An airline’s direct distribution works within their own reservation system, as well as pushing out information to the GDS. A second type of direct distribution channel is consumers who use the internet or mobile application to make their own reservations.
The projects has successfully implemented with proper authentication and services. There are 2 main development modules in the project. They are
1. Admin Module2. User/Customer Module
1. Admin Module: Admin plays the key role throughout the whole project.Admin having own username and password keeps track of the flight details and also about the customerHe can approve and can also reject the booking application of the customer.
2. User/Customer Modules: User also having his/her own username and password for log on. After log on he/she can view all the flights and their details and can book tickets as per the requirement. User can also view and edit his own profile.
AIRLINE RESERVATION SYSTEM 3
INTERFACE SOFTWARE BPUT UNIVERSITY
TABLE OF CONTENTS
Index
1. INTRODUCTION
2. REQUIRED SPECIFICATIONS
2.1 System Study
2.2 System specification
2.3 System Requirement study
2.4 Software specification
a. Java Server Pages
b. Java Script
c. Struts Framework and Servlet.
d. HTML
e. introduction to SQL Server.
3. SYSTEM DESIGN
3.1 Date base Design
3.2 Table Structures.
3.3 Data Flow Diagram.
3.4 ER Diagram.
4. IMPLEMENTATION
5. TESTING
6. CODING
7. CONCLUSION
8. APPENDIX
9. BIBLIOGRAPHY
AIRLINE RESERVATION SYSTEM 4
INTERFACE SOFTWARE BPUT UNIVERSITY
LIST OF TABLES
BOOKING_DETAILS
CUSTOMERDETAILS
FEEDBACK_DETAILS
FLIGHTDETAILS
LOGIN
NOTICE
PAYMENTDETAILS
REGISTRATION
AIRLINE RESERVATION SYSTEM 5
INTERFACE SOFTWARE BPUT UNIVERSITY
LIST OF FIGURES
Data Flow Diagram
Entity Relationship Diagram
AIRLINE RESERVATION SYSTEM 6
INTERFACE SOFTWARE BPUT UNIVERSITY
CHAPTER-1 INTRODUCTION
AIRLINE RESERVATION SYSTEM 7
INTERFACE SOFTWARE BPUT UNIVERSITY
Introduction
Online Air Ticket Booking system is to provide an option to customers to book the tickets online and to check the confirmation online. This system will help the company to sell the flight tickets online. Unless like in the previous stage people as to walk into travel agency or this company ticket counter to buy the tickets and also to check the flight timings. This problem is over come introducing this system.
Existing System
Presently the company has ticket counters in the airport. Where people as to come to book the tickets or to check the flight timings. Also there are many travel agents take the advance booking. In turn these agents will check out with the main ticket counter officials for the ticket confirmation. This is very lengthy and tedious process.
Proposed System The proposed system will available online. So anybody who is interested in the flight timings and ticket booking they check online only.
Objectives of the project 1. Online air ticketing saves time by reducing the time involved in the
physical transportation of the customer to the reservation counter; online air ticketing process saves time in absolute terms.
2. It enables the customer to purchase tickets from the remote areas, thereby
increasing the customer-centricity of the services provided. 3. With a segment of customers opting for the online facilities, the pressure at
the reservation counter is substantially reduced. 4. Reduction in the pressure at the reservation counter creates scope to curtail
the number of employees at the reservation counters, contributing in cost-cut to the company.
5. With faster, easier and hassle-free services to the customer, the company is
poised for a better competitive advantage in face of the oligopolistic structure.
AIRLINE RESERVATION SYSTEM 8
INTERFACE SOFTWARE BPUT UNIVERSITY6. Online portal can be used to ascertain any particular facilities that the
customer might be looking forward to during the journey. 7. The portal can also be used to inform the prospective customers about the
future economy option and other function benefits that the company could have planned; thereby, enabling the customer to plan in advance.
8. With the induction of the cash on delivery system, the customer can easily
deliver his air-tickets while being at home.
AIRLINE RESERVATION SYSTEM 9
INTERFACE SOFTWARE BPUT UNIVERSITY
CHAPTER-2REQUIRED SPECIFICATIONS
2.1. System studyAIRLINE RESERVATION SYSTEM 10
INTERFACE SOFTWARE BPUT UNIVERSITY
System study is a process that is to be done before any project begins.
This will held to understand how the existing system is functioning and what are the
drawbacks in it once the drawbacks have been identified it will be easy to design
the new system avoiding these drawbacks also system study should explain what is
the need for computerization.
2.2 OVERVIEW OF THE SOFTWARE:
2.2.1. Overview of java technology
History of java:
Java language was developed by James Gosling and his team at sun micro
systems and released formally in 1995. Its former name is oak. Java Development
Kit 1.0 was released in 1996. To popularize java and is freely available on Internet.
Overview of java:
Java is loosely based on C++ syntax, and is meant to be Object-Oriented
Structure of java is midway between an interpreted and a compiled language. Java
programs are compiled by the java compiler into Byte Codes which are secure and
portable across different platforms. These byte codes are essentially instructions
encapsulated in single type, to what is known as a java virtual machine (JVM)
which resides in standard browser.
Jvm verifies these byte codes when downloaded by the browser for integrity.
Jvm available for almost all OS. JVM converts these byte codes into machine
specific instructions at runtime.
Features of java:
AIRLINE RESERVATION SYSTEM 11
INTERFACE SOFTWARE BPUT UNIVERSITY Java is object-oriented language and supports encapsulation,
inheritance, polymorphism and dynamic binding, but does not support
multiple inheritance. Every thing in java is an object except some
primitive data types.
Java is portable architecture neutral that is java programs once
compiled can be executed on any machine that is enabled.
JAVA is distributed in its approach and used for internet programming.
Java is robust, secured, high performing and dynamic in nature.
Java supports multithreading. There for different parts of the program
can be executed at the same time
Java and internet:
Java is strongly associated with internet and known as internet programming
language. Internet users can use java to create applet programs and run them locally
using java enabled browser search as hot java. Applets can be downloaded from
remote machine via internet and run it on local machine.
Java and World Wide Web:
World Wide Web is an open ended information retrieval system designed to
be used in the distributed environment. This system contains web pages that provide
both information and controls. We can navigate to a new web page in any direction.
This is made possible worth HTML java was meant to be used in distributed
environment such as internet. So java could be easily incorporated into the web
system and is capable of supporting animation graphics, games and other special
effect. The web has become more dynamic and interactive with support of java. We
can run a java program on remote machine over internet with the support of web.
Column Name Data type SizeBid Number 22Date_of_booking Varchar2 4000Date_of_journey Varchar2 4000Class Varchar2 4000No_of_seat Number 22Cid Number 22Fid Number 22Full Name Varchar2 4000Address Varchar2 4000Mob_no Number 22Dd/Cheque/Scrool no Varchar2 4000Flight_from Varchar2 4000Flight_to Varchar2 4000Flight_name Varchar2 4000Mode_of_payment Varchar2 4000
Table name : NoticePurpose : stores noticesPrimary key : Notice_no
column Name Data type SizeFid number 22Fname Varchar2 4000Flt_from Varchar2 4000Flt_to Varchar2 4000
Deparature_time number 22
Arrival_time number 22
Available number 22
Price number 22
Class Varchar2 4000
Table name : Registration
AIRLINE RESERVATION SYSTEM 43
INTERFACE SOFTWARE BPUT UNIVERSITYPurpose : stores new user detailsPrimary key :Rid
Column Name Data type SizeRid number 22Fname Varchar2 4000Lname Varchar2 4000Gender Varchar2 4000Email Varchar2 4000Address Varchar2 4000Mob_no number 22Slno number 22
3.3 Data Flow Diagram
AIRLINE RESERVATION SYSTEM 44
INTERFACE SOFTWARE BPUT UNIVERSITY
Definition:
A data flow diagram is a graphical technique that depicts information flow and the
transforms that applied as data move from input to output. The Data flow diagram
used to represent a system or software at any level of abstraction. In fact DFDs may
be portioned into levels.
A level of DFD, also called a context model, represents the entire software elements
as a single bubble with input and output by arrow. A level of DFD is portioned into
several bubbles with inter connecting arrows. Each of the process represented at
level one is sub function of the over all depicted in the context model.
The DFD Notations:
Hardware person and other program
Information of the system to be modeled.
Data Item(s): Arrowhead indicates the
direction of flow
Stored Information that is used by the s/w
Level 0:
AIRLINE RESERVATION SYSTEM 45
External Entity
Process
Store
INTERFACE SOFTWARE BPUT UNIVERSITY
DATA FLOW DIAGRAM FOR OVERALL SYSTEM
AIRLINE RESERVATION SYSTEM 46
AIRLINE RESRVATION SYSTEM
LOGIN
ADMIN USER
DATABASE
INTERFACE SOFTWARE BPUT UNIVERSITY
Level-0
INPUT
DATASTORE
AIRLINE RESERVATION SYSTEM 47
(0.0) PROCESS OUTPUT
INTERFACE SOFTWARE BPUT UNIVERSITY
LEVEL - 1
1 ST LEVEL DFD (FOR LOGIN)
User Name
Password Type
LOGIN
1 ST LEVEL DFD (FOR REGISTRATION)
Customer Details
LOGIN REGISTRATION
AIRLINE RESERVATION SYSTEM 48
(1.0)
LOGINLogin Successfully
(1.1)
REGISTRATION
Login Successfully
INTERFACE SOFTWARE BPUT UNIVERSITY
2 nd LEVEL DFD (FOR VALID ADMIN)
Flight Management (2.0.1)
View Customer(2.0.2)VALID ADMIN
View Booking(2.0.3) View Feedback(2.0.4) Give announcement(2.0.5)
FROM TO ARRIVAL TIME DEPARATURE TIME CLASS SEAT AVAILABLE PRICE
FLIGHTDETAILS
2 nd LEVEL DFD (FOR EDIT FLIGHT)
SELECT FLIGHT VIEWED
FLIGHTDETAILS
AIRLINE RESERVATION SYSTEM 50
(2.0.1.0)
ADD FLIGHT SUCESSFULLY ADDED
(2.0.1.1)
SEARCH
UPDATED SUCCESSFULY
UPDATEFLIGHT
INTERFACE SOFTWARE BPUT UNIVERSITY
2 nd LEVEL DFD (FOR VIEW CUSTOMER)
SELECT CUSTOMER VIEWED
CUSTOMERDETAILS
2 nd LEVEL DFD (FOR VIEW BOOKING)
SELECT CUSTOMER VIEWED
BOKING_DETAILS
AIRLINE RESERVATION SYSTEM 51
(2.0.2) VIEW CUSTOMER
VIEWEDSUCESSFULLY
(2.0.3)PROCESSVIEWBOOKING
VIEWED SUCCESSFULLY
INTERFACE SOFTWARE BPUT UNIVERSITY
2 nd LEVEL DFD (FOR VIEW FEEDBACK)
SELECT NAME VIEWED
NOTICE
2 nd LEVEL DFD (FOR ANNOUNCEMENT)
SELECT DATE VIEWED
NOTICE
AIRLINE RESERVATION SYSTEM 52
(2.0.4)PROCESSVIEWBOOKING
FEEDBACKVIEWED SUCCESSFULLY
(2.0.5)PROCESSVIEWBOOKING
ANNOUNCEMENTVIEWED SUCCESSFULLY
INTERFACE SOFTWARE BPUT UNIVERSITY
3 rd LEVEL DFD (FOR VIEW BOOKING)
MY PROFILE (3.0.1)
CHANGE PASSWORD(3.0.2)
VIEW FLIGHT(3.0.3)VALID USER MY BOOKING(3.0.4)
CANCELLATION(3.0.5)
GIVE FEEDBACK(3.0.6)
VIEW ANNOUNCEMENT(3.0.7)
3 rd LEVEL DFD ( FOR MY PROFILE )
MY PROFILE EDIT PROFILE(3.0.1.0)
DELETE PROFILE(301.1)
AIRLINE RESERVATION SYSTEM 53
(3.0)
PROCESS
(3.0.1)
PROCESS
INTERFACE SOFTWARE BPUT UNIVERSITY
3 RD LEVEL DFD (FOR EDIT PROFILE)
SELECT NAME EDITED
CUSTOMERDETAILS
3 RD LEVEL DFD (FOR DELETE PROFILE)
SELECT NAME DELETED
CUSTOMERDETAILS
AIRLINE RESERVATION SYSTEM 54
(3.0.1.0)
PROCESSUPDATEDSUCCESSFULLY
(3.0.1.1)
PROCESSDELETEDSUCCESSFULLY
INTERFACE SOFTWARE BPUT UNIVERSITY
4 TH LEVEL DFD (FOR NOTICE MANAGEMENT)
ADD NOTICE(4.0.1)
ADMIN EDIT NOTICE(4.0.2)
DELETE NOTICE(4.0.3)
4 TH LEVEL DFD (FOR EDIT NOTICE)
SELECT NOTICE MODIFIED
NOTICE
AIRLINE RESERVATION SYSTEM 55
(4.0)
PROCESS
(4.0.2)
PROCESSNOTICEMODIFIEDSUCCESSFULLY
INTERFACE SOFTWARE BPUT UNIVERSITY
3.4 ER-DIAGRAM
AIRLINE RESERVATION SYSTEM 56
LOGIN
SLNO
USERNAME
PASSWORD
TYPE
CUSTOMERDETAILS
CUSTOMERID NAME ADDRESS
EMAIL
GENDER PHONENO
CID
BOOKING_DETAILS
BID
CID
DATE_OF_BOOKIN DATE_OF_JOURNY
CLASS NO_OF_SEATS
FID
FULL_NAME
ADDRESS
MOB_NO DD
FLIGHTFROM
FLIGHTTO
FLIGHTNAME
MODE_OF_PAY
HAS A
HAS A
HAS A
INTERFACE SOFTWARE BPUT UNIVERSITY
AIRLINE RESERVATION SYSTEM 57
PAYMENTDETAILS
PID BID
DATE_OF_PAYMENT
PAYMENTMODE
ACCOUNTNO
FLIGHTDETAILS
FID
FNAME FLT_FROM
FLT_TO
ARRIVALTIME
AVAILLABLEPRICE
CLASS
NOTICE
NOTICENOSUBJECT
CONTENT
DATE_OF_NOTICE
USERNAME
FEEDBACK_DETAILS
FEEDBACK_NO COMMENTS
SUGGESTION
DATE_OF_FEEDBACKNAME
INTERFACE SOFTWARE BPUT UNIVERSITY
4. SYSTEM TESTING AND IMPLEMENTATION
4.1. System testing:Theoretically, a new designed system should have all the pieces in
working order, but in reality, each piece works independently. Now is the time
to put all pieces into one system and test it to determine whether it meets the
user’s requirements. The purpose of the system is to consider all the likely
variations to which it will be subjected and then push the system to its limits. It
is tedious but necessary step in system development. One needs to be familiar
with the following basic terms.
UNIT TESTING: Unit Testing is testing changes made in an existing or a
new program.
SEQUENTIAL OR SERIES TESTING: Sequential or Series Testing is
checking the logic of one or more programs in the candidate system, where
the output of one program will affect the processing done by another
program.
SYSTEM TESTING: System Testing is executing a program to check logic
changes made in it and with the intention of finding errors making the
program fail.
ACCEPTANCE TESTING: Acceptance Testing is running the system with
live data by the actual user of the system.
Testing is vital to the success of the system. System testing makes a
logical assumption that if all the parts of the system are correct, the goal will be
successfully achieved. In adequate testing or no-testing leads to errors that may
not appear until months later. Another reason for system testing is its utility as a
user-oriented vehicle before implementation. The best program and the user
have communication barriers due to different backgrounds. The system
AIRLINE RESERVATION SYSTEM 58
INTERFACE SOFTWARE BPUT UNIVERSITYtester(designer, programmer, or user) who has developed some computer
mastery can bridge this barrier.
4.1.1 Unit Testing:
This focuses on the smallest unit of software design. The module
using the details design description as a guide; important control paths are tested
to uncover errors within the boundary of the module.
Unit test consideration:
The module interface id tested to ensure that information properly
flows into and out of the program unit under test. The local data structures are
examined to ensure that the data stored temporarily maintains it integrity during
all steps in an algorithm execution. Boundary conditions are tested to ensure that
the module operates properly at boundaries established to limit or restrict
processing. The test of data flow across a module interface is required before
any other test. If data do not enter and exit properly, all other tests are moot.
Unit Procedure:
Unit test is normally considered adjunct to the coding style.
After source level code has been developed, reviewed and verified for
correct syntax, unit test case design begins. Each test case should be
coupled with a set of expected results.
Normally, a driver is a “main program” that accepts test case data,
passes such data to the module to be tested and prints the relevant
results. Stubs serve to replace modules that are subroutines called by
the module to be tested. A Stub or ‘dummy stub program’ uses the
subroutine module’s interface to do minimal data manipulation and
returns.
AIRLINE RESERVATION SYSTEM 59
INTERFACE SOFTWARE BPUT UNIVERSITYUnit testing is simplified when a module with high cohesion is designed. When a
module addresses only one function, the number of test cases is reduced and
errors can be more easily predicted and uncovered.
4.1.2 Integration Testing:
Integration is a systematic technique for constructing the program
structure, while at the same time conducting tests to uncover errors associated with
interfacing. The objective is to make unit-tested modules and build a program
structure that has been dictated by design. Incremental integration is the program
that is the program that is constructed and tested in small segments where errors are
easier to isolate and correct.
Top down Integration:
Top-down integration is an incremental approach to the construction of
program structure. Modules are integrated by moving downward through the
control hierarchy, beginning with the main control module. Module subroutine to
the main control module is incorporated into the structure either in a depth-first
manner is engaged for this system. Breadth-first incorporates all modules directly
subroutine at each level, moving across the structure horizontally.
The integration process is performed in a series of five steps:
The main control module is used as a test driver and stubs are
substituted for all modules directly subroutine to the main control
module.
Depending on the integration approach selected (depth or breadth first)
subroutine stub are replaced one at a time with actual modules.
Tests are conducted as each module is integrated.
AIRLINE RESERVATION SYSTEM 60
INTERFACE SOFTWARE BPUT UNIVERSITY On the completion of each set of test, another stub is replaced with the
real module.
Registration testing is conducted to ensure that new errors have not
been introduced.
4.1.3 Validation testing:
At the end of integration testing, the system is completely assembled
as a package with interfacing errors corrected after which a final series of
software tests namely validation testing begins. Validation succeeds when the
software functions in a manner that can be reasonably expected by the user.
Criteria:
Software validation is achieved through black box tests that
demonstrate conformity with requirements.
4.1.4 System Testing:
System testing is actually a series of different tests whose primary
purpose is to fully exercise the computer-based system. Although each test has a
different purpose, all work should verify that all system elements have been
properly integrated and perform allocated functions. Being the most important
test, the performance test is covered briefly below:
Performance Testing:
For real-time systems, software that provides required function but does
not conform to performance requirement is unacceptable. Performance testing is
designed to test the run-time performance of software within the context of an
integrated system. Performance testing occurs throughout all steps in the testing
process. Even at the unit level, the performance of an individual module may be
accessed as tests are conducted. However, it is not until all system elements are
fully integrated that the true performance of a system can be ascertained.
AIRLINE RESERVATION SYSTEM 61
INTERFACE SOFTWARE BPUT UNIVERSITY
4.1.5 Debugging:
Debugging is not testing not occurs as a consequence of testing, that is
when a test case uncovers an error, debugging is the process that results in the
removal of the error.
Normally three categories for debugging approaches are proposed:
Brute force
Back-tracking
Cause-elimination
4.1.5.1 Brute force:
This is the most common and least efficient method for isolating the
cost of a software error. Brute-force debugging method is usually applied when
all else fails. Using a “let the computer finding the error” philosophy, memory-
dumps are taken, runtime traces are invoked and the program is loaded with
WRITE (in this case message box) statements. In the information that is
produced, a clue is found leading to the cause of the error.
4.1.5.2 Back-tracking:
This is fairly common debugging approach that can be used
successfully in small programs. Beginning at the site where a symptom has been
uncovered, the source code is traced backwards (manually) until the site of the
cost is found.
AIRLINE RESERVATION SYSTEM 62
INTERFACE SOFTWARE BPUT UNIVERSITY
Cause-Elimination:
This approach is manifested by induction/deduction and introduces the
concept of ‘binary partition’. A ‘cause hypothesis’ is devised and the error
related data are used to prove or disprove the hypothesis. Alternatively, a list of
all possible causes is developed, and tests are conducted to eliminate each. If
initial tests indicate that a particular cause hypothesis shows promise, that data
are refined in an attempt to isolate the path.
Each of the debugging approaches can be supplemented with
debugging tools. A wide variety of debugging compilers, dynamic debugging
aids (tracers), automatic test case generators, memory dumps and cross-reference
maps can be applied. However, tools are not a substitute for careful evaluation,
based on a complete software design document and clear source code.
4.2. System implementation
After proper testing and validation, the question arises whether the
system can be implemented or not. Implementation includes all those activities that
take place to convert from the old system to the new. The new system may be
totally new; replacing an existing module or automated system, or it may be major
modification to an existing system. In either case proper implementation is essential
to provide a reliable to provide a reliable system to meet organization requirements.
All planning has now, be completed and the transformation to a fully
operational system can commence. The first job will be writing, debugging
documenting of all computer programs and their integration into a total system. The
master and transaction files are decided, and this general processing of the system is
established. Programming is complete when the programs conformed to the detailed
specification.
AIRLINE RESERVATION SYSTEM 63
INTERFACE SOFTWARE BPUT UNIVERSITYWhen the system is ready for implementation, emphasis switches to
communicate with the finance department staff. Open discussion with the staff is
important form the beginning of the project. Staff can be expected to the concerned
about the effect of the automation on their jobs and the fear of redundancy or loss of
status must be allayed immediately. During the implementation phase it is
important that all staff concerned be apprised of the objectives of overall operation
of the system. They will need shinning on how computerization will change their
duties and need to understand how their role relates to the system as a whole. An
organization-training program is advisable; this can include demonstrations,
newsletters, seminars etc.
The department should allocate a member of staff, who understands
the system and the equipment, and should be made responsible for the smooth
operation of the system. An administrator should coordinate the users to the system.
Users should be informed about new aspects of the system that will,
affect them. The features of the system explained with the adequate documentation.
New services such as security, on-line application from the back-ups must be
advertise on the staff when the time is ripe.
Existing documents such as employee loan details should be entered into the new
system. Since these files are very large, conversion of these may continue long after
the system based on current files has been implemented. Hence we need to assign
responsibility for each activity.
The system may come into full operation via number of possible
routes. Complete change over at one point time is conceptually the most tidy.
But this approach requires careful planning and coordination, particularly during
the changeover. A phased approach, possible implementing the system of the
section relating to one operation or procedure first and processing to more novel
or complex subsystems in the fullness of time. These likely to be less traumatic.
AIRLINE RESERVATION SYSTEM 64
INTERFACE SOFTWARE BPUT UNIVERSITY
A phased approach gives the staff time to adjust to the new system. But depends
on being able to split the system, without reliance on it. Thus approach is
sensible when the consequences of failure are disastrous, but will require extra
staff time. The fourth angle, is pilot operation permits any problems to be
tackled on a smaller scale operation. Pilot operation generally means the
implementation of the complete system, but at one location or branch only.
AIRLINE RESERVATION SYSTEM 65
INTERFACE SOFTWARE BPUT UNIVERSITY
Screen shot:
Login.jsp
Description : This page comes first when you run this projects. This page is by defult call index.jsp page.
AIRLINE RESERVATION SYSTEM 66
INTERFACE SOFTWARE BPUT UNIVERSITY
AdminHome.jsp
Description :This page comes after inputing correct username, password and type then clicking the Login button on Login page.
Fields :
Login -: Login id of admin Password -: password of admin
AIRLINE RESERVATION SYSTEM 67
INTERFACE SOFTWARE BPUT UNIVERSITY
Registration.jsp
Description: This page comes after clicking NewUser hyperlink at the Login page. This page is for the registration of new user by filling required fields available and all the data giving by the users through this page will store in database.
AIRLINE RESERVATION SYSTEM 68
INTERFACE SOFTWARE BPUT UNIVERSITY
UserHome.jsp
Description: This page comes after inputting correct username, password and type then clicking the Login button on Login page.
Fields:
Login -: Login id of user. Password -: password of user.
AIRLINE RESERVATION SYSTEM 69
INTERFACE SOFTWARE BPUT UNIVERSITY
ViewFlight.jsp
Description: This page comes after clicking the Attributes of user . It gives all the information of the flight.
AIRLINE RESERVATION SYSTEM 70
INTERFACE SOFTWARE BPUT UNIVERSITY
GiveFeedback.jsp
Description: This page is for storing the feedback given by the customer.
Fields: Name- Customer Name.
Comments-Comments given by the Customer.
Suggestion- Suggestion given by the Customer.
AIRLINE RESERVATION SYSTEM 71
INTERFACE SOFTWARE BPUT UNIVERSITY
ViewCustomer.jsp
Description: This page comes after clicking the Attributes of Admin i.e View Customer. It gives the details of Customers.
Fields:
Customer Name: Name of Customer.
Address: Address of Customer.
Gender: Gender of Customer.
Mob No: Mobile no of Customer.
AIRLINE RESERVATION SYSTEM 72
INTERFACE SOFTWARE BPUT UNIVERSITY
Annoucement.jsp
Description: This page comes after clicking the Attributes of Admin i.e. Give Announcement. It gives the details about the Announcement.
AIRLINE RESERVATION SYSTEM 73
INTERFACE SOFTWARE BPUT UNIVERSITY
ViewBooking.jsp
Description: This page comes after clicking the Attributes of Admin i.e View Booking. It gives details of the booking of ticket.
AIRLINE RESERVATION SYSTEM 74
INTERFACE SOFTWARE BPUT UNIVERSITY
ChangePassword.jsp
Description: This page comes after clicking the attribute of user i.e. Change Password. This page changes the old password of a User.
AIRLINE RESERVATION SYSTEM 75
INTERFACE SOFTWARE BPUT UNIVERSITY
DEVELOPMENT PROCESS
2.1. PROJECT LIFE CYCLE
The Software Development Life Cycle (SDLC) is the process by which
software is created. Some companies don't have anything more than an ad hoc
approach to software development, but these environments still have an SDLC-it's
just a bad one. Likewise, each company that has a formal SDLC probably has its
own, unique flavor of the SDLC. Sometimes the SDLC is a very complicated,
detailed approach that requires a whole team of project managers just to keep going.
The lifecycle of a project may include the following steps:
. By applying this simple set of definite steps and deliverables at the outset and
relating this to a transparent time and cost structure, we provide clients with an
effective framework against which to measure expectation, quality, progress and
cost for their project.
AIRLINE RESERVATION SYSTEM 76
INTERFACE SOFTWARE BPUT UNIVERSITY2.2. DEVELOPMENT PROCESS
Waterfall Model
Planning the development process involves several important considerations.
The first consideration is to define a product life-cycle model.A software LIFE-
CYCLE model encompasses all activities required to define, test, and develop.
AIRLINE RESERVATION SYSTEM 77
Design- v&v
Implementation-v&v
Requirement analysis-
Testing- v&v
Maintenance-v&v
INTERFACE SOFTWARE BPUT UNIVERSITY
FEASEBILITY STUDY
The main aim of feasibility study is to determine whether developing
the product is financially and technically feasible .The feasibility study involves.
An abstract definition of the problem.
Formation of different solution strategies.
Examination of alternative solution strategies and their benefits, indicating
resources required, developed, cost and time respect of each of the
alternative solution. A cost effective analysis is performed to determine
which solution is the best at this stage , it may also determine whether any
of this solution is not feasible due to the high cost , resource constraint or
extraordinary technically reason .
The module is totally feasible in all respect i.e. technically it reduces the time
consuming and in economically it reduces the cost.
The feasibility aspect of the project was considered at the time of the
negotiation with the officials and while discussing the same with the team.
FEASIBILITY ANALYSIS:
The advantage of computer based system is more likely to be
plagued by a scarcity of resources and difficulty delivery dates. A feasibility study
is not warranted for a system in which economic justification is obvious, technical
risk is low, few legal problem are expected and no reasonable alternative risks.
Even if there are different types of feasibility study reports but the following were
given importance for this project:-
AIRLINE RESERVATION SYSTEM 78
INTERFACE SOFTWARE BPUT UNIVERSITY Security Feasibility
Operational Feasibility
Economical Feasibility
Technical Feasibility
SEQURITY FEASIBILITY:
The security of the database from being tampered from an unauthorized
personnel different password fields were provided to different users. The
password are validated and given in the front-end keeping its flexibility and user
friendliness in view. As the concept goes usually the backend is not a frequently
visited area that’s why we kept the access of passwords in jsp. As our project
keeps, evaluates and relatives very important and confidential data about the
diseases and it’s eradication program , it is very important that user should
maintain their own individuality and identity so as one cannot overlap or interfere
or even tamper the restricted fields.
OPERATIONAL FEASIBILITY:
People are inherently resistance to change and computers have been
known to facilitate change. An estimate should be made of how strong a reaction
the user staff is likely to have towards the development of a computerized
system. It is common knowledge that computer installations have something to
do with turnover, transfer retraining and change in job status.
The end users are eager enough to use the s/w. This would reieve them from
physical labor and also financially to maintain various registers and paying a lot
of staffs in the working office and depot.
AIRLINE RESERVATION SYSTEM 79
INTERFACE SOFTWARE BPUT UNIVERSITY The top level officials or the outsides can vital information quickly and
correctly form our interpretation.
ECONOMICALLY FEASIBILITY:
Economically Feasibility is most frequently used for evaluating the
effectiveness of equipment information system. More commonly known as cost
benefit analysis, the procedure is to determine the benefits and saving that are
expected from equipment information system and compare them with costs. If
benefits outweigh costs, then the decision is made to design and implement the
system, otherwise design and implement the system, otherwise further justification
or alternation in the proposed system will have to be made if it is to have a chance
of being approved.
Keeping in view the no. of clients who would be using this software that
is the different places and locations, this project was developed keeping in view the
lowest hardware capacity computer available during that time. As can be seen in
our synopsis that we use p2 7 p3 computers the lowest available with the client
having the following configuration.
486 DX
60 MHz
1 GB HDD
12/16 MB RAM
AIRLINE RESERVATION SYSTEM 80
INTERFACE SOFTWARE BPUT UNIVERSITY
The software was developed in JSP & Oracle8.0 because we opted for a front-end
that will be very user friendly, web friendly and easier for the end user. This also
helped the end user to a very large extent because usually the end user is just a data
entry operator who knows the distinction between letter and number. Keeping this
IQ level of the user into view this type of front-end was used for smooth operation.
TECHNICAL FEASIBILITY:
Technical Feasibility involves financial considerations to accommodate
technical enhancement. If the budget is a serious constraint then the project is
judged ‘not feasible’.
Here the cost incurred by searching an appropriate s/w which may handle
by some few people and hidden to others, but it reduces the searching time, so it
technically fit.
The module reduce the work load of different end user , and gives a clear
picture about the s/w required so the user use this module , hence this system is
operationally feasible .
As this page is technically, economically sequritically and operationally
feasible, so this system is judged feasible.
Hardware Feasibility
For develop this project or implement this project we need different
types of hardware configuration for server and client. If we will use different type
of hardware’s then it may not work properly.
AIRLINE RESERVATION SYSTEM 81
INTERFACE SOFTWARE BPUT UNIVERSITY FOR SERVER
Machine: Pentium IV Server
Memory: 256 MB DDRAM
Hard Drive: 40 GB HDD or Higher
CPU Speed: 2.0Ghz Monitor: S.V.G.A
Keyboard: Standard
Printer: Laser
UPS: 5KVA
For client
Machine: Pentium IV Client
Memory: 128 MB DDRAM
Hard Drive: 10 GB HDD or Higher
CPU Speed: 1.0Ghz
Monitor: S.V.G.A Keyboard: Standard
Printer: Laser UPS: 2KVA
AIRLINE RESERVATION SYSTEM 82
INTERFACE SOFTWARE BPUT UNIVERSITY
Software Feasibility
Using different types of software, which have listed below so these
software’s also need for implement this project, developed this project. If we will
use different types of software then this project will not work.
Operating System: WINDOWS 98, 2000, Xp,2007
Front-end Tool: SERVLET, JSP, STRUTS
Back-end Tool: SQL SERVER
Server: Tomcat 6.0, WBLOGIC
Economical Feasibility
As soon as the specific requirements and solutions have been identified then
the cost of and benefits of each alternative would be evaluated.
AIRLINE RESERVATION SYSTEM 83
INTERFACE SOFTWARE BPUT UNIVERSITYCost Of Estimation Of the Project
The cost of the major hardware, software and accessories required for this
project are 20 lakhs.
Requirement Analysis and Specification
Before starting to design a software product, it is extremely important to understand
the precise requirements of the customer and to document them properly. The
requirements analysis and specifications phase starts once the feasibility study
phase is complete and the project is found to be financially sound and technically
feasible, the goal of the requirements analysis and specifications phase is to clearly
understand the customer requirements and to systematically organize these
requirements in a specification document, this phase consists of the following two
activities:
Requirements gathering analysis
Requirements specification
Requirements gathering analysis
We can elaborate the two main activities involved in the requirements
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
AIRLINE RESERVATION SYSTEM 90
INTERFACE SOFTWARE BPUT UNIVERSITY<!--Design by Free CSS Templateshttp://www.freecsstemplates.orgReleased for free under a Creative Commons Attribution 2.5 License
Name : ProfessionalDescription: A two-column, fixed-width design with dark color scheme background.Version : 1.0Released : 20081230
<p class="links">Welcome aboard RK Airlines, where you are
made to feel like an honoured guest and not just a passenger. At RK, a flight is not a journey between two airports but an experience of a lifetime.RK is built for people with things to do, places to be, people to see - who don't want to waste time, money or energy in the process. By minimizing the cost/time/tension of air travel, RK opens up a country full of opportunities. With RK, you've got a billion reasons to fly</div>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><!--Design by Free CSS Templateshttp://www.freecsstemplates.orgReleased for free under a Creative Commons Attribution 2.5 License
Name : ProfessionalDescription: A two-column, fixed-width design with dark color scheme background.Version : 1.0Released : 20081230
--><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>Professional by FreeCSSTemplates.org</title><link rel="stylesheet" type="text/css" href="style.css" media="screen" /> <script> function validateForm(frm){var uname=frm.uname.value;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><!--Design by Free CSS Templateshttp://www.freecsstemplates.orgReleased for free under a Creative Commons Attribution 2.5 License
Name : ProfessionalDescription: A two-column, fixed-width design with dark color scheme background.Version : 1.0Released : 20081230