You are on page 1of 134

Project Report-Kiosk Management System

Kiosk Management System


Project Report
Submitted in partial fulfillment of the requirements for the degree of

Bachelor of Technology/Engineering (B.Tech/ B.E.)

By

CHARU JAIN
CSE/08/413
June-July 2011

SHRI BALWANT INSTITUTE OF TECHNOLOGY


Approved by AICTE, Min of HRD, Govt of India & DTE, Govt of
Haryana
Affiliated to MD University, Rohtak
Page 1 of 123

Project Report-Kiosk Management System

Meerut Road (Pallri), Near DPS, Sonepat-131001, Haryana

Page 2 of 123

Project Report-Kiosk Management System

Kiosk Management System


Project Report
Submitted in partial fulfillment of the requirements for the degree of

Bachelor of Technology/Engineering (B.Tech/ B.E.)

By

CHARU JAIN
CSE/08/413
June-July 2011

under the Supervision of Mr. Sanjay

SHRI BALWANT INSTITUTE OF TECHNOLOGY


Approved by AICTE, Min of HRD, Govt of India & DTE, Govt of
Haryana
Affiliated to MD University, Rohtak
Meerut Road (Pallri), Near DPS, Sonepat-131001, Haryana
Page 3 of 123

Project Report-Kiosk Management System

CERTIFICATE
This is to certify that the Project titled KIOSK MANAGEMENT SYSTEM and
submitted by CHARU JAIN having Roll No CSE/08/413 for the partial fulfillment of
the requirements for the degree of Bachelor of Technology/Engineering (B.Tech/
B.E.), embodies the bonafide work done by her under my supervision.

__________________________
Signature of the Supervisor
Place: SONEPAT
Date: 29-7-2011

Page 4 of 123

Project Report-Kiosk Management System

Acknowledgement
This report gives the details of the project work done in Summer
training for partial fulfillment of the requirements for the degree of
Bachelor

of

Technology/Engineering

(B.Tech/

B.E.),

under

the

Supervision of Mr. Sanjay.


I am very grateful to my supervisor Mr. Sanjay for him help and able
guidance for the project. I am very thankful to my Institute, for
providing me resources and facilities to help in the project.

____________________
Signature of the Student
Name: CHARU JAIN
Date: 29-7-2011

Page 5 of 123

Project Report-Kiosk Management System

Table of Contents
1 Introduction.....................................................................................................................10
1.1 Purpose....................................................................................................................10
1.2 Scope.......................................................................................................................10
2 Feasibility Report............................................................................................................11
1.1 Purpose....................................................................................................................14
Five common factors (TELOS)....................................................................................14
1.2 Scope.......................................................................................................................15
1.3 System Overview...................................................................................................15
1.4 Project References..................................................................................................16
1.5 Acronyms and Abbreviations.................................................................................16
1.6 Points of Contact.....................................................................................................17
1.6.1 Information......................................................................................................17
1.6.2 Coordination....................................................................................................17
2.1 Environment............................................................................................................17
2.1.1 Organizations Involved....................................................................................17
2.1.2 Input/ Output....................................................................................................18
2.1.3 Processing........................................................................................................18
2.1.4 Security............................................................................................................18
2.1.5 System Interaction...........................................................................................18
2.2 Current Functional Procedures...............................................................................19
2.3 Functional Objectives.............................................................................................19
2.4 Performance Objectives..........................................................................................19
2.5 Assumptions and Constraints..................................................................................19
2.6 Methodology...........................................................................................................20
2.8 Recommendation....................................................................................................20
3.1 Description of Proposed System.............................................................................20
3.2 Improvements.........................................................................................................21
3.3 Time and Resource Costs........................................................................................21
3.4 Impacts....................................................................................................................21
Page 6 of 123

Project Report-Kiosk Management System

3.4.1 Equipment Impacts..........................................................................................22


3.4.2 Software Impacts.............................................................................................22
3.4.3 Organizational Impacts....................................................................................22
3.4.5 Developmental Impacts...................................................................................22
3.4.6 Site or Facility Impacts....................................................................................23
3.4.7 Security and Privacy Impacts...........................................................................23
3.5 Rationale for Recommendations.............................................................................23
3 Requirement Specification..............................................................................................25
1.1 Purpose ...................................................................................................................28
1.2 Document Conventions...........................................................................................28
1.3 Intended Audience and Reading Suggestions.........................................................29
1.4 Project Scope..........................................................................................................29
1.5 References:..............................................................................................................29
2. Overall Description:......................................................................................................29
2.1 Product Perspective.................................................................................................29
2.2 Product Features......................................................................................................30
2.3 Operating Environment...........................................................................................30
2.4 Design and Implementation Constraints.................................................................30
2.5 User Documentation...............................................................................................30
2.6 Assumptions and Dependencies.............................................................................31
The system used to run the application must support the latest version of JavaBeans. 31
Also, the system must have Oracle 10g installed on it.................................................31
Back up of the databases in case of hardware failure, disaster, natural calamities.......31
3. System Features............................................................................................................31
4. External Interface Requirements:.................................................................................31
4.1 User Interfaces........................................................................................................31
Home Page:.......................................................................................................................31
4.2 Hardware Interfaces................................................................................................32
4.3 Software Interfaces.................................................................................................32
4.4 Communications Interfaces....................................................................................32
5. Other Nonfunctional Requirements:.............................................................................32
5.1 Performance Requirements.....................................................................................32
5.2 Safety Requirements...............................................................................................32
Page 7 of 123

Project Report-Kiosk Management System

5.3 Security Requirements............................................................................................33


5.4 Software Quality Attributes....................................................................................33
1 Adaptability: The project is adaptable; it works according to the user instruction. The
user with small change (with the concern of technical expertise) can make it work
according to his/her will. ...................................................................................................33
2 Availability: This project is developed for knowledge in the six weeks training. So its
availability cannot be defined now....................................................................................33
3 Correctness: The correctness of the data stored in the database depends upon the user
as user is responsible for the data present in database. .....................................................33
6. Other Requirements......................................................................................................33
4 Design Specification.......................................................................................................35
1. Revision History............................................................................................................39
2. Approved By.................................................................................................................39
3. Introduction...................................................................................................................40
3.1 Document Outline...................................................................................................40
3.2 Document Description............................................................................................40
3.2.1 Introduction......................................................................................................41
Purpose .........................................................................................................................41
Document Conventions.................................................................................................41
Project Scope................................................................................................................41
3.2.2 System Overview.............................................................................................42
4. Design Considerations..................................................................................................42
4.1 Assumptions and Dependencies.............................................................................42
The system used to run the application must support the latest version of JavaBeans. 42
Also, the system must have Oracle 10g installed on it.................................................42
4.2 General Constraints.................................................................................................42
4.3 Goals and Guidelines..............................................................................................43
4.5 Development Methods............................................................................................43
5. Architectural Strategies.................................................................................................43
6. System Architecture......................................................................................................43
..........................................................................................................................44
7. Policies and Tactics.......................................................................................................45
8. Detailed System Design................................................................................................46
8.1 Classification...........................................................................................................47
Page 8 of 123

Project Report-Kiosk Management System

8.2 Definition................................................................................................................47
8.3 Responsibilities.......................................................................................................47
8.4 Constraints..............................................................................................................48
8.5 Composition............................................................................................................48
ER Diagram..................................................................................................................50
8.6 Database Design......................................................................................................51
8.7 Table schemas........................................................................................................52
8.8 Class Diagrams and Classes....................................................................................55
8.10 Resources..............................................................................................................59
8.11 Processing.............................................................................................................59
8.12 Detailed Subsystem Design..................................................................................59
9. Source Code Details......................................................................................................59
10. Output.......................................................................................................................126
12. Bibliography.............................................................................................................130
5 Conclusion..................................................................................................................132
6 Checklist......................................................................................................................132
119

Page 9 of 123

Project Report-Kiosk Management System

1 Introduction
1.1 Purpose
Kiosk Management System is the online service that can be used in Reservation Centers
which allows users to reserve various facilities. Here we can take Roadways, Railways,
Airlines and Hotel Reservation as our application. The Administrator has options to
control the KMS functionalities and the users.
Users may be of three types: - Administrator, Authorized User and Visitor.
Administrator provides Login ID and Password to the user.
Authorized User will have access to all the services provided by KMS.
Visitors are unauthorized users who can just view the details that are provided by
Administrator.

1.2 Scope
The feasibility report gives us a brief about the project how project is made. Its economic,
commercial, operational all things are include The basic information provided by the
project are:
It will provide the different login option for each user of the project that include the
related information according to his privileges and display the features on just clicking
the option

1.3 Objectives
The system fulfills following objectives: 1. This application has basically three types of users as: Administrator, Visitor and
Authorized User.
2. In this application, user has a common access to book his reservation to Roadways,
Railways, Airlines and Hotel.
3. User should have a valid login id to make reservations.
4. A visitor can search for particular reservation even though he is not registered.
5. No user can have direct interaction with the database.
6. Administrator has to Log-in before to do any transaction.
7. The properties of transaction should be maintained at each and every transaction.
Kiosks are a huge opportunity for online reservation. It is an interactive computerized
unit in a reservation that combines software and hardware to provide internet,
information, transaction facilities and many customer-activated services.

Page 10 of 123

Project Report-Kiosk Management System

2 Feasibility Report
TABLE OF CONTENTS
1 Introduction.....................................................................................................................10
1.1 Purpose....................................................................................................................10
1.2 Scope.......................................................................................................................10
2 Feasibility Report............................................................................................................11
1.1 Purpose....................................................................................................................14
Five common factors (TELOS)....................................................................................15
1.2 Scope.......................................................................................................................15
1.3 System Overview...................................................................................................15
1.4 Project References..................................................................................................16
1.5 Acronyms and Abbreviations.................................................................................16
1.6 Points of Contact.....................................................................................................17
1.6.1 Information......................................................................................................17
1.6.2 Coordination....................................................................................................17
2.1 Environment............................................................................................................17
2.1.1 Organizations Involved....................................................................................17
2.1.2 Input/ Output....................................................................................................18
2.1.3 Processing........................................................................................................18
2.1.4 Security............................................................................................................18
2.1.5 System Interaction...........................................................................................19
2.2 Current Functional Procedures...............................................................................19
2.3 Functional Objectives.............................................................................................19
2.4 Performance Objectives..........................................................................................19
2.5 Assumptions and Constraints..................................................................................20
2.6 Methodology...........................................................................................................20
2.8 Recommendation....................................................................................................20
3.1 Description of Proposed System.............................................................................21
3.2 Improvements.........................................................................................................21
3.3 Time and Resource Costs........................................................................................21
3.4 Impacts....................................................................................................................22
Page 11 of 123

Project Report-Kiosk Management System

3.4.1 Equipment Impacts..........................................................................................22


3.4.2 Software Impacts.............................................................................................22
3.4.3 Organizational Impacts....................................................................................22
3.4.5 Developmental Impacts...................................................................................23
3.4.6 Site or Facility Impacts....................................................................................23
3.4.7 Security and Privacy Impacts...........................................................................23
3.5 Rationale for Recommendations.............................................................................23
3 Requirement Specification..............................................................................................25
1.1 Purpose ...................................................................................................................28
1.2 Document Conventions...........................................................................................28
1.3 Intended Audience and Reading Suggestions.........................................................29
1.4 Project Scope..........................................................................................................29
1.5 References:..............................................................................................................29
2. Overall Description:......................................................................................................29
2.1 Product Perspective.................................................................................................29
2.2 Product Features......................................................................................................30
2.3 Operating Environment...........................................................................................30
2.4 Design and Implementation Constraints.................................................................30
2.5 User Documentation...............................................................................................30
2.6 Assumptions and Dependencies.............................................................................31
The system used to run the application must support the latest version of JavaBeans. 31
Also, the system must have Oracle 10g installed on it.................................................31
Back up of the databases in case of hardware failure, disaster, natural calamities.......31
3. System Features............................................................................................................31
4. External Interface Requirements:.................................................................................31
4.1 User Interfaces........................................................................................................31
Home Page:.......................................................................................................................31
4.2 Hardware Interfaces................................................................................................32
4.3 Software Interfaces.................................................................................................32
4.4 Communications Interfaces....................................................................................32
5. Other Nonfunctional Requirements:.............................................................................32
5.1 Performance Requirements.....................................................................................32
5.2 Safety Requirements...............................................................................................32
Page 12 of 123

Project Report-Kiosk Management System

5.3 Security Requirements............................................................................................33


5.4 Software Quality Attributes....................................................................................33
1 Adaptability: The project is adaptable; it works according to the user instruction. The
user with small change (with the concern of technical expertise) can make it work
according to his/her will. ...................................................................................................33
2 Availability: This project is developed for knowledge in the six weeks training. So its
availability cannot be defined now....................................................................................33
3 Correctness: The correctness of the data stored in the database depends upon the user
as user is responsible for the data present in database. .....................................................33
6. Other Requirements......................................................................................................33
4 Design Specification.......................................................................................................35
1. Revision History............................................................................................................39
2. Approved By.................................................................................................................39
3. Introduction...................................................................................................................40
3.1 Document Outline...................................................................................................40
3.2 Document Description............................................................................................40
3.2.1 Introduction......................................................................................................41
Purpose .........................................................................................................................41
Document Conventions.................................................................................................41
Project Scope................................................................................................................41
3.2.2 System Overview.............................................................................................42
4. Design Considerations..................................................................................................42
4.1 Assumptions and Dependencies.............................................................................42
The system used to run the application must support the latest version of JavaBeans. 42
Also, the system must have Oracle 10g installed on it.................................................42
4.2 General Constraints.................................................................................................42
4.3 Goals and Guidelines..............................................................................................43
4.5 Development Methods............................................................................................43
5. Architectural Strategies.................................................................................................43
6. System Architecture......................................................................................................43
..........................................................................................................................44
7. Policies and Tactics.......................................................................................................45
8. Detailed System Design................................................................................................46
8.1 Classification...........................................................................................................47
Page 13 of 123

Project Report-Kiosk Management System

8.2 Definition................................................................................................................47
8.3 Responsibilities.......................................................................................................47
8.4 Constraints..............................................................................................................48
8.5 Composition............................................................................................................48
ER Diagram..................................................................................................................50
8.6 Database Design......................................................................................................51
8.7 Table schemas........................................................................................................52
8.8 Class Diagrams and Classes....................................................................................55
8.10 Resources..............................................................................................................59
8.11 Processing.............................................................................................................59
8.12 Detailed Subsystem Design..................................................................................59
9. Source Code Details......................................................................................................59
10. Output.......................................................................................................................126
12. Bibliography.............................................................................................................130
5 Conclusion..................................................................................................................132
6 Checklist......................................................................................................................132
17

1.0 GENERAL INFORMATION


1.1 Purpose
Kiosk Management System is the online service that can be used in Reservation Centers
which allows users to reserve various facilities. Here we can take Roadways, Railways,
Airlines and Hotel Reservation as our application. The Administrator has options to
control the KMS functionalities and the users.
Users may be of three types: - Administrator, Authorized User and Visitor.
Administrator provides Login ID and Password to the user.
Authorized User will have access to all the services provided by KMS.
Visitors are unauthorized users who can just view the details that are provided by
Administrator.

Five common factors (TELOS)


1. Technical feasibility:

Page 14 of 123

Project Report-Kiosk Management System

In technical feasibility we consider that whether the following technology is available or


not and whether the required resources are available or not.
2. Economic Feasibility:
In economic feasibility, the most important is cost-benefit analysis. It is an analysis of the
costs to be incurred in the system and benefits derivable out of the system.
3. Operational Feasibility:
Operational feasibility is mainly concerned with issues like whether the system will be
used if it is developed and implemented. Whether there will be resistance from users that
will affect the possible application benefits?
4. Legal feasibility:
Determines whether the proposed system conflicts with legal requirements, e.g. a Data
Processing system must comply with the local Data Protection Acts.
5. Schedule feasibility:
Schedule feasibility is a measure of how reasonable the project timetable is. Given our
technical expertise, are the project deadlines reasonable?

1.2 Scope
The feasibility report gives us a brief about the project how project is made. Its economic,
commercial, operational all things are include The basic information provided by the
project are:
It will provide the different login option for each user of the project that include the
related information according to his privileges and display the features on just clicking
the option.
Kiosks are a huge opportunity for online reservation. It is an interactive computerized
unit in a reservation that combines software and hardware to provide internet,
information, transaction facilities and many customer-activated services.

1.3

System Overview

The system fulfills following objectives: 1. This application has basically three types of users as: Administrator, Visitor and
Authorized User.
2. In this application, user has a common access to book his reservation to Roadways,
Railways, Airlines and Hotel.
3.
4.
5.
6.

User should have a valid login id to make reservations.


User doesnt have to make different accounts to book their Reservations.
A visitor can search for particular reservation even though he is not registered.
Administrator has the right to show availability or non-availability of bus, flight and
hotels. (not for the trains as it relates to Indian Railways)
7. User can check their booked status anytime.
Page 15 of 123

Project Report-Kiosk Management System

8. User can also cancel their reservation, if not interested.


9. Booked reservations will be automatically updated in the database.
10. No user can have direct interaction with the database.
11. Administrator has to Log-in before to do any transaction.
12. The properties of transaction should be maintained at each and every transaction.
13. Administrator can view the all reports like containing reservation status of various
fields.
Responsible organization
The HCL and SBIT is the responsible organization which trained us throughout
the training.
System name or title
Name of our system is Kiosk Management System.
System category Major application: There is always room for improvements,
and the software we created can also be improved. This is especially because we
had to create it within a limited time. With more time, the software can be
improved to include security and different types of users. This would be the first
step in making the software network-enabled, and eventually web-enabled.
Operational status
Under Development
System environment or special conditions
Windows operating System, NetBeans and Oracle 10g software must be installed.
Different privileges for Administrator and the Authorized User are specified. He must
be authenticated by the System Administrator.

1.4 Project References


Book References
Software Engineering By Roger Pressman
Complete Reference HTML, JAVA, JEE
Web References
www.google.co.in
www.wikipedia.org

1.5 Acronyms and Abbreviations


Below is the list of acronyms and abbreviations used in this document and the meaning of
each:
KMS
:
Kiosk Management System
Arr_time
:
Arrival Time
Dept_time
:
Departure Time

Page 16 of 123

Project Report-Kiosk Management System

1.6

Points of Contact

