Trip booking

TRIP BOOKING

A PROJECT REPORT

Submitted by

Nimisha S. Panchal

In fulfillment for the award of the degree

of

BACHELOR OF ENGINEERING

in

Information Technology

C. G. Patel Institute of Technology, Tarsadi - Bardoli

Gujarat Technological University, Ahmedabad

May, 2013

CHHOTUBHAI GOPALBHAI PATEL INSTITUTE OF TECHNOLOGY, TARSADI

BARDOLI-394601

Information TechnologyInformation TechnologyInformation TechnologyInformation Technology

CertificateCertificateCertificateCertificate This is to certify that the dissertation entitled ““““Trip BookingTrip BookingTrip BookingTrip Booking” ” ” ” has been

carried out by Nimisha PanchalNimisha PanchalNimisha PanchalNimisha Panchal under my guidance in fulfilment of the degree of

Bachelor of Engineering in Department of Information Technology (8th Semester) of

Gujarat Technological University, Ahmedabad during the academic year 2012-13.

The work done by them is found satisfactory.

Date: 16th May 2013

Guided by: Signature of Jury Head of the Department

Prof. Tarunika Chaudhari _________________ Prof. Devendra Thakor

CANDIDATE’S DECLARATION

I declare that the information contained in this report is about the project work done by me

during final year IT Engineering and it is not submitted fully or in part to any other university

for awarding the B.E of Information Technology or any other.

Candidate : Nimisha S. Panchal

External Guide : Mr. Bhadresh Sorathiya, Indataa company

Internal Guide : Prof. Tarunika Chaudhari, Computer/IT Department

Submitted To : Head of Computer/IT Engineering Department,

Chhotubhai Gopalbhai Patel Institute of Technology,Tarsadi -Bardoli.

Submission date : 16th May 2013

i

ACKNOWLEDGEMENT

I owe a great many thanks to a great many people who helped and supported me during the

writing of this report.

My deepest thanks to Prof. Tarunika Chaudhari, the Guide of topic for guiding and correcting

various documents of mine with attention and care. She has taken make necessary correction

as and when needed. I express my thanks to our Head of the Department of, C. G. Patel

Institute of Technology, for extending his support.

My deep sense of gratitude to my guide support and guidance. Thanks and appreciation to the helpful people

at C. G. Patel Institute of Technology, for their support.

I would also thank my Institution and my faculty members without whom this Project would

have been a distant reality. I also extend my heartfelt thanks to my family, my best friend and

well wishers.

Nimisha S. Panchal

ii

ABSTRACT

This document is meant for describing all the features and procedures those

were followed while developing the system.

This document specially mentions the detail of the project how it was

developed, the primary requirement as well as various features and

functionalities of the project.

Trip booking system is helpful to the users for obtaining information about the

Trip that provides various Locations for the Trip across in India. User can

search as well as book their trip

With Trip booking system, user finds the event or service she wishes to book by

name or date, or whatever criteria the merchant has set up. After choosing the

exact date, time, seat location and other specific criteria, she confirms her

reservation. She may pay for the reservation or ticket on the spot, or use a credit

card number as a guarantee to hold her place. The confirmation is usually

available immediately as a print out page. Alternately, she may receive

confirmation.

iii

LIST OF FIGURES

Figure No Figure Description Page No

2.1 Spiral model 6

2.2 TimeLine Chart 11

4.1 ER Diagram 30

4.2 Usecase for Administrator 32

4.3 Usecase for User 33

4.4 Usecase for SignIn 34

4.5 Dfd Shapes 35

4.6 Level 0 36

4.7 Level 1 37

4.8 Level 2-admin 38

4.9 Level 2-user 39

4.10 Activity for administrator 41

4.11 Activity for user 42

4.12 Sequence diagram for Sign in 44

4.13 Sequence diagram for administrator 45

4.14 Sequence diagram for user 46

5.1 Multi-tier architechture 47

5.2 Home page 48

5.3 Sign up page 49

5.4 SignIn page 49

5.5 Search Hotel 50

5.6 Search Rentalcar 51

5.7 Search Trip 52

5.8 Book trip1 53

5.9 Book trip2 53

5.10 Book trip3 54

iv

5.11 Book trip 54

5.12 AboutUs 55

5.13 Contact with Us 56

5.14 Packages for Hotels 57

5.15 Packages for rentalcar 58

5.16 Holiday Places 59

5.17 India Map 60

5.18 Admin_home 61

5.19 Show Register 62

5.20 Show Contact/Feedbacks 63

5.21 Show Rentalcars 64

5.22 Show Hotels 65

5.23 Show Package for Rentalcar 66

5.24 Show Package for Holiday 67

5.25 Add Rentalcar 68

5.26 Upload Image 69

5.27 Update Hotel 70

6.1 user Sign in 71

6.2 Authorized user sign in 71

6.3 validation in signup page 72

6.4 validation in search hotel 73

6.5 validation in rentalcar 73

6.6 validation in Contact 74

