Tourist Help Center (GPRS)

Tourist Help Center

System Analysis and Design Report

MCA IV Semester

Session: 2007 - 2010

Guide Submitted by
Mr. Rajeev Mathur Abhishek Singh
(Director, Department of Computer Science) Rajat Patwa
MCA IV Semester

Lachoo Memorial College of Science & Technology

Jodhpur, Rajasthan.

MCA 2007-2010 -1-

 Tourist Help Center (GPRS)

DEPARTMENT OF COMPUTER SCIENCE

LACHOO MEMORIAL COLLEGE OF SCIENCE & TECHNOLOGY
JODHPUR, RAJASTHAN

CERTIFICATE

This is to certify that project entitled “Tourist Help Center (GPRS)” has
been analysis and designed by:

Mr. Abhishek Singh

Mr. Rajat Patwa

In partial fulfillment of MCA IV Semester

Mr. Rajeev Mathur R L Mathur

(Director of DOCS) (Principal)
(Project Guide)

Date:

MCA 2007-2010 -2-

 Tourist Help Center (GPRS)

Acknowledgement

Despite the project “Tourist Help Center (GPRS)” is made by us. We like
to acknowledge the people for their guidance and encouragement to make this
project successful.

First of all, we are thankful to “Rajasthan Technical University” for

putting this practical paper in curriculum, which provides real world experience
before degree completion.

We can’t able to express our deep gratitude to “Mr. Rajeev Mathur

(Project Guide)” for this maiden experience of prepare a project report. Not only
for his guidance but also for encouragement and make faith in ourselves.

Our Sincere thank to “Mr. R.L. Mathur (Principal)” for inspiration and
precious help to make project a reality.

We are also obliged to “Mr. Priyadarshi Patni (Associate Professor)” and

Mr. Mukesh Upadhayay (Associate Professor) for his co-guidance. We are
thankful for invaluable helps in primary investigation of our project to the
completion of project.

Our special thanks to “Mr. Ashok Vyas (RTDC, Jodhpur)” and “Mr. Maan
Singh Rathore (Tourist Reception Center, Jodhpur)” for their kind help in
investigations and creative ideas. We are also thankful staff members of tourism
department.

Our deep thanks to staff members of “Department of Computer Science” for

their direct and indirect help in completion of project.

At last our deep gratitude to our parents, friends and great God for blessings
and encouragement.

Abhishek Singh
Rajat Patwa

MCA 2007-2010 -3-

 Tourist Help Center (GPRS)

Contents

1. Introduction
1.1 Abstract
1.2 Problem Definition
1.3 Project Innovation
2. Feasibility Study
2.1 Economical Feasibility
2.2 Technical Feasibility
2.3 Behavioral Feasibility
3. System Analysis
3.1 Data Flow Diagram
3.2 E R Diagram
4. System Design
4.1 Data Base Tables
4.2 Input/Output Forms
5. Conclusion
5.1 Advantages
5.2 Limitations
5.3 Future Expansions
6. Bibliography

MCA 2007-2010 -4-

 Tourist Help Center (GPRS)

Introduction

MCA 2007-2010 -5-

 Tourist Help Center (GPRS)

Introduction
1.1 Abstract
Now these days we are living in the world of the TECHNOLOGY. All the manual
processes are turning into an automated system. As we all know that today mobile
have become inevitable part of everyone’s life because of different reasons.

The first reason behind this is that they are affordable and suits to everyone’s
pocket as they come in different price ranges. But this is not the only reason. Also
different features and functionalities provided in the mobiles like chatting, SMS
(Short Message Service), MMS (Multimedia Message Service), internet
accessibility (GPRS), MP3 player, camera, voice and video recording, 2D and 3D
games and many more features had made mobiles important in life.

So keeping in mind the capabilities of mobile we selected this project so as to add

one more important & intelligent feature to mobile.

Following features of our project will definitely give a fair idea of how it is
worthwhile to user:

ü User can easily get the information from any where and at any time.
ü This entire project saves tourist’s energy & time because user can easily get
the information only by pressing button.
ü On the top of it, this project uses strong password protection system to
protect from any unauthorized access at server side.
ü Administrator can easily maintain all the information about Locations,
Accommodations, Cities, Transportations, etc with the help of our project.

Our project “Tourist Help Center (GPRS)” as the name suggests designed for
mobile device having GPRS Facilities. This will help a tourist to display all the
information on mobile about the particular location, accommodations,
transportations, fare charges, eating outs, etc in which he is living (resident).