1.6.1 Information
Name
SBIT
Mr. Mahendra
Charu
Chetna
Shikha
Sumit Kumar

Status
Sponsor
Trainer
Developer
Developer
Developer
Developer

Organization
Contact
SBIT
info.sbit@gmail.com
SBIT
mkshrivas@gmail.com
SBIT
cse08413.sbit@gmail.com
SBIT
chetnasaxena91@yahoo.com
SBIT
shikhamalik90@gmail.com
SBIT
sumit_kumar332@yahoo.com

1.6.2 Coordination
Various organizations that are involved for the project are:
HCL: Help us to provide the database for our project and also assist in database
development and its security implementation.
SBIT Management: Provided us the platform for the successful development of the
project
Under the guidance of our trainer Mr. Mahendra we tried to build up the project with
coordination.
The project is divided into several modules and each module is worked upon by each
member of the group. The specific schedule was provided by our project instructor based
on which our project explored.

2.0 MANAGEMENT SUMMARY


2.1

Environment

2.1.1 Organizations Involved


Kiosks are a huge opportunity for online reservation. It is an interactive computerized
unit in a reservation that combines software and hardware to provide internet,
information, transaction facilities and many customer-activated services. As the project
developed is single user and therefore it is used by the hardware administrator/system
administrator of the organization.
Project sponsor: SBIT
Developer:
Charu
Chetna
Page 17 of 123

Developer
Developer

SBIT
SBIT

cse08413.sbit@gmail.com
chetnasaxena91@yahoo.com

Project Report-Kiosk Management System

Shikha
Sumit Kumar

Developer
Developer

SBIT
SBIT

shikhamalik90@gmail.com
sumit_kumar332@yahoo.com

User: Hardware Administrator/System Administrator

2.1.2 Input/ Output


The project has been developed using the Oracle 10g as database. The JSP is used for the
coding. It also consist java beans includes methods and classes, exceptions, threads and
the connectivity is done through JDBC. Input and Output requirements depend upon the
functionality and the privileges provided. For instance. For each user the user id and
password has been provided that acts as input and the functionalities displayed according
to privileges shows the output.

2.1.3 Processing
Operating System: Windows XP Professional, Windows 2000, Windows 7
Browser: PCs: Microsoft Windows Internet Explorer and Mozillas Firefox browser
Software: NetBeans running on Java platform
Database: Oracle 10g
Web Server: Apache Tomcat
Hardware Requirements:Server Side:
Operating System: Windows 9x/XP, Windows Server 2007.
Processor: Pentium 3.0 GHz or higher
RAM: 256 MB or more
Hard Drive: 10 GB or more
Client side:
Operating System: Windows 9x or above
Web Browser(i.e. Internet Explorer, Mozilla Firefox . etc)
Processor: Pentium III or 2.0 GHz or higher.
RAM: 256 MB or more

2.1.4 Security
For ensuring the safety of the project, a login window is provided with the following
fields:
Username
Password
It forces the access of authenticated user only to the application. An additional feature is
also provided which stores the time of users login and logout. Session are used for
security.

2.1.5 System Interaction


The system runs the java software which is user friendly and platform independent.

Page 18 of 123

Project Report-Kiosk Management System

2.1.6 Physical Environment


Here we have made an interface having login page for the client as well as service
provider secondly we made the database having tables .In this we have client that sends
request for the services with his browser. Then the request stores at the remote place from
where the service provider can access the information.

2.2

Current Functional Procedures

The current functional procedure used by the organizations for maintaining their
hardware equipments involves the following elements:
Generally MS Excel is used by the most of the organizations which is not so user
friendly and chaotic in use for the novice user.
Retrieval and updating of the database is also a cumbersome process.
More time is consumed in case of handling the large database and sometimes it
becomes impossible to handle the data of a relatively large organization.
Sometimes it became completely unmanageable which ultimately lead to the
increase in assets of maintaining an unorganized way.

2.3

Functional Objectives

There will be two kinds of accounts in the Kiosk Management System


ADMIN Account
Authorized User Accounts
This will increase the capacity of the system by providing:
Better management of the trainers
Auto-generated notifications of the deliveries not yet provided
The application will be secured from the unauthorized access. Only the ADMIN is
granted with the permissions for adding and removing the users from the accounts.

2.4

Performance Objectives

Project Tasks are directly proportional to the Performance Criteria which have been set
for the project. The Performance Criteria, therefore, determines the amount of work to be
done. So, to increase the performance criteria it is almost always necessary to increase
the Work or to obtain resources with greater capabilities (i.e. they can perform the same
work in a shorter period of time).Therefore, the performance objectives are classified as
follows:
Increase in the performance
Increase in the productivity
Fast and Easy retrieval of the data
Better security measurements
Better accuracy

2.5

Assumptions and Constraints

The operator of the application should have the knowledge of the current system.
ADMIN will have all the permissions.
Page 19 of 123

Project Report-Kiosk Management System

The Clients would also be able to login to perform different requests.


A browser is needed for the application to talk input and to show the output to the users.
The users who are using this application should have internet connection. This will also
need the software oracle 10g and internet browser. The information of the all the user
will be stored in the oracle database.

2.6

Methodology

The survey will be done with visitors. All the perspectives of visitors about the current
system of their working will be taken. All the needs of the customer will be collected and
tried to be fulfilled. The current system of working is implemented with some advanced
features. Also survey is done with the college personals to know about what they want in
this application from their side. The quality of the software is maintained and the featured
provided by it will be helpful.

2.7

Evaluation Criteria
Ease of system use
It is easy to use, since it uses the GUI provided in the user dialog.
User friendly screens are provided.

Development time
To reduce the Resource Days by increasing the Resource Capability will not
necessarily reduce the Total Cost because the reduction in resource days may
be out weighed by the increased Resource Cost.

However, improved Resource Capability will reduce the task time and there is often a
delivery Time Cost associated with a project so that the cost to the organization will be
less or its income improved. This is the so called 'window of opportunity' factor.

2.8

Recommendation

It is strictly recommended to backup your database time to time. There are some risks
which could be tolerated in this application
If some user apply from the registration through sign up form and he will fill up wrong
details. In this case the ADMIN verify the data by the contact person and then forward
it.

3.0 PROPOSED SYSTEM


3.1

Description of Proposed System

Kiosks are a huge opportunity for online reservation. It is an interactive computerized


unit in a reservation that combines software and hardware to provide internet,
Page 20 of 123

Project Report-Kiosk Management System

information, transaction facilities and many customer-activated services. Computer


kiosks can store data locally, or they can retrieve data from a remote server over a
network. Kiosks can be used to provide information, which is great when it comes to egovernance, or for facilitating online transactions, or collecting cash in exchange for
commodities.
Kiosk Management System is the online service that can be used in Reservation Centers
which allows users to reserve various facilities. Here we can take Roadways, Railways,
Airlines and Hotel Reservation as our application. The application is developed using
Java, to make it more powerful we have used Oracle as the back end. In the case of Bus,
Train and Flight ticket reservation the user will have many options like search for seat
availability, search stations, check Reservation Status, reserve or cancel the tickets, view
Fares, etc. In Hotel Booking, accommodations in various Hotels are provided for users.
The Administrator has options to control the KMS functionalities and the users.
Users may be of three types: - Administrator, Authorized User and Visitor.
Administrator provides Login ID and Password to the user.
Authorized User will have access to all the services provided by KMS.
Visitors are unauthorized users who can just view the details that are provided by
Administrator.

3.2

Improvements

This system will improve to existing system and meet the following objectives Decrease the burden on organization
Make the services available to customers
Help the organization to manage their services
Utilize the resources in a time and cost effective way
Make the application distributed
To minimize dependency and reduce redundancy and bugs
Ensure security in terms of authentication and access of information

3.3

Time and Resource Costs

This system is a very flexible. The functionality can be extending according to the need
of clients.It contains several functionalities that can run in parallel during its
development. Early stages of development need some more no of employees to
understand the requirements. After database design burden on the development team will
decrease. After design phase it requires moderate number of developers to work. Under
normal circumstances, the project will take about 4 to 5 months to complete even after
some of the employees may not be available during the middle time. Initial development
cost will be more as it includes the database design and all other design activities as more
employees will be required to implement this. As project will go on its development
members will decrease and automatically the cost will reduce also.

3.4

Impacts

Kiosks are a huge opportunity for online reservation. It is an interactive computerized


unit in a reservation that combines software and hardware to provide internet,
information, transaction facilities and many customer-activated services.

Page 21 of 123

Project Report-Kiosk Management System

3.4.1 Equipment Impacts


The new equipment requires a central database that will contain all the information and
records of an Authorized User as well as list of services provided by it. Another side
which will access to these services will have access to these services from anywhere
through the internet.
The suggested system is different from the current existing systems in terms of the
equipments as the traditional existing system does not have a central database.

3.4.2 Software Impacts


The application should support database and procedures to access it from a distant place.
The platform independency is also one of the needs of the current hour. So a database
like oracle, mysql, sqlserver are required to implement the whole project. In order to
ensure security and stop unauthorized access, application requires secure soft wares like
java technology, java servlets and to make it accessible to all, it requires a language that
browsers can easily understand like html, xml etc.

3.4.3 Organizational Impacts


The proposed system can be developed easily with a little bit effort of the members that
are going to develop it. They need a basic knowledge of database, java technology and
browser language that is html.
So these all are simple concepts and can be performed easily by all members. Therefore
no personnel or skill requirement changes are required to implement this project.

3.4.4 Operational Impacts


Various operational impacts are categorized as:
User operating procedures: - This software provides a very friendly environment to
all types of users using it. They will be able to interact with the system in an easy and
efficient way which was not there in traditional system. The interface provides these all
facilities to users using this software.
Operating center procedures: - This software will the overall operating environment
to be automatic, easy and effective. It will reduce the redundancy and control the insecure
operations.
Data entry procedures:- Data will be entered by users using a graphical interface which
is connected to remote database. In database it is stored in form of tables. To enter data in
the database user just provides data and click on add button in user interface.
System failure contingencies and recovery procedures:- System can be recovered
from damages by keeping a regular backups of data in the database. It will stop
corruption of data also.

3.4.5 Developmental Impacts


Describe the developmental impacts, such as:
Specific activities to be performed by the user in support of development of the
system :- In order to complete this system, all the components will be required to connect
together in a systematic way.
Page 22 of 123

Project Report-Kiosk Management System

Resources required developing databases:-In order to develop the database clean


details of the functionality expected from this software is required. Dependency among
the various fields and services is also required.
Computer processing resources required to develop and test the new system:-It just
requires an organization whose details are maintained in the database and a member
institute who wants to avail the services. A client just needs to access some or all the
services from a remote place using his web browser to test its functionality.
Privacy and security implications:- As security and privacy are the main needs to be
implemented in this web project. It is being ensured by providing a user id and password
to gain access to his private data. Different types of user will access the data with
different restrictions on them.

3.4.6 Site or Facility Impacts


It describes online reservation. It is an interactive computerized unit in a reservation that
combines software and hardware to provide internet, information, transaction facilities
and many customer-activated services.

3.4.7 Security and Privacy Impacts


Imposing the security and privacy restrict the any user other than the administrator itself
to modify or update the database until he is not authenticated by the system administrator
to use the system. This will somehow affects the development process of the system
database at a steady rate.

3.5

Rationale for Recommendations

This system provides best features and functionality as compare to other alternatives.
Some of the alternatives were good from security point of view but do not provide a fast
functionality as expected. Similarly other alternatives lack security and some special
features.
In all the proposed software is the best alternative for the implementation of the current
requirements. It provides best functionality by providing the following
easiness of use by users
maintaining of data in the database
High performance in terms of data retrieval, access and modification.
Ensuring security and maintainability
Interaction with the new and old users.

4.0 Alternative System


The alternative system for this software may include the following

Page 23 of 123

Project Report-Kiosk Management System

Traditional excel based system :- This type of information can also be managed by
using some traditional computer systems like excel based system where user maintains all
the information in his/her computer in excel sheets instead of database. All the records
are maintained by employees itself and modified when required. But it will not be
accessible from a remote place and also information may corrupt easily and can become
redundant. Therefore this alternative is not suitable for the implementation of this project.
An alternative system can also de developed using any simple programming language
like c++, vb etc. But this type of system will not maintain security and platform
independency and performance. SO this type of system can not fulfill all the requirements
of a safe web based application. It is provided by our system using java technology and
java servlets which ensures security and maintains platform independency.

Page 24 of 123

Project Report-Kiosk Management System

3 Requirement Specification

Table of Contents
1 Introduction.....................................................................................................................10
1.1 Purpose....................................................................................................................10
1.2 Scope.......................................................................................................................10
2 Feasibility Report............................................................................................................11
1.1 Purpose....................................................................................................................14
Five common factors (TELOS)....................................................................................14
1.2 Scope.......................................................................................................................15
1.3 System Overview...................................................................................................15
1.4 Project References..................................................................................................16
1.5 Acronyms and Abbreviations.................................................................................16
1.6 Points of Contact.....................................................................................................17
1.6.1 Information......................................................................................................17
1.6.2 Coordination....................................................................................................17
2.1 Environment............................................................................................................17
2.1.1 Organizations Involved....................................................................................17
2.1.2 Input/ Output....................................................................................................18
2.1.3 Processing........................................................................................................18
2.1.4 Security............................................................................................................18
2.1.5 System Interaction...........................................................................................18
2.2 Current Functional Procedures...............................................................................19
2.3 Functional Objectives.............................................................................................19
2.4 Performance Objectives..........................................................................................19
2.5 Assumptions and Constraints..................................................................................19
2.6 Methodology...........................................................................................................20
2.8 Recommendation....................................................................................................20
3.1 Description of Proposed System.............................................................................20
3.2 Improvements.........................................................................................................21
3.3 Time and Resource Costs........................................................................................21
3.4 Impacts....................................................................................................................21

Page 25 of 123

Project Report-Kiosk Management System

3.4.1 Equipment Impacts..........................................................................................22


3.4.2 Software Impacts.............................................................................................22
3.4.3 Organizational Impacts....................................................................................22
3.4.5 Developmental Impacts...................................................................................22
3.4.6 Site or Facility Impacts....................................................................................23
3.4.7 Security and Privacy Impacts...........................................................................23
3.5 Rationale for Recommendations.............................................................................23
3 Requirement Specification..............................................................................................25
1.1 Purpose ...................................................................................................................28
1.2 Document Conventions...........................................................................................28
1.3 Intended Audience and Reading Suggestions.........................................................29
1.4 Project Scope..........................................................................................................29
1.5 References:..............................................................................................................29
2. Overall Description:......................................................................................................29
2.1 Product Perspective.................................................................................................29
2.2 Product Features......................................................................................................30
2.3 Operating Environment...........................................................................................30
2.4 Design and Implementation Constraints.................................................................30
2.5 User Documentation...............................................................................................30
2.6 Assumptions and Dependencies.............................................................................31
The system used to run the application must support the latest version of JavaBeans.31
Also, the system must have Oracle 10g installed on it.................................................31
Back up of the databases in case of hardware failure, disaster, natural calamities.......31
3. System Features............................................................................................................31
4. External Interface Requirements:.................................................................................31
4.1 User Interfaces........................................................................................................31
Home Page:.......................................................................................................................31
4.2 Hardware Interfaces................................................................................................32
4.3 Software Interfaces.................................................................................................32
4.4 Communications Interfaces....................................................................................32
5. Other Nonfunctional Requirements:.............................................................................32
5.1 Performance Requirements.....................................................................................32

Page 26 of 123

Project Report-Kiosk Management System

5.2 Safety Requirements...............................................................................................32


5.3 Security Requirements............................................................................................33
5.4 Software Quality Attributes....................................................................................33
1 Adaptability: The project is adaptable; it works according to the user instruction. The
user with small change (with the concern of technical expertise) can make it work
according to his/her will. ...................................................................................................33
2 Availability: This project is developed for knowledge in the six weeks training. So its
availability cannot be defined now....................................................................................33
3 Correctness: The correctness of the data stored in the database depends upon the user
as user is responsible for the data present in database. .....................................................33
6. Other Requirements......................................................................................................33
4 Design Specification.......................................................................................................35
1. Revision History............................................................................................................39
2. Approved By.................................................................................................................39
3. Introduction...................................................................................................................40
3.1 Document Outline...................................................................................................40
3.2 Document Description............................................................................................40
3.2.1 Introduction......................................................................................................41
Purpose .........................................................................................................................41
Document Conventions.................................................................................................41
Project Scope................................................................................................................41
3.2.2 System Overview.............................................................................................42
4. Design Considerations..................................................................................................42
4.1 Assumptions and Dependencies.............................................................................42
The system used to run the application must support the latest version of JavaBeans.42
Also, the system must have Oracle 10g installed on it.................................................42
4.2 General Constraints.................................................................................................42
4.3 Goals and Guidelines..............................................................................................43
4.5 Development Methods............................................................................................43
5. Architectural Strategies.................................................................................................43
6. System Architecture......................................................................................................43
..........................................................................................................................44
7. Policies and Tactics.......................................................................................................45
8. Detailed System Design................................................................................................46
Page 27 of 123

Project Report-Kiosk Management System

8.1 Classification...........................................................................................................47
8.2 Definition................................................................................................................47
8.3 Responsibilities.......................................................................................................47
8.4 Constraints..............................................................................................................48
8.5 Composition............................................................................................................48
ER Diagram..................................................................................................................50
8.6 Database Design......................................................................................................51
8.7 Table schemas........................................................................................................52
8.8 Class Diagrams and Classes....................................................................................55
8.10 Resources..............................................................................................................59
8.11 Processing.............................................................................................................59
8.12 Detailed Subsystem Design..................................................................................59
9. Source Code Details......................................................................................................59
10. Output.......................................................................................................................126
12. Bibliography.............................................................................................................130
5 Conclusion..................................................................................................................132
6 Checklist......................................................................................................................132

1. Introduction
1.1 Purpose
The purpose of our project is to provide the online service that can be used in Reservation
Centers which allows users to reserve various facilities. Here we can take Roadways,
Railways, Airlines and Hotel Reservation as our application online reservation.

1.2 Document Conventions


The format of this SRS is simple. Bold face and indentation is used on general topics and
or specific points of interest. The remainder of the document will be written using the
standard font, New Times Roman.
Only following points are taken into consideration:
Headings are written in Times New Roman with 14 font size in BOLD.
And the details are written in Times with 11 font size.