6.7 validation in update rental car 74

6.8 validation in update hotel 75

v

TABLE OF CONTENTS

Acknowledgement i

Abstract ii

List of Figures iii

Table of Contents v

Chapter:1 INTRODUCTION

1.1 Project Overview 1

1.2 Purpose 2

1.3 Project Scope 2

1.4 Objective 3

1.4.1 Main Objectives 3

1.4.2 Secondary Objectives 3

Chapter:2 PROJECT MANAGEMENT

2.1 Project Planning 5

2.1.1 Project Development Approach and Justification 5

2.1.2 Software scope 7

2.1.3 Resources 7

2.2 Project Scheduling 8

2.2.1 Basic principles 8

2.2.2 Timeline Chart 9

2.3 Risk Management 11

2.3.1 Risk Identification 12

2.3.2 Risk Identification artifacts 12

2.3.3 Risk Projection 12

2.3.4 Risk Refinement 13

2.3.5 Tracking and Control 13

vi

Chapter:3 SYSTEM REQUIREMENTS STUDY

3.1 User Classes and Characteristics 15

3.2 Hardware And Software Requirements 22

3.3 Functional and Non-Functional Requirements 22

3.3.1 Functional Requirements 22

3.3.2 Non Functional Requirements 23

3.4 Constraints 23

3.4.1 Hardware Limitations 23

3.4.2 Interfaces to other applications 23

3.4.3 Parallel Operations 23

3.4.4 Higher Order Language Requirements 24

3.4.5 Reliability Requirement 24

3.4.6 Safety and Security consideration 24

3.5 Assumptions and Dependencies 24

Chapter:4 SYSTEM ANALYSIS

4.1 Study of Current System 25

4.2 Problems and Weaknesses of Current System 25

4.3 Requirements of New System 25

4.3.1 User Requirements 25

4.3.2 System Requirements 26

4.4 Feasibility Study 26

4.4.1 Technical Feasibility 26

4.4.2 Operational Feasibility 27

4.4.3 Economic Feasibility 27

4.5 Requirement Validation 27

4.6 Features Enhancement 29

4.7 ER Diagram 29

vii

4.8 Use Case Diagrams 31

4.9 Dataflow Diagrams 35

4.10 Activity Diagrams 40

4.11 Sequence Diagrams 43

Chapter:5

SYSTEM DESIGN AND IMPLEMENTATION

5.1 System Architecture 47

5.2 Design And GUI 48

Chapter:6

TEST CASES

6.1 SignIn authentication 71

6.2 Email and other Validation 72

Conclusion 76

References 77

Report of Trip Booking

1 Information Technology

1. INTRODUCTION

1.1 PROJECT OVERVIEW

Trip Booking is impressive web based application for the tourist who are looking for

vacation across in India. It provides 24/7 support for user to book their trip. The

application has been developed in J2EE as a front end and MYSQL as a back end.

Basically, there are several modules in the trip booking web application.

Search module

This module deals with the users regarding the contact and address information of the

specific trip location, using this module user can search hotels and rentals cars for

their trip. User can search for hotels and rental cars with specific date. User can

search for their trip without any registration.

Sign up

This module deals with the user who wants to book their trip. This process is most

requiring for reserve the trip or cancels the trip. To get latest packages and offers by

booking the trip users have need to sign up in the site and they have to fill require

$information for signup.

Sign in

This module only used by the register users and admin. Only admin can login/sign in

the admin_home. After sign in in their account user can check for latest offers and

book as well as reschedule for the trip.

Trip module

This module deals with the users that they can search for Trip for specific date and

search for both rentalcar and hotel,by finding result they can go for book module.



Book module

This module deals with the user who registers in the site for book their trip across in

India. Only register user can book as well as schedule their trip. To use this module

user need to register in the site for details. User can book hotels and rental cars.

Admin_home module

Only Admin can use this module for update the web page. Using this module admin

maintain the pricing issues regarding the hotels and rental cars. Admin display the

latest packages for the tourist who has created account for book and reschedule the

trip. When any unwanted things done by user on the page then admin can block the

user for such limit of time.

1.2 PURPOSE

This web application enables the user to do the things such as search for rental cars

and hotels for two travel cities on a specified date, choose hotels based on the details,

the user can get reservation and cancellation of reservation.

User can book rental car for travelling across in India. The prices of the rental car

counted as per km between two cities by the system. The pricing issues also depend

on type of car which is selected by tourist. To book a Hotel/rental car the system asks

the user to enter his details such as name, address, city, state, credit card number and

contact number. Then it checks the validity of card and book the hotel. The system

also allows the user to cancel his/her reservation, if any problem occurs.

1.3 PROJECT SCOPE

The sytem accessible by user that they can get experience most effective and useful

feature from the site. The application is accessible by different user all around the

world organization with different access to data. The data should be very secure

because the organization is developing the system to manage good user relation. This



data is high confidential in development of business strategy and marketing plans.

Data of product and organizations once entered in database can’t be deleted as other

