Karnatak Law Society’s

GOGTE INSTITUTE OF TECHNOLOGY

Udyambag Belagavi -590008 Karnataka,
India.

A Course Project Report on

“Travel and Hotel Booking System”

Submitted for the requirements of 4th semester B.E. in ISE for

“Database Management System (18IS43)”

Submitted by

NAME USN
1)Pratyush Prakash 2GI19IS038

2)Prashant Badiger 2GI19IS035

3)Prajwal Jainkeri 2GI19IS033

Under the guidance of

Prof. Sudhindra Deshpande

Associative Professor

Academic Year 2020-2021 (Even semester)

1|Page
 Karnataka Law Society’s
GOGTE INSTITUTE OF TECHNOLOGY
Udyambag Belagavi -590008 Karnataka,
India.

Department of Information Science and Engineering

Certificate
This is to certify that the Course Project work titled “Travel And Hotel Booking System”carried
out by Pratyush Prakash, Prashant Badiger, Prajwal Jainkeri bearing USNs:
2GI19IS038, 2GI19IS035,2GI19IS033 is submitted in partial fulfilment of the requirements
for 4th semester B.E. in INFORMATION SCIENCE AND ENGINEERING, Visvesvaraya
Technological University, Belagavi. It is certified that all corrections/ suggestions indicated
have been incorporated in the report. The course project report has been approved as it
satisfies the academic requirements prescribed for the said degree.

Date: Signature of Guide

Place: Belagavi Prof. Sudhindra Deshpande

Associate Professor

KLS Gogte Institute of Technology, Belagavi

Name of the Examiners Signature of the Examiners

1.___________________ 1.____________________

2.____________________ 2.____________________

Marks allocation:

2|Page
Batch No.: 14
Seminar Title: Marks USN
Travel and hotel Range 2GI19IS038 2GI19IS035 2GI19IS033
Booking System

Abstract (PO2) 0-2

Application of the
topic to the course 0-3
(PO2)
Literature survey
and its findings 0-4
(PO2)
Methodology,
Results and
0-6
Conclusion
(PO1, PO3, PO4)
Report and Oral
presentation skill 0-5
(PO9, PO10)
Total 20

Table of Contents:

1. Introduction:........................................................................................................2
2. Literature survey:.................................................................................................5
3. Database design:..................................................................................................6
4. Database design:..................................................................................................8
ER-MODEL:.........................................................................................................9
Relational model.................................................................................................11
ER-Relational Mapping......................................................................................13
5. Schema Diagram:...............................................................................................16

3|Page
 4. Normalization:...................................................................................................17
6. Table Creations..................................................................................................22
7. Populating Tables...............................................Error! Bookmark not defined.
8. User Interface Designs.......................................Error! Bookmark not defined.
9. SQL Queries.......................................................Error! Bookmark not defined.
10. Conclusions......................................................................................................35
11. References........................................................................................................35

Travel and Hotel Booking System :

1. Introduction:
A Database Management System (DBMS) is a software application that is used to
create, access, maintain, and manage databases. We can install it like any other application
and use SQL for all the operations we intend to perform on databases. A DBMS accepts the
incoming data either from an application or from a user who is manually entering it.

• It doesn’t matter if it is a large or small DBMS; with the help of it, we can store and
retrieve data and make changes whenever we want.
• Some commands are predefined in DBMS and these commands can be used to
manipulate the database. Also, these commands are the interface between the database
and the end-users to establish communication.

4|Page
Characteristics of DBMS;

• A DBMS provides security and removes redundancy.

• It supports multi-user environment that allow different users to view.
• The DBMS follows the ACID concept (atomicity, consistency, isolation and durability).
• It supports multiple views of the same data.