Page 28 of 123

Project Report-Kiosk Management System

1.3 Intended Audience and Reading Suggestions


This document is intended to be read by the developer team, project managers HCL
group members, user SBIT. This is a technical document and the terms should be
understood by the customer.
The Remaining part of the SRS contains the following description:

Overall description of the project


System feature
Internal interface requirement
Other non functional requirement.

1.4 Project Scope


Kiosks are a huge opportunity for online reservation. It is an interactive computerized
unit in a reservation that combines software and hardware to provide internet,
information, transaction facilities and many customer-activated services. Computer
kiosks can store data locally, or they can retrieve data from a remote server over a
network. Kiosks can be used to provide information, which is great when it comes to egovernance, or for facilitating online transactions, or collecting cash in exchange for
commodities.

1.5 References:

Book References

Software Engineering By Roger Pressman

Complete Reference HTML

Complete Reference JAVA

Web References

www.google.co.in

www.wikipedia.org

2. Overall Description:
2.1 Product Perspective
As the name implies, kiosk management main function is to act as an agent, that is to
say,it provides Ticket Booking facility, Book hotel rooms for the user of this website.
But there is a restriction for the user of this site is that the user use all the facility of this
site when you have a registered user of this site.

Page 29 of 123

Project Report-Kiosk Management System

2.2 Product Features


1. This application has basically three types of users as: Administrator, Visitor and
Authorized User.
2. In this application, user has a common access to book his reservation to Roadways,
Railways, Airlines and Hotel.
3. User should have a valid login id to make reservations.
4. User doesnt have to make different accounts to book their Reservations.
5. A visitor can search for particular reservation even though he is not registered.
6. Administrator has the right to show availability or non-availability of bus, flight and
hotels. (not for the trains as it relates to Indian Railways)
7. User can check their booked status anytime.
8. User can also cancel their reservation, if not interested.
9. Booked reservations will be automatically updated in the database.
10. No user can have direct interaction with the database.
11. Administrator has to Log-in before to do any transaction.
12. The properties of transaction should be maintained at each and every transaction.
13.Administrator can view the all reports like containing reservation status of various
fields.

2.3 Operating Environment


For an efficient system processing, we need the following softwares:
Operating System : Windows XP Professional, Windows 2000, Windows 7
Browser : PCs: Microsoft Windows Internet Explorer , Mozillas Firefox,etc.
Software: NetBeans running on Java platform
Database : Oracle 10g

2.4 Design and Implementation Constraints


Security: The files in which the information regarding account should be secured
against malicious deformations.
Fault Tolerance: Data should not become corrupted in case of system crash or power
failure.

2.5 User Documentation


Not applicable

Page 30 of 123

Project Report-Kiosk Management System

2.6 Assumptions and Dependencies

The system used to run the application must support the latest version of
JavaBeans.

Also, the system must have Oracle 10g installed on it.

Back up of the databases in case of hardware failure, disaster, natural calamities.

No data loss in case of handling of the system by the administrators or the system
related personnel.

3. System Features
ENJOY LIFE is a website through which people can book tickets, Book Hotel rooms/
buses/trains/flights according to their comfort and needs without going to its source
booking office.

3.1 Validate Registration


This feature provides registration facility for customers. If the customer registered by this
feature than they utilize the functionality of this website. If they not registered then they
have not an authority to use the feature of this.

3.2 Login Info


This feature maintains the role .There are three type of role: Admin, Authorized User,
Visitor.

3.3 Booking Hotel/Bus/Train/Flight


This feature provides booking facility for hotels, trains, flights and trains.

4. External Interface Requirements:


4.1 User Interfaces

Home Page:

In home page of Enjoy life a menu is available. In this menu 8 different tabs are
available.

They are :
o Home
o Trains
o Buses
o Flights

Page 31 of 123

Project Report-Kiosk Management System

o Hotel
o About Us
o Register
o Contact Us

4.2 Hardware Interfaces


The hardware interfaces involved may include:

The use of keyboard or keypad functions


The output screen (monitor)

4.3 Software Interfaces


Operating System : Windows XP Professional, Windows 2000, Windows 7
Browser : any web browser i.e.: Internet Explorer ,Mozillas Firefox ,etc.
Software : NetBeans running on Java platform
Database : Oracle 10g

4.4 Communications Interfaces


To use the social networking system efficiently user need to have an internet connection
with a personal computer running with any well established Operating System like
Windows. User needs to have installed Internet browser and email client on his machine
for the same.

5. Other Nonfunctional Requirements:


5.1 Performance Requirements
The performance of the project depends upon the team work, coordination and time
scheduling among them. The performance can be improved by assigning the work to the
skilled staff. The design of the project is based on the skill of the developer. Each
member needs to be skilled in its assigned work. Each member is assigned with the
particular module. And the assigned work is to be completed within the deadline allotted
for it.

5.2 Safety Requirements


The product is designed in NetBeans, so one must install NetBeans before running the
product. The users have to be very much careful while installing the NetBeans. And one
of the safety requirements is to protect the system from various viruses.

Page 32 of 123

Project Report-Kiosk Management System

5.3 Security Requirements

For ensuring the safety of the project, a login window is provided with the
following fields:
Username
Password

The authentication or the non- authentication needs to be confirmed.


The database password i.e. the root password is again required to make the
database secured from any damage or loss of data.
Sessions are created for security purpose.

5.4 Software Quality Attributes


1 Adaptability: The project is adaptable; it works according to the user instruction.
The user with small change (with the concern of technical expertise) can make it
work according to his/her will.
2 Availability: This project is developed for knowledge in the six weeks training. So
its availability cannot be defined now.
3 Correctness: The correctness of the data stored in the database depends upon the
user as user is responsible for the data present in database.
4 Maintainability: The maintainability of the project is easy.
5 Portability: This project can be run on NetBeans at any system where NetBeans and
Oracle 10g is installed.

6. Other Requirements
Scalability: System should be able to handle a number of users.
For e.g. Handling around thousand users at the same time.
Usability: Simple user interfaces that a layman can understand.
Speed: Speed of the system should be responsive i.e. response to a particular action
should be available in short period of time. For e.g. on registering as a new user the
notification about the approval is sent immediately to the respective user through email.
Updating the account takes few seconds for the changes if the entry is not starred.

Appendix A: Glossary
Administrator- That provides Login ID and Password to the user.
Authorized User- will have access to all the services provided by KMS.
Visitors- are unauthorized users who can just view the details that are provided by
Administrator.
Database- In which data is stored
DFD- Data Flow Diagram
Interface- through which client send request
Server- that serves request

Page 33 of 123

Project Report-Kiosk Management System

Page 34 of 123

Project Report-Kiosk Management System

4 Design Specification
Table of Contents
1 Introduction.....................................................................................................................10
1.1 Purpose....................................................................................................................10
1.2 Scope.......................................................................................................................10
2 Feasibility Report............................................................................................................11
1.1 Purpose....................................................................................................................14
Five common factors (TELOS)....................................................................................14
1.2 Scope.......................................................................................................................15
1.3 System Overview...................................................................................................15
1.4 Project References..................................................................................................16
1.5 Acronyms and Abbreviations.................................................................................16
1.6 Points of Contact.....................................................................................................17
1.6.1 Information......................................................................................................17
1.6.2 Coordination....................................................................................................17
2.1 Environment............................................................................................................17
2.1.1 Organizations Involved....................................................................................17
2.1.2 Input/ Output....................................................................................................18
2.1.3 Processing........................................................................................................18
2.1.4 Security............................................................................................................18
2.1.5 System Interaction...........................................................................................18
2.2 Current Functional Procedures...............................................................................19
2.3 Functional Objectives.............................................................................................19
2.4 Performance Objectives..........................................................................................19
2.5 Assumptions and Constraints..................................................................................19
2.6 Methodology...........................................................................................................20
2.8 Recommendation....................................................................................................20
3.1 Description of Proposed System.............................................................................20
3.2 Improvements.........................................................................................................21
3.3 Time and Resource Costs........................................................................................21
3.4 Impacts....................................................................................................................21
3.4.1 Equipment Impacts..........................................................................................22
Page 35 of 123

Project Report-Kiosk Management System

3.4.2 Software Impacts.............................................................................................22


3.4.3 Organizational Impacts....................................................................................22
3.4.5 Developmental Impacts...................................................................................22
3.4.6 Site or Facility Impacts....................................................................................23
3.4.7 Security and Privacy Impacts...........................................................................23
3.5 Rationale for Recommendations.............................................................................23
3 Requirement Specification..............................................................................................25
1.1 Purpose ...................................................................................................................28
1.2 Document Conventions...........................................................................................28
1.3 Intended Audience and Reading Suggestions.........................................................29
1.4 Project Scope..........................................................................................................29
1.5 References:..............................................................................................................29
2. Overall Description:......................................................................................................29
2.1 Product Perspective.................................................................................................29
2.2 Product Features......................................................................................................30
2.3 Operating Environment...........................................................................................30
2.4 Design and Implementation Constraints.................................................................30
2.5 User Documentation...............................................................................................30
2.6 Assumptions and Dependencies.............................................................................31
The system used to run the application must support the latest version of JavaBeans. 31
Also, the system must have Oracle 10g installed on it.................................................31
Back up of the databases in case of hardware failure, disaster, natural calamities.......31
3. System Features............................................................................................................31
4. External Interface Requirements:.................................................................................31
4.1 User Interfaces........................................................................................................31
Home Page:.......................................................................................................................31
4.2 Hardware Interfaces................................................................................................32
4.3 Software Interfaces.................................................................................................32
4.4 Communications Interfaces....................................................................................32
5. Other Nonfunctional Requirements:.............................................................................32
5.1 Performance Requirements.....................................................................................32
5.2 Safety Requirements...............................................................................................32

Page 36 of 123

Project Report-Kiosk Management System

5.3 Security Requirements............................................................................................33


5.4 Software Quality Attributes....................................................................................33
1 Adaptability: The project is adaptable; it works according to the user instruction. The
user with small change (with the concern of technical expertise) can make it work
according to his/her will. ...................................................................................................33
2 Availability: This project is developed for knowledge in the six weeks training. So its
availability cannot be defined now....................................................................................33
3 Correctness: The correctness of the data stored in the database depends upon the user
as user is responsible for the data present in database. .....................................................33
6. Other Requirements......................................................................................................33
4 Design Specification.......................................................................................................35
1. Revision History............................................................................................................39
2. Approved By.................................................................................................................39
3. Introduction...................................................................................................................40
3.1 Document Outline...................................................................................................40
3.2 Document Description............................................................................................40
3.2.1 Introduction......................................................................................................41
Purpose .........................................................................................................................41
Document Conventions.................................................................................................41
Project Scope................................................................................................................41
3.2.2 System Overview.............................................................................................42
4. Design Considerations..................................................................................................42
4.1 Assumptions and Dependencies.............................................................................42
The system used to run the application must support the latest version of JavaBeans. 42
Also, the system must have Oracle 10g installed on it.................................................42
4.2 General Constraints.................................................................................................42
4.3 Goals and Guidelines..............................................................................................43
4.5 Development Methods............................................................................................43
5. Architectural Strategies.................................................................................................43
6. System Architecture......................................................................................................43
..........................................................................................................................44
7. Policies and Tactics.......................................................................................................45
8. Detailed System Design................................................................................................46
8.1 Classification...........................................................................................................47
Page 37 of 123

Project Report-Kiosk Management System

8.2 Definition................................................................................................................47
8.3 Responsibilities.......................................................................................................47
8.4 Constraints..............................................................................................................48
8.5 Composition............................................................................................................48
ER Diagram..................................................................................................................50
8.6 Database Design......................................................................................................51
8.7 Table schemas........................................................................................................52
8.8 Class Diagrams and Classes....................................................................................55
8.10 Resources..............................................................................................................59
8.11 Processing.............................................................................................................59
8.12 Detailed Subsystem Design..................................................................................59
9. Source Code Details......................................................................................................59
10. Output.......................................................................................................................126
12. Bibliography.............................................................................................................130
5 Conclusion..................................................................................................................132
6 Checklist......................................................................................................................132

Page 38 of 123

Project Report-Kiosk Management System

1. Revision History
Version

Name

Reason For Changes

Date

1.0

Kiosk
management
system

Initial Revision

29-7-2011

2. Approved By
Approvals should be obtained from faculty/ HOD

Name

Department

Date

Mr.Abhishek
Shukla

CSE

29-7-2011

Mr. Sanjay

CSE

29-7-2011

Page 39 of 123

Signature

Project Report-Kiosk Management System

3. Introduction
A software development process, also known as a software development life cycle
(SDLC), is a structure imposed on the development of a software product. Similar
terms include software life cycle and software process. It is often considered a subset
of systems development life cycle. There are several models for such processes, each
describing approaches to a variety of tasks or activities that take place during the
process.
The following sections and subsections are designed to give a detailed knowledge of
the kiosk management system which we have designed during the training section as
a small project. Different phases we covered in this project are :
Creation of Various Pages regarding Services provided by Administrator as
Railways, Roadways, Airlines and Hotel Reservation
Creation of Users (Administrator, Visitor, Authorized User)
Creation of Databases Relevant to the Application
Design of Dynamic Search Engine of the application to search for the relevant
services on the basis of inputs provided by User.

3.1 Document Outline


Here is the outline of the software design specification for our project. The following is
just an outline order that we have used to present the architecture and design of the entire
system in this document:
Introduction to the Project : Kiosks Management System
System Overview
Design Considerations
o Assumptions and Dependencies
o

General Constraints

Goals and Guidelines

Development Methods

Architectural Strategies
System Architecture
Policies and Tactics
Detailed System Design
Glossary
Bibliography

3.2 Document Description


Here is the description of the contents (by section and subsection) of the proposed
template for software design specifications:
Page 40 of 123

Project Report-Kiosk Management System

3.2.1 Introduction
Purpose
This section should provide a high-level overview of how the functionality and
responsibilities of the system were partitioned and then assigned to subsystems or
components. The main purpose here is to gain a general understanding of how and why
the system was decomposed, and how the individual parts work together to provide the
desired functionality.
The purpose of our project is to provide the online service that can be used in Reservation
Centers which allows users to reserve various facilities. Here we can take Roadways,
Railways, Airlines and Hotel Reservation as our application online reservation.

Document Conventions
The format of this SRS is simple. Bold face and indentation is used on general topics and
or specific points of interest. The remainder of the document will be written using the
standard font, New Times Roman.
Only following points are taken into consideration:
Headings are written in Times New Roman with 14 font size in BOLD.
And the details are written in Times New Roman with 11 font size.
This document is intended to be read by the developer team, project managers HCL
group members, user SBIT. This is a technical document and the terms should be
understood by the customer.
The Remaining part of the SRS contains the following description:
Overall description of the project
System feature
Internal interface requirement
Other non functional requirement.

Project Scope
The software development team designs, implements, tests, and delivers these
Requirements to you. A Requirement is an atomic unit of a software product from the
viewpoint of the user. As a rule, Requirements are always correct, unambiguous,
verifiable, and traceable.
Kiosks are a huge opportunity for online reservation. It is an interactive computerized
unit in a reservation that combines software and hardware to provide internet,
information, transaction facilities and many customer-activated services. Computer
kiosks can store data locally, or they can retrieve data from a remote server over a
network. Kiosks can be used to provide information, which is great when it comes to egovernance, or for facilitating online transactions, or collecting cash in exchange for
commodities.

Page 41 of 123

Project Report-Kiosk Management System

3.2.2 System Overview


The system fulfills following objectives: -

This application has basically three types of users as: Administrator, Visitor and
Authorized User.
In this application, user has a common access to book his reservation to
Roadways, Railways, Airlines and Hotel.
User should have a valid login id to make reservations.
User doesnt have to make different accounts to book their Reservations.
A visitor can search for particular reservation even though he is not registered.
Administrator has the right to show availability or non-availability of bus, flight
and hotels. (not for the trains as it relates to Indian Railways)
User can check their booked status anytime.
User can also cancel their reservation, if not interested.
Booked reservations will be automatically updated in the database.
No user can have direct interaction with the database.
Administrator has to Log-in before to do any transaction.
The properties of transaction should be maintained at each and every transaction.
Administrator can view the all reports like containing reservation status of various
fields.
Application should provide the multiple Transaction services.

4. Design Considerations
This section describes many of the issues which need to be addressed or resolved before
attempting to devise a complete design solution.

4.1 Assumptions and Dependencies

The system used to run the application must support the latest version of
JavaBeans.
Also, the system must have Oracle 10g installed on it.
Back up of the databases in case of hardware failure, disaster, natural calamities.
No data loss in case of handling of the system by the administrators or the system
related personnel.

4.2 General Constraints


There are no such global limitations or constraints of this project. This project is just a
starting towards the development of concurrent server but further different ideas can be
implemented on this.
The P.C should have a servlet-2.5 version,JSP-2.0 version,Http-1.1version.
The system should capable of arranging storage space .
The user must have correct knowledge of both hardware and software.
The correct compilation of project is required.

Page 42 of 123

Project Report-Kiosk Management System

4.3 Goals and Guidelines

To have a knowledge of advance java and oracle.


The coding of project is quite easy to understand.
No wastage of storage space.
The goal of our project is to provide the online service that can be used in Reservation
Centers which allows users to reserve various facilities. Here we have take Roadways,
Railways, Airlines and Hotel Reservation as our application online reservation.

4.5 Development Methods


For interface design JSP will be used.
Use various types of controls like text fields, Label, Check box, List etc.
Servlet will be used to process the request received from the user.
The interaction to database will be done through Java bean only.
Database connectivity, Exception Handling, commit/ rollback using JDBC in
order to maintain ACID properties of Transaction.
There is use of different functions such as add , get to fulfill the user needs.
There is no time limit of using this project.
The user can access this project up to his/her satisfactory.

5. Architectural Strategies
JSP: For interface design JSP will be used. Use various types of controls like text fields,
Label, Check box, List etc. User is going to interact with the jsp pages.
Servlet: It will be used to process the request received from the user. It will be act as
mediator between JSP and JAVA Bean.
Java Bean: The interaction to database will be done through Java bean only. Therefore
to save/retrieve data from the database Java Bean will be used.
JDBC: Database connectivity, Exception Handling, commit/ rollback using JDBC in
order to maintain ACID properties of Transaction.
Oracle: ORACLE is a fourth generation relational database management system. A DBMS must
be secure from unauthorized access and provide efficient solutions for failure recovery. The
ORACLE Server provides efficient and effective solutions for the major database features.