tables related to them. Performance evaluation of marketing strategy should be done

time to time.

User can easily search and book their trip by using this web application. Using this

web application user can book their trip without any extra charges and get cheap cost

compare to any other booking process. User can book their trip and they can also

search for different destination for their holiday packets. The application also provides

facilities for user that they can search for their trip without any registration for free.

For book or schedule their trip their require registration. The application contains

overall information regarding its works.

1.4 OBJECTIVES

1.4.1 Main Objectives

� To manage register data effectively

� To provide contact information regarding users

� To perform analysis on database

� To simplify marketing strategy of booking system

� To provide security as only and authorized user can interact with system

� To provide Trip regarding information to user

1.4.2 Secondary Objectives

Global Accessibility

As data are stored on the server database of the system, it should be available to all

visitors as well as administrator.

Location Independence

It should be accommodate wide variety of clients in different geographical areas.



Flexible Deployment

User should have easy accessibility to data through local database that are replicated

in the respective locations.

Reusability

The system should be built so as to make the components reusable for future

developments.



2. PROJECT MANAGEMENT

2.1 PROJECT PLANNING

The objective of software project planning is to provide a framework that enables the

manager to make reasonable estimates, cost, and scheduling. These estimates are made

within a limited time frame at the beginning of a software project and should be updated

regularly as the project progresses.

2.1.1 Project Development Approach and Justification

To solve actual problems in industry settings, software engineer or a team of engineers

must incorporate development strategy that encompasses the process, methods and tools

layers and generic phases. This strategy is often referred to as process model or an

engineering paradigm. A process model for software engineering is chosen based on the

nature of the project and application, the methods and tools to be used.

Spiral Model:

Justification

• In spiral model, the requirements are changing, so even if the requirements are given;

they can also vary as per the new requirements of the user.

• The requirements in this project kept on changing as per the user modifications and

hence,

• Spiral model process flow was appropriate or such kind of a situation, and hence spiral

model approach has been used.



Figure 2.1 Spiral Model

• The risk assessment component of this model provides both developers and users

with a measuring tool that other models do not have. This model has great value of

risk management.

• As the user’s requirements were changing frequently we followed spiral model so

that we can repeat the development process. And cope with the changing

requirements. We have to verify each and every developed design or page with the

user. And if changes were recommended again the development was carried out.



2.1.2 Software Scope

• The first activity in the project planning is the determination of software scope.

Function and performance allocated to software during system engineering should be

assessed to establish a project scope that is unambiguous and understandable at the

management and technical levels.

• Software Scope described the data and control to be processed, function, performance,

constraint, interface, and reliability. Defining the software scope for this project we have

to collect information from the company networking person by asking some questions.

These questions includes like from which server, how many clients, solutions to connect

client to server etc.

2.1.3 Resources

The second software planning task is to estimation of the resources required to

accomplish the software development effort. The above figure illustrates development

resources as a pyramid. The development environment – hardware and software tools-sits

at the foundation of the resources pyramid and provide the infrastructure to support the

development effort. At a higher level, we encounter reusable software components-

software building blocks that can dramatically reduce development costs and accelerate

delivery. At the top of the pyramid is the primary resource-people.

2.1.3.1 Human Resource

The human resources required are Database, network administrator (Project guide).

2.1.3.2 Reusable Software Resources

For our project there is no existing specification, design, code or data of past projects are

included. But the new components are building for our need.



2.2 PROJECT SCHEDULING

2.2.1 Basic Principal

“Software project scheduling is an activity that distributes estimated effort across the

planned project duration by allocating the effort to specific software engineering tasks.”

Proper scheduling requires:

• All tasks appear in network.

• Effort and timing are intelligently allocated to each task.

• Interdependencies between tasks are properly indicated.

• Resources are allocated for the work to be done.



2.2.2 TimeLine Chart

2.2.2.1 Time Allocation

Each task to be scheduled must be allocated some number of work units. In my software

project, time allocated to task that check server is connected. The time that was spent in

each part of system development is shown in the activity chart.

2.2.2.2 Task Sets

We have selected the “Spiral Model” so that there are six different work tasks to work

together. A tasks set is a collection of software engineering work tasks, milestones, and

deliverables that must be accomplished to complete a particular project. Tasks set are

designed to accommodate different types of projects and different degree of Rigor. Most

software organizations encounter the following projects.

• Concept Development.

• New Application development.

• Application enhancement.

• Application maintenance.

• Re-engineering project.

Refinement of major tasks

The above tasks are again refinement as follows:

� Analysis of required system

1) Study of required flow

2) Study of methodology

� Defining goals and objectives

1) Preparing the goal

2) Defining the flow of the project



� Finding out resources required

1) Identifying the resources

2) Making arrangement for getting the resources

� Coding and Testing.

1) Designing the tables and creating them.

2) Coding for the Forms.

3) Validation of the forms.

4) Testing

� Documentation

1) Divide document in small parts

2) Documentation of each part

3) Integration of all parts

4) Review of project documentation