1.2 Problem Definition

Indian tourism sector is a great industry which provides great employment. But in
present scenario tourism sector facing many problem like tourists get cheated by
unauthorized people (Lapka) and situation going worst day by day, to protect them
we made laws against it; but still it is not sufficient enough to overcome situation.

MCA 2007-2010 -6-

 Tourist Help Center (GPRS)

As complain centers are static and, it can’t assume that everyone have enough
knowledge about it.

Another problem is that we still providing traditional knowledge acquisition tools

like help desk, hand books, tourist reception centers, static websites etc. which
provides insufficient and incorrect information sometimes, so it is not trustworthy.
Help desks and reception centers need tourist to go physically, which is not
economic.

In present system when tourists come to any city they are not aware about
distances, fares has to pay for cabs, hotel charges, emergency services, and contact
persons for some enquiry. To solve this it is not possible to make physical offices
at every part of city.

In the field of tourism, tourist belongs from different countries with different
language understandings, so requires interpreters, but there is no such way
provided in current system to find & contact right person.

1.3 Project Innovations

ü Computerization of information system.
ü 24X7 availability.
ü Distance calculation between current location and destination.
ü Fare calculation for different type of cabs.
ü Listing hotels according to budget and choice.
ü List of important tourist places of city, fairs etc.
ü Contact information to contact right person in emergency.
ü List of guides, translators with information that they are vacant or engaged.
ü Listing eating outs.

MCA 2007-2010 -7-

 Tourist Help Center (GPRS)

Feasibility Study

MCA 2007-2010 -8-

 Tourist Help Center (GPRS)

Feasibility Study
Provided data about users requirements, full identification of system objectives, a
feasibility study is carried out to select the best system that meets performance
standards.

Any system performance is judged under 3 steps:

ü Statement of constraints: Encompassing all the factors that limit

the solution of the problem.
ü Identification of specific system objectives.
ü Description of outputs as required by the users.

There are 3 types of feasibility considerations

2.1 Economical Feasibility

The proposed system is one-time investment considering capitals costs:

ü Hardware Cost
ü Software Infrastructure Cost
ü Software Development Cost
ü Software Deployment Cost

However, the proposal system may incur equipment operational costs such
as:

ü License or equivalent fee (such as ‘annual registration fee’)

imposed by the organization.
ü Public utilities such as telephone service, Internet Connectivity.
ü Maintenance cost.

MCA 2007-2010 -9-

 Tourist Help Center (GPRS)

2.2 Technical Feasibility

Technical feasibility centers on the following situations:

ü Whether the current/existing manual process of the system is

compatible enough to accommodate technical enhancements
accommodated by the proposed candidate system.
ü Hardware or software repairs and availability and maintenance in
case of damage or wear-tear.

In our project “Tourist Help Center (GPRS)” we propose the following software
and hardware:

Software Requirements

ü ASP.NET framework.
ü MS-Access (Database) or Oracle 10G
ü Microsoft Windows XP (OS)
ü Sun Java 2 Micro edition

Hardware Requirements

ü For Server:

• 128 MB RAM (256 MB Recommended)

• 40 GB Hard Disk

ü For Client or Mobile user:

• 128kb ROM for JVM and System classes

• 32kb RAM (min) for Application classes

2.3 Behavioral Feasibility

People always resist Change. Any user staff finds it uneasy to switch over man-
managed system to computer managed system due to lack of computer
knowledge.

MCA 2007-2010 - 10 -
 Tourist Help Center (GPRS)

The proposed system is quite:

ü User friendly
ü Interactive
ü The user need not require any profound technical knowledge or skills
to use the system.

By the above discussion, we conclude that, the proposed system considered

in all aspect i.e. economically, technically and behaviourally feasible.

MCA 2007-2010 - 11 -
 Tourist Help Center (GPRS)

System
Analysis

MCA 2007-2010 - 12 -
 Tourist Help Center (GPRS)

3.1
Data
Flow
Diagrams

MCA 2007-2010 - 13 -
 Tourist Help Center (GPRS)

Context Diagram: DFD Level 0

Context Diagram

ADMINISTRATOR

Insert, Delete, Update Data Authentication

Tourist Help
Center
(Information)
System

Query Submit Result

(Response)

TOURIST

MCA 2007-2010 - 14 -
 Tourist Help Center (GPRS)