6. System Architecture
JSP:- Java Server Pages (JSP) is a server-side programming technology that enables the
creation of dynamic web pages and applications. This is accomplished by embedding
Java code into HTML, XML, DHTML, or other document types. When a client such as a
web browser makes a request to the Java application container, which is typically a web
server, the static page is converted behind the scenes, and displayed as dynamic content
to the viewer. It has been speculated that JSP was released to compete with PHP, a
commonly used open-source programming language.

Page 43 of 123

Project Report-Kiosk Management System

SERVLET:- A Servlet is a Java class which conforms to the Java Servlet API, a
protocol by which a Java class may respond to HTTP requests. A Servlet is an object that
receives a request and generates a response based on that request. The basic Servlet
package defines Java objects to represent Servlet requests and responses, as well as
objects to reflect the servlet's configuration parameters and execution environment.

MVC ARCHITECTURE
JAVA BEANS: - JavaBeans are reusable software components for Java that can be
manipulated visually in a builder tool. Practically, they are classes written in the Java
programming language conforming to a particular convention. They are used to
encapsulate many objects into a single object (the bean), so that they can be passed
around as a single bean object instead of as multiple individual objects. A JavaBeans is a
Java Object that is serializable, has a nullify constructor, and allows access to properties
using getter and setter methods.
DAO: - The Java Data Access Object (Java DAO) is an important component in business
applications. Business applications almost always need access to data from relational or
object databases and the Java platform offers many techniques for accessing this data.
The oldest and most mature technique is to use the Java Database Connectivity (JDBC)
API, which provides the capability to execute SQL queries against a database and then
fetch the results, one column at a time. Although this API provides everything a
developer needs to access data and to persist application state, it is a cumbersome API to
develop against - which makes a Java DAO code generator particularly useful.

6.1 Subsystem Architecture


Some of the most important services are:
Page 44 of 123

Project Report-Kiosk Management System

Home : For this we use jsp pages and there are different fields about the project.
About Us: This tab hold the information about project. The main function that are
provided by Enjoy the life are define here.
Contact Us: This page hold the contact information about the developers.
Register Page: This is the JSP page. This is the page that help the user to register for this
site. There are a simple registration form that are filled by the user and after that the user
are register for this site.
Login Page: This is the JSP page. The login page hold the two fields. These are Name,
Password, by using these field validation are provided that the user is authenticated or
not.
Hotel: This is the JSP page and provide all the related details about the hotels to the
viewer.
Flight: This is the JSP page and provide all the related details about the flights to the
viewer.
Bus: This is the JSP page and provide all the related details about the buses to the viewer.
Train: This is the JSP page and provide all the related details about the trains to the
viewer.

7. Policies and Tactics


There are certain policies and tactics which should be kept in mind for correct
compilation of project.
The P.C should have a servlet-2.5 version,JSP-2.0 version,Http-1.1version.
The system should capable of arranging storage space .
The user must have correct knowledge of both hardware and software.
The correct compilation of project is required.
The project contains error handling mechanism also.
The testing of project is simply through running it.
Since we have developed the project in JAVA language that is user friendly & Platform
independent.
The technique used in the project as a backend is ORACLE the frontend is designed
using JSP forms .
In coding guidelines we have implemented mouseover concept using CSS.
We have implemented SERVLET that will communicate with JSP forms.
The memory usage of the system required is minimum 256MB (RAM).
Connectivity is done through DAO.
Architecture is based on MVC(Model View Controller )

Page 45 of 123

Project Report-Kiosk Management System

The file created during the six weeks: hotel_1.jsp


home.jsp
Adminstrator.jsp
admin.jsp
adminbus.jsp
adminflight.jsp
adminhotels.jsp
admintrain.jsp
trains.jsp
buses.jsp
contactus.jsp
flight.jsp
help.jsp
register.jsp
hotelSearch.java
trainSearch.java
busSearch.java
admin.java
flightSearch.java
registrationServlet.java
stationServlet.java

8. Detailed System Design


The description about the project is that we have endeavored to form three type of users:Administrator, Authorized User and Visitor.
Administrator provides Login ID and Password to the user.
Authorized User will have access to all the services provided by KMS.
Visitors are unauthorized users who can just view the details that are provided by
Administrator.
Benefits
This software reduce lost of register work storage & also excel sheets as earlier done by
Programmers.
Page 46 of 123

Project Report-Kiosk Management System

Backup of data is possible in case if data is loss or corrupted

8.1 Classification
Kiosk Management System includes mainly three Modules:
Module 1
Module 2
Module 3

8.2 Definition
Module 1
Analysis design & coding of the following modules
Creation of Various Pages regarding Services provided by Administrator as
Railways, Roadways, Airlines and Hotel Reservation
Creation of Users (Administrator, Visitor, Authorized User)
Creation of Databases Relevant to the Application
Design of Dynamic Search Engine of the application to search for the relevant
services on the basis of inputs provided by User.
Kiosk Management System will provide various types of information to the visitor such
as information regarding roadways, railways, airlines and hotel reservation, contact
information, etc.
Module 2
Analysis design & coding of the following modules
Searching of Relevant data from the database as entered by Administrator
Booking/Reservation/Cancel of the Services by logging as an Authorized User
Onscreen confirmation of the Reservation and through report as well
Printing of Copy of Reservation, if cannot be done at that time then can be done
later using some Booking ID, etc.
Module 3
Analysis design & coding of the following modules
Report generation by the Administrator such as day/monthly reports on various
issues for tracking purpose to enhance the services.
Providing Packages/Offers for the Authorized Users, if user is interested then
further information on packages.
Booking/Reservation/Cancel of Packages

8.3 Responsibilities
Some of the most important services are:
Home : For this we use jsp pages and there are different fields about the project.
About Us: This tab hold the information about project. The main function that
are provided by Enjoy the life are define here.

Page 47 of 123

Project Report-Kiosk Management System

Contact Us: This page hold the contact information about the developers.
Register Page: This is the JSP page. This is the page that help the user to register
for this site. There are a simple registration form that are filled by the user and
after that the user are register for this site.
Login Page: This is the JSP page. The login page hold the two fields. These are
Name, Password, by using these field validation are provided that the user is
authenticated or not.
Hotel: This is the JSP page and provide all the related details about the hotels to
the viewer.
Flight: This is the JSP page and provide all the related details about the flights to
the viewer.
Bus: This is the JSP page and provide all the related details about the buses to the
viewer.
Train: This is the JSP page and provide all the related details about the trains to
the viewer.

8.4 Constraints
Software is limited for distant places .With distant place it may cause difficulties.
Not very high level Software i.e not for the Network communication.
Every Record to be fetch must in Database Table first.

8.5 Composition
This mainly includes three types of user.
Users may be of three types: - Administrator, Authorized User and Visitor.
Administrator provides Login ID and Password to the user.
Authorized User will have access to all the services provided by KMS.
Visitors are unauthorized users who can just view the details that are provided by
Administrator.

DFD

Page 48 of 123

Project Report-Kiosk Management System

Page 49 of 123

Project Report-Kiosk Management System

ER Diagram

name
address

Room type
H id

city
H id
state

Room
details

have

Hotel
Pin no
Contact
no
No
of
room
s
No
of
days

No
rooms

email
Book
ing
id

fare
login

book

ha
s

Check
in

passwor
d
login
rol
e

Booke
d by

User
Check
out

fare

have

Booking hotel

Booking
date

of

Total
fare

Booked
user

email
F
name
passwo
rd

L
name

Booki
ng
payme
nt

Payment
id
Booking
id

gender
payment

amoun
t

addres
s
tax

book

Page 50 of 123

Project Report-Kiosk Management System

Bus
type
F no

sourc
e

Bus no

destina
tion

flight

E
fare

sea
t

sourc
e
descr
iptio
n

bus

No
of
seats

Ac 1
sleeper
Ac 2

train

destina
tion
Ac 3

sourc
e

sto
ppa
ge

B
fare

station

8.6 Database Design


Sno

Table name

Description

login

Different types of login users

hotel

Different types of hotels

train_details

Different types of trains

flight_details

station

Different types of stations

bus_details

Different types of buses

room_details

Different types of rooms

registration

Page 51 of 123

destina
tion

Different types of flights

Different types of users details

Project Report-Kiosk Management System

8.7 Table schemas

Page 52 of 123

Project Report-Kiosk Management System

Page 53 of 123

Project Report-Kiosk Management System

Page 54 of 123

Project Report-Kiosk Management System

8.8 Class Diagrams and Classes


Loginprocess

Hoteprocess

Traindetails

Page 55 of 123

Project Report-Kiosk Management System

Flightdetails

Station

Page 56 of 123

Project Report-Kiosk Management System

Busdetails

Roomdetails

Registration

Page 57 of 123

Project Report-Kiosk Management System

8.9 User/Interactions

Home : For this we use jsp pages and there are different fields about the project.
About Us: This tab hold the information about project. The main function that
are provided by Enjoy the life are define here.
Contact Us: This page hold the contact information about the developers.
Register Page: This is the JSP page. This is the page that help the user to register
for this site. There are a simple registration form that are filled by the user and
after that the user are register for this site.
Login Page: This is the JSP page. The login page hold the two fields. These are
Name, Password, by using these field validation are provided that the user is
authenticated or not.
Hotel: This is the JSP page and provide all the related details about the hotels to
the viewer.
Flight: This is the JSP page and provide all the related details about the flights to
the viewer.
Bus: This is the JSP page and provide all the related details about the buses to the
viewer.
Train: This is the JSP page and provide all the related details about the trains to
the viewer

Page 58 of 123

Project Report-Kiosk Management System

8.10 Resources
Resources used are CSS file, MVC2 Architecture, JDBC, JSP forms, Servlet, Data
Access Object(DAO), Transfer Object (TO).

8.11 Processing
In this we have used MVC2 Architecture, DAO connectivity through Transfer Object,
JSP forms and Servlet are also used for Communication.

8.12 Detailed Subsystem Design


MVC Architecture
o Model. The model manages the behavior and data of the application
domain, responds to requests for information about its state (usually from
the view), and responds to instructions to change state (usually from the
controller).
o View. The view manages the display of information.
o Controller. The controller interprets the mouse and keyboard inputs from
the user, informing the model and/or the view to change as appropriate

9. Source Code Details


SLOC: Source Lines of Code. Use the free software sloc to calculate the SLOC
S.No

Filename

SLOC

1.

hotel_1.jsp

600

2.

home.jsp

152

3.

Adminstrator.jsp

32

4.

admin.jsp

35

5.

adminbus.jsp

43

6.

adminflight.jsp

47

7.

adminhotel.jsp

52

8.

admintrain.jsp

49

9.

buses.jsp

317

10.

flight.jsp

326

11.

trains.jsp

326

Page 59 of 123

Project Report-Kiosk Management System

12.

register.jsp

296

13

contactus.jsp

45

// admin.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<script type='text/javascript'>
function formValidation()
{
var eid = document.form2.email_id;
var pswd = document.form2.password;
if(ValidateEmail(eid))
{
if(validatePassword(pswd))
{
}return false;
}
}
function ValidateEmail(eid)
{
var mailformat = /^\w+([\.-]?\w+)*@\w+([\.-]?\w+)*(\.\w{2,3})+$/;
if(eid.value.match(mailformat))
{
return true;
}
else
{
alert("You have entered an invalid email address!");
eid.focus();
return false;
}
}
Page 60 of 123

Project Report-Kiosk Management System

function alphanumeric(pswd)
{
var letters = /^[0-9a-zA-Z]+$/;
if(pswd.value.match(letters))
{
return true;
}
else
{
alert('Please input alphanumeric characters only');
pswd.focus();
return false;
}
}
</script>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<div id="page-background"><img src="./image/bk5.jpg" width="100%"
height="100%"></div>
<div id="content">
<table align="right" >
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Homepage"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
</table>
<form action="./admin" method="post" name="form2">
<center><img src="./image/ad5.jpg" height="150" width="1100"></center>
<font size="5">
<table align="center">
<pre>
<tr><td> Login Id </td>
<td><input type="text" name="login"> </td></tr>
<tr><td>Password</td>
<td><input type="password" name="password"> </td>
</tr>
<tr>
<td><input type="submit" value="Sign in"></td>
<td><input type="reset" value="Reset"></td>
</tr>
</pre>

Page 61 of 123

Project Report-Kiosk Management System

</table>
</font>
</form></div>
</body>
</html>

// administrator.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<script type="text/javascript">
javascript:window.history.forward(1);
</script>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<div id="page-background"><img src="./image/bk5.jpg" width="100%"
height="100%"></div>
<div id="content">
<table align="right" >
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Homepage"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Logout"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
</table>
<font size="3">
<table align="center">
<tbody>

Page 62 of 123

Project Report-Kiosk Management System

<pre>
<tc><td>
<a href="./adminbus.jsp"><img src="./image/q5.jpg"
width="150"><br/><center>Buses</center></a>
</td>
</tc>
<tc><td>
<a href="./admintrain.jsp"> <img src="./image/tt4.jpg"
width="150"><br/><center>Trains</center></a>
</td></tc>
<tc><td>
<a href="./adminflight.jsp"><img src="./image/ff.jpg"
width="150"><br/><center>Flights</center></a>
</td></tc>
<tc><td>
<a href="./adminhotels.jsp"> <img src="./image/hh.jpg"
width="150"><br/><center>Hotels</center></a>
</td></tc>
</pre>
</tbody>
</table>
</font>
</div>
</body>
</html>

height="100"

height="100"

height="100"

height="100"

// adminbus.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<div id="page-background"><img src="./image/bk5.jpg" width="100%"
height="100%"></div>

Page 63 of 123

Project Report-Kiosk Management System

<div id="content">
<table align="right" >
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Homepage"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
</table>
<form method="post" action="./bus_detailServlet">
<font size="3">
<table align="center">
<tbody>
<pre>
<tc><td>
<a href="./adminbus.jsp"><img src="./image/q5.jpg" height="100"
width="150"><br/><center>Buses</center></a>
</td>
</tc>
<tc><td>
<a href="./admintrain.jsp"><img src="./image/tt4.jpg" height="100"
width="150"><br/><center>Trains</center></a>
</td></tc>
<tc><td>
<a href="./adminflight.jsp"><img src="./image/ff.jpg" height="100"
width="150"><br/><center>Flights</center></a>
</td></tc>
<tc><td>
<a href="./adminhotels.jsp"><img src="./image/hh.jpg" height="100"
width="150"><br/><center>Hotels</center></a>
</td></tc>
</pre>
</tbody>
</table>
</font>
<table><tbody>
<TR><TD>
<font size="5"> <h2>Bus Details:</h2> </font>
</TD> </TR>
<TR>
<TD height="25">Bus no</TD>
<TD height="25" width="78%"><input type="text" name="bus_no"> </TD></TR>
<TR>
<TD height="14">No of seats</TD>
<TD height="14" width="78%"><input type="text" name="no_of_seats">
</TD></TR>

Page 64 of 123

Project Report-Kiosk Management System

<TR>
<TD height="14">Bus type</TD>
<TD height="14" width="78%"><input type="text" name="bus_type">
</TD></TR>
<TR>
<TD height="14">Description</TD>
<TD height="14" width="78%"><input type="text" name="description">
</TD></TR>
<TR>
` <TD height="14">Source</TD>
<TD height="14" width="78%"><input type="text" name="source"> </TD></TR>
<TR>
<TD height="14">Destination</TD>
<TD height="14" width="78%"><input type="text" name="destination">
</TD></TR>
<tr>
<td><input type="submit" value="Submit"</td>
</tr>
</tbody>
</table>
</form>
</div>
</body>
</html>
// admintrain.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>

Page 65 of 123

Project Report-Kiosk Management System

<div id="page-background"><img src="./image/bk5.jpg" width="100%"


height="100%"></div>
<div id="content">
<table align="right" >
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Homepage"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
</table>
<form method="post" action="./train_detailsServlet">
<font size="3">
<table align="center">
<tbody>
<pre>
<tc><td>
<a href="./adminbus.jsp"><img src="./image/q5.jpg" height="100"
width="150"><br/><center>Buses</center></a>
</td>
</tc>
<tc><td>
<a href="./admintrain.jsp"><img src="./image/tt4.jpg" height="100"
width="150"><br/><center>Trains</center></a>
</td></tc>
<tc><td>
<a href="./adminflight.jsp"><img src="./image/ff.jpg" height="100"
width="150"><br/><center>Flights</center></a>
</td></tc>
<tc><td>
<a href="./adminhotels.jsp"><img src="./image/hh.jpg" height="100"
width="150"><br/><center>Hotels</center></a>
</td></tc>
</pre>
</tbody>
</table>
</font>
<table><tbody>
<TR>
<TD>
<font size="5"><h2>Train Details:</h2></font>
</TD>
</TR>
<TR>
<TD height="14">Train no</TD>
<TD height="14" width="78%"><input type="text" name="train_no">
</TD></TR>

Page 66 of 123

Project Report-Kiosk Management System

<TR>
<TD height="14">Train name</TD>
<TD height="14" width="78%"><input type="text" name="train_name">
</TD></TR>
<TR>
<TD height="14">Source</TD>
<TD height="14" width="78%"><input type="text" name="source"> </TD></TR>
<TR>
<TD height="14">Destination</TD>
<TD height="14" width="78%"><input type="text" name="destination">
</TD></TR>
<TR>
` <TD height="14">Ac1</TD>
<TD height="14" width="78%"><input type="text" name="ac1"> </TD></TR>
<TR>
<TD height="14">Ac2</TD>
<TD height="14" width="78%"><input type="text" name="ac2"> </TD></TR>
<TR>
<TD height="14">Ac3</TD>
<TD height="14" width="78%"><input type="text" name="ac3"> </TD></TR>
<TR>
<TD height="14">Sleeper</TD>
<TD height="14" width="78%"><input type="text" name="sleeper"> </TD></TR>
<tr>
<td><input type="submit" value="Submit"</td>
</tr>
</tbody>
</table>
</form>
</div>
</body>
</html>
//adminhotels.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}

Page 67 of 123

Project Report-Kiosk Management System