Figure 2.2 Time Line Chart

2.3 RISK MANAGEMENT

Software is a difficult undertaking. Lots of things can go wrong and frankly, many often

do. It’s for this reason that being prepared understanding the risks and taking proactive

measure to avoid or manage them is a key element of good software project management.

Recognizing what can go wrong is the first step called „Risk Identification‟. Next each

risk is analyzed to determine the likelihood that it will occur and the damage that it will

do if it does occur. Once this information is established, risks are ranked, by probability

and impact. Finally a plan is developed to manage those risks with high probability.



2.3.1 Risk Identification

Risk identification is a systematic attempt to specify threats to the project plan. By

identifying known and predictable risks, I take first step towards avoiding them when

possible and controlling them when necessary.

2.3.2 Risk identification artifacts

I considered the following types of risk to identify the risk in proper manners. The next

table shows the type of risks.

Table 2.1 Risk Type

Risk Type

Description

Project

Risks

This type of risk can threaten the project plan. If project risks

become real, then project schedule problems and their impact

on a software project.

Technical

Risks

This type of risk can threaten the quality and timeliness of

software to be produced. If a technical risk becomes a reality

then implementation may become impossible or difficult.

Business

Risks

This type of risk can threaten the viability of the software to be

built. Business risks often the project or the product.

2.3.3 Risk Projection

Risk projection ,also called risk estimation, attempts to rate each risk in two ways-the

likelihood or probability that risk is real and consequences of the problems associated

with the risk should it occur. The following table shows the artifacts used in the risk

projections.



Table 2.2 Risk Category

Risk category Description

Catastrophic

Risk can cause the whole system to fail.

Critical

There may be significant degradation of the system may result

Minor

The risk can be easily recovered from the system failure.

Negligible

The risk can be negligible and shall not affect in the

performance in the system at all.

2.3.4 Risk Refinement

I should always ready for an unforeseen event that may or may not occur. The strategy

that I had used in for the risk refinement is risk management and contingency planning

because it assumes that mitigation efforts have failed and that the risk has become a

reality. The next table shows the risks planning and steps which shall be taken to

overcome the risks.

2.3.5 Tracking and Control

Weekly status reports were sent to the Teachers and each module discusses in the

meetings. Information about work done and the further working report is exchanged

during the weekly meetings to make sure is on schedule to meet all our milestones.



Table 2.3 Tracking and Control of Risk Types

Risk ID#

Risk Type

Impact

Affected component

1 Project/Catastrophic

Critical

Schedule

2 Business/Critical

Critical

Performance

3 Project/Minor

Critical

Performance

4 Technical/Minor

Critical

Performance

5 Technical/Critical

Minor Performance

6 Technical/Catastrophic

Critical

Performance

7 Project/Minor

Minor Support

8 Business/Critical

Critical

Schedule

9 Business/Critical

Critical

Support



3. SYSTEM REQUIREMENTS STUDY

3.1 USER CLASSES AND CHARACTERISTIC

Administrator

� Display new hotels and Rental cars discounts

� Update hotels and Rental car options

� Maintaining pricing and ticket issues

� Generating and view reports

� Making user account and assigning authority to them

� Block the users if any unfair able thing done by user

User

� Search different hotels and rental cars

� Log in into system to securely provide information to user

� Querying Database to filter information required by users

� Book their trip

� Cancel or Reschedule their trip

� Generating history reports

� Search by different months, date for future trip

� Give feedback



3.1.1 DATA DICTIONARY

3.1.1.1 Administrator

Hotel detail

Table 3.1 hotel

Field_name Data type Constraint Detail

hotel_id int(11) primary key

location varchar(18) not-null

hotel_name varchar(25) not-null

hotel_address varchar(23) not-null

hotel_contact varchar(12) not-null

available_hotel varchar(7) not-null

check_in varchar(13) not-null

check_out varchar(15) not-null

room varchar(3) not-null

adult varchar(4) not-null

child varchar(5) not-null

Hotel_image blob not-null



Rental car

Table 3.2 rentalcar


id int(11) primary key

source varchar(14) not-null

destination varchar(15) not-null

car_agency varchar(30) not-null

agency_contact varchar(13) not-null

car_type varchar(20) not-null

available_car varchar(10) not-null

pickup varchar(12) not-null

time1 varchar(8) not-null

dropoff varchar(13) not-null

time2 varchar(9) not-null

car_image blob



3.1.1.2 User

Sign Up

Table 3.3 signup


user_accid int(11) Primary key

username varchar(15) not-null

password varchar(14) not-null

name varchar(18) not-null

address varchar(20) not-null

country varchar(21) not-null

zip varchar(10) not-null

email varchar(25) not-null

mobile decimal(15,0) not-null

birthday date null

sex char(10) null



Book

Table 3.4 Booking


user_accid int(11) primary key

name varchar(15) not-null

address varchar(25) not-null

city varchar(15) not-null

state varchar(15) not-null

zip varchar(8) not-null

email varchar(21) not-null