2. Literature survey:
The project, Hotel Management System is a web-based application that allows the
hotel manager to handle all hotel activities online. Interactive GUI and the ability to
manage various hotel bookings and rooms make this system very flexible and
convenient. The hotel manager is a very busy person and does not have the time to
sit and manage the entire activities manually on paper. This application gives him
the power and flexibility to manage the entire system from a single online system.
Hotel management project provides room booking, staff management and other
necessary hotel management features. The system allows the manager to post
available rooms in the system. Customers can view and book room online. Admin
has the power of either approving or disapproving the customer’s booking request.
Other hotel services can also be viewed by the customers and can book them too.
The system is hence useful for both customers and managers to portable manage the
hotel activities.

Advantages

 Sometime it happens that the rooms get booked soon when one visits the place
therefore user can make advance booking using this system.
 It saves user time in searching a room.
 The system is useful as it calculates an exact cost of rooms for requested number
of days.
 It saves organization resources and expenses.
 This system is effective and saves time and cost of users.

Disadvantages

5|Page
  The booking process usually requires a customer identity, which the system
cannot detect.
 It requires a reliable internet connection.

Travel Reservation Software is online Travel Booking Software that configures travel data for hotels,
flights, package, tour, and car-rental services in Travel Reservation System to provide flights, hotels,
tour booking for customers.

Travel Reservation Software provides inventory and rate in real-time data to customer. Also it allow to
book hotels in different geographical locations.

Technoheaven design, create and deliver the customized Travel Reservation Software for travel agent
which give adaptable reservation and inventory management for flights, hotels, cars in real time.

Travel Reservation Software also offer quick supplier connectivity to integrate global hotel, flight,
tour, package and transfer inventory in travel booking engine/travel portal of travel agent with
advanced functionality of GDS API Integration and Travel API Integration using Flight API, Hotel
API, Travel API, Transfer API to build successful Online Travel Reservation Software System for
travel website.

Travel Itinerary Creation Software Features:

 Itinerary Creation
 Dynamic Packaging (flight, hotel, tour, Transfer in one package)
 Flight Quotation
 Hotel Quotation
 Tour Quotation
 Activity Quotation
 Manage online booking
 Multilanguage and Multi-Currency.
 User-friendly
 Mobile-friendly Design

3. Database design:
The Data Model is defined as an abstract model that organizes data description, data
semantics, and consistency constraints of data. The data model emphasizes on what data is
needed and how it should be organized instead of what operations will be performed on data.
Data Model is like an architect's building plan, which helps to build conceptual models and
set a relationship between data items.

The two types of data modelling techniques are;

1. Entity relationship(E-R) Model

2. UML (Unified Modelling Language)

Types of Data Models: There are mainly three different types of data models: conceptual
data models, logical data models, and physical data models, and each one has a specific

6|Page
purpose. The data models are used to represent the data and how it is stored in the database
and to set the relationship between data items.

1. Conceptual Data Model: This Data Model defines WHAT the system contains. This
model is typically created by Business stakeholders and Data Architects. The purpose
is to organize, scope and define business concepts and rules.
2. Logical Data Model: Defines HOW the system should be implemented regardless of
the DBMS. This model is typically created by Data Architects and Business Analysts.
The purpose is to developed technical map of rules and data structures.
3. Physical Data Model: This Data Model describes HOW the system will be
implemented using a specific DBMS system. This model is typically created by DBA
and developers. The purpose is actual implementation of the database.

Advantages of data models:

• The main goal of a designing data model is to make certain that data objects offered by
the functional team are represented accurately.
• The data model should be detailed enough to be used for building the physical
database.
• The information in the data model can be used for defining the relationship between
tables, primary and foreign keys, and stored procedures.
• Data Model helps business to communicate the within and across organizations.
• Data model helps to documents data mappings in ETL process
• Help to recognize correct sources of data to populate the model.

7|Page
Disadvantages of data model: • To develop Data model, one should know

physical data stored characteristics.

• This is a navigational system produces complex application development,

management. Thus, it requires a knowledge of the biographical truth.
• Even smaller change made in structure require modification in the entire application.
• There is no set data manipulation language in DBMS.