</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<div id="page-background"><img src="./image/bk5.jpg" width="100%"
height="100%"></div>
<div id="content">
<table align="right" >
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Homepage"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
</table>
<form method="post" action="./hotelServlet">
<font size="3">
<table align="center">
<tbody>
<pre>
<tc><td>
<a href="./adminbus.jsp"><img src="./image/q5.jpg"
width="150"><br/><center>Buses</center></a>
</td>
</tc>
<tc><td>
<a href="./admintrain.jsp"><img src="./image/tt4.jpg"
width="150"><br/><center>Trains</center></a>
</td></tc>
<tc><td>
<a href="./adminflight.jsp"><img src="./image/ff.jpg"
width="150"><br/><center>Flights</center></a>
</td></tc>
<tc><td>
<a href="./adminhotels.jsp"><img src="./image/hh.jpg"
width="150"><br/><center>Hotels</center></a>
</td></tc>
</pre>
</tbody>
</table>
</font>
<table><tbody>
<TR>
<TD>
<font size="5"> <h2>Hotel Details:</h2></font>
</TD>

Page 68 of 123

height="100"

height="100"

height="100"

height="100"

Project Report-Kiosk Management System

</TR>
<TR>
<TD height="14">Hotel id</TD>
<TD height="14" width="78%"><input type="text" name="hotel_id">
</TD></TR>
<TR>
<TD height="14">Hotel Name</TD>
<TD height="14" width="78%"><input type="text" name="hotel_name">
</TD></TR>
<TR>
<TD height="14">Address</TD>
<TD height="14" width="78%"><input type="text" name="address"> </TD></TR>
<TR>
<TD height="14">City</TD>
<TD height="14" width="78%"><input type="text" name="city"> </TD></TR>
<TR>
` <TD height="14">Country</TD>
<TD height="14" width="78%"><input type="text" name="country"> </TD></TR>
<TR>
<TD height="14">Pin Code </TD>
<TD height="14" width="78%"><input type="text" name="pin_no"> </TD></TR>
<TR>
<TD height="14">Contact no</TD>
<TD height="14" width="78%"><input type="text" name="contact_no">
</TD></TR>
<TR>
<TD height="14">Email id</TD>
<TD height="14" width="78%"><input type="text" name="email_id">
</TD></TR>
<tr>
<td><input type="submit" value="Submit"</td>
</tr>
</tbody>
</table>
</form>
</div>
</body>
</html>
// adminflight.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">

Page 69 of 123

Project Report-Kiosk Management System

<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<div id="page-background"><img src="./image/bk5.jpg" width="100%"
height="100%"></div>
<div id="content">
<table align="right" >
<tr>
<td valign="top" align="right" width="50"> <a href="./home.jsp"
title="Homepage"><img src="./image/home.jpg" width="50" height="45"></a></td>
</tr>
</table>
<form method="post" action="./flight_detailServlet">
<font size="3">
<table align="center">
<tbody>
<pre>
<tc><td>
<a href="./adminbus.jsp"><img src="./image/q5.jpg"
width="150"><br/><center>Buses</center></a>
</td>
</tc>
<tc><td>
<a href="./admintrain.jsp"><img src="./image/tt4.jpg"
width="150"><br/><center>Trains</center></a>
</td></tc>
<tc><td>
<a href="./adminflight.jsp"><img src="./image/ff.jpg"
width="150"><br/><center>Flights</center></a>
</td></tc>
<tc><td>
<a href="./adminhotels.jsp"><img src="./image/hh.jpg"
width="150"><br/><center>Hotels</center></a>
</td></tc>
</pre>

Page 70 of 123

height="100"

height="100"

height="100"

height="100"

Project Report-Kiosk Management System

</tbody>
</table>
</font>
<table>
<tbody>
<TR><TD>
<font size="5"> <h2>Flight Details:</h2></font>
</TD></TR>
<TR>
<TD height="14">Flight no</TD>
<TD height="14" width="78%"><input type="text" name="flight_no">
</TD></TR>
<TR>
<TD height="14">Source</TD>
<TD height="14" width="78%"><input type="text" name="source"> </TD></TR>
<TR>
<TD height="14">Destination</TD>
<TD height="14" width="78%"><input type="text" name="destination">
</TD></TR>
<TR>
<TD height="14">Business Seat</TD>
<TD height="14" width="78%"><input type="text" name="b_seat"> </TD></TR>
<TR>
` <TD height="14">Economy Seat</TD>
<TD height="14" width="78%"><input type="text" name="e_seat"> </TD></TR>
<TR>
<TD height="14">Business Fare </TD>
<TD height="14" width="78%"><input type="text" name="b_fare"> </TD></TR>
<TR>
<TD height="14">Economy Fare</TD>
<TD height="14" width="78%"><input type="text" name="e_fare"> </TD></TR>
<tr>
<td><input type="submit" value="Submit"</td>
</tr>
</tbody>
</table>
</form>
</div>
</body>
</html>

//adminbus_detailDao.java

Page 71 of 123

Project Report-Kiosk Management System