cartype varchar(12) not-null

bank_name varchar(18) not-null

cardnumber varchar(16) not-null

cardholder varchar(25) not-null

exp-date varchar(25) not-null



Contact

Table 3.5 Contact


review_id int(11) not-null

Name varchar(20) not-null

Occupation varchar(21) not-null

Rate varchar(15) not-null

LikeForm varchar(18) not-null

Email varchar(23) not-null

Query varchar(50) not-null

Package for Rental car

Table 3.6 package for rentalcar


id int(11) not-null

source varchar(16) not-null

destination varchar(15) not-null

car_type varchar(20) not-null

pickup varchar(18) not-null

dropoff varchar(20) not-null

offer varchar(10) not-null



Package for Hotel

Table 3.7 package for Hotel


id int(11) not-null


check_in varchar(15) not-null

check_out varchar(16) not-null

offer varchar(11) not-null

Holiday places

Table 3.8 Holiday places


id int(11) not-null


description varchar(500) not-null

image blob not-null



3.2 HARDWARE AND SOFTWARE REQUIREMENT

Hardware and Software Requirements are used to describe the minimum hardware

and software requirements to run the Software.

3.2.1 Hardware Requirements:

� Processor: Intel Pentium 4 or Higher

� RAM: 512MB or Higher

� Hard Disk: 40 GB(or as per requirement)

� Monitor: 15” color monitor

� Mouse: Microsoft Compatible pointing device

� Keyboard: Standard Keyboard

3.2.2 Software Requirements:

� OS: Windows XP or Higher

� Front End: J2EE

� Back End: MYSQL

� Development Tools: NetBeans IDE 7.1.2, Apache Tomcat

� Supportive Tools: Microsoft Office Word 2003/2007, RF Flow, Browser

3.3 FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS

3.3.1 Functional Requirements

3.3.1.1 Activities of Proposed System

The Basic activities involved in the system are:

• Generate the report by Administrator

• Managing user information by Administrator

• Latest packages updated by administrator

• Any User or visitor can search hotels and rental car without any registration

• User selects and books the hotels as well as cars. And reschedule and cancel their

trip



3.3.2 Non Functional Requirements

There are lots of features that I have included in the application. But some of them

were described over here.

3.3.2.1 Easy to maintain Shop data records

All the records are stored in the site database. Back up can be taken easily.

3.3.2.2 Less Time Consuming

All the entries are done easily so it requires less time and also calculation is done

automatically through computer so take less time.

3.3.2.3 Editing of Data

Easy to change the records.

3.3.2.4 Security of data

Security of data is important factor of the system success. I have providing the

security for the database so no one can illegal access to the database.

3.4 CONSTRAINTS

3.4.1 Hardware Limitations

This application requires Telephone line for access.

3.4.2 Interfaces to Other Applications

This Trip Booking is a web based application and can be used in anywhere.

3.4.3 Parallel Operations

This is a GUI based application hosted on a server so multiple users access it at a time

using server’s IP.



3.4.4 Higher Order Language Requirements

I am going to use J2EE as Frontend and MY SQL as Backend.

3.4.5 Reliability Requirement

The main reliability requirement is the validation used. Without proper validation the

system does not allow to enter that value into the database. For e.g. in the email id,

the user cannot enter any dummy value, the validation checks that whether there is

‘@’ or ‘.’ symbol in that. Also any null value is not allowed in place of compulsory

fields.

3.4.6 Safety and Security Consideration

There are three levels of security in the system. The highest level of security is

assigned to the administrator who has all the rights to insert, edit and delete using

administrator controls.

Second level security is web application related security. In that User must have login

to use the web application.

The lowest level is given to the employees. They are registered by administrators.

They can manage their dash boards after login.

3.5 ASSUMPTION AND DEPENDENCIES

• Each user has Username and Password.

• Each User has unique ID.

• All the access rights and permissions are given to the Administrator.

• No one can enter the system without having a login and password.

• User and Adminstrator can change the password.



4. SYSTEM ANALYSIS

4.1 Study of Current System

All this kind of applications want to provide best information of services to their

users, but right now the scenario is the users have to create account in the site for get

the right way to book their trip. For get more information and any suggestion for the

application user can not give the feedback to administrator. Although this system

works well but it is more time consuming and somewhat complex to understand by

some of users. Current system is also not user friendly.

In current system user is not able to get the information about places and locations if

he/she does not know the email or contact of particular location. If user finds problem

on the book or cancel off their trip then he/she has to wait for some days in some

cases.

4.2 Problem and weaknesses of current system

• It’s so much time consuming.

• Sometimes user doesn’t get 24/7 support.

• System is not user friendly.

• System security is not concern properly.

• In some what create complexity to user due to number of modules and

advertisement.

4.3 Requirement of New System

4.3.1 User Requirement

User who knows how to use any information helpdesk system can easily use our

application otherwise only little bit training can make them able to use our

application.



4.3.2 System Requirement

Following are the basic functions our project is required to perform:

1) Administrator can manage users Details...