Data Flow Diagram Level 1

DFD Level 1

ADMINISTRATOR

User Id,
Password
Information Data Entries
Login successful /
Unsuccessful

1.0
Login 2.0
Authentication
Process Data
Complaint Info
Entry
(through Process
E-mail)
User Id, Password verification
Data (Help center information)

4.0 HELP CENTER DATA BASE

Complaint
Posting Complaint
Process
Query to Database

Query Result
Complaint 3.0
Information
Search Query Retrieval
process

TOURIST(S) Response

MCA 2007-2010 - 15 -
 Tourist Help Center (GPRS)

DFD Level 2(Information Retrieval Process)

DFD Level 2

TOURIST(S)

Request for Location Name

Information Page Fare for Cab
Distance
Static Html Page Type of Vehicle

3.2 Distance
Distance
3.1 Calculation
Static Process 3.3
Information Fare
Search Calculation
Process Process

Current,
Destination
Name
Fare Chart
Requested Info Data Location Coordinates
(Longitude, Latitude)

HELP CENTER DATA BASE

MCA 2007-2010 - 16 -
 Tourist Help Center (GPRS)

3.2
Entity
Relationship
Diagrams

MCA 2007-2010 - 17 -
 Tourist Help Center (GPRS)

Entity-Relationship Diagrams
1. Tourist - Hotel ER (Accommodation searching)

Alt_Num
Location

Contact_No
Hotel_Name Tariff_Start
E-mail

Date_Time

Hotel_Type
IP_ADR Complaint

Tariff_End

Hotel_Id

tourist searches hotel

MCA 2007-2010 - 18 -
 Tourist Help Center (GPRS)

2. Tourist – Guide ER (Availability searching)

Status Contact_No

Type
E-mail
Agent_Name Alt_No
Date_Time

IP_ADR Complaint
Aggent_Id

tourist availability_ guide

search

MCA 2007-2010 - 19 -
 Tourist Help Center (GPRS)

3. Tourist – Administrator ER (Complaint posting)

Contact_No

E-mail

E-mail Password

Date_Time Designation
User_Name

IP_ADR Complaint Login_Id

tourist complaints administrator

MCA 2007-2010 - 20 -
 Tourist Help Center (GPRS)

4. Administrator - Guide ER (Status update)

Contact_No

E-mail Type Status

User_Name
Alt_No

Contact_No Agent_Name
Password

Aggent_Id
Login_Id Designation

administrator Status_update guide

MCA 2007-2010 - 21 -
 Tourist Help Center (GPRS)

System
Design

MCA 2007-2010 - 22 -
 Tourist Help Center (GPRS)

4 .1
Database
Tables

MCA 2007-2010 - 23 -
 Tourist Help Center (GPRS)

Database tables

1. Admin_Master Table
Field Name Data type / Size Description
Constraints
Login_Id Varchar 10 Administrator ID
Password Password 20 Password
Username Varchar 50 Name
Contact_No Integer 12 Contact_No
E-mail Varchar 50 E-mail
Designation Varchar 20 Designation

2. TP_Master Table
Field Name Data type / Size Description
Constraints
TP_Id Varchar 10 Tourist Place Id
TP_Name Varchar 20 Tourist Place Name
TP_Loc Varchar 20 Location
Description Varchar 50 Description

3. User_Log
Field Name Data type / Size Description
Constraints
IP_Addr Varchar 32 IP Address
Date_Time Date ** Date and time
Complaint Varchar 50 complaint
Email_id Varchar 50 Email id

4. Loc_Info
Field Name Data type / Size Description
Constraints
Area_Name Varchar 50 Name of the area
Longitude Integer ** Longitude
Latitude Integer ** Latitude

MCA 2007-2010 - 24 -
 Tourist Help Center (GPRS)

5. Hotel_Info
Field Name Data type / Size Description
Constraints
Hotel_Id Varchar 10 Hotel Id
Hotel_Type Varchar 10 Hotel Grade
Hotel_Name Varchar 20 Hotel Name
Location Varchar 20 Location of Hotel
Contanct_No Integer 12 Contanct_No
Alt_Num Integer 12 Alt_Num
Tariff_Start Integer 10 Starting Tariff
Tariff_End Integer 10 Ending Tariff

6. Guide_Info
Field Name Data type / Size Description
Constraints
Agent_Id Integer 10 Agent Id
Agent_Name Varchar 20 Name of the Agent
Type Varchar 20 Type of Agent
Contact_No Integer 12 Contact Number
Alt_Num Integer 12 Alternate number
Status Varchar ** Agent Status