ackage com.kms.mvc.DAO;
import com.kms.mvc.bean.bus_detailbean;
import java.sql.*;
import java.util.*;
public class adminbus_detailDao {
public int addbus_detail(bus_detailbean bean)throws Exception
{
Connection conn = connectionDao.getConnection();
CallableStatement cs=conn.prepareCall("{call prcbus_detail(?,?,?,?,?,?)}");
cs.setString(1,bean.getBus_no());
cs.setString(2,bean.getNo_of_seats());
cs.setString(3,bean.getBus_type());
cs.setString(4,bean.getDescription());
cs.setString(5,bean.getSource());
cs.setString(6,bean.getDestination());
return cs.executeUpdate();
}
}
//bus_detailServlet.java
package com.kms.mvc.controller;
import com.kms.mvc.DAO.adminbus_detailDao;
import com.kms.mvc.bean.*;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
/**
*
* @author charu
*/
public class bus_detailServlet extends HttpServlet {
private String msg;
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {
String msg=null;
bus_detailbean bean=new bus_detailbean();
bean.setBus_no(request.getParameter("bus_no"));

Page 72 of 123

Project Report-Kiosk Management System

bean.setNo_of_seats(request.getParameter("no_of_seats"));
bean.setBus_type(request.getParameter("bus_type"));
bean.setDescription(request.getParameter("description"));
bean.setSource(request.getParameter("source"));
bean.setDestination(request.getParameter("destination"));
adminbus_detailDao Dao=new adminbus_detailDao();
try{
int result=Dao.addbus_detail(bean);
if(result>0)
{
msg="success !!!!!!";
}
}catch(Exception ex)
{
msg=ex.getMessage();
System.out.println(ex);
}
finally {
request.setAttribute("msg",msg);
request.getRequestDispatcher("./adminbus.jsp").forward(request,response);
}
}
// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +
sign on the left to edit the code.">
/**
* Handles the HTTP <code>GET</code> method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
/**
* Handles the HTTP <code>POST</code> method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/

Page 73 of 123

Project Report-Kiosk Management System

@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
/**
* Returns a short description of the servlet.
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
//home.jsp
html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Home page</title>
</head>
<body background = "./image/homebg.jpg">
<font color="white" size="5">
<script type="text/javascript">
var d = new Date();
var time = d.getHours();
if (time < 10)
{document.write("<b><I>Hello :)Good morning</I></b>");}
else{document.write("<b><I> Hello!! Have a Good day ahead:)</I></b>");}
</script>
<script type="text/javascript">
var d = new Date();
theDay=d.getDay();
switch (theDay)
{case 5: document.write("<b><i>Finally Friday!!!!!</i></b>");
break;
case 6: document.write("<b><i>Super Saturday!!!!!<i></b>");
break;

Page 74 of 123

Project Report-Kiosk Management System

case 0: document.write("<b><i>Sleepy Sunday!!!!<i></b>");


break;
default: document.write("<b><i>I'm really looking forward to this weekend!<i></b>");}
</script>
<script type="text/javascript">
function validateForm()
{
var x=document.forms["form1"]["login"].value
var atpos=x.indexOf("@");
var dotpos=x.lastIndexOf(".");
if (atpos<1 || dotpos<atpos+2 || dotpos+2>=x.length)
{
alert("Not a valid e-mail address");
return false;
}
}
</script>
<table>
<tbody>
<tr>
<td> <img src="./image/enjoylife1.jpg" width="350" height="200"></td>
<td> <img src="./image/home_1.jpg" width="950" height="200"></tr>
<form action="./Login" method="post">
<font size="4"/>
<table> </tc>
</tbody>
</table>
<table>
<tbody>
<th>
<td valign="top" width="50"> <a href="./home.jsp" title="Homepage"><img
src="./image/home.jpg" width="50" height="45"></a>Home</td>
</th>
<th>
<td height="30" width="50">
<a href="./flights.jsp" title="Airline reservation"><img
src="./image/Flights.jpg" width="50" height="45"></a>Airline</td>

Page 75 of 123

Project Report-Kiosk Management System

</th>
<th>
<td height="30" width="50"> <a href="./hotels_1.jsp" title="Hotel
Reservation"><img src="./image/hotel.jpg" width="50" height="45"></a>Hotel</td>
</th>
<th>
<td height="30" width="50">
<a href="./trains.jsp" title="Train Reservation"><img
src="./image/trains.jpg" width="50" height="45"></a>Train</td>
</th>
<th>
<td height="30" width="50">
<a href="./buses.jsp" title="Bus Reservation"><img src="./image/bus.jpg"
width="50" height="45"></a>Bus</td>
</th>
<th>
<td height="30" width="50"> <a href="./gallery.jsp" title="Gallery"><img
src="./image/gallery.jpg" width="50" height="45"></a>Gallery</td>
</th>
<th>
<td height="30" width="50">
<a href="./contactus.jsp" title="Contact Us"><img src="./image/Contact
us.jpg" width="50" height="45"></a>Contact</td>
</th>
<th>
<td height="30" width="50">
<a href="./help.jsp" title="Help!"><img src="./image/help2.jpg"
width="50" height="45"></a>Help</td>
</th>
<th>
<td height="30" width="50">
<a href="./admin.jsp" title="Help!"><img src="./image/help2.jpg"
width="50" height="45"></a>Admin</td>
</th>
</tbody>
</form>
<tbody>
<tr><table align="left">
<marquee behavior="scroll"direction="right" height="250" width="1400">
<img src="./image/home2.jpg" width="300" height="250">
<img src="./image/home3.jpg" width="300" height="250">
<img src="./image/home4.jpg" width="300" height="250">
<img src="./image/home5.jpg" width="300" height="250">

Page 76 of 123

Project Report-Kiosk Management System

<img src="./image/home1.jpg" width="300"height="250">


<img src="./image/home6.jpg" width="300"height="250">
<img src="./image/home7.jpg" width="300"height="250">
<img src="./image/home8.jpg" width="300"height="250">
</marquee>
</table>
<form action="./loginServlet" method="post" name="form1">
<font face="times new roman" size="5" color="black">
<table background ="./image/purple.jpg" align="left" width="1350" height="50">
<tbody>
<tc>
<td>
<img src="./image/login_icon[1].png" height="150" width="200"></td>
<td> Login Id </td>
<td><input type="text" name="login"> </td>
</tc>
<tc>
<td>Password</td>
<td><input type="password" name="password"> </td>
</tc>
<tc>
<td><input type="submit" value="Sign in"</td>
<br>
<td><input type="reset" value="Reset"></td>
</tc>
<tc>
<td><h3><center> <a href="./register.jsp"><pre><img
src="./image/NMI3registration_icon[1].jpg" width="200" height="50" align="center">
</center></a></h3> </td>
</tc>
</tbody>
</table>
</pre>
</font>
</form>
</table>
</body>
</html>
loginSevlet.java
package com.kms.mvc.controller;
import com.kms.mvc.DAO.loginDao;

Page 77 of 123

Project Report-Kiosk Management System

import com.kms.mvc.bean.*;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
/**
*
* @author Shikha
*/
public class loginServlet extends HttpServlet {
/**
* Processes requests for both HTTP <code>GET</code> and <code>POST</code>
methods.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {
String msg=null;
try{
loginbean login = new loginbean();
login.setEmail_id(request.getParameter("email_id"));
login.setPassword(request.getParameter("password"));
loginDao dao = new loginDao();
if(dao.validate(login))
{
msg= "User, " + login.getEmail_id();
HttpSession session = request.getSession();
session.setMaxInactiveInterval(60*5);
session.setAttribute("msg", msg);
session.setAttribute("email",login.getEmail_id());
response.sendRedirect("./newjsp.jsp");
}
else
{
msg="Invalid Login ID or Password...";
request.setAttribute("msg", msg);

Page 78 of 123

Project Report-Kiosk Management System

request.getRequestDispatcher("./home.jsp").forward(request, response);
}
} catch (Exception ex)
{
msg=ex.getMessage();
System.out.println(ex);
}
}
// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +
sign on the left to edit the code.">
/**
* Handles the HTTP <code>GET</code> method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
/**
* Handles the HTTP <code>POST</code> method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
/**
* Returns a short description of the servlet.
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>

Page 79 of 123

Project Report-Kiosk Management System

}
loginDao.java
package com.kms.mvc.DAO;
import com.kms.mvc.bean.*;
import java.sql.*;
public class loginDao {
private boolean status;
public boolean validate(loginbean login)throws Exception
{
Connection con = connectionDao.getConnection();
String query= "select email_id,password from registration where email_id=? and
password=?";
PreparedStatement ps = con.prepareStatement(query);
ps.setString(1, login.getEmail_id());
ps.setString(2, login.getPassword());
ResultSet rs = ps.executeQuery();
if(rs.next())
{
if(rs.getString(1).equals(login.getEmail_id()) &&
rs.getString(2).equals(login.getPassword()))
{
status = true;
}
}
con.close();
return status;
}
}
loginbean.java
package com.kms.mvc.bean;
public class loginbean {
private String email_id;
private String password;
private String rol;
public loginbean() {
}
public String getEmail_id() {
return email_id;
}
public void setEmail_id(String email_id) {

Page 80 of 123

Project Report-Kiosk Management System

this.email_id = email_id;
}
public String getPassword() {
return password;
}
public void setPassword(String password) {
this.password = password;
}
public String getRol() {
return rol;
}
public void setRol(String rol) {
this.rol = rol;
}
}
//trains.jsp
<%@page import="java.util.Iterator"%>
<%@page import="java.util.List"%>
<%@page import="com.kms.mvc.bean.train_detailsbean"%>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:50; z-index:1; padding:10px;}
</style>
</head>
<body>
<div id="page-background"><img src="./image/train1.jpg" width="100%"
height="100%"></div>
<div id="content">
<font color="white"/>
<font size="5" />
<table>
<tc>
<td><img src="./image/logo[1].png" width="200" height="200"><td>

Page 81 of 123

Project Report-Kiosk Management System

<td> <img src="./image/rail.png" width="1100" height="200"></td>


</tc></table>
<form method="get" action="./trainSearch">
<table background="./image/ww1.jpg" width="576" height="288">
<tbody>
<pre> <tr><td><h3> <i><u>Book your tickets now... </u></i></h3><td><tr>
</pre>
<tbody>
<tr>
<td height="14" width="100">From</td>
<td height="14" width="100">To</td>
</tr>
<tr>
<td height="14" width="100">
<select name="from">
<optgroup label="Top Indian Departure cities">
<option value="BOM">Mumbai
(Bombay)</option>
<option value="delhi">New Delhi
(Delhi)</option>
<option value="MAA">Chennai
(Madras)</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option value="goa">Goa</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="HYD">Hyderabad</option>
<option value="PNQ">Pune
(Poona)</option>
<option value="CCU">Kolkata
(Calcutta)</option>
<option
value="AMD">Ahmedabad</option>
<option
value="ATQ">Amritsar</option>
<option
value="GAU">Guwahati</option>
<option
value="TRV">Thiruvananthapuram</option>
</optgroup>
<optgroup label="Cities in
Alphabetical Order">
<option
value="IXA">Agartala</option>

Page 82 of 123

Project Report-Kiosk Management System

<option
value="AGX">Agatti</option>
<option
value="AGR">Agra</option>
<option
value="AMD">Ahmedabad</option>
<option
value="AJL">Aizawl</option>
<option
value="IXD">Allahabad</option>
<option
value="IXV">Along</option>
<option
value="ATQ">Amritsar</option>
<option
value="IXU">Aurangabad</option>
<option
value="IXB">Bagdogra/Siliguri</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option
value="IXG">Belgaum</option>
<option
value="BHU">Bhavnagar</option>
<option
value="BHO">Bhopal</option>
<option
value="BBI">Bhubaneswar</option>
<option
value="BHJ">Bhuj</option>
<option value="CBD">Car
Nicobar</option>
<option
value="IXC">Chandigarh</option>
<option value="MAA">Chennai
(Madras)</option>
<option
value="CJB">Coimbatore</option>
<option
value="CDP">Cuddapah</option>
<option value="DAE">Daporijo
(Daporizo)</option>
<option
value="DED">Dehradun</option>
<option
value="DIB">Dibrugarh</option>

Page 83 of 123

Project Report-Kiosk Management System

<option
value="DMU">Dimapur</option>
<option value="DIU">Diu</option>
<option
value="IXY">Gandhidham/Kandla</option>
<option
value="GAY">Gaya</option>
<option value="GOI">Goa</option>
<option
value="GAU">Guwahati</option>
<option
value="GWL">Gwalior</option>
<option
value="HBX">Hubli</option>
<option
value="HYD">Hyderabad</option>
<option
value="IMF">Imphal</option>
<option
value="IDR">Indore</option>
<option
value="JLR">Jabalpur</option>
<option
value="JAI">Jaipur</option>
<option
value="JSA">Jaisalmer</option>
<option
value="IXJ">Jammu</option>
<option
value="JGA">Jamnagar</option>
<option
value="JDH">Jodhpur</option>
<option
value="JRH">Jorhat</option>
<option
value="IXH">Kailashahar</option>
<option
value="KNU">Kanpur</option>
<option
value="NAG">Nagpur</option>
<option value="DEL">New Delhi
(Delhi)</option>
<option value="IXI">North
Lakhimpur</option>
<option value="IXT">Pasighat
(Passighat)</option>

Page 84 of 123

Project Report-Kiosk Management System

<option
value="PAT">Patna</option>
<option
value="PBD">Porbandar</option>
<option value="IXZ">Port
Blair</option>
<option value="PNQ">Pune
(Poona)</option>
<option
value="BEK">Puttaparthi</option>
<option
value="RPR">Raipur</option>
<option
value="RJA">Rajahmundry</option>
<option
value="RAJ">Rajkot</option>
<option
value="IXR">Ranchi</option>
<option
value="SHL">Shillong</option>
<option
value="IXS">Silchar</option>
<option
value="SSE">Sholapur</option>
<option
value="SXR">Srinagar</option>
<option
value="TEZ">Tezpur</option>
<option value="TEI">Tezu</option>
<option
value="TRV">Thiruvananthapuram</option>
<option value="TRZ">Tiruchirapalli
(Trichy)</option>
<option value="TIR">Tirupati
(Tirupathi)</option>
<option value="TCR">Tuticorin
(Thoothukudi)</option>
<option
value="UDR">Udaipur</option>
<option value="BDQ">Vadodara
(Baroda)</option>
<option
value="VNS">Varanasi</option>
<option value="VGA">Vijayawada
(Vijaywada)</option>

Page 85 of 123

Project Report-Kiosk Management System

<option
value="VTZ">Visakhapatnam (Vishakhapatnam)</option>
<option value="WGC">Warangal
(Warrangal)</option>
</optgroup>
</select></td>
<td height="14" width="100">
<select name="to">
<optgroup label="Top Indian Departure cities">
<option value="BOM">Mumbai
(Bombay)</option>
<option value="delhi">New Delhi
(Delhi)</option>
<option value="MAA">Chennai
(Madras)</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option value="goa">Goa</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="HYD">Hyderabad</option>
<option value="PNQ">Pune
(Poona)</option>
<option value="CCU">Kolkata
(Calcutta)</option>
<option
value="AMD">Ahmedabad</option>
<option
value="ATQ">Amritsar</option>
<option
value="GAU">Guwahati</option>
<option
value="TRV">Thiruvananthapuram</option>
</optgroup>
<optgroup label="Cities in
Alphabetical Order">
<option
value="IXA">Agartala</option>
<option
value="AGX">Agatti</option>
<option
value="AGR">Agra</option>
<option
value="AMD">Ahmedabad</option>

Page 86 of 123

Project Report-Kiosk Management System

<option
value="AJL">Aizawl</option>
<option
value="IXD">Allahabad</option>
<option
<option
value="TEZ">Tezpur</option>
<option value="TEI">Tezu</option>
<option
value="TRV">Thiruvananthapuram</option>
<option value="TRZ">Tiruchirapalli
(Trichy)</option>
<option value="TIR">Tirupati
(Tirupathi)</option>
<option value="TCR">Tuticorin
(Thoothukudi)</option>
<option
value="UDR">Udaipur</option>
<option value="BDQ">Vadodara
(Baroda)</option>
<option
value="VNS">Varanasi</option>
<option value="VGA">Vijayawada
(Vijaywada)</option>
<option
value="VTZ">Visakhapatnam (Vishakhapatnam)</option>
<option value="WGC">Warangal
(Warrangal)</option>
</optgroup>
</select>
</td>
</tr>
<pre>
<tr>
<td><br><input type="submit" value="Search"/></td>
</tr></pre>
</tbody>
</table>
</form>
<%
if(request.getAttribute("trainList")!=null)
{

Page 87 of 123

Project Report-Kiosk Management System

List<train_detailsbean> list =(List<train_detailsbean>)


request.getAttribute("trainList");
Iterator<train_detailsbean> it = list.iterator();
if(it.hasNext())
{
%>
<table border="1">
<thead>
<tr>
<th>TRAIN_NO</th>
<th>TRAIN_NAME</th>
<th>SOURCE</th>
<th>DESTINATION</th>
<th>AC1</th>
<th>AC2</th>
<th>AC3</th>
<th>SLEEPER</th>
</tr>
</thead>
<tbody>
<%
it = list.iterator();
while(it.hasNext())
{
train_detailsbean bean = it.next();
%>
<tr>
<td><%= bean.getTrain_no()%></td>
<td><%=bean.getTrain_name()%></td>
<td><%=bean.getSource()%></td>
<td><%=bean.getDestination()%></td>
<td><%=bean.getAc1()%></td>
<td><%=bean.getAc2()%></td>
<td><%=bean.getAc3()%></td>
<td><%=bean.getSleeper()%></td>
<td><a href="./train1.jsp?train_no=<%= bean.getTrain_no()
%>">view</a></td>
</tr>
<%
}
%>
</tbody>
</table>

Page 88 of 123

Project Report-Kiosk Management System

<% }else
{
%>
<font color="red"><b>No Record Found</b></font>
<%
}
}
%>

</div>
</body>
</html>
//buses.jsp
<%@page import="java.util.Iterator"%>
<%@page import="com.kms.mvc.bean.bus_detailbean"%>
<%@page import="java.util.List"%>
<%@page contentType="text/html" pageEncoding="UTF-8" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<font size="5"> <center></center></font>
</head>
<body>
<div id="page-background"><img src="./image/path1.jpg" width="100%"
height="100%"></div>
<div id="content">
<font color="white"/>
<font size="5"/>
<table>
<tc>
<td><img src="./image/logo[1].png" width="200" height="200"><td>
<td> <img src="./image/roadways.jpg" width="1100" height="200"></td>

Page 89 of 123

Project Report-Kiosk Management System

</tc></table>
<form method="get" action="./busSearch">
<table background="./image/ww1.jpg" width="576" height="288">
<tbody>
<pre> <tr><td><h3> <i><u>Book your tickets now... <u></i></h3><td><tr>
</pre> <th> <tr>
<td height="25" width="80">Leaving</td>
<td height="25" width="80">From</td>
</tr>
</th> <tr>
<td height="14" width="100">
<select name="from">
<optgroup label="Top Indian Departure cities">
<option value="BOM">Mumbai
(Bombay)</option>
<option value="delhi">New Delhi
(Delhi)</option>
<option value="MAA">Chennai
(Madras)</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option value="GOI">Goa</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="HYD">Hyderabad</option>
<option value="PNQ">Pune
(Poona)</option>
<option value="CCU">Kolkata
(Calcutta)</option>
<option
value="AMD">Ahmedabad</option>
<option
value="ATQ">Amritsar</option>
<option
value="GAU">Guwahati</option>
<option
value="TRV">Thiruvananthapuram</option>
</optgroup>
<optgroup label="Cities in
Alphabetical Order">
<option
value="IXA">Agartala</option>

Page 90 of 123

Project Report-Kiosk Management System

<option
value="AGX">Agatti</option>
<option
value="AGR">Agra</option>
<option
value="AMD">Ahmedabad</option>
<option
value="AJL">Aizawl</option>
<option
value="IXD">Allahabad</option>
<option
value="IXV">Along</option>
<option
value="ATQ">Amritsar</option>
<option
value="IXU">Aurangabad</option>
<option
value="IXB">Bagdogra/Siliguri</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option
value="IXG">Belgaum</option>
<option
value="BHU">Bhavnagar</option>
<option
value="BHO">Bhopal</option>
<option
value="BBI">Bhubaneswar</option>
<option
value="BHJ">Bhuj</option>
<option value="CBD">Car
Nicobar</option>
<option
value="IXC">Chandigarh</option>
<option value="MAA">Chennai
(Madras)</option>
<option
value="CJB">Coimbatore</option>
<option
value="CDP">Cuddapah</option>
<option value="DAE">Daporijo
(Daporizo)</option>
<option
value="DED">Dehradun</option>
<option
value="DIB">Dibrugarh</option>

Page 91 of 123

Project Report-Kiosk Management System

<option
value="DMU">Dimapur</option>
<option value="DIU">Diu</option>
<option
value="IXY">Gandhidham/Kandla</option>
<option
value="GAY">Gaya</option>
<option value="GOI">Goa</option>
<option
value="GAU">Guwahati</option>
<option
value="GWL">Gwalior</option>
<option
value="HBX">Hubli</option>
<option
value="HYD">Hyderabad</option>
<option
value="IMF">Imphal</option>
<option
value="IDR">Indore</option>
<option
value="JLR">Jabalpur</option>
<option
value="JAI">Jaipur</option>
<option
value="JSA">Jaisalmer</option>
<option
value="IXJ">Jammu</option>
<option
value="JGA">Jamnagar</option>
<option
value="JDH">Jodhpur</option>
<option
value="JRH">Jorhat</option>
<option
value="IXH">Kailashahar</option>
<option
value="KNU">Kanpur</option>
<option
value="IXK">Keshod</option>
<option
value="HJR">Khajuraho</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="KLH">Kolhapur</option>

Page 92 of 123

Project Report-Kiosk Management System

<option value="CCU">Kolkata
(Calcutta)</option>
<option value="CCJ">Kozhikode
(Calicut)</option>
<option
value="KUU">Kullu/Manali</option>
<option value="IXL">Leh</option>
<option
value="LKO">Lucknow</option>
<option
value="LUH">Ludhiana</option>
<option
value="IXM">Madurai</option>
<option
value="IXE">Mangalore</option>
<option value="BOM">Mumbai
(Bombay)</option>
<option
value="MZU">Muzzafarpur</option>
<option
value="MYQ">Mysore</option>
<option
value="NAG">Nagpur</option>
<option value="DEL">New Delhi
(Delhi)</option>
<option value="IXI">North
Lakhimpur</option>
<option value="IXT">Pasighat
(Passighat)</option>
<option
value="PAT">Patna</option>
<option
value="PBD">Porbandar</option>
<option value="IXZ">Port
Blair</option>
<option value="PNQ">Pune
(Poona)</option>
<option
value="BEK">Puttaparthi</option>
<option
value="RPR">Raipur</option>
<option
value="RJA">Rajahmundry</option>
<option
value="RAJ">Rajkot</option>

Page 93 of 123

Project Report-Kiosk Management System

<option
value="IXR">Ranchi</option>
<option
value="SHL">Shillong</option>
<option
value="IXS">Silchar</option>
<option
value="SSE">Sholapur</option>
<option
value="SXR">Srinagar</option>
<option
value="TEZ">Tezpur</option>
<option value="TEI">Tezu</option>
<option
value="TRV">Thiruvananthapuram</option>
<option value="TRZ">Tiruchirapalli
(Trichy)</option>
<option value="TIR">Tirupati
(Tirupathi)</option>
<option value="TCR">Tuticorin
(Thoothukudi)</option>
<option
value="UDR">Udaipur</option>
<option value="BDQ">Vadodara
(Baroda)</option>
<option
value="VNS">Varanasi</option>
<option value="VGA">Vijayawada
(Vijaywada)</option>
<option
value="VTZ">Visakhapatnam (Vishakhapatnam)</option>
<option value="WGC">Warangal
(Warrangal)</option>
</optgroup>
</select></td>
<td height="14" width="100">
<select name="to">
<optgroup label="Top Indian Departure cities">
<option value="BOM">Mumbai
(Bombay)</option>
<option value="DEL">New Delhi
(Delhi)</option>
<option value="MAA">Chennai
(Madras)</option>

Page 94 of 123

Project Report-Kiosk Management System

<option value="BLR">Bangaluru
(Bangalore)</option>
<option value="goa">Goa</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="HYD">Hyderabad</option>
<option value="PNQ">Pune
(Poona)</option>
<option value="CCU">Kolkata
value="IXG">Belgaum</option>
<option
value="BHU">Bhavnagar</option>
<option
value="BHO">Bhopal</option>
<option
value="BBI">Bhubaneswar</option>
<option
value="BHJ">Bhuj</option>
<option value="CBD">Car
Nicobar</option>
<option
value="IXC">Chandigarh</option>
<option value="MAA">Chennai
(Madras)</option>
<option
value="CJB">Coimbatore</option>
<option
value="CDP">Cuddapah</option>
<option value="DAE">Daporijo
(Daporizo)</option>
<option
value="DED">Dehradun</option>
<option
value="DIB">Dibrugarh</option>
<option
value="DMU">Dimapur</option>
<option value="DIU">Diu</option>
<option
value="IXY">Gandhidham/Kandla</option>
<option
value="GAY">Gaya</option>
<option value="GOI">Goa</option>
<option
<option
value="VTZ">Visakhapatnam (Vishakhapatnam)</option>

Page 95 of 123

Project Report-Kiosk Management System

<option value="WGC">Warangal
(Warrangal)</option>
</optgroup>
</select>
</td>
</tr>
<td><pre>
<input type="submit" size="200"
align="center"value="Find Buses"/></td>
</pre></tr>
</pre>
</tbody>
</table>
</form>
<%
if(request.getAttribute("busList")!=null)
{
List<bus_detailbean> list =(List<bus_detailbean>)
request.getAttribute("busList");
Iterator<bus_detailbean> it = list.iterator();
if(it.hasNext())
{
%>
<table background="./image/ww1.jpg" border="1">
<thead>
<th>
<tr>
<th>BUS_NO</th>
<th>NO_OF_SEAT</th>
<th>BUS_TYPE</th>
<th>DESCRIPTION</th>
<th>SOURCE</th>
<th>DESTINATION</th>
</th>
</thead>
<tbody>
<%
it = list.iterator();
while(it.hasNext())
{
bus_detailbean bean = it.next();
%>
<tr>
<td><%= bean.getBus_no()%></td>

Page 96 of 123

Project Report-Kiosk Management System

<td><%=bean.getNo_of_seats()%></td>
<td><%=bean.getBus_type()%></td>
<td><%=bean.getDescription()%></td>
<td><%=bean.getSource()%></td>
<td><%=bean.getDestination()%></td>
<td><a href="./buses1.jsp?bus_no=<%= bean.getBus_no()%>"><font
color="white">Book now</font></a></td>
</tr>
<%
}
%>
</font>
</tbody>
</table>
<% }else
{
%>
<font color="red"><b>No Record Found</b></font>
<%
}
}
%>
</div>
</body>
</html>
Bus_detailSevlet.java
Bus_detailDao.java
trainbean.java
//flight.jsp

<%@page import="java.util.Iterator"%>
<%@page import="com.kms.mvc.bean.flight_detailbean"%>
<%@page import="java.util.List"%>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}

Page 97 of 123

Project Report-Kiosk Management System

#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}


#content {position:relative;left:150; z-index:1; padding:10px;}
</style>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title> Airlines</title>
</head>
<body>
<div id="page-background"><img src="./image/airline[1].jpg" width="100%"
height="100%"></div>
<div id="content">
<font color="blue"/>
<font size="5"/>
<table>
<tc>
<td><img src="./image/logo[1].png" width="200" height="200"><td>
<td> <img src="./image/plane1.jpg" width="900" height="200">
</td> <td> <img src="./image/air2.jpg" width="300" height="200">
</td>
</tc></table>
<form method="get" action="./flightSearch">
<table background="./image/ww1.jpg" width="576" height="288"> <tbody>
<pre> <tr><td><h3> <i><u>Book your tickets now... </u></i></h3><td><tr>
</pre> <tr>
<td height="30" width="100">From</td>
<td height="30" width="100">To</td>
</tr>
<tr>
<td height="30" width="100">
<select name="from">
<optgroup label="Top Indian Departure cities">
<option value="BOM">Mumbai
(Bombay)</option>
<option value="delhi">New Delhi
(Delhi)</option>
<option value="MAA">Chennai
(Madras)</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option value="GOI">Goa</option>
<option value="COK">Kochi
(Cochin)</option>

Page 98 of 123

Project Report-Kiosk Management System

<option
value="HYD">Hyderabad</option>
<option value="PNQ">Pune
(Poona)</option>
<option value="CCU">Kolkata
(Calcutta)</option>
<option
value="AMD">Ahmedabad</option>
<option
value="ATQ">Amritsar</option>
<option
value="GAU">Guwahati</option>
<option
value="TRV">Thiruvananthapuram</option>
</optgroup>
<optgroup label="Cities in
Alphabetical Order">
<option
value="IXA">Agartala</option>
<option
value="AGX">Agatti</option>
<option
value="AGR">Agra</option>
<option
value="AMD">Ahmedabad</option>
<option
value="AJL">Aizawl</option>
<option
value="IXD">Allahabad</option>
<option
value="IXV">Along</option>
<option
value="ATQ">Amritsar</option>
<option
value="IXU">Aurangabad</option>
<option
value="IXB">Bagdogra/Siliguri</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option
value="IXG">Belgaum</option>
<option
value="BHU">Bhavnagar</option>
<option
value="BHO">Bhopal</option>

Page 99 of 123

Project Report-Kiosk Management System

<option
value="BBI">Bhubaneswar</option>
<option
value="BHJ">Bhuj</option>
<option value="CBD">Car
Nicobar</option>
<option
value="IXC">Chandigarh</option>
<option value="MAA">Chennai
(Madras)</option>
<option
value="CJB">Coimbatore</option>
<option
value="CDP">Cuddapah</option>
<option value="DAE">Daporijo
(Daporizo)</option>
<option
value="DED">Dehradun</option>
<option
value="DIB">Dibrugarh</option>
<option
value="DMU">Dimapur</option>
<option value="DIU">Diu</option>
<option
value="IXY">Gandhidham/Kandla</option>
<option
value="GAY">Gaya</option>
<option value="GOI">Goa</option>
<option
value="GAU">Guwahati</option>
<option
value="GWL">Gwalior</option>
<option
value="HBX">Hubli</option>
<option
value="HYD">Hyderabad</option>
<option
value="IMF">Imphal</option>
<option
value="IDR">Indore</option>
<option
value="JLR">Jabalpur</option>
<option
value="JAI">Jaipur</option>
<option
value="JSA">Jaisalmer</option>

Page 100 of 123

Project Report-Kiosk Management System

<option
value="IXJ">Jammu</option>
<option
value="JGA">Jamnagar</option>
<option
value="JDH">Jodhpur</option>
<option
value="JRH">Jorhat</option>
<option
value="IXH">Kailashahar</option>
<option
value="KNU">Kanpur</option>
<option
value="IXK">Keshod</option>
<option
value="HJR">Khajuraho</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="KLH">Kolhapur</option>
<option value="CCU">Kolkata
(Calcutta)</option>
<option value="CCJ">Kozhikode
(Calicut)</option>
<option
value="KUU">Kullu/Manali</option>
<option value="IXL">Leh</option>
<option
value="LKO">Lucknow</option>
<option
value="LUH">Ludhiana</option>
<option
value="IXM">Madurai</option>
<option
value="IXE">Mangalore</option>
<option value="BOM">Mumbai
(Bombay)</option>
<option
value="MZU">Muzzafarpur</option>
<option
value="MYQ">Mysore</option>
<option
value="NAG">Nagpur</option>
<option value="DEL">New Delhi
(Delhi)</option>

Page 101 of 123

Project Report-Kiosk Management System

<option value="IXI">North
Lakhimpur</option>
<option value="IXT">Pasighat
(Passighat)</option>
<option
value="PAT">Patna</option>
<option
value="PBD">Porbandar</option>
<option value="IXZ">Port
Blair</option>
<option value="PNQ">Pune
(Poona)</option>
<option
value="BEK">Puttaparthi</option>
<option
value="RPR">Raipur</option>
<option
value="RJA">Rajahmundry</option>
<option
value="RAJ">Rajkot</option>
<option
value="IXR">Ranchi</option>
<option
value="SHL">Shillong</option>
<option
value="IXS">Silchar</option>
<option
value="SSE">Sholapur</option>
<option
value="SXR">Srinagar</option>
<option
value="TEZ">Tezpur</option>
<option value="TEI">Tezu</option>
<option
value="TRV">Thiruvananthapuram</option>
<option value="TRZ">Tiruchirapalli
(Trichy)</option>
<option value="TIR">Tirupati
(Tirupathi)</option>
<option value="TCR">Tuticorin
(Thoothukudi)</option>
<option
value="UDR">Udaipur</option>
<option value="BDQ">Vadodara
(Baroda)</option>

Page 102 of 123

Project Report-Kiosk Management System

<option
value="VNS">Varanasi</option>
<option value="VGA">Vijayawada
(Vijaywada)</option>
<option
value="VTZ">Visakhapatnam (Vishakhapatnam)</option>
<option value="WGC">Warangal
(Warrangal)</option>
</optgroup>
</select></td>
<td height="14" width="100">
<select name="to">
<optgroup label="Top Indian Departure cities">
<option value="mumbai">Mumbai
(Bombay)</option>
<option value="DEL">New Delhi
(Delhi)</option>
<option value="MAA">Chennai
(Madras)</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option value="goa">Goa</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="HYD">Hyderabad</option>
<option value="PNQ">Pune
(Poona)</option>
<option value="CCU">Kolkata
(Calcutta)</option>
<option
value="AMD">Ahmedabad</option>
<option
value="ATQ">Amritsar</option>
<option
value="GAU">Guwahati</option>
<option
value="TRV">Thiruvananthapuram</option>
</optgroup>
<optgroup label="Cities in
Alphabetical Order">
<option
value="IXA">Agartala</option>
<option
value="AGX">Agatti</option>

Page 103 of 123

Project Report-Kiosk Management System

<option
value="AGR">Agra</option>
<option
value="AMD">Ahmedabad</option>
<option
value="AJL">Aizawl</option>
<option
value="IXD">Allahabad</option>
<option
value="IXV">Along</option>
<option
value="ATQ">Amritsar</option>
<option
value="IXU">Aurangabad</option>
<option
value="IXB">Bagdogra/Siliguri</option>
<option value="BLR">Bangaluru
(Bangalore)</option>
<option
value="IXG">Belgaum</option>
<option
value="BHU">Bhavnagar</option>
<option
value="BHO">Bhopal</option>
<option
value="BBI">Bhubaneswar</option>
<option
value="BHJ">Bhuj</option>
<option value="CBD">Car
Nicobar</option>
<option
value="IXC">Chandigarh</option>
<option value="MAA">Chennai
(Madras)</option>
<option
value="CJB">Coimbatore</option>
<option
value="CDP">Cuddapah</option>
<option value="DAE">Daporijo
(Daporizo)</option>
<option
value="DED">Dehradun</option>
<option
value="DIB">Dibrugarh</option>
<option
value="DMU">Dimapur</option>

Page 104 of 123

Project Report-Kiosk Management System

<option value="DIU">Diu</option>
<option
value="IXY">Gandhidham/Kandla</option>
<option
value="GAY">Gaya</option>
<option value="GOI">Goa</option>
<option
value="GAU">Guwahati</option>
<option
value="GWL">Gwalior</option>
<option
value="HBX">Hubli</option>
<option
value="HYD">Hyderabad</option>
<option
value="IMF">Imphal</option>
<option
value="IDR">Indore</option>
<option
value="JLR">Jabalpur</option>
<option
value="JAI">Jaipur</option>
<option
value="JSA">Jaisalmer</option>
<option
value="IXJ">Jammu</option>
<option
value="JGA">Jamnagar</option>
<option
value="JDH">Jodhpur</option>
<option
value="JRH">Jorhat</option>
<option
value="IXH">Kailashahar</option>
<option
value="KNU">Kanpur</option>
<option
value="IXK">Keshod</option>
<option
value="HJR">Khajuraho</option>
<option value="COK">Kochi
(Cochin)</option>
<option
value="KLH">Kolhapur</option>
<option value="CCU">Kolkata
(Calcutta)</option>

Page 105 of 123

Project Report-Kiosk Management System

<option value="CCJ">Kozhikode
(Calicut)</option>
<option
value="KUU">Kullu/Manali</option>
<option value="IXL">Leh</option>
<option
value="LKO">Lucknow</option>
<option
value="LUH">Ludhiana</option>
<option
value="IXM">Madurai</option>
<option
value="IXE">Mangalore</option>
<option value="BOM">Mumbai
(Bombay)</option>
<option
value="MZU">Muzzafarpur</option>
<option
value="MYQ">Mysore</option>
<option
value="NAG">Nagpur</option>
<option value="DEL">New Delhi
(Delhi)</option>
<option value="IXI">North
Lakhimpur</option>
<option value="IXT">Pasighat
(Passighat)</option>
<option
value="PAT">Patna</option>
<option
value="PBD">Porbandar</option>
<option value="IXZ">Port
Blair</option>
<option value="PNQ">Pune
(Poona)</option>
<option
value="BEK">Puttaparthi</option>
<option
value="RPR">Raipur</option>
<option
value="RJA">Rajahmundry</option>
<option
value="RAJ">Rajkot</option>
<option
value="IXR">Ranchi</option>

Page 106 of 123

Project Report-Kiosk Management System

<option
value="SHL">Shillong</option>
<option
value="IXS">Silchar</option>
<option
value="SSE">Sholapur</option>
<option
value="SXR">Srinagar</option>
<option
value="TEZ">Tezpur</option>
<option value="TEI">Tezu</option>
<option
value="TRV">Thiruvananthapuram</option>
<option value="TRZ">Tiruchirapalli
(Trichy)</option>
<option value="TIR">Tirupati
(Tirupathi)</option>
<option value="TCR">Tuticorin
(Thoothukudi)</option>
<option
value="UDR">Udaipur</option>
<option value="BDQ">Vadodara
(Baroda)</option>
<option
value="VNS">Varanasi</option>
<option value="VGA">Vijayawada
(Vijaywada)</option>
<option
value="VTZ">Visakhapatnam (Vishakhapatnam)</option>
<option value="WGC">Warangal
(Warrangal)</option>
</optgroup>
</select>
</td>
</tr>
<tr>
<td><pre>
<input type="submit" value="Find Fights"></pre></td>
</tr>
</tbody>
</table>
</form>
<%
if(request.getAttribute("flightList")!=null)

Page 107 of 123

Project Report-Kiosk Management System

{
List<flight_detailbean> list =(List<flight_detailbean>)
request.getAttribute("flightList");
Iterator<flight_detailbean> it = list.iterator();
if(it.hasNext())
{
%>
<table border="1">
<thead>
<tr>
<th>FLIGHT_NO</th>
<th>SOURCE</th>
<th>DESTINATION</th>
<th>B_SEAT</th>
<th>E_SEAT</th>
<th>B_FARE</th>
<th>E_FARE</th>
</tr>
</thead>
<tbody>
<%
it = list.iterator();
while(it.hasNext())
{
flight_detailbean bean = it.next();
%>
<tr>
<td><%= bean.getFlight_no()%></td>
<td><%=bean.getSource()%></td>
<td><%=bean.getDestination()%></td>
<td><%=bean.getB_seat()%></td>
<td><%=bean.getE_seat()%></td>
<td><%=bean.getB_fare()%></td>
<td><%=bean.getE_fare()%></td>
<td><a href="./flight1.jsp?flight_no=<%= bean.getFlight_no()
%>">view</a></td>
</tr>
<%
}
%>
</tbody>
</table>
<% }else

Page 108 of 123

Project Report-Kiosk Management System

{
%>
<font color="red"><b>No Record Found</b></font>
<%
}
}
%>
</div>
</body>
</html>
//hotel_1.jsp
<%@page import="java.util.Iterator"%>
<%@page import="java.util.List"%>
<%@page import="com.kms.mvc.bean.hotelbean"%>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<html>
<head>
<style type="text/css">
html, body {height:100%; margin:0; padding:0;}
#page-background {position:fixed; top:0; left:0; width:100%; height:100%;}
#content {position:relative; z-index:1; padding:10px;}
</style>
</head>
<title>HOTEL BOOKING</title>
<body>
<div id="page-background"><img src="./image/b4.jpg" width="100%"
height="100%"></div>
<div id="content">
<p align="center"><img src="./image/b7.jpg" height="300" width="1000"></p>
<br>

<form method="get" action="./hotelSearch">


<table align="center">
<tr>
<td><center><h1>Hotel Booking</h1></center></td>
</tr>
<font color="black" size="5" face="times new roman">
<tr>

Page 109 of 123

Project Report-Kiosk Management System

<td width="20%" height="30">First Name</td>


<td width="78%"><input name="fname" type="text" id="fname"
size="50" /></td>
</tr>
<tr>
<td height="30">Last Name</td>
<td><input name="lname" type="text" id="lname" size="50" /></td>
</tr>
<tr>
<td height="30">Address</td>
<td><input name="address" type="text" id="address" size="50"
/></td>
</tr>
<tr>
<td height="30">Nationality</td>
<td><input name="nationality" type="text" id="nationality"
size="50" /></td>
</tr>
<tr>
<td height="30">Country</td>
<td><select name="country" id="country">
<option value="Afghanistan"
>Afghanistan</option>
<option value="Albania" >Albania</option>
<option value="Algeria" >Algeria</option>
<option value="American Samoa" >American
Samoa</option>
<option value="Andorra" >Andorra</option>
<option value="Angola" >Angola</option>
<option value="Anguilla" >Anguilla</option>
<option value="Antarctica" >Antarctica</option>
<option value="Antigua and Barbuda" >Antigua
and Barbuda</option>
<option value="Argentina" >Argentina</option>
<option value="Armenia" >Armenia</option>
<option value="Aruba" >Aruba</option>
<option value="Australia" >Australia</option>
<option value="Austria" >Austria</option>
<option value="Azerbaijan" >Azerbaijan</option>
<option value="Bahamas" >Bahamas</option>
<option value="Bahrain" >Bahrain</option>
<option value="Bangladesh"
>Bangladesh</option>
<option value="Barbados" >Barbados</option>
<option value="Belarus" >Belarus</option>

Page 110 of 123

Project Report-Kiosk Management System

<option value="Belgium" >Belgium</option>


<option value="Belize" >Belize</option>
<option value="Benin" >Benin</option>
<option value="Bermuda" >Bermuda</option>
<option value="Bhutan" >Bhutan</option>
<option value="Bolivia" >Bolivia</option>
<option value="Bosnia and Herzegowina" >Bosnia
and Herzegowina</option>
<option value="Botswana" >Botswana</option>
<option value="Bouvet Island" >Bouvet
Island</option>
<option value="Brazil" >Brazil</option>
<option value="British Indian Ocean Territory"
>British Indian Ocean Territory</option>
<option value="Brunei Darussalam" >Brunei
Darussalam</option>
<option value="Bulgaria" >Bulgaria</option>
<option value="Burkina Faso" >Burkina
Faso</option>
<option value="Burundi" >Burundi</option>
<option value="Cambodia" >Cambodia</option>
<option value="Cameroon" >Cameroon</option>
<option value="Canada" >Canada</option>
<option value="Canary Islands" >Canary
Islands</option>
<option value="Cape Verde" >Cape
Verde</option>
<option value="Cayman Islands" >Cayman
Islands</option>
<option value="Central African Republic" >Central
African Republic</option>
<option value="Chad" >Chad</option>
<option value="Chile" >Chile</option>
<option value="China" >China</option>
<option value="Christmas Island" >Christmas
Island</option>
<option value="Cocos (Keeling) Islands" >Cocos
(Keeling) Islands</option>
<option value="Colombia" >Colombia</option>
<option value="Comoros" >Comoros</option>
<option value="Congo" >Congo</option>
<option value="Cook Islands" >Cook
Islands</option>
<option value="Costa Rica" >Costa Rica</option>
<option value="Cote D'Ivoire" >Cote
D'Ivoire</option>

Page 111 of 123

Project Report-Kiosk Management System

<option value="Croatia" >Croatia</option>


<option value="Cuba" >Cuba</option>
<option value="Cyprus" >Cyprus</option>
<option value="Czech Republic" >Czech
Republic</option>
<option value="Denmark" >Denmark</option>
<option value="Djibouti" >Djibouti</option>
<option value="Dominica" >Dominica</option>
<option value="Dominican Republic" >Dominican
Republic</option>
<option value="East Timor" >East Timor</option>
<option value="East Timor" >East Timor</option>
<option value="Ecuador" >Ecuador</option>
<option value="Egypt" >Egypt</option>
<option value="El Salvador" >El
Salvador</option>
<option value="Equatorial Guinea" >Equatorial
Guinea</option>
<option value="Eritrea" >Eritrea</option>
<option value="Estonia" >Estonia</option>
<option value="Ethiopia" >Ethiopia</option>
<option value="Falkland Islands (Malvinas)"
>Falkland Islands (Malvinas)</option>
<option value="Faroe Islands" >Faroe
Islands</option>
<option value="Fiji" >Fiji</option>
<option value="Finland" >Finland</option>
<option value="France" >France</option>
<option value="France, Metropolitan" >France,
Metropolitan</option>
<option value="French Guiana" >French
Guiana</option>
<option value="French Polynesia" >French
Polynesia</option>
<option value="French Southern Territories"
>French Southern Territories</option>
<option value="Gabon" >Gabon</option>
<option value="Gambia" >Gambia</option>
<option value="Georgia" >Georgia</option>
<option value="Germany" >Germany</option>
<option value="Ghana" >Ghana</option>
<option value="Gibraltar" >Gibraltar</option>
<option value="Greece" >Greece</option>
<option value="Greenland" >Greenland</option>
<option value="Grenada" >Grenada</option>

Page 112 of 123

Project Report-Kiosk Management System

<option value="Guadeloupe"
>Guadeloupe</option>
<option value="Guam" >Guam</option>
<option value="Guatemala" >Guatemala</option>
<option value="Guinea" >Guinea</option>
<option value="Guinea-bissau" >Guineabissau</option>
<option value="Guyana" >Guyana</option>
<option value="Haiti" >Haiti</option>
<option value="Heard and Mc Donald Islands"
>Heard and Mc Donald Islands</option>
<option value="Honduras" >Honduras</option>
<option value="Hong Kong" >Hong
Kong</option>
<option value="Hungary" >Hungary</option>
<option value="Iceland" >Iceland</option>
<option value="India" >India</option>
<option value="Indonesia" >Indonesia</option>
<option value="Iran (Islamic Republic of)" >Iran
(Islamic Republic of)</option>
<option value="Iraq" >Iraq</option>
<option value="Ireland" >Ireland</option>
<option value="Israel" >Israel</option>
<option value="Italy" >Italy</option>
<option value="Jamaica" >Jamaica</option>
<option value="Japan" >Japan</option>
<option value="Jersey" >Jersey</option>
<option value="Jordan" >Jordan</option>
<option value="Kazakhstan"
>Kazakhstan</option>
<option value="Kenya" >Kenya</option>
<option value="Kiribati" >Kiribati</option>
<option value="Korea, Democratic People's
Republic of" >Korea, Democratic People's Republic of</option>
<option value="Korea, Republic of" >Korea,
Republic of</option>
<option value="Kuwait" >Kuwait</option>
<option value="Kyrgyzstan" >Kyrgyzstan</option>
<option value="Lao People's Democratic Republic"
>Lao People's Democratic Republic</option>
<option value="Latvia" >Latvia</option>
<option value="Lebanon" >Lebanon</option>
<option value="Lesotho" >Lesotho</option>
<option value="Liberia" >Liberia</option>
<option value="Libyan Arab Jamahiriya" >Libyan
Arab Jamahiriya</option>

Page 113 of 123

Project Report-Kiosk Management System

<option value="Liechtenstein"
>Liechtenstein</option>
<option value="Lithuania" >Lithuania</option>
<option value="Luxembourg"
>Luxembourg</option>
<option value="Macau" >Macau</option>
<option value="Macedonia, The Former Yugoslav
Republic of" >Macedonia, The Former Yugoslav Republic of</option>
<option value="Madagascar"
>Madagascar</option>
<option value="Malawi" >Malawi</option>
<option value="Malaysia" >Malaysia</option>
<option value="Maldives" >Maldives</option>
<option value="Mali" >Mali</option>
<option value="Malta" >Malta</option>
<option value="Marshall Islands" >Marshall
Islands</option>
<option value="Martinique" >Martinique</option>
<option value="Mauritania" >Mauritania</option>
<option value="Mauritius" >Mauritius</option>
<option value="Mayotte" >Mayotte</option>
<option value="Mexico" >Mexico</option>
<option value="Micronesia, Federated States of"
>Micronesia, Federated States of</option>
<option value="Moldova, Republic of" >Moldova,
Republic of</option>
<option value="Monaco" >Monaco</option>
<option value="Mongolia" >Mongolia</option>
<option value="Montserrat" >Montserrat</option>
<option value="Morocco" >Morocco</option>
<option value="Mozambique"
>Mozambique</option>
<option value="Myanmar" >Myanmar</option>
<option value="Namibia" >Namibia</option>
<option value="Nauru" >Nauru</option>
<option value="Nepal"
selected="selected">Nepal</option>
<option value="Netherlands"
>Netherlands</option>
<option value="Netherlands Antilles" >Netherlands
Antilles</option>
<option value="New Caledonia" >New
Caledonia</option>
<option value="New Zealand" >New
Zealand</option>
<option value="Nicaragua" >Nicaragua</option>

Page 114 of 123

Project Report-Kiosk Management System

<option value="Niger" >Niger</option>


<option value="Nigeria" >Nigeria</option>
<option value="Niue" >Niue</option>
<option value="Norfolk Island" >Norfolk
Island</option>
<option value="Northern Mariana Islands"
>Northern Mariana Islands</option>
<option value="Norway" >Norway</option>
<option value="Oman" >Oman</option>
<option value="Pakistan" >Pakistan</option>
<option value="Palau" >Palau</option>
<option value="Panama" >Panama</option>
<option value="Papua New Guinea" >Papua New
Guinea</option>
<option value="Paraguay" >Paraguay</option>
<option value="Peru" >Peru</option>
<option value="Philippines" >Philippines</option>
<option value="Pitcairn" >Pitcairn</option>
<option value="Poland" >Poland</option>
<option value="Portugal" >Portugal</option>
<option value="Puerto Rico" >Puerto
Rico</option>
<option value="Qatar" >Qatar</option>
<option value="Reunion" >Reunion</option>
<option value="Romania" >Romania</option>
<option value="Russian Federation" >Russian
Federation</option>
<option value="Rwanda" >Rwanda</option>
<option value="Saint Kitts and Nevis" >Saint Kitts
and Nevis</option>
<option value="Saint Lucia" >Saint Lucia</option>
<option value="Saint Vincent and the Grenadines"
>Saint Vincent and the Grenadines</option>
<option value="Samoa" >Samoa</option>
<option value="San Marino" >San
Marino</option>
<option value="Sao Tome and Principe" >Sao
Tome and Principe</option>
<option value="Saudi Arabia" >Saudi
Arabia</option>
<option value="Senegal" >Senegal</option>
<option value="Seychelles" >Seychelles</option>
<option value="Sierra Leone" >Sierra
Leone</option>
<option value="Singapore" >Singapore</option>

Page 115 of 123

Project Report-Kiosk Management System

<option value="Slovakia (Slovak Republic)"


>Slovakia (Slovak Republic)</option>
<option value="Slovenia" >Slovenia</option>
<option value="Solomon Islands" >Solomon
Islands</option>
<option value="Somalia" >Somalia</option>
<option value="South Africa" >South
Africa</option>
<option value="South Georgia and the South
Sandwich Islands" >South Georgia and the South Sandwich Islands</option>
<option value="Spain" >Spain</option>
<option value="Sri Lanka" >Sri Lanka</option>
<option value="St. Barthelemy" >St.
Barthelemy</option>
<option value="St. Eustatius" >St.
Eustatius</option>
<option value="St. Helena" >St. Helena</option>
<option value="St. Pierre and Miquelon" >St.
Pierre and Miquelon</option>
<option value="Sudan" >Sudan</option>
<option value="Suriname" >Suriname</option>
<option value="Svalbard and Jan Mayen Islands"
>Svalbard and Jan Mayen Islands</option>
<option value="Swaziland" >Swaziland</option>
<option value="Sweden" >Sweden</option>
<option value="Switzerland"
>Switzerland</option>
<option value="Syrian Arab Republic" >Syrian
Arab Republic</option>
<option value="Taiwan" >Taiwan</option>
<option value="Tajikistan" >Tajikistan</option>
<option value="Tanzania, United Republic of"
>Tanzania, United Republic of</option>
<option value="Thailand" >Thailand</option>
<option value="The Democratic Republic of
Congo" >The Democratic Republic of Congo</option>
<option value="Togo" >Togo</option>
<option value="Tokelau" >Tokelau</option>
<option value="Tonga" >Tonga</option>
<option value="Trinidad and Tobago" >Trinidad
and Tobago</option>
<option value="Tunisia" >Tunisia</option>
<option value="Turkey" >Turkey</option>
<option value="Turkmenistan"
>Turkmenistan</option>

Page 116 of 123

Project Report-Kiosk Management System

<option value="Turks and Caicos Islands" >Turks


and Caicos Islands</option>
<option value="Tuvalu" >Tuvalu</option>
<option value="Uganda" >Uganda</option>
<option value="Ukraine" >Ukraine</option>
<option value="United Arab Emirates" >United
Arab Emirates</option>
<option value="United Kingdom" >United
Kingdom</option>
<option value="United States" >United
States</option>
<option value="United States Minor Outlying
Islands" >United States Minor Outlying Islands</option>
<option value="Uruguay" >Uruguay</option>
<option value="Uzbekistan" >Uzbekistan</option>
<option value="Vanuatu" >Vanuatu</option>
<option value="Vatican City State (Holy See)"
>Vatican City State (Holy See)</option>
<option value="Venezuela" >Venezuela</option>
<option value="Viet Nam" >Viet Nam</option>
<option value="Virgin Islands (British)" >Virgin
Islands (British)</option>
<option value="Virgin Islands (U.S.)" >Virgin
Islands (U.S.)</option>
<option value="Wallis and Futuna Islands" >Wallis
and Futuna Islands</option>
<option value="Western Sahara" >Western
Sahara</option>
<option value="Yemen" >Yemen</option>
<option value="Yugoslavia" >Yugoslavia</option>
<option value="Zambia" >Zambia</option>
<option value="Zimbabwe" >Zimbabwe</option>
</select></td>
</tr>
<tr>
<td height="30">Telephone</td>
<td><table width="100%" border="0" cellspacing="0"
cellpadding="0">
<tr>
<td width="8%">Home</td>
<td width="25%"><input name="home" type="text" id="home"
size="15" /></td>
<td width="8%">Office</td>
<td width="59%"><input name="office" type="text" id="office"
size="15" /></td>

Page 117 of 123

Project Report-Kiosk Management System

</tr>
</table></td>
</tr>
<tr>
<td height="30">Mobile (Optional)</td>
<td><input name="mobile" type="text" id="mobile" size="50" /></td>
</tr>
<tr>
<td height="30">E-mail</td>
<td><input name="email" type="text" id="email" size="50" /></td>
</tr>
<tr>
<td height="30">Category Of Hotel</td>
<td><input name="category[]" type="checkbox" value="5 Star" />
5 Star
<input name="category[]" type="checkbox" value="4 Star" />
4 Star
<input name="category[]" type="checkbox" value="3 Star" />
3 Star
<input name="category[]" type="checkbox" value="2 Star" />
2 Star
<input name="category[]" type="checkbox" value="Standard" />
Standard
<input name="category[]" type="checkbox" value="Budget" />
Budget
</td>
</tr>
<tr>
<td height="30">Category Of Room</td>
<td><input name="room[]" type="checkbox" value="Normal" />
Normal
<input name="room[]" type="checkbox" value="Standard" />
Standard
<input name="room[]" type="checkbox" value="Deluxe" />
Deluxe
<input name="room[]" type="checkbox" value="Suite" />
Suite </td>
</tr>
<tr>
<td height="30">No. of Room Required</td>
<td>Single
<select name="single" id="single">
<option value="0">0</option>
<option value="1">1</option>
<option value="2">2</option>

Page 118 of 123

Project Report-Kiosk Management System

<option value="3">3</option>
<option value="4">4</option>
<option value="5">5</option>
<option value="6">6</option>
<option value="7">7</option>
<option value="8">8</option>
<option value="9">9</option>
<option value="10">10</option>
<option value="11">11</option>
<option value="12">12</option>
</select>
Double
<select name="double" id="double">
<option value="0">0</option>
<option value="1">1</option>
<option value="2">2</option>
<option value="3">3</option>
<option value="4">4</option>
<option value="5">5</option>
<option value="6">6</option>
<option value="7">7</option>
<option value="8">8</option>
<option value="9">9</option>
<option value="10">10</option>
<option value="11">11</option>
<option value="12">12</option>
</select>
Twin Double
<select name="twin_double" id="twin_double">
<option value="0">0</option>
<option value="1">1</option>
<option value="2">2</option>
<option value="3">3</option>
<option value="4">4</option>
<option value="5">5</option>
<option value="6">6</option>
<option value="7">7</option>
<option value="8">8</option>
<option value="9">9</option>
<option value="10">10</option>
<option value="11">11</option>
<option value="12">12</option>
</select>
Triple
<select name="triple" id="triple">
<option value="0">0</option>

Page 119 of 123

Project Report-Kiosk Management System

<option value="1">1</option>
<option value="2">2</option>
<option value="3">3</option>
<option value="4">4</option>
<option value="5">5</option>
<option value="6">6</option>
<option value="7">7</option>
<option value="8">8</option>
<option value="9">9</option>
<option value="10">10</option>
<option value="11">11</option>
<option value="12">12</option>
</select></td>
</tr>
<tr>
<td height="30">Check In Date</td>
<td><input name="checkin" type="text" id="checkin" size="50"
/></td>
</tr>
<tr>
<td height="30">Check Out Date</td>
<td><input name="checkout" type="text" id="checkout" size="50"
/></td>
</tr>
</font>
<tr>
<td><input type="submit" value="Find Hotels"</td>
</tr>
</table>
</form></div>
<%
if(request.getAttribute("hotelList")!=null)
{
List<hotelbean> list =(List<hotelbean>)
request.getAttribute("hotelList");
Iterator<hotelbean> it = list.iterator();
if(it.hasNext())
{
%>
<table border="1">
<thead>
<tr>

Page 120 of 123

Project Report-Kiosk Management System

<th>HOTEL_ID</th>
<th>HOTEL_NAME</th>
<th>ADDRESS</th>
<th>CITY</th>
<th>COUNTRY</th>
<th>PIN_NO</th>
<th>CONTACT_NO</th>
<th>EMAIL_ID</th>
</tr>
</thead>
<tbody>
<%
it = list.iterator();
while(it.hasNext())
{
hotelbean bean = it.next();
%>
<tr>
<td><%= bean.getHotel_id()%></td>
<td><%=bean.getHotel_name()%></td>
<td><%=bean.getAddress()%></td>
<td><%=bean.getCity()%></td>
<td><%=bean.getCountry()%></td>
<td><%=bean.getPin_no()%></td>
<td><%=bean.getContact_no()%></td>
<td><%=bean.getEmail_id()%></td>
<td><a href="./viewSheat?hotel_id=<%= bean.getHotel_id()
%>">view</a></td>
</tr>
<%
}
%>
</tbody>
</table>
<% }else
{
%>
<font color="red"><b>No Record Found</b></font>
<%
}
}
%>
</body>
</html>

Page 121 of 123

Project Report-Kiosk Management System

//hotelDao.java
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package com.kms.mvc.DAO;
import com.kms.mvc.bean.hotelbean;
import java.sql.*;
import java.util.*;
/**
*
* @author Shikha
*/
public class hotelDao {
public List<hotelbean> getHotelInfo(hotelbean bean) throws Exception
{
Connection con = connectionDao.getConnection();
PreparedStatement ps = con.prepareCall("select * from hr.hotel where city=?");
ps.setString(1, bean.getCity());
ResultSet rs = ps.executeQuery();
List<hotelbean> list = new ArrayList<hotelbean>();
while(rs.next())
{
bean = new hotelbean();
bean.setHotel_id(rs.getString(1));
bean.setHotel_name(rs.getString(2));
bean.setAddress(rs.getString(3));
bean.setCountry(rs.getString(4));
bean.setCity(rs.getString(5));
bean.setPin_no(String.valueOf(rs.getInt(6)));
bean.setContact_no(String.valueOf(rs.getLong(7)));
bean.setEmail_id(rs.getString(8));
list.add(bean);
}
con.close();
return list;
}

Page 122 of 123

Project Report-Kiosk Management System

public int addhotel(hotelbean bean)throws Exception


{
Connection conn = connectionDao.getConnection();
CallableStatement cs=conn.prepareCall("{call prchotel(?,?,?,?,?,?,?,?)}");
cs.setString(1,bean.getHotel_id());
cs.setString(2,bean.getHotel_name());
cs.setString(3,bean.getAddress());
cs.setString(4,bean.getCity());
cs.setString(5,bean.getCountry());
cs.setString(6,bean.getPin_no());
cs.setString(7,bean.getContact_no());
cs.setString(8,bean.getEmail_id());
return cs.executeUpdate();
}}
//hotelSearch.java
package com.kms.mvc.controller;
import java.util.List;
import com.kms.mvc.DAO.hotelDao;
import com.kms.mvc.bean.hotelbean;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class hotelSearch extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
try {
hotelbean bean = new hotelbean();
bean.setCity(request.getParameter("city"));
hotelDao dao = new hotelDao();
List<hotelbean> list = dao.getHotelInfo(bean);
request.setAttribute("hotelList", list);
request.getRequestDispatcher("./hotels_1.jsp").forward(request,response);
}catch(Exception ex){

Page 123 of 123

Project Report-Kiosk Management System

System.out.println(ex);
}
finally {
out.close();
}
}
}
//hotelbean.java
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package com.kms.mvc.bean;
/**
*
* @author Shikha
*/
public class hotelbean {
private String hotel_id;
private String hotel_name;
private String address;
private String city;
private String country;
private String pin_no;
private String contact_no;
private String email_id;
public hotelbean() {
}
public String getAddress() {
return address;
}
public void setAddress(String address) {
this.address = address;
}
public String getCity() {

Page 124 of 123

Project Report-Kiosk Management System

return city;
}
public void setCity(String city) {
this.city = city;
}
public String getContact_no() {
return contact_no;
}
public void setContact_no(String contact_no) {
this.contact_no = contact_no;
}
public String getCountry() {
return country;
}
public void setCountry(String country) {
this.country = country;
}
public String getEmail_id() {
return email_id;
}
public void setEmail_id(String email_id) {
this.email_id = email_id;
}
public String getHotel_id() {
return hotel_id;
}
public void setHotel_id(String hotel_id) {
this.hotel_id = hotel_id;
}
public String getHotel_name() {
return hotel_name;
}
public void setHotel_name(String hotel_name) {
this.hotel_name = hotel_name;
}

Page 125 of 123

Project Report-Kiosk Management System

public String getPin_no() {


return pin_no;
}
public void setPin_no(String pin_no) {
this.pin_no = pin_no;
}
}