2) Administrator can manage all system related details

3) All the users can get information regarding the Trip

4) Minimum Storage Space

5) Time required to open up the application should be as less as possible.

4.4 FEASIBILITY STUDY

Objective of Feasibility Study

An important outcome of the preliminary investigation is the determination that the

system requested is feasible. The feasibility study is carried out to examine the

likelihood that the system will be useful to the tourist.There are three aspects in the

feasibility study namely.

• Technical Feasibility

• Operational Feasibility

• Economic Feasibility

4.4.1 Technical Feasibility

The main purpose of checking Technical Feasibility is to examine whether the current

technology is sufficient for the development of the system. The outcomes of the

technical feasibility are as follows:

• Trip booking application is developed using J2EE as front end which provides

facility for making the system dynamic.

• It provides faster response to the user. It is accurate, reliable and easy to use.

• Further expansion of the system is possible by its network implementation.

• The application that is developed is technically feasible because the persons in the

organization are familiar with the technology that is being used to develop this

application.

• So, this application is Technically Feasible.



4.4.2 Operational Feasibility

Operational Feasibility measures how well the solution will work in the organization

and how end-user & management will feel about the system. Proposed system is

helpful for the users who are booking trips across in India that are available in nearby

region where they live. It will allow them to query them to get the appropriate and

adequate information.

On studying the operational feasibility of the project, the following conclusions

could be derived:

• Operationally the software will be most feasible due to its strong requirement for the

Trip across in India management.

• Due to good accuracy percentage of software, it can be easily deployed.

• Due to its easy functionality for users, who are not from IT background easily, can

use the software.

Thus, it is operationally feasible to develop the proposed system.

4.4.3 Economic Feasibility

The main purpose of checking Economical Feasibility is to examine whether the

financial investment in the system will meet the organization’s requirements or not.

The application does not involved purchasing or installing of any registered software.

The only requirement for running this application successfully is an Internet

Connection.

4.5 Requirement validation

It means that the developed software is as per requirement or not? Simply stating

whatever we are doing is right or wrong as per requirements? Here we check each and

every requirement and compare with our product and that it satisfies the user need. It

is a most crucial part of analysis phase. If the validation is inadequate, errors in

requirements will be propagated to the system design and implementation. For

validating the requirements, our project guide, and guided us at every stage of

analysis.



Administrator Login:

� If the administrator has already id and password then he/she can directly login

� Here the specified range must be followed for entering the password.

Check for duplicate Username

� If administrator try to add same username that is already exist then it will display

a message on that page and ask for another different username to proceed further.

Registration Validation

� User name validation

� Password validation

� Address validation

� Email validation

� Mobile number validation

Booking Validation

� Name validation

� Email validation

� Mobile number validation

� Zip code validation

� Cardholder name validation

� Card Number validation

� Expiration Date validation

Empty Fill Check:

� If any field is compulsory and if that one is left blank then an error message will

be displayed.



4.6 Features Enhancement

4.6.1 Web Page

The system offers a unified that provides access to various modules of the system as

per the type of user i.e. Admin or User. The admin can use respective dashboard for

management of the information as well as the user’s details and authorities assigned

to them. The user can use the respective dashboard for querying the info database.

4.6.2 Feedback

The user gives the query regarding the information and in feedback user can also

gives their opinion regarding the website and the functionality or services that have

been provided.

4.6.3 User Get SignUp and access all module

The user can create a new account with their unique username and password. they can

use every modules of the webpage. user can get various package information for the

trip.as well as they can also get information about the holiday places with the

description.user can get information about the rentalcar detail and hotel detail directly

from database ,so if hotel/rentalcar available then they can book it as per their search

for it.

4.7 Entity Relationship DIAGRAM

In software engineering, an entity-relationship model (ERM) is an abstract and

conceptual representation of data. Entity-relationship modeling is a database modeling

method, used to produce a type of conceptual schema or semantic data model of a

system, often a relational database, and its requirements in a top-down fashion.

Diagrams created by this process are called entity-relationship diagrams, ER

diagrams, or ERDs.



Fig 4.1 ER Diagram


4.8 USE– CASE DIAGRAM

A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use

present a graphical overview of the functionality provided by a system in terms of

actors, their goals (represented a

cases. The main purpose of a use case diagram is to show what system functions are

performed for which actor. Roles of the actors in the system can be depicted. Use

Case diagrams are formally included in

the Unified Modeling Language (UML) and the Systems Modeling Language

(SysML).

CASE DIAGRAM

in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose is to


actors, their goals (represented as use cases), and any dependencies between those use



Case diagrams are formally included in two modeling languages defined by the OMG:


Diagram building blocks

31

in the Unified Modeling Language (UML) is a type of

case analysis. Its purpose is to


s use cases), and any dependencies between those use



two modeling languages defined by the OMG:




Use case Administrator

Fig 4.2 use case for Administrator



Use case User

Fig 4.3 use case for user



Use case Sign In

Fig 4.4 use case for Sign In


