Government Engineering College, Modasa Computer Engineering 2013

ID:130007235 Travel habit website
GOVERNMENT ENGINEERING COLLEGE,

MODASA
COMPUTER ENGINEERING
2013
CERTIFICATE
Date:
This is to certify that the dissertation entitled “TRAVEL HABIT WEBSITE” has been carried
out by 1. KADIVAR KRIAHNA 2. PANDAYA DIPALI 3. BARIA SHILPA under my
guidance in fulfillment of the degree of Bachelor of Engineering in COMPUTER
ENGINEERING (7th Semester) of Gujarat Technological University, Ahmedabad during the
academic year 2013.
GUIDES: 1. Mr. Hardik Patel
HEAD OF THE DEPARTMENT
1
ACKNOWLEDGEMENT
As human being, it is quite apparent that we have limited knowledge, but we have
always tried to make the most of what we know, I would there for, like to begin by thank in
mighty, who is the ocean of knowledge for helping us to undertake many in such a big
enterprise as we have done.I would like to give sincere thanks to Pro. J.S.Dhobi , Head of
Computer
Department who gave us opportunity to get Industrial Training in our last year First, I would
like to thank Mr. Kevin Gajjar Director of IMPLICITSOLUTION, for providing me
opportunity to undergo training during last year.My sincere thanks to Mr. Bhavin Thakkar
Project Manager of the company forproviding me this wonderful opportunity at their
company. I also want to
sincere thanks Prof. Hardik Patel, who gave us valuable guidance during the project.
I would also like to thank all Engineers of our company for providing me the
opportunities of working on live projects. This has taught and industryperspective of many
issues involved in the process of programming troubleshooting. The people and atmosphere
of IMPLICIT has given me a rich repertoire of experience, I shall always guide me
throughout my career. Last but
not least I would like to thank my parents and other family members who always guided me
throughout the part of success and our friends who have helped indirectly through the entire
project and also have been source of encourage
-krishna kadivar
- dipali pandya
- shilpa baria
2
ABSTRACT
Travel habit website basically dot net technology based application which improves
Website knowledge of student.
This Project is aimed at developing online information about this web

Site. This is Web based tool. Any users can Registration or Cancellation of ticket in online
System. Even System will Provide Suggestions about other Service providers When
Particular Service is Cancelled So user doesn't have to spend much time on finding the
information.
Website development will be on module based so future enhancement will be easy one. All
users will get this message in form of push notifications So for reading this notification user
doesn't have to open the Web site.
User can select the train, buses or any other daily or regular based private vehicles and can
select the timing.
3
INTRODUCTION
With Implicit, you will acquire a complete set of customized software, IT
consultation, and its solutions. Our team of business technology professionals and software
engineers will assists you in every sphere of hurdle and problem. With four years of
experience and training that, span the spectrum of platforms of skills and endeavor. Our
systematic functional approach, ringing on your doorsteps with information technology
environments, different databases and bequeaths technologies. “What we articulate today
others adopt tomorrow. Our customer centric and relationship management will accomplish
in a streamline to achieve the customer satisfaction. Our visionary perception to achieve the
target within necessary deadline allotted. Our creative attitude and time management will
bring the bright future.”
Shared values methodologies have been at the heart of Implicit since our inception. These
values influence our way of culture while interacting with clients to promote ethically sound
practices in business relations.
Honesty:
Established transparent rules and obligations in any kind of proposal or Contract
Audacity:
Entrepreneurship in sense of risks, balanced by prudence and clearsightedness
Loyalty and trust:

Empowers employees and teams and allow managers to experience the effects of
their initiatives and decisions. Open minded and genuine
transparency in transferring of information worldwide.
Independency:
Includes creativity, innovation, and openness in mind in respect of other diverse culture,
customs, habits, and environments. Team spirit: To build a better framework in company
affairs employees’ motivation is very necessary in terms of teambuilding and efforts.
Involvement: Right kind of approach and involvement is necessary for any developing
company
Fun:
It is difficult to imagine any corporate vision, implementation and rejuvenation of a company.
Bestow it solution provider “Implicit adopt policies and methodologies to meet customer’s
requirements by delivering best output software solution within budget in real time.” At
Implicit, technology meets creativity and our strength lies in seamlessly merging the two
disciplines to create unique, user-driven solutions for our clients. Our IT solutions help not
only big organization but also small and medium size. We cater to specific needs of clients
across various industries. Our IT professionals implement and customize all the programming
and software services with quality software development andit implementation. Our services
are cost effective and competitive as well. Our on prompt action results in satisfied customer.
More than eight years of hard-core experience in the field of information technology, provide
solutions in various languages specially .NET and PHP. Implicit is a fast developing IT
company with the state of an art technology with determined people.
4
LIST OF TABLES
Sr. Table no. Name of table Page no.
No.
1 2.1.3 Roles and Responsibility 14
2 2.2.2 Risk Analysis 16
3 2.2.3 Risk Planning 16
4 4.7.3 Registration 41
5 4.7.3 Vehicle Type 41
6 4.7.3 Vehicle Information 41
7 4.7.3 Package 42
8 4.7.3 Reservation 42
9 4.7.3 Route Information 43
10 4.7.3 Payment Method 44
11 4.7.3 Payment 45
12 4.7.3 Package Seletion 46
13 4.7.3 Notification 47
14 4.7.3 Comments 47
15 4.7.3 Rating 48
16 4.7.3 CMS 49
17 4.7.3 Admin 49
18 4.7.3 Feedback 50
5
LIST OF FIGUERS
Sr. Figure No Figure Description Page No

no.
1 2.1.1 Project Development Approach 12
2 2.3 Schedule Representation 17
3 4.1 Class Diagram 19
4 4.2 Use case Diagram 20
5 4.3.1 Activity Diagram for admin 22
6 4.3.2 Activity Diagram for User 23
7 4.4.1 Sequence Diagram for admin 24
8 4.4.2 Sequence Diagram for user 25
9 4.5 E-R Diagram 26
10 4.6.1 data flow Diagram 27
6
TABLE OF CONTENTS
Acknowledgement
Abstract
List of Figures
List of Tables
Table of Contents
Chapter 1: Introduction
Chapter 2: Project Management
Chapter 3: System Requirement Study
Chapter 4: System Analysis
Chepter 5:Conclusion and Discussion
7
1
Introduction
Project Summary
Project Purpose
Project Scope
Technology & Literature Review
8
CHAPTER 1
INTRODUCTION
1.1 Project summery

1.2 Purpose
1.3 Scope
1.4 Technology and Literature Review
1. INTRODUCTION
1.1 Project summery
Travel Habit Website provides online information to user at airport, at rail, at AMTS stands,
at metro and user that can access online. All the data are online and up to date. This project is
useful for foreigner and localized people.
When the foreigners come in our country for the any reason, they get all the information
of registration.
1.2 Purpose
Travel Habit Website is a web application which provides services to everyone by facilities
information regarding Travelling, vehicle, Facilities, and information related the different
type of travelling.
Some people are not able to pay the travelling bill. That’s why I include the different-
different type of packages. Also contain the information regarding different type of payment
modes. Information related facilities that can admin give to the user. This project is more
effective and quick.
9
1.3 Scope
 Currently there is no generalized system which can be used as a whole in hospital. So,
everyone has to keep different system for each and every component.
 So I am going to develop a system which can be used as generalized system which

can be used in each and every area of their vehicle services is provided.
 All the information is available in this web site up to date.
 When the vehicle are add or remove in the provided routing servicesn, at that time this
information are add or remove from the website.
 Use of this website, reduce the cost and reduce consume of time.
 This website is more effective and quick for the people.
1.4 Technology and literature review
 Front-End Software:
 Visual studio 2010.
 Microsoft Visio 2007
 .NET framework 4.0
 ASP.NET /c#.NET
 Back-End Software:
 SQL server 2010
 Other Technology:
 HTML5
 CSS3
10
2
Project Management
Project Planning & Scheduling
Risk Management
Estimation
11
2. PROJECT MANAGEMENT
2.1 Project planning and scheduling
2.1.1 Project Development Approach
To developed this project we will follow the iterative model because we need
to check the tool after every development process and module weather it is working
proper or not if we check directly in the end and if some problem occurs than we
might have to change at high level which will increase the coast of project as well as
will consume more time.
 Planning and Feasibility Study
 Analysis
 Design
 Development
 Testing
 Deployment
 Release and Maintenance
[Fig1]
12
2.1.2 Project Plan

Project management is the discipline of planning, organizing and managing
resources to bring about the successful completion of specific project goals and
objectives.
The primary challenge of project management is to achieve all of the project

goals and objectives while honoring the project constraints. Typical constraints are
scope, time and budget. The secondary—and more ambitious—challenge is to
optimize the allocation and integration of inputs necessary to meet pre-defined
objectives.
Milestones:
 Studying various modules of Helpdesk Support System & its problems. Project