4. Database design:
The goals of database design are multiple:
I. Satisfy the information content requirements of the specified users and applications.
II. Provide a natural and easy-to-understand structuring of the information
III. Support processing requirements and any performance objectives, such as response
time, processing time, and storage space.
These goals are very hard to accomplish and measure and they involve an inherent trade-off:
if one attempts to achieve more naturalness and understandability of the model, it may be at
the cost of performance. The problem is aggravated because the database design process
often begins with informal and incomplete requirements. In contrast, the result of the design
activity is a rigidly defined database schema that cannot easily be modified once the database
is implemented. We can identify six main phases of the overall database design and
implementation process:
Steps for database design and implementation:

1. Requirement’s collection and analysis.

2. Conceptual database design.
3. Choice of a DBMS.
4. Data model mapping (also called logical database design).
5. Physical database design.
6. Database system implementation and tuning.
The design process consists of two parallel activities, as illustrated in Figure 10.1. The
first activity involves the design of the data content, structure, and constraints of the database;
the second relates to the design of database applications. To keep the figure simple, we have
avoided showing most of the interactions between these sides, but the two activities are
closely intertwined. For example, by analysing data-base applications, we can identify data
items that will be stored in the database. In addition, the physical database design phase,
during which we choose the storage structures and access paths of database files, depends on
the applications that will use these files for querying and updating. On the other hand, we
usually specify the design of database applications by referring to the database schema
constructs, which are specified during the first activity. Clearly, these two activities strongly
influence one another. Traditionally, database design methodologies have primarily focused
on the first of these activities whereas software design has focused on the second; this may be
called datadriven versus process-driven design. It now is rec-organized by database designers

8|Page
and software engineers that the two activities should proceed hand-in-hand, and design tools
are increasingly combining them.
ER-MODEL:
• ER model stands for an Entity-Relationship model. It is a high-level data model. This
model is used to define the data elements and relationship for a specified system.
• It develops a conceptual design for the database. It also develops a very simple and
easy to design view of data.
• In ER modelling, the database structure is portrayed as a diagram called an
entityrelationship diagram.

1. Entity: An entity may be any object, class, person or place. In the ER diagram, an
entity
can be represented as rectangles.
Weak entity: An entity that depends on another entity called a weak entity.
The weak entity doesn't contain any key attribute of its own. The weak entity
is represented by a double rectangle
2. Attribute: The attribute is used to describe the property of an entity. Eclipse is used
to represent an attribute.

9|Page
 a. Key attribute: The key attribute is used to represent the main characteristics of
an entity. It represents a primary key. The key attribute is represented by an
ellipse with the text underlined
b. Composite attribute: An attribute that composed of many other attributes is
known as a composite attribute. The composite attribute is represented by an
ellipse, and those ellipses are connected with an ellipse.
c. Multivalued attribute: An attribute can have more than one value. These
attributes are known as a multivalued attribute. The double oval is used to
represent multivalued attribute.
d. Derived attribute: An attribute that can be derived from another attribute is
known as a derived attribute. It can be represented by a dashed ellipse.
3. Relationship: A relationship is used to describe the relation between entities.
Diamond or rhombus is used to represent the relationship.
a. One-to-one relation: When only one instance of an entity is associated with the
relationship, then it is known as one-to-one relationship.
b. One-to-many relation: When only one instance of the entity on the left, and
more than one instance of an entity on the right associates with the
relationship then this is known as a one-to-many relationship.
c. Many-to-one relation: When more than one instance of the entity on the left,
and only one instance of an entity on the right associates with the relationship
then it is known as a many-to-one relationship
d. Many-to-many relation: When more than one instance of the entity on the left,
and more than one instance of an entity on the right associates with the
relationship then it is known as a many-to-many relationship.

10 | P a g e
ER diagram:

Relational model

Relational Model (RM) represents the database as a collection of relations. A relation