4.9 DATAFLOW DIAGRAM

In software engineering, a

the "flow" of data through an

they are a preliminary step used to create an overview of the system which can late

elaborated DFDs can also be used for the

design).Dataflow diagrams are constructed from a limited repertoire of shapes,

connected with arrows. The most important shape types as shown in

Data flow diagrams can be used in both Analysis and Design phase of SDLC.

There are different notations to draw data flow diagrams, defining different visual

representations for processes, data stores, data flow, and external entities.

For Example,

DIAGRAM

a data flow diagram (DFD) is a graphical representation of

the "flow" of data through an information system, modeling its process aspects. Often

they are a preliminary step used to create an overview of the system which can late

elaborated DFDs can also be used for the visualization of data processing

Dataflow diagrams are constructed from a limited repertoire of shapes,

connected with arrows. The most important shape types as shown in figure.

Fig 4.5 dfd shapes



representations for processes, data stores, data flow, and external entities.

35

) is a graphical representation of

aspects. Often

they are a preliminary step used to create an overview of the system which can later be

data processing (structured

Dataflow diagrams are constructed from a limited repertoire of shapes,

figure.




Dataflow level 0

Fig 4.6 level 0

36



Dataflow level 1

Fig 4.7 level 1



Dataflow level 2-Admin

Fig 4.8 level 2-Admin



Dataflow level 2-User

Fig 4.9 level 2-User



4.10 ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified

Modeling Language, activity diagrams can be used to describe the business and

operational step-by-step workflows of components in a system. An activity diagram

shows the overall flow of control.

Activity diagrams are constructed from a limited repertoire of shapes, connected with

arrows. The most important shape types:

• rounded rectangles represent activities

• diamonds represent decisions

• bars represent the start (split) or end (join) of concurrent activities

• a black circle represents the start (initial state) of the workflow

• an encircled black circle represents the end (final state)

Arrows run from the start towards the end and represent the order in which activities

happen.

Hence they can be regarded as a form of flowchart. Typical flowchart techniques lack

constructs for expressing concurrency. However, the join and split symbols in activity

diagrams only resolve this for simple cases; the meaning of the model is not clear

when they are arbitrarily combined with decisions or loops.



Activity for Administrator

Fig 4.10 Activity for administrator



Activity for User

Fig 4.11 Activity for User



4.11 SEQUENCE DIAGRAM

A sequence diagram in a Unified Modeling Language (UML) is a kind of interaction

diagram that shows how processes operate with one another and in what order. It is a

construct of a Message Sequence Chart.

A sequence diagram shows object interactions arranged in time sequence. It depicts

the objects and classes involved in the scenario and the sequence of messages

exchanged between the objects needed to carry out the functionality of the scenario.

Sequence diagrams typically are associated with use case realizations in the Logical

View of the system under development.



Sequence for SignIn

Fig 4.12 Sequence Diagram for Sign in



Sequence for Administrator

Fig 4.13 Sequence Diagram for Administrator



Sequence for User

Fig 4.14 Sequence Diagram for User



5. System Design And Implementation

This chapter describes the system architecture as well as the design of the system and look

and feel of the system after development.

5.1 System Architecture Our system works on multi-tier architecture that helps separate the various layers of

the software system like Graphic UI and the business logic from the actual data.

Figure 5.1 Multi-tier Architecture

In this figure the Application UI constitutes the presentation layer where as the BLL is the Program logic layer and DLL is responsible for interaction with database which provides the security of data. Also we can deploy various components on various platforms because they can be separated.



5.2 Design and GUI

Designing for the Web is different from designing traditional software user interfaces.

Mainly, the designer has to give up full control and share responsibility for the UI with users

and their client hardware/software.

Of course there are also similarities between designing for the Web and traditional UI design: at the most basic level, both are interactive systems, and both are software designs as opposed to the design of physical objects.

5.2.1 Application Home Page

Figure 5.2 home page

This is the home page of the web application. Application allows user to do things like search and book trip packages. Admin responsible for all latest updation and maintenance.



5.2.2 User Sign up/Sign in page

Figure 5.3 SignUp page

Figure 5.4 SignIn page



This figures are shows the SignIn Page only signup user can signIn in the application.

5.2.3 Search Modules

Figure 5.5 Search Hotel

This figure shows the Search module for Hotel. This module provide user to search hotel from database. User/web visitor can search hotel as per their requirement, they can search hotel by different date and locations. after then user can book hotel.



Figure 5.6 Search Rentalcar

This figure shows the Search module for Rental car. This module provide user to search Rental car from database. User/web visitor can search Rental car as per their requirement, they can search rentalcar by different date and locations. After then user can book rentalcar.



Figure 5.7 Search Trip

This figure shows the Search module for Trip. This module provide user to search Trip from database. User web visitor can search trip as per their requirement, they can search trip by different date and locations. After then user can book trip. using this module user can search for both rentalcar and hotel as per their requirement.



5.2.4 Book Module

Figure 5.8 Book trip

Figure 5.9 Book trip1



Figure 5.10 Book trip2

Figure 5.11 Book Trip



These figures are shows how user book their trip.this module provide user to book their trip. Figure 5.8 shows book module for user who are not registered in the application. To use this module visitor need to signup in the web application. Figure 5.9 and figure 5.10 shows book module for signed in user.using this module user can see overall available and unavailable record for for hotels and rentalcar.user go for search for the trip as per their requirement. Figure 5.11 shows book module for book the trip. After search for the trip user go for book the trip.

5.2.5 AboutUs

Figure 5.12 AboutUs

This module use to provide information about web application developer. this module also introduce the application.



5.2.6 ContactUs

Figure 5.13 Contact with us

Using this module any visitor or user can give their feedback and opinions regarding application services.



5.2.7 Vacation Packages

Figure 5.14 Packages for hotels

This module use to provide information about latest vacation packages for hotels. This module shows latest offers provides as per updated packages for hotels.



Figure 5.15 Packages for rentalcar

This module use to provide information about latest vacation packages for rentalcars. This module shows latest offers provides as per updated packages for rentalcars.



Figure 5.16 Holiday places

This module use to provide information about holiday palces. this module shows information about the holiday place id ,location and description about the place. Any one can use this module to find their favourite place for the trip.



5.2.8 India Map

Figure 5.17 India map

This module shows the map for India.this map shows major cities of states among india.using this module user can see each state of India with famous cities if it.



5.2.9 Admin_home

Figure 5.18 Admin_home

This module only used by authorized admin ,using this module admin can update latest packages for trip as well as he/she can display new hotels and rentalcar.admin can also maintain pricing issues for the trip.



Figure 5.19 Show Register

This module only used by authorized admin ,using this module admin see registered data from database.



Figure 5.20 Show Contact/Feedback

This module only used by authorized admin ,using this module admin see contact data from database. using this module admin see the query/comment from user/website visitor and try to improve their service based on it.



Figure 5.21 Show Rentalcar

This module only used by authorized admin ,using this module admin see rentalcar data from database. using this module admin see inserted cars .based on requirement admin can modify the table. On right hand site we can see two operation i.e. used by admin.using update button admin update the table. using delete button admin delete the rows from table.



Figure 5.22 Show Hotels

This module only used by authorized admin ,using this module admin see hotel data from database. using this module admin see inserted Hotels .based on requirement admin can modify the table. On right hand site we can see two operation i.e. used by admin. using update button admin update the table. using delete button admin delete the rows from table.



5.2.10 Show Packages

Figure 5.23 show Package for rentalcar

This module only used by authorized admin ,using this module admin see package data from database. using this module admin see inserted packages for rentalcar .based on requirement admin can modify the table. On right hand site we can see two operation i.e. used by admin. using delete button admin delete the rows from table.



Figure 5.24 Show package for holiday

This module only used by authorized admin ,using this module admin see package data from database. using this module admin see inserted packages for holiday.based on requirement admin can modify the table. On right hand site we can see two operation i.e. used by admin. using delete button admin delete the rows from table.



5.2.11 Add New rentalcar

Figure 5.25 Add Rentalcar

This module only used by authorized admin ,using this module admin add rentalcars in database. using this module admin can inserted rentalcar.based on requirement admin can modify the table.



Figure 5.26 Upload Image

This module only used by authorized admin ,using this module admin upload image for hotels and rentalcar after adding new hotels and rentalcar in database.



Figure 5.27 Update Hotel

This module only used by authorized admin ,using this module admin can update hotel as well as rental cars.so as per the need admin modify the table.



6. TEST CASES

6.1 SignIn authentication

Figure 6.1 User sign in

Figure 6.2 authorized user Signed In



Figure 6.1 and 6.2 shows that only authorized user can signed in.so only authorized user can book their trip.

6.2 Email And Other Validation

Figure 6.3 validation in SignUp page



Figure 6.4 validation in search hotel

Figure 6.5 validation in rentalcar



Figure 6.6 validation in contact

Figure 6.7 validation in update rentalcar



Figure 6.8 validation in update Hotel

As shown in above figures we can validate email address, date as well as each fields. So we can prevent datalog to enter invalid information. hence we can make the application is reliable. As shown in figure above we can also provide validation to prevent the duplication of data in database.hence we can serve best services for the user.



CONCLUSION

Trip Booking provides 24/7 support for user to book their trip. The application enable

to user to do the things like searching, booking their trip in their benefit cost. With online Trip booking systems, users have the freedom of choosing the service or

merchandise among what is available and knowing precisely what they are getting. Since the reservation is made in real time, the user receives immediate assurance that what he wants is or is not available.

Also, because users conduct their own transactions and receive confirmations, they are free to make changes during even after the process, with minimum of complicating factors.



REFERENCES

• www.google.co.in

• www.w3schools.org

• www.wikipedia.org

• www.Tutorialspoint.com

• www.roseindia.net

• www.stackoverflow.com

• www.ibm.com