10. Output
Home.jsp

flights.jsp
Page 126 of 123

Project Report-Kiosk Management System

hotels_1.jsp

trains.jsp

Page 127 of 123

Project Report-Kiosk Management System

buses.jsp

Page 128 of 123

Project Report-Kiosk Management System

admin.jsp

adminbus.jsp

// gallery

Page 129 of 123

Project Report-Kiosk Management System

11.Glossary
JSP: JSP pages are Java Server Pages that compile dynamically into servlets. A JSP is a
text-based document that describes how to process a request to create a response JSP
makes it easier to author pages "by hand" JSP tags for invoking JavaBeans TM
components.
Servlets: Servlet are small programs that execute on the server side of a Web
connection. Just as applets dynamically extend the functionality of a Web browser,
servlets dynamically extend the functionality of a Web server.
HTML :Hypertext used to structure content on a website. Although the HTML
certification contains the means to significantly impact the appearance of the page,
HTML should be used exclusively for structure with CSS used to format the page.
JavaScript: JavaScript is used here for the validations and making project more secure.
it allows to make the dynamic web pages.
CSS: CSS stands for Cascading Style Sheets. This is a document format. This provides
a set of style rules which can be incorporated in a XHTML or HTML document.

12. Bibliography
Bibliography or References must be included in the report according to the format given
in the following examples. References should be cited properly inside the text of the
report