is nothing but a table of values. Every row in the table represents a collection of related data
values. These rows in the table denote a real-world entity or relationship. The table name and
column names are helpful to interpret the meaning of values in each row. The data are
represented as a set of relations. In the relational model, data are stored as tables. However,
the physical storage of the data is independent of the way the data are logically organized.
Entity Types of Entity Attributes Key attributes Primary Key

Admin Strong A_ID, password, A_ID A_ID

name
Travel agency Strong T_ID, name, T_ID T_ID
address, cell
Tourist Place Strong trs_ID, trs_name, trs_ID trs_ID
loc
Customer Strong C_ID, cell, C_ID C_ID
c_name, age
,address
Bill Strong B_ID, B_date, B_ID B_ID
amount

11 | P a g e
 Hotel Strong H_ID, name, H_ID H_ID
address

Relational model concepts:

1. Attribute: Each column in a Table. Attributes are the properties which define a
relation.
2. Tables – In the Relational model the, relations are saved in the table format. It is
stored along with its entities. A table has two properties rows and columns. Rows
represent records and columns represent attributes.
3. Tuple – It is nothing but a single row of a table, which contains a single record.
4. Relation Schema: A relation schema represents the name of the relation with its
attributes.
5. Degree: The total number of attributes which in the relation is called the degree of the
relation.
6. Cardinality: Total number of rows present in the Table.
7. Column: The column represents the set of values for a specific attribute.
8. Relation instance – Relation instance is a finite set of tuples in the RDBMS system.
Relation instances never have duplicate tuples.
9. Relation key - Every row has one, two or multiple attributes, which is called relation
key.
10. Attribute domain – Every attribute has some pre-defined value and scope which is
known as attribute domain

Relationship Entities Cardinality Participation

involved Ratio
Admin manages Admin and 1:N One Admin can have many
customer Branch customer but one customer
can not belong to many
Admin, so the relationship
between Admin and
customer is one to many
relationship.

12 | P a g e
 Admin manages Branch and 1:1 One admin manages one
travel agency Account travel agency also one travel
agency is managed by one
admin , so the relationship
between Admin and Travel
agency is one to one.

Customers pay Bill Customer and 1:N One customer can pay many
Bill bill , one bill cannot be paid
by many customer , so the
relation between customer
and bill is one to many.

Hotel has Bill Hotel and Bill 1:N One hotel can have many bill
but one bill cannot have
many hotel , so the
relationship between hotel
and bill is one to many .

Travel agency Travel agency M:N Many travel agency can

books Hotel and hotel books many hotel so the
relationship between Travel
Agency and Hotel is many to
many.
Travel Agency visits Travel agency M:N Many travel agency can
tourist place and tourist suggest many tourist , so the
place relationship between travel
Agency and tourist place is
many to many
ER-Relational Mapping:

ER-to-Relational Mapping Algorithm:

Step 1: Mapping of Regular Entity Types:

• For each regular (strong) entity type E in the ER schema, create a relation R that
includes all the simple attributes of E.
• Choose one of the key attributes of E as the primary key for R. If the chosen key of E
is composite, the set of simple attributes that form it will together form the primary
key of R.

Step 2: Mapping of Weak Entity Types

13 | P a g e
 • For each weak entity type W in the ER schema with owner entity type E, create a
relation R and include all simple attributes (or simple components of composite
attributes) of W as attributes of R.
• In addition, include as foreign key attributes of R the primary key attribute(s) of the
relation(s) that correspond to the owner entity type(s).
• The primary key of R is the combination of the primary key(s) of the owner(s) and the
partial key of the weak entity type W, if any.

Step 3: Mapping of Binary 1:1 Relation Types

For each binary 1:1 relationship type R in the ER schema, identify the relations S and T that
correspond to the entity types participating in R. There are three possible approaches:

(1) Foreign Key approach: Choose one of the relations-S, say-and include a foreign key
in S the primary key of T. It is better to choose an entity type with total participation in R in
the role of S.