Planning. Have started collecting the Requirements.
 Continue with requirements of organization with regards to user of the system to

be included.
 Gathering the requirements of the project using different fact-finding techniques.
 Requirement Classification & Feasibility Study. Time, Cost, Risk & Work
Analysis. Model specification.
 Creating Custom UML design based on analysis.
 Started System Flow Diagram.
 Completed the Administrator side interface design and linked with database such
that add, update; delete to the data can be done.
 Completed the customer side interface design
 Started System Implementation with Module Specification.
 Then started implantation of administrator module as well as of report generation.
13
2.1.3 Roles and Responsibility:
Role Responsibility
Project Manager: Hardik Patel Defining requiring resources
Providing required resources
Project planning, tracking and monitoring
Team Member: Kadivar Krishna Designing and Documentation
: Pandya dipali Execution of project as defined schedule
: Baria shilpa Analysis
Testing
Software development as per the design and

documentation
Dependences:
 The success of project depends on the end-user because it is prepared for him/her.
They would decide either the Medical Tourism System is as per their requirement or
not.
 The user is aware of rules and regulations.
 The user is well familiar with the computer system and has enough basic knowledge
of computers and internet.
 Whenever the admin user wants to interact with the system he must login to the
system.
14
2.2 Risk management
Risk management is the area that tries to ensure that the impact of risks on cost, quality and
schedule is reduced.Many problems can plague a software project. Lots of things can go
wrong, many often do. It’s for this reason that being prepared – understanding the risks and
take proactive measures to avoid or manage them – is a key element of good software project
management.
Different steps in Risk management are Risk Identification, Risk Analysis and Risk Planning.
2.2.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.
 Project risk: project risks become real; it is likely that project schedule and personal
requirement problems and their impact on a software project.
o Admin not get proper information
o Proper information is not provide
 Technical risk: 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.
o Internet connection problem
o Device fail
15
2.2.2 Risk Analysis
Risk type Description/cause Probability Effects
Image quality Low resolution Low High

images may affect
the picture quality
Viruses Viruses may corrupt Medium High

the software file
System failure In case of system Low Medium

crash,development
software may get lost
2.2.3 Risk Planning
Risk type Remedies / Plans
Image quality Keep a high definition image capturing tool

for capturing images on spot
Viruses Install a good antivirus to remove the bugs
System failure Backup software should be kept/ contact

developer
16
2.3 Project scheduling
Schedule Representation.
Starting Date: 01/07/12
Customer Planning Risk Analysis

Communication
(As per First phase as per iterative model
iterative Model)
Customer Evaluation Construction Engineering
(a) First Phase
Customer
Planning Risk Analysis
Communication
(As per
iterative Model) Second phase as per iterative model
Customer Evaluation Construction Engineering
(b )Figure: Schedule Representation
17
3
System Requirement Study
User Characteristics
Hardware Requirements
Software Requirements
Constraints
CHAPTER 3
SYSTEM REQUIREMENT STUDY

18
3.1 Use characteristics
3.2 Hardware and Software Requirement
3.1 User Charecteristics
 Admin:
Has the authority to add/update/delete information related to vehicle detail,

reservation detail, route information, package information, notification and
any other information.
Admin manage the detail related the vehicle r such as vehicle category,
register vehicle detail . He also manage the FAQ.
 Register User:
The applicant Who will search the information in detail and viewing photo
gallery, vehicle, equipment information and also feedback.
 Free Traveller:
The applicant who will search the detail and get the appropriate information.
Free traveler is only view all the information online and up to date.
3.2 Hardware and Software Requirement
19
Hardware Requirement (Minimum)
Server
 Processor : Intel core i3 CPU or equivalent
 Hard Disk : 160 GB or equivalent
 System Memory : 2 GB
Client
 Mobile Phone and any other devices
Software Requirement (minimum)
Server
 Platform : .NET framework 4.0
 Operating system : Window Server or equivalent
 Web server : SQL server 2010
Client
 Operating system : Window 7 Ultimate or equivalent
 Browser : Internet Explorer, opera…
3.4 CONSTRAINTS :
3.3.1 User Interface :

The User-Interface is with desktop to visit a website.
3.3.2 Communications Interface :

Only web interaction is needed as a communication part from user.
20
3.3.3 Software Interface :