7. Fare_Master
Field Name Data type / Size Description
Constraints
Vehicle_type Varchar 20 Vehicle Type
Charge_1st_KM Integer ** Charges for the 1st
KM
Charge_Per_KM Integer ** Charges Per KM

MCA 2007-2010 - 25 -
 Tourist Help Center (GPRS)

8. Emer_Cont_Master
Field Name Data type / Size Description
Constraints
Srevice_Type Varchar 10 Type of Service
Adress_Line1 Varchar 50 Address
Area Varchar 20 Area
City Varchar 20 City
Contact_No Integer 12 Contact Number
Alt_Num1 Integer 12 Alternate Number1
Alt_Num2 Integer 12 Alternate Number2
ESP_Name Varchar 20 ESP Name

9. Eating_outs_Master
Field Name Data type / Size Description
Constraints
Registration_No Varchar 10 Registration
Number
EO_Name Varchar 20 Name of the Eating
Out
Location Varchar 20 Location
Food_Type Varchar 10 Type of Food

MCA 2007-2010 - 26 -
 Tourist Help Center (GPRS)

4.2
Input/Output
Forms

MCA 2007-2010 - 27 -
 Tourist Help Center (GPRS)

Input/Output Forms
1. Administrator Login Form

2. Administrator Task Control (Pick A Task)

MCA 2007-2010 - 28 -
 Tourist Help Center (GPRS)

3. User Task Control (Pick A Task)

MCA 2007-2010 - 29 -
 Tourist Help Center (GPRS)

4. Administrator Forms
Figure 4.1

Figure 4.2

MCA 2007-2010 - 30 -
 Tourist Help Center (GPRS)

Figure 4.3

Figure 4.4

MCA 2007-2010 - 31 -
 Tourist Help Center (GPRS)

Figure 4.5

Figure 4.6

MCA 2007-2010 - 32 -
 Tourist Help Center (GPRS)

Figure 4.7

Figure 4.8

MCA 2007-2010 - 33 -
 Tourist Help Center (GPRS)

Figure 4.9

Figure 4.10

MCA 2007-2010 - 34 -
 Tourist Help Center (GPRS)

Figure 4.11

Figure 4.12

MCA 2007-2010 - 35 -
 Tourist Help Center (GPRS)

Figure 4.13

Figure 4.14

MCA 2007-2010 - 36 -
 Tourist Help Center (GPRS)

Figure 4.15

Figure 4.16

MCA 2007-2010 - 37 -
 Tourist Help Center (GPRS)

5. User (Tourist) Forms

Figure 5.1

Figure 5.2

MCA 2007-2010 - 38 -
 Tourist Help Center (GPRS)

Figure 5.3

Figure 5.4
Figure 5.4.1

Figure 5.4.2

MCA 2007-2010 - 39 -
 Tourist Help Center (GPRS)

Figure 5.5
Figure 5.5.1

Figure 5.5.2

MCA 2007-2010 - 40 -
 Tourist Help Center (GPRS)

Conclusion

MCA 2007-2010 - 41 -
 Tourist Help Center (GPRS)

Conclusion
5.1 Advantages
ü It reduces man power from help centers so save governments money,
can be use in other development areas.
ü It is a mobile based application so user can get information any time
(24x7).
ü It reduces use of paper in printing catalogues etc. so it saves
environment as well.

5.2 Limitations
ü User must have a GPRS enabled mobile.
ü Application run only on JAVA enabled mobile so JVM must be
installed in mobile.
ü User need to establish connection with server for requests and access
information.
ü User has to contact himself/herself to emergency service provider, no
information will send by application.

5.3 Future Expansions

ü To provide SMS center so that more people who don’t have GPRS
enabled mobile can also use application.
ü To provide chat room so that people can get guidelines from mentors
online in emergency.
ü To design proxy server system so that actual server burden can be
reduced.

MCA 2007-2010 - 42 -
 Tourist Help Center (GPRS)

Bibliography

MCA 2007-2010 - 43 -
 Tourist Help Center (GPRS)

Bibliography
References
ü A. Silberschatz, Henry F. Korth and S. Sudarshan “Database System
Concept”.
ü Elias M. Awad “System Analysis and Design” Galgotia Publication Ltd.

MCA 2007-2010 - 44 -