(2) Merged relation option: An alternate mapping of a 1:1 relationship type is possible by
merging the two entity types and the relationship into a single relation. This may be
appropriate when both participations are total.

(3) Cross-reference or relationship relation option: The third alternative is to set up a third
relation R for the purpose of cross-referencing the primary keys of the two relations S and T
representing the entity types.

Step 4: Mapping of Binary 1:N Relationship Types.

• For each regular binary 1:N relationship type R, identify the relation S that represent
the participating entity type at the N-side of the relationship type.
• Include as foreign key in S the primary key of the relation T that represents the other
entity type participating in R.
• Include any simple attributes of the 1:N relation type as attributes of S.

Step 5: Mapping of Binary M:N Relationship Types.

• For each regular binary M:N relationship type R, create a new relation S to represent
R.
• Include as foreign key attributes in S the primary keys of the relations that represent
the participating entity types; their combination will form the primary key of S.

14 | P a g e
 • Also include any simple attributes of the M:N relationship type (or simple
components of composite attributes) as attributes of S.

Step 6: Mapping of Multivalued attributes.

• For each multivalued attribute A, create a new relation R. This relation R will include
an attribute corresponding to A, plus the primary key attribute K-as a foreign key in
Rof the relation that represents the entity type of relationship type that has A as an
attribute.
• The primary key of R is the combination of A and K. If the multivalued attribute is
composite, we include its simple components.

Step 7: Mapping of N-ary Relationship Types.

• For each n-ary relationship type R, where n>2, create a new relationship S to
represent R.
• Include as foreign key attributes in S the primary keys of the relations that represent
the participating entity types.
• Also include any simple attributes of the n-ary relationship type (or simple
components of composite attributes) as attributes of S.

15 | P a g e
5. Schema Diagram:

16 | P a g e
 4. Normalization:
The process of decomposing unsatisfactory "bad" relations by breaking up their
attributes into smaller relations. Normalization is carried out in practice so that the
resulting designs are of high quality and meet the desirable properties

Normal form: Condition using keys and Functional Dependencies of a relation to certify
whether a relation schema is in a particular normal form Types of Normal form :

• First Normal Form (1NF)

• Second Normal Form (2NF)
• Third Normal Form (3NF)
• Boyce- Codd Normal Form (BCNF)
1NF: Disallows composite attributes, multivalued attributes, and nested relations; attributes
whose values for an individual tuple are non-atomic

2NF: A relation schema R is in second normal form, if every non-prime attribute A in R is

fully functionally dependent on the primary key

3NF: A relation schema R is in third normal form, if it is in 2NF and no non-prime attribute
A in R is transitively dependent on the primary key

BCNF: A relation schema R is in BCNF if whenever an FD X -> A holds in R, then X is a

superkey of R.

Each normal form is strictly stronger than the previous one

– Every 2NF relation is in 1NF

– Every 3NF relation is in 2NF

– Every BCNF relation is in 3NF

17 | P a g e
Normalisation:

18 | P a g e
 Lab Project Report On

“Online Banking Management”

Batch No: 01
NAME USN
Pratyush Prakash 2GI19IS038

Prashant Badiger 2GI19IS035

Prajwal Jainkeri 2GI19IS033

Under the Guidance of

Prof.Sudhindra. B.Deshpande
KLS, GIT, Department of ISE, Belagavi
Course Name: Database Management System
Semester: IV
Course Code: 18IS43

DEPARTMENT of INFORMATION SCIENCE AND ENGINEERING

Academic Year 2019-20

19 | P a g e
 Lab Project Report on

1. Title
2. Problem statement for that the project
3. Need Analysis, Variables involved
4. Atleast two alternate solutions to solve the problem defined or meet the need analysis
5. Comparison between the solutions and reason for selecting the final solution
6. Working model of the final solution