Page 130 of 123

Project Report-Kiosk Management System

1. BOOK
108AdvancedJava
Head First java
Software Engineering by Pressman (6th Edition)
Java 2Complete Reference(5th Ed 2002)
2. REFERENCES
www.yahoo.com
http://en.wikipedia.org/wiki/
www.google.com
http://developers.sun.com/solaris/articles/javapps.html
www.oracle.com/applications/projects/intro.html

Page 131 of 123

Project Report-Kiosk Management System

5 Conclusion

Creation of Various Pages regarding Services provided by Administrator as


Railways, Roadways, Airlines and Hotel Reservation
Creation of Users (Administrator, Visitor, Authorized User)
Creation of Databases Relevant to the Application
Design of Dynamic Search Engine of the application to search for the
relevant services on the basis of inputs provided by User.

Kiosk Management System will provide various types of information to the visitor
such as information regarding roadways, railways, airlines and hotel reservation,
contact information, etc.

6 Checklist
This checklist is to be attached as the last page of the report.
This checklist is to be duly completed by the student and verified by the
Supervisor, Project Coordinator and HOD

1.

Is the report properly hard bound?

Yes / No

2.

Is the Cover page (on hard bound cover) in proper format?

Yes / No

3.

Is the Title page (Inner cover page) in proper format?

Yes / No

4.

(a) Is the Certificate from the Supervisor in proper format?

Yes / No

(b) Has it been signed by the Supervisor?

Yes / No

(a)

Yes / No

5.

Is the Acknowledgement from the Student in proper

format?
(b) Has it been signed by the Student?
7.

Does the Table of Contents include page numbers?

Yes / No

(i).

Yes / No

Are the Pages numbered properly?

Page 132 of 123

Project Report-Kiosk Management System

8.

(ii).

Are the Figures numbered properly?

Yes / No

(iii).

Are the Tables numbered properly?

Yes / No

(iv).

Are the Captions for the Figures and Tables proper?

Yes / No

(v).

Are the Appendices numbered properly?

Yes / No

Is the conclusion of the Report based on discussion of the

Yes / No

work?
9.

10.

Are References or Bibliography given in the Report?

Yes / No

Have the References been cited inside the text of the Report?

Yes / No

Is the citation of References in proper format?

Yes / No

A Compact Disk (CD) containing the softcopy of the Final


Report (preferably in PDF format) and a Final Project
Presentation in MS power point only (made to the Supervisor /
Examiner has been placed in a protective jacket securely
fastened to the inner back cover of the Final Report. Write the
name and Roll No on the CD.

Yes / No

Declaration by Student
I certify that I have properly verified all the items in the checklist
and ensure that the report is in proper format as specified in the
course handout.
Name:
Place:
Date:
Signature of the Student:

Verification by Supervisor

Page 133 of 123

Project Report-Kiosk Management System

I have duly verified all the items in the checklist and ensured that the
report is in proper format.
Name:
Place:
Date:
Signature of the Supervisor:

Verification by Project Coordinator


I have duly verified all the items in the checklist and ensured that the
report is in proper format.
Name:
Place:
Date:
Signature of the Project Coordinator:

Verification by Head of Department (HOD)


I have duly verified all the items in the checklist and ensured that the
report is in proper format.
Name:
Place:
Date:
Signature of the HOD:

Page 134 of 123

You might also like