In this we require only browser that supports flash files with appropriate flash player.
3.3.4 Detailed Description of Functional Requirements :
To display various details about travel type,fares , travel related information and special
Purpose
offers.
Only registered user can do travel from the site while unregistered users can even fill
Inputs the details and can do service from this site. No registered user can not get the facilities
of traveling.
The processing contains validated data to be filled in the database means only
Processing
appropriate data will proceed.
Outputs Details information about for service of site and special offers can be seen on the site.
4
System Analysis
Requirements of System
21 Feasibility Study
Requirement Validation
Function of System
Data Modeling
Functional & Behavioral Modeling
4.1 Class-Diagram
22
23
4.2 USECASE DIAGRAM
 ACTOR:
 A coherent set of roles that users of use cases play when interacting with the use
`cases.
 USE CASE:
 A description of sequence of actions, including variants, that a system performs that
yields an observable result of value of an actor.
 UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any
product after analysis.
 Use case diagram can be useful for getting an overall view of the system and
clarifying that can do and more importantly what they can’t do.
 Use case diagram consists of use cases and actors and shows the interaction between
the use case and actors.
 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.
 A Use case is a description of set of sequence of actions. Graphically it is rendered as
an ellipse with solid line including only its name. Use case diagram is a behavioral
diagram that shows a set of use cases and actors and their relationship. It is an
association between the use cases and actors. An actor represents a real-world object.
Primary Actor – Sender, Secondary Actor Receiver.
Use Case Diagram graphically represents the interaction between the system and its
environment. They graphically describe who will use the system and what ways the
user expects to interact with the system. A Use Case Diagram shows actors, use cases
and their relationships.
24
Use Case Diagram
25
4.3.1 Activity diagram for Admin
26
4.3.2 Activity diagram for user
27
4.4.1 Sequence- Diagram for Admin
28
4.4.2Sequence- Diagram for User
29
4.5 E-R Diagram
30
4.6 .1Data-Flow Diagram(Level -0)
31
4.6.2. Data-Flow Diagram(Level -1)
32
33
5
System Design
Database Design
Relationships
System Procedural Design
34
Data Dictionary
1 Admin Master
2 Booking Master
3 Vehicle Master
4 Payment
5 Contact
6 Comment Master
7 Seat Master
8 User info
9 City Master
10 Feedback
1. ADMIN Master:-
Sr No. Field Name Data Type DESCRIPTION

1 Aid Int Unique key
2 Aname Nvarchar Store name
3 Uname Nvarchar Store address
4 Upass Nvarchar Password of admin
5 Entrydate datetime date
6 Cpass Nvarchar Confirm password
35
2. Booking Master:-
Sr No. Field Name DATATYPE DESCRIPTION
1 Bid Int Autoincrement
2 Vname Nvarchar Store name
3 Email Nvarchar Store detail
4 Totalseat int Total booking seat
5 Totalfares int Store total fares
6 Paymethod Nvarchar Store paymethod
7 Bankname Nvarchar Store bankname
8 Card no float Store card no
9 CCV no int Store ccv no
10 Branch name Nvarchar Branch name
11 status int Status
3. Vehicle Master
Sr no. Field Name DATATYPE DESCRIPTION
1 Vid Int Autoincrement
2 Vname Nvarchar Name of vehicle
3 Detail Nvarchar Detail of vehicle
4 Rto no Int Rto no of vehicle
5 Images image Image of vehicle
6 Arrivalplace Nvarchar Store arriavl place
7 Diparture Nvarchar Store diparture place
8 Totalseat int Store Total seat
9 Fares double Store fares
10 Entrydate datetime Entry date
11 Type Nvarchar Store type
12 Contact no float Store contact no
13 Time Nvarchar Store time
14 Comment Nvarchar comment
36
4. PAYMENT:-
Sr no. Field name DATATYPE DESCRIPTION
1 Bid Int Unique key
2 Vtype Nvarchar Store vehicle type
3 Arrival Nvarchar Store arrival place
4 Departure Int Store departure place
5 Amount Int Store amount
6 Totalseat Int Store total seat
7 Totalfares Int Total fares
8 Email Nvarchar User email id
9 Bank name Nvarchar Store bank name
10 Branch name Nvarchar Store branch name
11 Payment type Nvarchar Payment type
12 ATM type Nvarchar Atm type
13 Card no Int Store card no
14 CCV no Int Store CCV no
15 Vname Nvarchar Vehicle name
16 Status Int Store status
5. Contact:-
1 Cid Int Unique key
2 Cname Nvarchar Contact name
3 Cemail Nvarchar Store email id
4 Cmobile no float Store mobile no
5 Cmessage Nvarchar Store message
6 Entry date datetime Store date
6. Comment Master:-
1 Cmid Int Unique key
2 Uname Nvarchar User name
3 Vname Nvarchar Store vehicle name
4 Comment Nvarchar Store comment
5 Entry date datetime Entry date
37
7. Seat Master:-
1 Sid Int Autoincrement
2 Vname Nvarchar Vehicle name
3 Totalseat Int Store total seat
4 Bookseat Int Store booking seat
5 Available seat Int Store available seat
8. Userinfo:-
1 UID Int User id
2 Fname Nvarchar First name of user
3 Lname Nvarchar Store last name
4 Address Nvarchar Store address
5 City Nvarchar Store city
6 Pincode Int Store pincode
7 Contact no Float Store Contact no
8 Email Nvarchar Store Email id
9 Uname Nvarchar User name
10 Upassword Nvarchar Password of user
11 Entry date datetime Store date
38
9.City Master:-
Sr No. Field Name DATATYPE DESCRIPTION
1 Cid Int Autoincrement
2 Cname Nvarchar City name
10. FEEDBACK:-
1 Fid Int Autoincrement
2 Email Int Based on PK
3 Feedback Nvarchar Store feedback
4 Status Nvarchar Store status
5 Aid Int Store id
39
CHAPTER 5
CONCLUSIONS AND DISCUSSION
5.1 Self Analysis of Project Viabilities
5.2 References
5.1 Self Analysis of Project Viabilities
Software will definitely undergo change once it is delivered to the customer. There are
many reasons for the change. Change could happen because of some unexpected input
values into the system. In addition, the changes in the system could directly affect the
software operations. The software should be developed to accommodate changes that
could happen during the post implementation period
5.2 References
1. Professional Asp.Net (Wrox Publication). We have used this book to get the
fundamental knowledge of Active Server Pages.
2. Asp.Net Complete Reference.
3.Sql Server 2005 (Wrox Publication)
4. www.wikipedia.com
We used this site to enhance our knowledge about various fundamentals and concepts.
40
41

Government Engineering College, Modasa Computer Engineering 2013

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Government Engineering College, Modasa Computer Engineering 2013

Transféré par

Droits d'auteur :

Formats disponibles

ID:130007235 Travel habit website

GOVERNMENT ENGINEERING COLLEGE,

GUIDES: 1. Mr. Hardik Patel

HEAD OF THE DEPARTMENT

This Project is aimed at developing online information about this web

Loyalty and trust:

Sr. Figure No Figure Description Page No

Chapter 2: Project Management

Chapter 3: System Requirement Study

Chapter 4: System Analysis

Chepter 5:Conclusion and Discussion

Technology & Literature Review

1.1 Project summery

 So I am going to develop a system which can be used as generalized system which

 All the information is available in this web site up to date.

 This website is more effective and quick for the people.

1.4 Technology and literature review

 Visual studio 2010.

 Microsoft Visio 2007

 .NET framework 4.0

 SQL server 2010

Project Planning & Scheduling

2.1.2 Project Plan

The primary challenge of project management is to achieve all of the project

 Continue with requirements of organization with regards to user of the system to

 Gathering the requirements of the project using different fact-finding techniques.

 Creating Custom UML design based on analysis.

 Started System Flow Diagram.

 Completed the customer side interface design

 Started System Implementation with Module Specification.

 Then started implantation of administrator module as well as of report generation.

2.1.3 Roles and Responsibility:

Project Manager: Hardik Patel Defining requiring resources

Providing required resources

Project planning, tracking and monitoring

Team Member: Kadivar Krishna Designing and Documentation

: Pandya dipali Execution of project as defined schedule

: Baria shilpa Analysis

Software development as per the design and

 The user is aware of rules and regulations.

2.2 Risk management

2.2.1 Risk Identification

Risk identification is a systematic attempt to specify threats to the project

o Admin not get proper information

o Proper information is not provide

o Internet connection problem

2.2.2 Risk Analysis

Risk type Description/cause Probability Effects

Image quality Low resolution Low High

Viruses Viruses may corrupt Medium High

System failure In case of system Low Medium

2.2.3 Risk Planning

Risk type Remedies / Plans

Image quality Keep a high definition image capturing tool

Viruses Install a good antivirus to remove the bugs

System failure Backup software should be kept/ contact

2.3 Project scheduling

Starting Date: 01/07/12

Customer Planning Risk Analysis

(As per First phase as per iterative model

Customer Evaluation Construction Engineering

(a) First Phase