Marks allocation:
Batch No. : 14
1 Project Title: Travel And Hotel Boooking Mark USN
. System s 2GI19IS053 2GI19IS008 2GI19IS064
Rang
e
2 Problem statement (PO2) 0-1
.
3 Need Analysis, Variables involved
0-2
. (PO1,PO2)
4 Alternate solutions to solve the
0-3
. problem(PO3)
5 Comparison between the solutions
. and reason for selecting the final 0-4
solution(PO1,PO3,PO4)
6 Working model of the final solution
0-5
. (PO3,PO12)
7 Report and Oral presentation skill
0-5
. (PO9,PO10)
Total 20
* 20 marks is converted to 10 marks for CGPA calculation

21 | P a g e

1.Engineering Knowledge: Apply the knowledge of mathematics, science, engineering

fundamentals and an engineering specialization to the solution of complex engineering
problems.
2.Problem Analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences and Engineering sciences.
3.Design/Development of solutions:Design solutions for complex engineering problems and
design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environmental
considerations.
4.Conduct investigations of complex problems: Use research-based knowledge and
research methods including design of experiments, analysis and interpretation of data, and
synthesis of the information to provide valid conclusions.
5.Modern tool usage:Create, select, and apply appropriate techniques, resources, and
modern engineering and IT tools including prediction and modeling to complex engineering
activities with an understanding of the limitations.
6.The engineer and society:Apply reasoning informed by the contextual knowledge to assess
societal, health, safety, legal and cultural issues and the consequent responsibilities relevant to
the professional engineering practice.
7.Environment and sustainability: Understand the impact of the professional engineering
solutions in societal and environmental contexts, and demonstrate the knowledge of, and need
for sustainable development.
8.Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the engineering practice.
9.Individual and team work: Function effectively as an individual and as a member or leader
in diverse teams, and in multidisciplinary settings.
10.Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to comprehend and
write effective reports and design documentation, make effective presentations, and give and
receive clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the
engineering management principles and apply these to one's own work, as a member and
leader in a team, to manage projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for and have the preparation and ability to
engage in independent and lifelong learning in the broadest context of technological change.

21 | P a g e
 6. Table Creations

1. Admin Tabel :

CREATE TABLE ADMIN(

A_ID int,

Password varchar(15),

A_Name varchar(15),

primary key(A_ID)

);

insert into ADMIN values(5,'xyz@','Prashant');

insert into ADMIN values(525,'prat123','Prajwal');

insert into ADMIN values(58,'pqr!!!','Pratyush');

insert into ADMIN values(78,'abc12345','Prakash');

insert into ADMIN values(88,'mypass!2','Pathak');

insert into ADMIN values(74,'toy65@','Kaushal');

insert into ADMIN values(49,'pp0705','Amit');

insert into ADMIN values(97,'kk9705','Shreyas');

insert into ADMIN values(61,'ss9@05','Saurav');

insert into ADMIN values(09,'mo95','Mohit');

22 | P a g e
2. Travel Agency Table:

CREATE TABLE TRAVEL_AGENCY(

T_ID varchar(15),

Name varchar(15),

Address varchar(30),

Cell int,

primary key(T_ID)

);

insert into TRAVEL_AGENCY values('A20','Raj Travels','Mumbai',945871552);

insert into TRAVEL_AGENCY values('U99','Mehara

Travels','Ambawadi,Mumbai',957812321);

insert into TRAVEL_AGENCY values('Z12','Mukund

Travels','Andheri,Mumbai',886458142);

insert into TRAVEL_AGENCY values('M416','Custome Travels','Kalyani

Nagar,Pune',784562391);

insert into TRAVEL_AGENCY values('K98','Tisco Travels','Laxmi

Road,Pune',746268943);

insert into TRAVEL_AGENCY values('A340','Rathore Travels','Boaring

Road,Patna',945317849);

insert into TRAVEL_AGENCY values('M24','Ambe Travels','Exhibition

Road,Patna',979464128);

insert into TRAVEL_AGENCY values('P40','Maa Travels','Firaya

Lal,Ranchi',778845412);

insert into TRAVEL_AGENCY values('A89','Rahul

Travels','Tilakwadi,Belgaum',624588172);

insert into TRAVEL_AGENCY values('X65','Prakash

Travels','Udayambag,Belgaum',984512666);

23 | P a g e
3. Tourist Place Table:

CREATE TABLE TOURIST_PLACE(

Trs_ID varchar(15),

Trs_Name varchar(25),

Location varchar(30),

primary key(Trs_ID)

);

insert into TOURIST_PLACE values('X19U27','Akasht Srisvatav','Taj Mahal,Agra');

insert into TOURIST_PLACE values('P18P45','Arnav Sinha','The Holy City,Varanasi');

insert into TOURIST_PLACE values('L18X18','Roshini Mehta','The Golden Temple,Amritsar');

insert into TOURIST_PLACE values('O18M24','Rehaan Saudagar','The Golden City,Jaisalmair');

insert into TOURIST_PLACE values('Q19A64','Neha Sharma','Red Fort,New Delhi');

insert into TOURIST_PLACE values('M19Y69','Prashant Khot','The Gateway of India,Mumbai');

insert into TOURIST_PLACE values('A17V54','Riya Kulkarni','Mecca Masjid,Hyderabad');

insert into TOURIST_PLACE values('G17W89','Manoj Vajpayee','Amer Fort,Jaipur');

insert into TOURIST_PLACE values('V17I66','Pankaj Tripathi','The Beaches of Goa,Goa');

insert into TOURIST_PLACE values('U16O76','Raj Kumar Rao','The Ellora Caves,Aurangabad');

24 | P a g e
 4. Hotel Table:

CREATE TABLE HOTEL(

H_ID varchar(15),

H_Nmae varchar(30),

Address varchar(30),

primary key(H_ID)

);

insert into HOTEL values('M24G','Jaypee Palace Amarvilas','Fatehbad Road,Agra');

insert into HOTEL values('K15F','Brijram Palace','Dashaswmedh ,Varanasi');

insert into HOTEL values('H55L','Radiasson Blue Hotel','Airport Road,Amritsar');

insert into HOTEL values('O16D','Hotel Jaisal Khot','Jaisalkhot Kuldhara,Jaisalmair');

insert into HOTEL values('W45H','Hyatt Delhi Residences','Aerocity IGI Airport,New Delhi');

insert into HOTEL values('S88U','The Taj Mahal Palace','Appollo Bunder Road,Mumbai');

insert into HOTEL values('Y91Z','The Falaknuma Palace','Engine Bowli,Hyderabad');

insert into HOTEL values('R88Y','Rambagh Palace','Bhawani Singh Road,Jaipur');

insert into HOTEL values('E65T','The Lella Goa','Mobor Cavelossim,Goa');

insert into HOTEL values('D26I','Lemon Tree Hotel','Chikalthana Road,Aurangabad');

25 | P a g e
 5. Bill Table :

CREATE TABLE BILL(

BILL_ID int,

BILL_Date date,

Amount varchar(15),

primary key(BILL_ID)

);

insert into BILL values(2785,'2021-05-22','RS 23808');

insert into BILL values(5930, '2021-08-12','RS 11969');

insert into BILL values(1520, '2021-11-04','RS 27031');

insert into BILL values(1400, '2021-10-16','RS 15969');

insert into BILL values(4950, '2021-11-14','RS 26996');

insert into BILL values(7800, '2021-03-19','RS 11969');

insert into BILL values(2690, '2021-01-07','RS 8808');

insert into BILL values(1028, '2021-06-30','RS 7031');

insert into BILL values(1000, '2021-08-28','RS 9669');

insert into BILL values(1500, '2021-07-01','RS 9420');

insert into BILL values(1200, '2021-05-09','RS 11269');

26 | P a g e
insert into BILL values(8800, '2021-05-10','RS 8853');

6. Customer Table:

CREATE TABLE CUSTOMER(

C_ID varchar(15),

Name varchar(20),

Age int,

Address varchar(30),

Cell int,

primary key(C_ID)

);

insert into CUSTOMER values('GH7542','Hemant Jadav',25,'Bengaluru',889415624);

insert into CUSTOMER values('FC9562','Kavita Tiwary',26,'Pune',957164824);

insert into CUSTOMER values('TS8445','Rohan Sharma',32,'Patna',878695412);

insert into CUSTOMER values('TK2871','Racheal Green',35,'Mumbai',948571368);

insert into CUSTOMER values('TK2471','Rajat Sharma',24,'Pune',952384257);

insert into CUSTOMER values('TK2971','Rahul Patil',33,'Hyderabad',624897516);

insert into CUSTOMER values('AM2808','Adven Math',29,'Patna',726489571);

insert into CUSTOMER values('GP6969','Shreyas Kumar',27,'Jaipur',776632125);

27 | P a g e
insert into CUSTOMER values('RD9854','Prince Raj',23,'Kolkata',996413528);

insert into CUSTOMER values('LR0420','Jethala Gada',36,'Bangalore',764558459);

insert into CUSTOMER values('LR6969','Tarak Mehta',34,'Ranchi',625548715);

insert into CUSTOMER values('LR8969','Baby Singh',32,'Chennai',624100578);

6. Books table :
CREATE TABLE BOOKS(
T_ID varchar(15),
H_ID varchar(15),
primary key(T_ID,H_ID),
foreign key(T_ID) references TRAVEL_AGENCY(T_ID),
foreign key(H_ID) references HOTEL(H_ID)
);

insert into BOOKS values('A20','M24G');

insert into BOOKS values('U99','K15F');
insert into BOOKS values('Z12','H55L');
insert into BOOKS values('M416','O16D');
insert into BOOKS values('K98','W45H');
insert into BOOKS values('A340','S88U');
insert into BOOKS values('M24','Y91Z');
insert into BOOKS values('P40','R88Y');
28 | P a g e
 insert into BOOKS values('A89','E65T');
insert into BOOKS values('X65','D26I');

7. Visits Table :

CREATE TABLE VISITS(

T_ID varchar(15),

Trs_ID varchar(15),

primary key(T_ID,Trs_ID),

foreign key(T_ID) references TRAVEL_AGENCY(T_ID),

foreign key(Trs_ID) references TOURIST_PLACE(Trs_ID)

);

insert into VISITS values('A20','X19U27');

insert into VISITS values('U99','P18P45');

insert into VISITS values('Z12','L18X18');

insert into VISITS values('M416','O18M24');

insert into VISITS values('K98','Q19A64');

insert into VISITS values('A340','M19Y69');

insert into VISITS values('M24','M19Y69');

insert into VISITS values('P40','G17W89');

29 | P a g e
insert into VISITS values('A89','V17I66');

insert into VISITS values('X65','U16O76');

GRAPHICAL USER INTERFACE DESIGN

1 MAIN WINDOW FOR DROP DOWN

30 | P a g e
2. ADMIN

3 BILL

31 | P a g e
4 BOOKS

HOTEL

32 | P a g e
TOURIST PLACE

Travel Agency

33 | P a g e
VISITS

CUSTOMER

34 | P a g e
 10. Conclusions
As we know Travelling has become a part of our life. Most of the people loves travelling.
So for travelling we need a good guide, and a travel agency so that the travelling and hotel
booking become easy. Hotel booking is very important during travelling . With the help of this
program we can easily get the details of travel agency, tourist place, hotel in the specific
region.

11. References
➢ www.guru99.com
➢ www.javapoint.com
➢ www.geeksforgeeks.com ➢
www.tutorialspoint.com

35 | P a g e