Final Tour & Travel Final Project Report, Aman, 2819154

/Tour//&/Travel///Management/System
//////////////////////////////////Report/
on/
Tour/&/Travel/ Management/System
Submitted/in/partial/fulfillment/of/the/requiremen
ts/for/the/award/of/the/degree/of/
Bachelor/of/Technoloy
/in/
Computer/Science/&/Engineering/ /
Submitted/By/
Aman/Gupta
Under/the/Supervision/of//
////////////////////////////Dr.Deepti/Dhingra/
Assistant/ Professor
Panipat/Institute/of/Engineering/&/Technology,/Samalkha
,/P anipat
Affiliated/to//
/
Kurukshetra/University/Kurukshetra,/India
/(2022-2023)/
Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-1

Table/of/Contents
DECLARATION ........................................................................................................................ii
CERTIFICATE .......................................................................................................................... iii
ACKNOWLEDGEMENT .........................................................................................................iv
ABSTRACT............................................................................................................................... v
CHAPTER/1:/INTRODUCTION........................................................................................... 9
1.1 Topic/of/the/System .................................................................................................... 9

1.2 Project/Abstract ........................................................................................................... 9
1.3 Purpose/of/the/System ................................................................................................. 9
1.4 Target/User .................................................................................................................. 9
1.5 Topic/Background ....................................................................................................... 9
1.6 Problem/Context ........................................................................................................ 10
1.7 Objectives/of/the/System........................................................................................... 13
1.7.1 Project/Objectives .............................................................................................. 13
1.7.2 Learning/Objectives ........................................................................................... 13
1.8 Scope/of/the/System .................................................................................................. 14
1.9 Limitation/of/the/System ........................................................................................... 14
1.10 Success/Criteria ......................................................................................................... 15
1.11 Functionalities/of/the/System .................................................................................... 15
1.11.1 Core/Features ..................................................................................................... 16
1.11.2 Enhanced/Features ............................................................................................. 16
1.11.3 Special/Features ................................................................................................. 17
1.13 Conclusion ................................................................................................................. 17
CHAPTER/2:/ PROBLEM/DESCRIPTION ...................................................................... 18
2.1 Current/Problem/Description .................................................................................... 18

2.1.1 Description/of/Problem/Area ............................................................................. 18
2.2 Problem/Importance/and/Justification....................................................................... 18
2.3 Proposed/Solution...................................................................................................... 18
2.4 Nature/of/Challenge................................................................................................... 19
2.4.1 Domain/Challenge ............................................................................................. 19
2.4.2 Technical/Challenge........................................................................................... 19
2.5 Feasibility/Study ........................................................................................................ 20
2.5.1 Technical/Feasibility .......................................................................................... 21

2.5.2 Economic/Feasibility ......................................................................................... 22

2.5.3 Schedule/Feasibility ........................................................................................... 22
2.6 Conclusion ................................................................................................................. 23
CHAPTER/3:/ LITERATURE/REVIEW ........................................................................... 24
3.1 Introduction/to/Literature/Review ............................................................................. 24

3.2 Advanced/Preliminary/Research ............................................................................... 24
3.3 Academic/Research ................................................................................................... 24
3.3.1 Software/Methodology/and/Software/Engineering/Concepts ........................... 25
3.3.3 Project/Management/Principles ......................................................................... 25
3.4 Domain/Research ...................................................................................................... 26
3.4.1 Desktop/Application/Development.................................................................... 26
3.4.2 Desktop/Architecture ......................................................................................... 27
3.4.3 Security/and/Permissions ................................................................................... 28
3.5 Critical/Evaluation/of/Literature/Review .................................................................. 28
3.6 Critical/Success/Factor .............................................................................................. 28
3.7 Conclusion ................................................................................................................. 28
CHAPTER/4:/ RESEARCH/METHODS............................................................................ 30
4.1.1 Primary/Research ............................................................................................... 30

4.1.2 Questionnaire ..................................................................................................... 30
4.1.3 Interview ............................................................................................................ 31
4.2 Secondary/Research .................................................................................................. 32
4.2.1 Technical/Research ............................................................................................ 32
4.3 Conclusion: ................................................................................................................ 36
CHAPTER/5:/ ANALYSIS ................................................................................................... 37
5.1 Analysis/of/Questionnaire ......................................................................................... 37

5.1.1 Overall/conclusion/of/Questionnaire ................................................................. 37
5.2.1 Overall/conclusion/of/Interview ........................................................................ 37
CHAPTER/6:/ SYSTEM/DESIGN....................................................................................... 38
6.1 Introduction ............................................................................................................... 38

6.2 UML/Diagram ........................................................................................................... 38
6.2.1 Use/Case............................................................................................................. 38
6.2.2 Use/diagram/of/login ......................................................................................... 38

6.2.2 Sequence/Diagrams............................................................................................ 54
6.2.3 Activity/Diagram ............................................................................................... 60
CHAPTER/7:/ IMPLEMENTATION ................................................................................. 62
7.1 Introduction ................................................................................................................. 62

7.2 Tools/for/implementation ........................................................................................... 62
7.3 Implementation/plan ................................................................................................... 63
7.3.1 Implementation/Approach ....................................................................................... 63
7.3.2./ Implementation/Approach/Steps ........................................................................... 63
7.3.3 Implementation/of/complex/modules ................................................................... 64
7.4 Technical/Quality/and/other/features ........................................................................ 65
7.4.1 Memory/Utilization ............................................................................................... 65
7.4.2 Performance ........................................................................................................... 65
7.4.3 User/interface........................................................................................................ 65
CHAPTER/8:/TESTING ....................................................................................................... 66
8.1 Tasks/to/be/analysed.................................................................................................. 66
8.2 Test/group .................................................................................................................. 66
8.3 Testing ....................................................................................................................... 67
CHAPTER/9:/CRITICAL/EVALUTION ........................................................................... 70
9.1 Critical/Evaluation..................................................................................................... 70
9.2. Factors/of/Benefit/(Usefulness/of/System/to/Target/Audience) ............................... 70
9.3 Degree/of/Success ..................................................................................................... 71
9.3.1 Critical/Appraisal ............................................................................................... 71
CHAPTER/10:/CONCLUSION ........................................................................................... 72
10.1 Limitation/and/Error/in/the/Developed/System: ....................................................... 72

10.2 Future/Enhancement .................................................................................................. 72
10.3 What/would/have/done/if/given/time/redo/the/project? ............................................ 72
10.4 Computational/Challenges ........................................................................................ 73
10.5 Learning/Experience/Gathered .................................................................................. 73
Chapter/11:/References ......................................................................................................... 75

DECLARATION
I/henceforth/declare/that/the/present/work/in/this/project/report/entitled/"Tour/&/Trav
el/Management/System,"/submitted/to/Kurukshetra/University,/Kurukshetra,/India/in/
partial/fulfilment/for/the/award/of/the/degree/of/Bachelor/of/Technology/in/Computer
/Science/and/Engineering.,/is/an/authentic/record/of/my/own/work/carried/out/during/t
he/period/from/January/2022/to/June/2022/under/the/advice/of/guide/Name/with/desig
nation.
I/hereby/proclaim/that/this/submission/would/be/my/own/work/and/that,/to/the/highes
t/possible/standard/and/belief,/it/contains/material/originally/released/or/written/by/an
other/person,/nor/material/that/has/been/accepted/for/a/substantial/portion/of/any/other/u
niversity/or/other/institute/of/higher/learning's/degree/or/diploma,/except/where/citati
on/has/been/made/in/the/text.
Name:/-/Aman/Gupta 2819154
////////////
/////////////Date:/-/01/06/2022

CERTIFICATE
This/is/to/certify/that/the/Project-I/report/(PROJ–CS-
302A)/entitled/“TOUR/&/TRAVEL/MANAGEMENT/SYSTEM/done/by/AMAN/GUPTA/is/
an/authentic/work/carried/out/by/him/at/PIET,/Samalkha,/Panipat/under/my/guidance./The/ma
tter/embodied/in/this/project/work/has/not/been/submitted/earlier/for/the/award/of/any/degree
/or/diploma/to/the/best/of/my/knowledge/and/belief.
Mr./Gaurav/Gambhir
Ms./Deepti/Dhingra Mr./Jitendra/Kumar
(Project/Guide) (Project/Coordinators)
Prof./Dr./S/C/Gupta
HOD/(CSE)
PIET,/Samalkha

ACKNOWLEDGEMENT
It gives us a great sense of pleasure to present the report of the B. Tech Project undertaken
during B. Tech. Pre-Final Year. We owe special debt of gratitude to Assistant Professor Ms.
Deepti Dhingra, Department of Computer Science & Engineering, PIET, Samalkha for her
constant support and guidance throughout the course of our work. Her sincerity, thoroughness
and perseverance has been a constant source of inspiration for us. It is only her cognizant efforts
that our endeavors have seen light of the day.
We also take the opportunity to acknowledge the contribution of Professor Dr. S C Gupta,
Head, Department of Computer Science & Engineering, PIET, Samalkha for his full support
and assistance during the development of the project.
We also do not like to miss the opportunity to acknowledge the contribution of all faculty
members of the department for their kind assistance and cooperation during the development
of our project. Last but not the least, we acknowledge our friends for their contribution in the
completion of the project.
//Name/:Aman/Gutpa
/
/Roll/No.:/2819154

ABSTRACT
The/system/“An/Travel/&/Tour/Management/System”/deals/with/the/Desktop/application/for/Bo
oking/Whole/Tour/and/Hotel/Booking/plan/Online./One/of/the/biggest/challenges/is/to/generate/OT
P/for/phone/number/Verification/and/Adding/the/Feature/to/payment/after/Booking/the/Hotel/room.
/Transaction/remains/in/history/forever/so/that/user/can/check/it/in/future./At/the/end/Feedback/for
m/feature/will/added/to/a/real/review/for/hotel/form/client.
One/of/the/biggest/challenges/is/to/generate/OTP/for/phone/number/Verification/and/Adding/the/Feature/to/paym
ent/after/Booking/the/Hotel/room./Transaction/remains/in/history/forever/so/that/user/can/check/it/in/future./At/the/
end/Feedback/form/feature/will/added/to/a/real/review/for/hotel/form/client.

CHAPTER/1:/INTRODUCTION
1.1 Topic/of/the/System
Title:/-/“An/Travel/&/Tour/Management/System”
1.2 Project/Abstract
The/system/“An/Travel/&/Tour/Management/System”/deals/with/the/Desktop/application/
for/Booking/Whole/Tour/and/Hotel/Booking/plan/Online./One/of/the/biggest/challenges/is/to
/generate/OTP/for/phone/number/Verification/and/Adding/the/Feature/to/payment/after/Booki
ng/the/Hotel/room./Transaction/remains/in/history/forever/so/that/user/can/check/it/in/future./
At/the/end/Feedback/form/feature/will/added/to/a/real/review/for/hotel/form/client.
1.3 Purpose/of/the/System
In/the/age/of/technologies/where/everything/is/on/our/fingertips/nobody/wants/to/stand/in/un
ending/queues/and/waste/their/precious/time./The/main/motive/of/the/application/is/to/ease/th
e/process/of/Easy/Hotel/Booking/from/online/and/payment/money/transferring/by/avoiding/t
he/hectic/process/to/stand/in/the/queue./In/the/current/scenario/many/times/we/saw/that/to/wh
en/we/go/Out/of/Station/then/there/is/a/great/problem/to/booking/hotel/Because/we/don’t/Kn
ow/any/thing/about/that/Place/,/While/by/online/booking/we/can/see/the/Review/regarding/a n
y/hotel/on/our/Application/which/was/earlier/client/Feedback.
Whenever/any/product/is/planning/to/be/made/there/is/always/a/background/study/on/the/targ
et/users./This/time/we/are/going/to/plan/for/Tour/Management/system/in/Finance/based/on/an
y/computingdevice./This/application/is/for/all/the/users/who/are/willing/to/Book/hotel/with/e
ase/and/security./Also,/this/application/used/by/the/all/Merchants/or/Hotel/Owner/who/are/fa
cing/problem/for/Less/Booking/of/Hotel/Room/by/Offline,/Via/our/application/Hotel/Owner/
can/reach/can/push/his/Hotel/Globally/ which/increase/its/profit.
1.4 Topic/Background
As/we/know/that/the/internet/plays/an/important/role/in/every/individual's/life/and/everything
/in/this/world/is/evolving/as/per/the/technology/development./At/the/outset/of/present-
day/period,/Computers/played/a/major/role/in/computing/and/as/the/technology/expands/every
thing/has/changed/and/the/computers/became/workstation/computers,/super/computers/and/so
/on./Later/developed/the/mobile/technology/and/now/mobility/got/to/be/everything./Everythi
ng/made/simple/using/mobility.

From/last/2/decades,/the/utilization/of/mobile/devices/has/incredibly/increased,/which/has/led
/to/ease/of/carrying/out/day/to/day/activities./In/addition,/with/the/advancement/of/wireless/t
echnologies,/wireless/networks/have/taken/over/the/entire/world./Nowadays,/business/and/fin
ancial/transactions/can/be/done/easily/and/securely,/anywhere/and/anytime./Using/the/Interne
t,/connections/can/be/established/with/any/devices/almost/anywhere/in/the/world/and/can/sha
re/necessary/information/amongst/them.
Since/the/customer’s/spend/most/of/their/time/online,/we/see/an/opportunity/to/Book/Hotel/R
oom/from/one/person/by/just/few/clicks./The/system/is/targeted/to/the/internet/user./This/app
lication/provides/the/facility/to/transfer/money/online./Money/can/be/transferred/from/one/us
er/to/Hotel/Owner/.
1.5 Problem/Context
In/the/Era/of/Computer/Technology,/we/need/to/communicate/and/accelerate/our/life/with/th
e/help/of/Information/and/Technology./We/all/require/certain/types/of/services/online,/which
/requires/less/workout/or/interference/of/human/being./Smart/devices/can/help/to/overcome/t
he/t rouble/of/the/customers/of/standing/and/searching/best/hotel/.There/is/lack/of/research/an
d/functionalities/in/the/current/system/as/well./We/are/in/such/an/era/today/that/our/most/of/t
he/work/has/been/shifted/to/mobiles./The/development/and/implementation/of/smart/applicati
on/which/are/more/effective/and/simpler/than/the/current/offline/market/system./We/feel/har
d/to/carry/cash/with/us/and/sometimes/it/may/be/lost.
1.5.1 Rationale/behind/the/System:/Why/do/we/need/this/System?
The/problems/that/are/traced/needs/to/be/considered/and/the/researcher/has/decided/to/constru
ct/s uch/an/desktop/application/that/would/focus/on/providing/solutions/for/the/above-
mentioned/problems.
1.5.2 Benefits/of/the/System:/What/are/the/potential/benefits/derived?
Upon/implemented,/the/system/could/bring/about/significant/tangible/and/intangible/benefits:
 Tangible/Benefits
Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

10
S./No. Tangible/Benefits Description

Users/doesn’t/have/to/pay/anything/for/using/this/s yst
em/on/their/devices./Everything/in/this/system/is/free
1. No/investment
/ of/ cost./ Even/ user/ have/ flexibility/ to/ use/ any
interface/there/is/no/restriction/in/the/system.
This/system/can/be/accessible/anywhere/if/the/user/ha
s/got/the/laptop./If/any/case/happens/that/the/mobile/i
2. Accessibility/of/system s/not/with/him/her/then/he/she/can/access/his/her/acc
ount/to/any/other/ mobile/by/just/ entering
his/her/email/and/password.
Customer/using/QR Customers/can/use/QR/code/to/make/payments.
3.
Code
View/Transaction User/have/the/option/to/view/the/transaction/paymen
4. t/receipt/.
Receipt
Hotel/P Client/can/see/Hotel/preview/,before/Booking/an
5.
review y/room/in/any/hotel.
Users/have/the/facility/to/get/select/a/plan/,/which/f urth
6. Trip/Plan er/give/you/more/facility.
.
User/has/the/flexibility/of/using/their/Laptop/to/use/th
7. Accessibility e/application/.
It/is/beneficial/for/finance/department/as/much/as/the
8. Economic/benefit user/ can/ transfer/ money/ through/ this/ application/ a
s/much/government/get/the/benefit.
Table/1:/Tangible/Benefits
 Intangible/Benefits
S./No. Intangible/Benefits Description

It/reduces/our/effort/to/great/extent./E.g./If/we/want/to
1. Reduces/effort book/hotel/then/first/we/have/to/know/all/about/th
e/hotel/,/is/that/the/hotel/is/safe/or/not/,/but/on/our

11
application/all/safe/or/best/performer/hotel/presen
t/which/is/all/maintain/by/our/developers.
This/system/ensures/ that/ user/gets/ the/ value/of/their

2. Time/Saving time/ and/ don't/ have/ to/ rely/ upon/ anybody/ else/ fo
r/placing/their/order.
The/application/that/is/developed/would/ facilitate/it
3. Friendly/User/Inte rface s/end/users/with/interactive/graphical/interfaces/that
would/be/easily/adaptable.
The/user/interface/will/be/user- friendly/and/easy/to/use
4. Customer/Satisfaction which/will/result/in/improved/satisfaction/of/th
e/customers.
This/system/will/provide/ transparency/ in/ Hotel/staf
f/and/the/client/for/better/performance/which/make/cli
5. Transparency
ent/as/well/as/Hotel/management/happy.
Maintenance/of/the/application/is/painless/for/its/user
./The/application/will/need/no/version/updates/and/he
6. Maintainability
nce/require/no/maintenance/until/the/user/transforms
the/settings/accordingly.
Keeping/in/mind/the/target/audience,/the/application/
Ease/of/learning/and will/be/designed/for/the/generalized/audience/and/hen
7.
/Usability. ce/ will/ be/ easy/ to/ use.
Table/2:/Intangible/Benefits
1.6 Objectives/of/the/System
1.6.1 Project/Objectives
In/order/to/achieve/the/aim/of/the/system,/it/is/necessary/to/achieve/the/objectives/of/the/syste
m./The/prime/objective/is/to/design/such/a/system/for/users/which/will/resolve/the/problem/of
/users/standing/in/never-
ending/queues/for/hours/just/to/get/cash./It/will/provide/transparency/between/hotel/manage
ment/and/Client/.The/other/objectives/are/summarized/below:

12
 This/system/is/basically/consisting/of/only/one/phase/i.e./the/Desktop/application./Thi
s/desktop/application/is/internally/sub/divided/into/three-
part/first/admin,/second/Hotel/management/and/last/the/users./All/the/interaction/of/u
sers/will/be/done/through/desktop/app/with/this/interface/after/the/login/and/same/for/
the/admin/and/ the/merchant/part/all/have/its/owninterface.
 Secure/data/center/is/required/to/store/and/fetch/the/data/as/per/requirement/because/i
f/the/data/is/not/secure/then/anyone/can/use/the/database/and/miss/use/the/database/wh
ich/is/not/better/for/this/application.
 To/begin/with/Desktop-
based/online/tourism/system/an/internet/connection/is/essential/to/complete/the/money
/transfer/process/at/the/end.
 Assume/that/every/8/persons/out/of/10/having/Laptop/on/which/our/application/progr
am/will/execute.
 Still/ there/ is/ a/question/ of/ gathering/ user/ information./ Before/ Booking/online/ use
r/must/have/to/register/first/and/his/her/email/mobile/and/password/for/Book/Plan/and
/room/in/hotel.
1.6.2 Learning/Objectives
The/proposed/system/will/allow/the/developer/to/attain/relevant/knowledge/and/concepts/in/s
pecializing/Desktop-
based/software/development/and/authoring/tool./The/objectives/are/disreputably/emphasized/
on/its/concepts/and/ideas/rather/than/trained/expertise./The/developer/would/have/to/undergo/
various/sections/of/software/development,/project/management,/human/computer/interaction,/
usability/factors/along/with/the/mechanisms/of/development/principles/so/as/to/produce/highl
y/reusable/quality/software/on/time./But/the/prime/aim/to/undergo/desktop/computing/conce
pts/is/to/increase/preferred/output/with/user/satisfaction/within/less/effort/and/time/to/encount
er/an/easy/solution/for/the/travel/management/online/and/reduce/all/the/efforts/that/are/requir
ed/to/book/hotel/offline.
The/following/objectives/listed/below/are/of/prime/importance/to/the/developer:/-
 Gaining/knowledge/of/Desktop-Based/development/and/XML.
 Learning/the/concepts/of/Services/such/as/Desktop/Services,/Rest/API,/Microservices/etc.

13
 Learning/how/to/deal/with/Desktop-
based/software/and/development/along/with/its/databasemanagement.
 Able/to/perceive/real/time/application/with/their/integration/on/mobile/devices.
 Implementation/and/integration/of/database/services/with/Desktop/applications.
 Understanding/HCIU-
/Design/guidelines/and/principles/to/ensure/system/being/developed/will/be/usa
bility/and/quality/product.
 Understanding/of/data/gathering/methods/and/its/actual/implementation.
 Better/understanding/of/project/management/concepts/i.e.,/scheduling,/budgeting,/cos
t/estimation,/work/break/down/structure,/Gantt/chart,/Pert/chart/etc.
 Learning/queries/for/updating/data/from/the/desktop/to/JDBC.
 Learning/and/Practices/of/MySQL/Query.
 Learning/and/practices/of/ the/GUI/like/Swing,/ AWT/,JSP-
servlet/and/Spring/MVC,/Spring/Data,/Spring/Boot,Spring/Security.
1.7 Scope/of/the/System
The/proposed/system/will/be/beneficial/in/a/number/of/ways./The/“Travel/&/Tour/Managem
ent/System”/is/actually/about/automating/the/whole/process/to/Book/hotel/room/and/select/pre-
derived/plan/of/application/by/just/choose/and/payment/at/the/end/of/it.
Mainly/this/system/focuses/on/security/and/services/to/the/layman/so/that/they/can/fetch/their
/details/whenever/they/require/and/the/personal/data/of/client./ It/is/one/of/the/main/motto/of/
our/system.
1.8 Limitation/of/the/System
Limitations/are/always/a/part/of/every/project./The/project/scope/is/limited/to/a/confine
d/boundary/as/listed/below:
 The/system/is/being/developed/for/only/Desktop/based/users.
 To/validating/the/ticket/the/mobile/device/with/at/least/3.2/MP/of/rear/camera/is/require
d/in/order/to/upload/document/images.
 The/customer/will/need/the/internet/connection/for/transferring/money/for/payment/for/al
l/hotel/charges.
1.9 Assumptions/Made
This/system/is/although/easy/to/use/in/terms/of/its/functionalities/but/even/then,/there/are/som
e/assumptions/that/need/to/be/made/before/the/development/of/the/system:
14
 Users/need/to/have/basic/knowledge/of/using/laptops/ and/desktop/application/etc.
 Good/knowledge/of/English/and/basics/of/Internet/is/required,/i.e.,/user/needs/to/be/a/
computer/literate.
 The/smartphone/users/have/not/yet/encountered/any/secure/solution/to/protect/their/dat
a/from/being/stolen/or/mishandled
1.10 Success/Criteria
Success/Factors/depends/upon/the/depth/of/understanding/and/experience/gained/from/the/ap
plications/viewed/for/the/review/and/how/efficiently/the/developer/cracks/the/problems/faced/i
n/the/application/that/lead/to/development/of/such/an/application.
 Application/is/properly/working/and/compatible/with/mentioned/browser/version./Ap
plication/will/be/useless/if/it/is/unable/to/run/properly/on/the/physical/device./There/s
hould/not/be/any/anomalous/or/false/functioning/during/its/working/on/physical/device.
 System/meets/all/requirements/of/the/proposed/solution./If/the/application/provides/d
esired/operations/and/produces/expected/output/i.e.,/if/it/is/meeting/user/requirements,/
passing/of/above/test/cases./Application/must/fulfill/the/core/as/well/as/enhanced/syste
m/requirements/mentioned/above.
 Project/will/be/treated/as/constructive/if/it/is/proper/evaluation/of/Usability/&/HCI./Th
e/developer/will/be/able/to/provide/successful/implementation/of/Desktop/application/
in/termsof/interactivity,/effectiveness/and/efficiency.
1.11 Functionalities/of/the/System
The/proposed/system/having/some/core,/enhanced/and/some/special/functionality./So,/let’s/k
now/them/one/by/one/and/use/of/these/functionalities/in/this/system.
1.11.1 Core/Features
Functionality Description
An/Travel/&/Tour/Management/System
All/users/at/first/have/to/register/themselves/to/the/system./All
Register
the/users/will/get/a/unique/email///mobile/number/and/password.

15
All/users/will/get/a/unique/email///mobile/number/and
Sign-in password/through/which/they/can/logged/in/into/th
e/application.
After/login/Client/an/make/his/full/Travel/and/Tour/plan/o
Tour/Plan n/our/management/system.
Hotel/Variety User/can/see/the/best/and/real/image/of/hotel/room/which/the
y/want/according/to/there/plan/they/can/choose/just/by/one/cli
ck.
Transfer/Money User/can/pay/his/whole/trip/payment/at/the/end/via/scannin
g/QR/code.
Booked/Receipt Client/can/view/his/Booked/Hotel/Receipt/which/can/help/th
e/client/at/the/Check-
In/time/by/showing/the/receipt/to/hotel/management/counter.
Table/3:/Core/Feature
1.11.2 Enhanced/Features
Maintain/Records
This/System/maintain/Proper/management/of/data/of/client/&/paymen
t
Note/pad
Hear/we/add/extra/feature/of/note/pad/on/which/client/can/add/hi
s/Important/notes/regarding/hotel/room/and/future/plan.
Manage/the/payment Secure/payment/transfer/to/respective/account.
Collect/end-user
Collect/user/data/for/authentication
./statistics
Calculator Hear/we/also/add/extra/feature/of
Calculator/on/which/client/can/
Calculator/his/Whole/expenses.
Table/4:/Enhanced/Features
1.11.3 Special/Features
Table/5:/Special/Features

16
Online/Hotel/Booking On/this/system/Client/can/Manage/his/Whole/travel/planning/on/a
Single/platform/which/is/provided/on/our/system/with/best/feature.

17
1.12 Conclusion
The/Chapter/1/includes/the/background/study/for/the/system./Studying/the/system/has/inferre
d/t he/purpose/of/the/system/and/goals//objectives/of/the/system./After/the/purpose/of/the/syst
em/is/identified,/the/developer/then/came/up/with/the/benefits/of/the/system/to/its/intended/en
d-
/user/and/how/the/system/can/benefit/its/users./The/developer/then/cultivated/the/desirable/fe
atures/to/be/implemented/in/the/proposed/system/to/resolve/the/problems/that/were/identified/i
n/the/problem/context/section./The/chapter/has/also/included/the/deliverables/the/system/will
/produce/after/it/is/completed./The/limitations/for/the/system/have/also/been/identified/that/limi
ts/the/scope/of/the/proposed/project.

18
CHAPTER/2:/PROBLEM/DESCRIPTION
2.1 Current/Proble m/Description

After/the/analysis/of/preliminary/investigation,/the/researcher/has/spotted/and/identified/some/
of/the/main/problem/areas/of/the/application/which/are/briefly/described/below:
2.1.1 Description/of/Problem/Area
 Overview/Booking:/Currently/users/cannot/Book/Hotel/room/online.
 Payment/:/ After/use/of/Hotel/Client/have/to/pay/his/charges/in/cash.
 Safe/:/ Client/document/are/safe/.
 Reliability:/As/we/do/money/transfer/in/cash/so/possibility/of/it/getting/lost/or/stole
n/is/high.
2.2 Problem/Importance/and/Justification
The/solution/for/the/current/system/is/to/develop/a/system/which/will/sort/out/all/the/above/p
roblems./The/proposed/system/will/work/upon/the/current/issues/and/will/overcome/the/prob
lem/that/it/has/right/now:
 Online/Room/booking/:/With/the/help/of/this/system/user/can/Book/online/to/any/
merchant/ online/present/hotel/just/by/seen/its/image.
 Reliable:/As/the/system/is/online/and/log/files/for/every/transaction/is/created/so/it/i
s/more/reliable/and/secure/than/previously/existing/solution.
 Over/storage/of/junk/data:/Banks/have/to/maintain/large/chunk/of/files/and/receipt
s/which/causes/storage/issues./With/keeping/everything/online/it/is/easier/to/maintain
/records/efficiently.

19
2.3 Proposed/Solution
The/solution/for/the/current/system/is/to/develop/a/system/which/will/sort/out/all/the/above/p
roblems./The/proposed/system/will/work/upon/the/current/issues/and/will/overcome/the/probl
em/that/it/has/right/now:
 Online/Room/booking/:/With/the/help/of/this/system/user/can/Book/online/to/any/m
erchant/ online/present/hotel/just/by/seen/its/image.
 Reliable:/As/the/system/is/online/and/log/files/for/every/transaction/is/created/so/it/is
/more/reliable/and/secure/than/previously/existing/solution.
 Over/storage/of/junk/data:/Banks/have/to/maintain/large/chunk/of/files/and/receipts
/which/causes/storage/issues./With/keeping/everything/online/it/is/easier/to/maintain/r
ecords/efficiently.
2.4 Nature/of/Challenge
2.4.1 Domain/Challenge
To/build/this/app,/the/researcher/would/have/to/undergo/some/major/challenges/during/the/d
evelopment/like:
 Desktop/Comme rce:/To/implement/the/concepts/and/ideas/involved/in/Desktop/com
merce/to/develop/the/Desktop/application
 Synchronization:/The/primary/challenge/in/developing/this/Desktop/would/be/imple
menting/the/concepts/of/web/services/to/communicate/with/the/database/in/order/to/sy
nc/with/the/application/to/fetch/the/relevant/data.
 Inte raction/Principles:/To/understand/the/interaction/principles/between/the/human/
and/the/mobile/devices/and/to/develop/the/application/keeping/in/mind/the/implement
ation/of/all/those/principles/which/will/justify/the/successful/implementation/o f/the/app
lication.
2.4.2 Technical/Challenge
The/challenges/that/would/come/on/the/way/of/the/researcher/while/working/on/th
e/technology/area/are/as/follows:
 Desktop/Platform:/The/very/first/thing/that/I/would/like/to/mention/here/is/the/know
ledge/of/platform./Since,/the/system/is/going/to/be/ developed/ on/ server/platform/an
d/I/am

20
totally/unknown/about/this/technology,/off-
course/I/have/started/learning/it/but/still/I/need/to/learn/many/concepts/of/server/base
d/application/for/successful/development/of/t his/project.
 Reading/QR:/It/is/itself/a/challenging/task/to/create/a/QR/code/scanner/for/smart/phon
e/cameras/taking/into/consideration/the/varying/camera/features/of/the/smart/phones.
 Save/Transactions:/It’s/a/challenging/task/to/save/the/transaction/for/future/reference.
 Integrating/Various/Modules/in/one/Application:/It/will/be/quite/challenging/to/int
egrate/various/modules/such/Model/View/Controller,/Spring/Data,/Spring/Boot,/Micr
oservices,/Rest/APIs.
 Hardware/Fragmentation:/There/are/thousands/of/varieties/of/devices/that/run/on/c
omputing/devices/platform/and/those/various/devices/exist/with/different/properties/s
uch/as/memory,/CPU/speed,/and/graphical/resolutions./There/is/also/a/fragmentation/
possible/on/the/operating/system/level./A/famous/example/is/the/fragmentation/on/An
droid/devices/with/different/screen/sizes/and/resolutions./Thus,/developer/must/have/to
/perform/market/research/to/find/out/which/handsets/are/most/popular/with/the/target/
audience/and/develop/for/those/first.
 Software/Fragmentation:/Since,/there/are/too/many/Java,/Spring/and/JavaScript/ver
sions/are/available/running/into/the/devices./So,/I/as/a/developer/can’t/focus/only/on/s i
ngle/or/latest/version/of/because/it’s/not/easy/for/users/to/upgrade/their/operating/syst
em/and/therefore/most/of/the/users/must/not/have/upgraded./Therefore,/developer/wil
l/have/to/learn/which/operating/systems/are/most/popular/and/develop/with/the/latest/w
idely/adopted/version/in/mind.
 All/Desktop/Services:/Since,/the/app/needs/to/communicate/with/the/remote/databas
e/in/order/to/sync/with/the/application/to/fetch/the/relevant/data,/thus/the/developer/m
ust/need/to/have/deep/knowledge/of/a/ Desktop/service/as/it/will/frequently/be/used/to
/fetch/data/from/or/suit/data/to/remote/database.
2.5 Feasibility/Study
Feasibility/study/is/an/analysis/and/evaluation/of/a/proposed/project/to/determine/if/it/is/feasibl
e/technical,/economically,/timely/and/operationally./Feasibility/study/for/the/project/is/conduct
ed/to/analyze/whether/the/proposed/project/is/possible//feasible/to/be/developed/within/sched
uled/time,/available/resources,/within/estimated/budget./After/feasibility/study/is/done,/it/is

21
evaluated/whether/to/proceed/with/the/project/or/not./The/feasibility/study/can/be/categorized/i
nto/following/four/parts:
 Technically/feasibility
 Economic/feasibility
 Schedule/feasibility
 Operational/feasibility
2.5.1 Technical/Feasibility
Technical/feasibility/is/conducted/to/verify/whether/the/project/is/feasible/to/be/developed/wi
thin/the/available/resources/or/not./The/technical/feasible/takes/into/account/the/technical/req
uirements/for/the/project,/the/technical/resources/required/by/the/project/for/its/successful/an
d/efficient/completion./The/specific/technical/resources/to/be/available/for/completing/the/pr
oject/successfully/are/given/below:
Hardware/Resources
S./No. Hardware/Resources
1. Processor-/Core/i3/and/later/version
2. RAM/(Memory)/-/2/GB/and/more
3. Monitor/–/Any/standard/monitor
4. Pen/Drive,/Mouse,/Printer,/Keyboard
5. System/Type-/64-bit/OS
6. Hard/Drive–/More/than/80/GB
7. Accessories/–/Internet/connection.
Table/6:/Hardware/Resources
Software/Resources
S./No. Software/Resources
VS/Code,/Note-Pad//Idea,/Spring/Suit,/Google/Chrome
1.
2. Plug-In/-/JDK/6.0///8.0/,later/(JRE/)/or/JDBC.
3. Database/Technology/–MySQL
4. Operating/System/(PC)/-/Windows/7/or/later
5. Operating/System/(Mobile/Phone)/–/Android/OS,/Iphone

22
6. Documentation/and/Presentation/tool/-/Microsoft/Office/2016
Table/7:/Software/Resources
Resources/of/Execution
S./No. Resources/for/Execution
1. Operating/system/-/Android/4.0/and/later
Android/Smartphone/-/GPS/enabled/mobile/phone,/Rear/Camera/(minimum
2.
3.2/MP),/Internet/services/like/Mobile/Data.
3. CPU:/600/MHZ
4. RAM:/100/MB/(estimated)
5. Disk/space:/50/MB/(estimated)
6. A/good/data/internet/connection/for/customers
Table/8:/Resources/for/Execution
2.5.2 Economic/Feasibility
The/main/purpose/of/conducting/economic/feasibility/is/to/identify/the/financial/benefits/and/
costs/associated/with/the/project/development./As/for/any/system/if/the/estimated/benefits/equ
al/or/surpasses/the/expected/costs/that/is/calculated/for/the/system/then/the/project/would/be/e
conomically/feasible./Since/the/proposed/system/programming/environment/is/based/on/andr
oid/which/is/an/open-
source/platform,/so/there/is/less/of/investment/in/the/development/portion./And/any/software/
or/program/that/is/produced/needs/to/be/tested/which/can/be/done/without/much/investment./
Only/required/investment/would/be/a/physical/device/to/test/the/system.
2.5.3 Schedule/Feasibility
Schedule/feasibility/for/a/project/is/done/to/verify/whether/the/project/can/be/completed/withi
n/scheduled/time/or/not/as/decided/by/the/Gantt/chart./Dates/are/fixed/for/each/phase/through
out/t he/project/and/it/is/to/be/ensured/that/the/project/is/able/to/complete/within/the/specified/
dates/a nd/the/schedule./If/the/project/is/able/to/be/completed/within/the/schedule,/the/schedul
ed/feasibility/is/high./Gantt/chart/is/a/project/management/tool/that/can/be/used/to/measure/th
e/scheduled/feasibility/of/the/project./The/proposed/timeline/for/the/application/would/consu
me/approximately/38/weeks/and/time/management/for/each/task/is/carried/out/aptly/through/
Gantt/chart.

23
Gantt/Chart:/-/Refer/to/Appendix
2.5.4 Operational/Feasibility
Operational/feasibility/measures/to/which/extent/the/proposed/system/resolves/the/problems/i
dentified/in/the/starting/phase/of/the/project;/how/the/project/intends/to/fulfil/the/requirement
s/identified/during/scope/definition/and/how/the/system/makes/use/of/the/opportunities/identifi
ed/d uring/scope/definition./The/project/will/be/operationally/feasible/undoubtedly/as/the/main
/motive/is/to/solve/the/problems/of/those/who/face/problems/in/nowadays/environment/whic
h/are/faced/by/masses.
2.5.5 Conclusion/of/Feasibility/Study
The/project/is/technically/feasible/since/the/hardware,/software/and/the/resources/needed/for/
executing/the/system/are/ready./After/evaluating/the/cost/and/benefits/incurred/on/and/derive
d/from/the/system,/it/is/concluded/that/the/project/is/economically/feasible./The/project/will/b
e/completed/on/time/and/deadlines/will/be/followed/as/scheduled/in/the/Gantt/chart./The/syst
em/will/be/socially/acceptable/and/will/satisfy/the/needs/of/users.
2.6 Conclusion
Chapter/2/is/all/about/the/problems/identified/in/the/current/area/of/study/i.e.,/the/problems/i
n/ticket/environment./The/developer/has/identified/all/the/problems/which/is/generally/facing
/by/t he/general/user./The/problems/have/been/documented/along/with/the/justification/for/eac
h/problem./After/all/the/problems/are/identified,/the/developer’s/next/task/was/to/provide/app
ropriate/solutions/to/resolve/the/problems./For/the/same/purpose,/the/solution/corresponding/to/
each/problem/has/been/documented/along/with/the/justification./A/feasibility/study/is/then/co
nducted/for/the/system/to/ensure/that/the/proposed/system/is/technically,/operationally,/econo
mically/feasible/and/can/be/completed/within/a/specified/time/frame./The/feasibility/study/is/su
ccessful,/creating/a/further/path/for/the/developer/to/move/ahead/with/the/project.

24
CHAPTER/3:/LITERATURE/REVIEW
3.1 Introduction/to/Literature/Review
A/literature/review/is/a/description/of/what/work/has/already/been/done/by/other/researchers/
related/to/the/present/topic./It/is/conducted/using/published/books,/journals/and/other/researc
h/papers/and/is/a/baseline/for/present/research./The/following/are/the/purpose/of/a/literature/r
eview:
 To/ perform/ critical/ evaluation/ of/ already/ conducted/ research/ to/ find/ out/ their/ ideas
,/strength,/weakness/and/their/methodologies.
 To/have/an/overview/of/already/existing/suggestions/related/to/the/subject,/review/th
e/findings/and/views/of/others.
 To/answer/certain/questions/and/remove/confusions/related/to/the/present/topic.
3.2 Advanced/Preliminary/Research
As/we/also/know/that/we/are/in/that/era/where/mobile/laptop/is/the/common/for/every/user./I
f/we/take/the/hundred/people/95%/of/the/people/having/own/smartphone/in/his/hand/so/why/n
ot,/we/develop/the/system/for/mobile/and/laptop/users./There/are/some/applications/already/e
xist/but/they/do/not/have/expense/tracker./Our/application/has/dedicated/expense/tracker/whi
ch/tracks/your/expenditure/and/shows/you/in/form/of/meaningful/charts.
3.3 Academic/Research
Before/developing/the/proposed/system,/the/developer/conducted/academic/research/by/readin
g/research/papers,/journals/etc./to/understand/the/real/need/of/money/transfer/application/for/t
he/users/and/its/advantages./How/it/will/be/useful/to/the/users./It/will/also/help/the/developer/
to/refine/the/functionalities/to/be/included/in/the/system.
3.3.1 QR/Code/Technology
Since/QR/scanning/is/one/of/the/challenges/of/the/proposed/system,/the/developer/has/gone/t
horough/the/ideology/to/implement/QR/code/scanning/and/it’s/decoding/in/the/system.

25
3.3.2 Software/Methodology/and/Software/Engineering/Concepts
In/order/to/deliver/a/user/satisfied/system/within/time,/the/developer/has/to/research/for/the/
methodology/which/best/suits/the/app.
3.3.3 Human/Computer/Interaction/Principles
It/is/necessary/for/a/good/design,/evaluation,/usable/interface/etc./that/is/user/friendly/with/vi
sibility,/affordance/etc./The/developer/must/be/clear/with/the/interaction/principles/between/t
he/human/and/the/mobile/devices/so/that/the/application/is/developed/keeping/in/mind/the/im
plementation/of/all/those/principles/which/will/justify/the/successful/implementation/of/the/a
pplication.
3.3.4 Project/Management/Principles
Project/management/techniques/will/be/aforethought/for/the/system/like/scheduling,/feasibility
,/risk/analysis/to/complete/the/development/smoothly.
The/books,/journals/and/online/articles/referred/for/doing/academic/research/are/as/follows:
 Books
Topic Book/Referred
 Pressman,/R./(2005)./Software/Engineering:/A/Practitioner'
s/Approach./5th/ed./Boston,/Mass.:/McGraw-Hill.
 Shelly/Cashman/(2002)./System/Analysis/and/design,2nd/Ed.
,/Shelly/Cashman/Series,/Sydney.
Software/Development/  Valacich,/J.,/George,/J./and/Hoffer,/J./(2001)./Essentials/of/sy
Life/Cycle stems/analysis/and/design./Upper/Saddle/River,/N.J.:/P
rentice/Hall.
 Kendall/and/Kendall/(2005);/System/Analysis/and/Design,4t
h/Ed, New/York:/Prentice/Hall.
 Desktop/Design/with/CORE/JAVA(Swing/,/AWT).
 Learning/JDBC/:/Functional/Desktop/Development/wit
h/MYSQL/DataBases/In/which/can/save/the/data/of/clie
Desktop/Development nt
 Spring/in/Action/by/Craig/Walls,/Ryan/Breidenbach

26
 Dix,/A.,/Finlay,/J.,/Abowd,/G./and/Beale,/R./(2004)./Human
-
Human/Computer/In
/computer/interaction./Harlow,/England:/Pearson/Pr
teraction/Principles entice-Hall.
 Human/Computer/Interaction-
/Alend/Dix,/Janet/Finlay,/Gregory/D./Abowd,/Russell/
Beale
Features/of/OOPS  Steven/Holzner/et/al./(2007)./Java2/Programming/Black/Book
Table/9:Books/References/for/Academic/Research
 Journals
Topic Journals/Referred
• (2015)/July/1st/ in/The/Economic/Times/“Definition/of/Trave
l/management/”
• (2016)/December/9/in/The/Indian/Express/under/Brand/solutio
n/“Akind/,how/they/work”
• Dr/Hem/Shweta/Rathore/(2016)/April./Adoption/byconsumers./Vol.
Travel/&/Tour • Dr./Poonam/Painuly,/Shalu/Rathi/(2016)/May./“Mobile/Deskto
p/application:/Anupcoming/mode/of/business/transactions”/Vol/
/M anagement
3/Issue/2
• Prof/Trilok/Nath/Shukla/(2016)/June/“Mobile/Desktop/applicatio
n/P resent/and/theFuture”/(JMEIT),/Volume/-3,/Issue-/3
Table/10:Journals/References/for/Acade mic/Research
3.4 Domain/Research
Domain/research/is/necessary/as/the/project/domain/varies/in/various/cases/and/once/this/is/fi
nished/for/a/particular/module,/then/we/can/work/on/analysis/and/designing/of/that/particular/
module/provides/ease/of/its/use./During/the/stages/of/research,/the/researcher/acknowledged/
that/there/are/enough/problems/faced/by/the/user/in/environment/of/getting/Booked/Room/vi
a/online.
The/application’s/domain/area/is/focused/on/Desktop-
based/application/and/mobile/computing./To/have/a/deep/knowledge/of/user/requirements/an
d/important/aspects/of/the/system,/researcher/has/to/implement/the/technology/to/reduce/probl
ems/.

27
3.4.1 Desktop/Application/Development
Desktop/application/development/is/the/complex/process/of/designing,/building,/testing/and/
deploying/on/a/Desktop/based/app./When/a/business/wants/to/create/an/online/presence,/the
y/may/choose/to/create/a/custom/web/application/but/hear/we/make/Desktop/application/whi
ch/can/be/further/connected/at/any/time/with/client./Desktop/applications/are/interactive/pag
es/that/enableuser/input/and/run/on/a/Desktop/with/a/local-
Database./What/makes/a/Desktop/application/unique./They/are/also/secure,/easy/to/backup/a
nd/are/more/affordable/than/mobile/application/development.
3.4.2 Desktop/Application/Architecture
Figure/1:Architecture
Figure/3:/Layers/of/Desktop/App/Architecture
 Presentation/layer,/Spring/frameworks,/enablescommunication/between/th
e/interface/and/Database.

28
 Business/layer/defines/the/business/logic/and/rules./It/processes/browser/requests,/ex
ecutes/the/business/logic/associated/with/the/requests,/and/then/sends/it/to/the/present
ation/layer.
 Persistence/layer/is/responsible/for/data/persistence/and/is/also/known/as/Data/Acces
s/Layer./It’s/closely/connected/to/the/business/layer/and/has/a/database/server/that/retr
ieves/data/from/corresponding/servers.
 Database/layer,/also/known/as/Data/Service/Layer,/holds/all/the/data/and/ensures/dat
a/security/by/separating/the/business/logic/from/the/client-side.
3.4.3 Security/and/Pe rmissions
Security/comes/at/two/parts/client-side/security/and/server-side/security./Client-
side/security/mainly/depends/upon/the/browser,/operating/system/and/device/used/by/the/use
r./On/server-
/side/we/use/Linux/servers/to/secure/our/servers./Along/with/it/we/will/use/Spring/Security/
module/of/Spring/framework/which/secures/our/application.
3.5 Critical/Evaluation/of/Literature/Review
The/development/of/the/proposed/App/for/user/is/researched/upon/so/as/to/come/to/the/concl
usion/what/all/features/are/required/by/the/end/user/to/enhance/the/online/money/transferring
/environment./The/literature/review/creates/the/groundwork/to/carry/out/further/research/givi
ng/an/idea/about/the/proposed/system./The/systems/similar/to/the/proposed/system/have/been/r
esearched/upon/to/create/a/base/line/for/the/system;/what/problems/the/developer/can/face,/w
hat/are/the/features/that/cannot/be/implemented/at/all.
While/reviewing/the/literature,/domain,/technical/and/academic/research/have/been/carried/ou
t/to/get/the/in-
depth/knowledge/of/the/features/to/be/implemented/in/the/proposed/system/and/to/e xplore/the
/technology/to/be/used/in/implementing/the/system./Therefore,/secondary/research/is/done/un
der/literature/review/by/studying/other’s/work/which/will/guide/the/developer/towards/devel
oping/the/proposed/system.
3.6 Critical/Success/Factor
The/Backup/Facility/in/Remote/database,/Push/Notification/and/Save/transaction/feature/the/
proposed/system/will/be/providing/to/its/users/are/the/critical/functionalities/of/this/project./Th
e/developer/needs/to/complete/all/the/features/identified/during/the/literature/review;/seconda
ry/research/that/are/to/be/implemented/in/order/to/deliver/an/efficient/system/to/the/end-user.
29
Tour & Travel Management/System
3.7 Conclusion
Chapter/3/includes/review/the/literature/of/the/past/to/establish/a/baseline/for/the/proposed/project./
Under/literature/review,/existing/systems/have/been/studied/to/gather/knowledge/in/the/area/of/the/st
udy;/what/features/are/new/in/the/market/and/what/all/features/the/developer/can/integrate/into/his/
new/system./The/chapter/also/includes/the/information/and/resources/that/are/a/part/of/the/literature/
review/and/are/studies/or/will/be/studied/in/future/to/collect/the/data/and/information/about/the/area/
of/study.

CHAPTER/4:/ RESEARCH/METHODS
4.1.1 Primary/Research
Primary/research/is/defined/as/the/collection/of/facts/or/information/about/the/field/of/study/
directly/from/the/actual/world,/for/the/first/time/about/a/certain/subject,/from/the/real/world./B
y/d irectly/asking/such/questions/to/forum/members/and/assessing/their/solutions,/it/is/possible
/to/remove/the/developer's/doubt/and/ambiguity/that/emerged/as/a/consequence/of/secondary/
research./The/developer/can/utilize/this/study/to/help/progress/the/project./Questionnaire/and
/interview/are/the/developer's/primary/research/methodology,/as/seen/below:
4.1.2 Questionnaire
A/questionnaire/is/a/set/of/questions/printed/on/a/sheet/of/paper/in/a/specific/order/in/order/t
o/elicit/information/from/target/users/in/a/short/period/of/time./The/respondents/are/given/the
/questionnaire/and/are/asked/to/read/and/understand/the/questions/before/responding/in/the/spa
ce/provided./The/developer/will/distribute/the/questionnaire/to/the/users/because/they/are/the/ty
pes/of/users/for/the/proposed/system.
Justification/for/conducting/Questionnaire
The/following/are/the/reasons/for/using/a/questionnaire/as/the/primary/data/collection/method:
 Because/the/system's/target/users/are/so/many,/it's/impossible/to/contact/each/of/the
m/individually/to/gather/their/requirements/and/suggestions.
 With/a/questionnaire,/it/is/possible/to/reach/a/large/number/of/people/at/once,/regardles
s/of/their/geological/location,/which/saves/time.
 Because/ statistical/approaches/may/be/applied/to/it,/the/ questionnaire/ analysis/is/e ffi

cient,/and/it/is/done/in/the/form/of/more/accurate/graphs/and/charts.
 Because/users/can/answer/questions/anonymously,/ there's/a/better/chance/of/ gettin

g/precise/requirements.
 It's/a/cost-
effective/strategy/because/ it/ may/be/emailed/ to/participants/or/ given/as/a/pamphlet.

Tour & Travel /Management/System
Questionnaire/for/customer
Respectfully,/Sir/Madame,
First/and/foremost,/thank/you/for/taking/the/time/to/participate/in/our/survey./This/poll/inquire
s/about/your/online/railway/ticket/booking/experiences/as/well/as/your/thoughts/concerning/o
nline/ticket/booking.
The/researcher/is/a/final-
year/B/Tech/student/in/the/Computer/Science/track/of/College/name,/Panipat./For/the/final/ye
ar/project,/primary/research/and/data/collection/is/done/using/a/survey./The/researcher/kindly/r
equests/that/you/take/a/few/minutes/to/read/over/the/questions/and/assist/us/in/completing/this/
survey/by/answering/the/questions/below./The/questions/were/carefully/crafted/while/adherin
g/to/all/of/Kurukshetra/University's/ethical/norms/for/study./"An/Tour/&/Travel/management///
System/"/is/the/project's/name.
Instruction
This/ component/ of/ the/ questionnaire/ will/ assist/ the/ researcher/ in/ estimating/ project/ stud
y/outputs./It/is/critical/that/you/thoroughly/answer/all/pertinent/questions.
Section/A:/-
/This/is/an/optional/section/that/contains/your/personal/and/professional/information.
Section/B:/-
/Select/the/most/appropriate/options/from/the/questions/below;/depending/on/the/r equiremen
ts,/you/may/select/more/than/one/option.
Section/C:/-
/Please/feel/free/to/express/your/opinions/suggestions/and/assist/the/researcher/in/comprehending/the/e
ssential/requirements.
4.1.3 Interview
A/face-to-
face/interview/is/a/form/of/primary/research/method/in/which/a/list/of/questions/is/prepared/i
n/advance/and/asked/to/the/respondent./The/majority/of/the/questions/are/open-
ended./I t's/made/to/compile/a/lot/of/information/on/a/specific/subject./In/interviews/for/the/pr
oposed/system,/those/questions/are/asked/that/demand/a/little/of/comprehensive/description/t

o/comprehend/the/requirement./Developers/are/the/interviewees/for/the/proposed/system./The
/goal/was/to/gain/a/unique/perspective/from/the/users/in/order/to/gather/as/much/information/
as/possible/regarding/the/system's/requirements.

Justification/for/Conducting/intervie w
The/following/are/the/reasons/why/an/interview/was/chosen/as/the/major/research/method:
 It/delivers/first-
hand/information,/increasing/the/likelihood/of/obtaining/accurate/facts/a nd/high-
quality/data,/as/well/as/new/insights/and/conclusions.
 It/will/aid/ in/ the/ gathering/of/detailed/ information/regarding/the/proposed/system'

s/functionality,/as/it/is/best/for/examining/problems.
 A/person's/sentiments,/ ideas,/and/ gestures/can/be/seen/ in/addition/to/ what/ they/sa

y,/allowing/the/interviewer/to/confirm/whether/or/not/what/they/are/discussing/is/corr
ect.
4.2 Secondary/Research
Secondary/research/is/usually/conducted/before/performing/primary/research./It/requires/gath
ering/information/from/previously/published/books,/journals,/and/research/papers/that/has/bee
n/independently/checked./It/is/done/in/order/to/learn/from/other/people's/mistakes/in/the/rele
vant/domain,/since/it/is/preferable/to/learn/from/other/people's/mistakes/and/save/time/rather/t h
an/repeating/the/same/mistake.
4.2.1 Technical/Research
This/has/to/do/with/the/technical/aspects/of/the/study,/such/as/the/platform,/computer/languag
e,/database,/technology,/and/methodological/decisions./Because/technical/research/is/an/impo
rtant/part/of/the/proposed/project/that/might/affect/its/execution,/it/is/completed/before/the/s yst
em/development/and/execution/phase/begins./To/determine/which/platforms,/programming/lan
guages,/databases,/technologies,/and/procedures/should/be/utilized/for/a/specific/project,/co
mplete/research/is/conducted/that/analyses/and/evaluates/a/variety/of/platforms,/programmin
g/languages,/databases,/technologies,/and/procedures./Why/Android?
For/the/creation/of/the/application,/the/researcher/chose/to/work/with/Android/technology/fo
r/the/following/reasons:

 Huge/Market:/Android/has/a/market/share/of/82.8/percent/in/the/smartphone/market./
As/a/result/of/its/popularity/in/the/market,/the/researcher/believes/that/if/the/developme
nt/is/based/on/this/technology,/the/success/rate/would/be/high.
Windows/ BlackBerry
Period Android iOS Others
Phone /OS
2016 85% 13% 1% 0.6% 0.4%
2015 81.8% 14.9% 2.3% 0.600% 0.4%
2014 86.8% 9.6% 2.5% 0.5% 0.7%
2013 80.8% 11.9% 2.4% 3.8% 1.2%
2012 65.3% 20.6% 3.1% 4.9% 6.1%
 Android/support/with/google/map:/Both/Android/and/Google/Map/are/Google/endea
vors,/and/for/simplicity/of/use,/they/have/offered/packaged/libraries/packed/with/t he/
Android/platform./This/compatibility/can/be/leveraged/in/the/proposed/method/to/obt
ain/the/current/location/using/Google-
Map/and/GPS/technology/in/Android/applications.
 Open-source/architecture:/Because/Android/is/an/open-
source/platform,/there/will/be/less/investment/necessary/in/the/development/phase./F
urthermore,/every/software/or/programmer/that/is/created/must/be/tested,/which/may/
be/done/inexpensively./Only/a/physical/device/to/test/the/system/would/be/required.

Justification/for/programming/language/selection(java)
The/developer/has/chosen/Java/as/the/programming/language/for/the/construction/of/the/sug
gested/system./Because/the/system/will/be/developed/on/the/Android/platform,/which/levera
ges/the/Java/programming/language/in/its/development/environment,/it's/a/no-brainer.
Justification/for/database/selection/(MySQL)
MYSQL/is/a/free/and/open-
source/database/that/is/built/into/Android./The/data/stored/in/MYSQL/is/much/more/efficient
/and/structured,/which/is/excellent/for/the/proposed/system/because/train/data/must/be/maint
ained/in/a/systematic/manner.
 The/data/types/TEXT/INTEGER/(similar/to/long/in/Java),/and/REAL/are/supported/b
y/MYSQL/ (similar/ to/ double/ in/ Java)./ And,/ because/ Java/ has/ been/ chosen/ as/ t
he/programming/language,/it/will/be/quite/beneficial/for/developers/to/work/with/it.
 It's/a/small/database,/requiring/only/about/270Kbyte/of/memory/at/runtime./As/a/resul
t,/t he/system/app/will/be/compatible/with/even/the/most/basic/Android/versions,/as/w
ell/as/phones/with/limited/capacity.
 MYSQL/is/a/relational/database/engine/that/supports/common/databases.
Justification/for/web/services/selection
Android/is/unable/to/communicate/with/the/remote/database/because/of/this./As/a/result,/a/we
b/service/is/required/to/connect/these/two./Web/Service/will/aid/in/the/retrieval/of/data/from/
or/the/fitting/of/data/to/a/distant/database./REST/web/service/will/be/used/to/implement/the/s
uggested/system/application./Representational/State/Transfer/(REST)/is/an/architectural/style/
for/networked/hypermedia/systems/that/is/primarily/used/to/create/lightweight,/maintainable,
/and/scalable/Web/services.
Justification/for/Rest
Lightweight:/It's/a/little/web/service,/and/since/the/suggested/system/is/an/Android/app,/it's/a
n/excellent/choice/for/the/mobile/app.

Easy/to/Build:/It/is/simple/to/construct/and/does/not/necessitate/the/use/of/any/toolkits,/makin
g/it/a/good/technology/to/use/for/the/suggested/system.
REST/produces/results/that/are/easily/legible/by/humans,/allowing/developers/to/change/the
m/more/easily.
Phase/of/V-/Model/methodology
Need/of/source Testing/Design
Users Testing
Account Integration/ of
Hotel Unit/one
Apply
Phase/of/V-/Model/methodology
During/the/development/of/the/system,/the/developer/will/use/this/methodology/to/complete/
the/following/phases.
 The/first/step/in/the/verification/process/is/to/do/a/requirement/analysis./The/develope
r/will/not/be/debating/how/the/system/will/be/developed/at/this/stage;/instead,/it/will/
be/a/broad/discussion/with/a/user/demand/document/attached./This/paper/will/include/
information/on/the/system's/function,/performance,/security,/data,/and/interface,/amon
g/other/things./The/business/analysts/need/this/paper/to/explain/how/the/system/works
/to/the/users./In/the/meanwhile,/it/will/only/be/a/suggestion.
 System/Design-
At/this/stage,/the/product's/probable/design/is/expressed./It's/written/with/the/requisite
/summaries/in/mind./Furthermore,/if/there/is/something/that/isn't/proper/in/the/design/
when/researching/the/documents,/the/developer/is/notified,/and/adjustments/are/sched
uled/as/a/result.

 Architecture/Design—
also/known/as/computer/architecture/design/or/software/design—
must/be/familiar/with/the/modules/and/their/functions/before/they/can/be/integrated.
 Module/Design-
The/architectural/design/is/split/into/sub/components/at/this/stage/so/that/they/can/be/
planned/and/defined/separately./Modules/are/the/units/that/make/up/the/s ystem./It/can/
be/decrypted/separately/by/the/programmer.
4.3 Conclusion:
The/research/methodologies/are/the/focus/of/Chapter/4./The/researcher/did/primary/and/seco
ndary/research,/as/well/as/technical/study,/to/arrive/at/a/final/conclusion/regarding/user/requi
rements,/technologies,/and/tools/to/be/used./The/developer/used/a/variety/of/research/approa
ches,/including/questionnaires/and/interviews./The/investigation/was/required/to/avoid/wasti
ng/time/later/in/the/development/process./The/researcher/now/has/a/good/idea/of/what/featur
es/should/be/included/in/the/system/and/how/to/fix/any/difficulties/that/have/arisen./After/e xte
nsive/research/on/the/topic,/technology,/language,/and/tools,/the/developer/is/confident/enou
gh/to/implement/the/suggested/programmer.

CHAPTER/5:/ ANALYSIS
5.1 Analysis/of/Questionnaire
5.1.1 Overall/conclusion/of/Questionnaire
The/users/were/delivered/to/a/variety/of/consumers,/including/students,/servicemen,/and/busi
nesspeople./This/sort/of/primary/research,/which/is/similar/to/a/survey,/helps/the/developer/un
derstand/the/user's/perspective/on/the/issues/they/face/while/Booking/hotel/room/at/the/offlin
e/market/and/how/they/might/be/improved/in/the/railway/environment./The/q uestionnaire-
based/survey/provided/the/developer/with/a/thorough/grasp/of/the/customers'/needs/when/Bo
ok/Hotel/room/via/Online/mode./As/a/result/of/their/input,/the/developer/was/able/to/implem
ent/the/features/that/these/users/wanted.
5.2.1/// Overall/conclusion/of/Intervie w
The/purpose/of/the/study/was/to/get/developer/feedback/on/the/planned/application/to/be/cre
ated./The/developer/benefited/greatly/from/this/type/of/study/in/identifying/the/issues/that/us
ers/have/while/ordering/general/Book/hotel/room/in/offline/mode/in/a/environment,/as/well/a
s/possible/remedies/to/the/issues./Only/the/actual/end-
users/who/would/implement/the/system/provided/knowledge/to/the/developer/of/the/proposed
/system/about/the/required/functions,/pros/a nd/drawbacks/of/each/module./As/a/result,/the/dev
eloper/focused/on/users/who/wish/to/go/by/book/room/and/want/to/take/room/at/rent/,/which/
is/where/such/a/system/may/be/built.

CHAPTER/6:/ SYSTEM/DESIGN
6.1 Introduction
When/the/developer/has/completed/the/research/and/analysis/phase,/the/design/phase/begins.
/The/design/step/entails/converting/user/specifications/and/software/components/into/a/softwa
re/interface/in/order/to/provide/a/platform/for/the/system's/implementation./It/includes/the/creat
ion/o f/system/blue/prints,/as/well/as/physical/modelling/utilizing/software/engineering/tools/a
nd/procedures.
The/requirements/are/used/as/input/in/the/design/phase/of/the/proposed/system,/and/the/desig
n/will/generate/a/guideline/for/implementation/as/a/result./After/finishing/the/research/and/an
alysis/portion,/three/to/four/design/components/for/each/module/must/be/created/and/provide
d/as/input/to/the/design.
6.2 UML/Diagram
Use/Cases:/The/developer/will/need/use/cases/so/that/the/flow/of/the/capabilities/specified/in
/the/proposed/system/can/be/analyzed/in/order/to/validate/the/architecture/and/assess/the/com
plexity/level/of/individual/modules./As/a/result,/forward/and/reverse/engineering/would/be/be
neficial/in/evaluating/the/system./Booch,/Rumbaugh,/and/Jacobson/(2008;/Booch,/Rumbaug
h,/&/Jacobson,/2008;/Booch,/Rumbaugh,/&/Jacob
Activity/Diagrams:/The/developer/will/use/Activity/Diagrams/to/depict/the/flow/of/control/o
f/software/modules/from/one/activity/to/the/next./This/would/aid/us/in/demonstrating/concur
rency/and/control/branches/in/the/proposed/system./Booch,/Rumbaugh,/and/Jacobson/(2008;/
Booch,/Rumbaugh,/&/Jacobson,/2008;/Booch,/Rumbaugh,/&/Jacob
6.2.1 Use/Case
6.2.2 Use/diagram/of/login
Login <<include>> OTP/verifi cation
<<include>>
Register/Us er
User
Table/11:Use/Case/Diagrams/of/Login

Use/ID UC-001
Use/Name Login
Describe This/makes/the/user/to/sign/in/to/his/account.
Actor(s) User/Admin
Assumption  Actor/should/have/internet/connectivity/so/can/signing/in.
Pre-Condition  The/actor/might/be/a/registered/user.
Post-Condition  Signed/In/successfully.
Primary/Pathway  Actor/press/on/Log/ In/button/ from/app/dashboard.
 Actor/strike/email/and/password.
 Actor/press/on/sign/in.
Alternate/Pathway(s)  Need/to/sign/ in/ to/synchronize.
Exception/Pathway  Actor/enters/email/and/password.
 The/ email/and/password/is/incorrect/does/not/exist/ in/databas
e.
 System/tells/ the/actor/to/re-enter/ the/ username/password.
 Go/in/step/2/of/primary/pathway.
Table/12:Use/Description/of/Login

6.2.3 Use/case/diagram:/view/Profile
UC-03
Profile <<extends>> Select/ID/
<<include>>
User Upload/ID/no.
Table/14:Use/Diagram/of/View/Profile

Use/ID UC-05
Use/Name View/Users
Description These/all/the/user/to/view/the/Hotel/list/when/user/can/search/t
he//Hotel/room/when/he/entered/the/source/and/destination/plac
e.
Actor(s) User/who/is/willing/to/travel
Assumption  We/think/that/user/already/login/into/the/system.
 We/think/that/ user/ must/know/ the/ source/and/ the/destinatio
n/station.
Pre-Condition  User/enter/the/source/station.
 User/makes/the/destination/station.
 User/press/the/view/Book/button.
 User/press/the/image/button/to/display.
Post-Condition  List/of/users/are/displayed
Primary/Pathway  Click/on/the/make/payment
 Enter/the/source/user
 Enter/the/destination/user
Alternate/Pathway(s) None
Exception/Pathway  It/may/happen/ that/ use/ wants/ to/ view/ the/ Hotel/Name/list/ w
ithout/e nter/the/source/and/the/destination

6.2.4 Use/case/Diagram:/create/Account
UC-08
Table/17:Use/Case/Description/Book/Create/Account
6.2.5 Use/case/Diagram:/view/Book/Hotel/Room
UC-05
Use/ID UC-05
Use/Name View/pack
Description This/all/the/user/to/view/the/train/list/when/user/can/search/th
e/train/when/he/entered/the/source/and/destination/station
Actor User/who/is/willing/to/travel
Expectations  We/assume/that/user/already/login/into/the/system.

 We/assume/that/user/must/know/the/source/and/the/destination
station.
Primary/Condition  User/enters/the/source/station.
 User/enters/the/destination/station.
 User/press/the/view/Book/Package/button.
 User/press/the/image/button/to/display.
Post/-/Condition  List/of/wallets/are/displayed
Pre-Pathway  Click/on/the/payment
 Enter/the/source/user
 Enter/the/destination/user
Another/Pathway(s) None
Exception/Pathway  It/ may/ happen/ that/ use/ wants/ to/ view/ the/ package/list/ wit
hout/enter/the/source/and/the/destination
6.2.6 Use/Case:/change/Personal/Detail
UC-09
Change /Password <<extends>> Update/Pers.Detail

* *
<<include>>/ <<include>>/
<<include>>
USER
Current/Number Current/Id
New/Password
Table/18:Use/Case/Diagram/Change/Personal/Detail

6.2.7 Use/case:/transactions
UC-07
Table/19:Use/Case/Diagram/Book/General/Ticket/History
Use/ID UC-07
Use/Name Transactions/History
Description This/allows/the/view/history.
Actor All/user/who/willing/to/payment
Exception  We/assume/that/user/already/login/into/the/system.
Primary/Condition  User/must/be/login
Post/-/Condition  Wallet/displayed
Pre-Pathway  Click/on/the/ view/general/ ticket
Left/Pathway None
6.2.8 Use/case:Notepad
UC-08
Table/20:Use/Case/Diagram/Transaction/History

Use/ID UC-08
Use/Name Transaction/History
Description This/allows/the/user/to/book/the/Transaction/History/without
standing/in/long/queue.
Actor(s) All/user/who/willing/to/make/payment.
Assumption  We/assume/that/user/already/login/into/the/system.
Pre-Condition  User/click/the/platform/button/to/view/history
Post-Condition  Ticket/Displayed
 Click/on/details/to/view/details.
 User/also/view/wallets/on/map.
Primary/Pathway  Click/on/the/ view/platform
Exception/Pathway  User/wants/to/view/the/ ticket/details/without/click/on/ ticket.
6.2.9 Use/case/Diagram:/View/Profile
UC-09
Profile <<extends>> Select/Image
<<include>>
TT Upload/Image
Table/21:Use/Diagrams/View/Profile
Use/ID UC-09
Use/Name TTE/Module:/View/the/Profile
Description This/makes/the/actor/to/view/his/own/profile/and/also/able/to/change
the/profile/picture/and/also/able/to/see/the/amount/available/in/hi
s/account.

Actor TTE
Exception  We/expect/that/to/change/the/profile/it/has/select/the/image/fro
m/phone/gallery.
Primary/Condition  TTE/should/be/having/his/login/credentials.
Post/-/Condition  TTE/may/be/able/to/view/the/profile/and/profile/is/changed
Pre-Pathway  TTE/provides/his/login/credentials.
Left/Pathway  It/might/happen/that/without/select/the/any/picture/TTE/wants/to
upload/the/picture.
Table/22:Use/Case/Description/View/Profile
6.2.10 Use/case/Diagram:/Add/detail
UC-10
Phone/Number /
<<extends>> Detail
* *
<<include>> <<include>>
User/email/ID Recharge/amount
TT
Table/23:Use/Case/Diagram/Recharge/User/Account
Use/ID UC-10
Use/Name Recharge/User/Account
Description This/allows/the/TTE/to/recharge/the/user/account/and/give/the
/flexibility/to/the/user/to/book/the/ticket/from/his/wallet/amou
nt
Actor(s) TTE
Assumption  TTE/know/the/email/of/the/user.
 Email/exists/in/the/database

Pre-Condition  TTE/enter/the/email/ID
 TTE/enter/the/amount/to/be/recharge
Post-Condition  User/account/is/recharged/successfully
Primary/Pathway  Click/on/the/recharge/user/account
 Enter/the/email/ID
 Enter/the/amount/to/be/recharge
Exception/Pathway  Amount/is/not/available/to/recharge/the/account
 Email/not/exists/in/the/database
Table/24:Use/Case/Description/Recharge/User/Account
Use/Diagram/for/Admin
UC-11
Table/25:Use/Diagram/of/Admin
Use/Case/ID UC-11
Use/Case/Name Admin/Module
Description This/allows/the/admin/to/view/active/user,/search/user,/registe
r/new/TTE,/register/new/user,/search/user
Actor(s) Admin
Assumption  Admin/should/have/some/knowledge/about/the/Admin/terms.
 Admin/already/login/into/the/system.

Pre-Condition  Admin/must/have/an/android/device/with/auto/perform/the/task.
Post-Condition  Admin/get/a/powerful/App/to/perform/the/task.
Primary/Pathway  Admin/search/the/user.
 Admin/also/able/ to/ view/ the/own/profile/and/ have/option/ t
o/change/the/profile/picture
 Admin/can/update/the/details/of/the/user
Left/Pathway  It/might/happen/that/at/the/time/of/login/admin/enter/the/incorrect
email/and/password.
Table/26:Use/Diagram/Description/for/Admi
n/Use/Diagram:/Vie w/Profile
UC-12
Profile <<extends>> Select/Image
<<include>>
Admin Upload/Image
Table/27:Use/Diagram/Vie w/Profile
Use/ID UC-12
Use/Name Admin/Module:/View/Profile
Description This/allows/admin/to/view/own/profile/and/also/able/to/change/the
profile/picture.
Actor Admin
Expectation  We/may/that/to/change/the/profile/it/has/select/the/image/fro
m/phone/gallery.
Primary/Condition  Admin/should/be/having/his/login/credentials.
Post/-/Condition  Admin/is/able/to/view/profile/and/profile/is/changed
Pre-Pathway  Admin/provides/his/login/credentials.

Left/Pathway  It/might/happen/that/without/select/the/any/picture/admin/wants
to/upload/the/picture.
Table/28:Use/Description/of/Vie w/Profile
 Use/Diagram:/Admin/Panel
UC-13
Table/29:Use/Case/Diagram/of/Admin/Panel
Use/Case/ID UC-13
Use/Case/Name TC/Panel
Description This/allows/the/admin/to/manage/the/register/new/user,/register/n
ew/TTE,/sear/the/user,/view/all/registered/user,/and/also/view/the/
active/user/of/the/system
Actor(s) Admin
Assumption  We/assume/that/admin/already/login/into/the/system
 We/assume/that/button/of/the/tc/panel/will/work/properly
Pre-Condition  Admin/click/on/the/Tc/panel/to/perform/the/further/task
Post-Condition  Tc/panel/activity/open/successfully
Primary/Pathway  Admin/must/be/login/into/the/system.

 Admin/click/on/the/Tc/panel/button/to/perform/the/task/of/the/tc
panel
Exception/Pathway  Tc/panel/button/not/work
Table/30:Use/Description/of/Admin/Panel
 Use/Case/Diagram:/Search/User
UC-14
Search/Employee / <<extends>> Search
<<include>>
Admin User/ID/Name
Table/31:Use/Diagram/of/Search/User
Use/ID UC-14
Use/Name Search/Employee
Description This/allows/the/admin/to/search/the/user/from/the/system/and/p
erform/the/further/task/like/update/user,/activate/and/deactivate/
user.
Actor(s) Search/Employee
Assumption  We/assume/that/email/exists/in/the/database.
 We/assume/that/field/should/not/be/blank/at/the/time/of/searc
h/user
Pre-Condition  Admin/must/be/login/into/the/system
 Email/exists/in/the/database
Post-Condition  User/is/search/successfully
Primary/Pathway  Admin/must/be/login/into/the/system
 Email/exists/in/the/database.
 Admin/click/on/the/tic/panel/button
 Admin/click/on/the/search/user/button
 Admin/enter/the/email/id/of/the/user

Exception/Pathway  Email/not/exists/in/the/database
 Search/button/not/able/to/find/the/email
Table/32:Use/Description/of/Search/User
 Use/Case/Diagram:/Active/User
UC-15
Active/Users <<extends>> Update/user/profile
<<extends>>
Manage/Status
Admin
Table/33:Use/Diagram/of/Active/User
Use/Case/ID UC-15
Use/Case/Name Active/User
Description This/allows/the/admin/to/manage/the/status/of/the/user./It/has/the/a u
thority/to/make/the/user/activate/or/deactivate.
Actor(s) Admin
Assumption  We/assume/that/some/user/is/found/in/the/active/user/list
 We/assume/that/button/of/the/active/user/is/work/properly
Pre-Condition  Admin/must/be/login/into/the/system
 Active/user/exists/in/the/database.
Post-Condition  Active/user/displayed
Primary/Pathway  Admin/must/be/login/into/the/system
 Admin/click/on/the/tic/panel
 Admin/click/on/the/active/user/button
Exception/Pathway  It/ may/ happen/ that/ none/ of/ the/ active/ users/ are/ exists/ in/ the
database
Table/34:Use/Case/Description/of/Active/User

 Use/Case/Diagram:/Manage/Status
UC-16
Manage/Status <<extends>> Deactivate/user
Admin
Table/35:Use/Diagram/of/Manage/Status
Use/Case/ID UC-16
Use/Case/Name Manage/Status
Description This/allows/the/admin/to/manage/the/details/of/the/user
Actor(s) Admin
Assumption  Some/of/the/user/is/exists/in/the/database/to/manage/the/status.
 Admin/login/into/the/system.
 Admin/know/how/to/manage/the/status/of/the/user.
Pre-Condition  Admin/must/be/login/into/the/system.
Post-Condition  User/status/successfully.
Primary/Pathway  Admin/must/be/login/into/the/system.
 Admin/Click/on/the/active/user
 Admin/click/on/the/particular/Email/ID/to/manage/the/status.
Exception/Pathway  Admin/not/click/on/the/particular/ID
Table/36:Use/Case/Description/of/Manage/Status

 Use/Diagram:/Change/Password
UC-17
Chan g e/P ass wo r d <<extends>> Updat e /P assw o r d

* *
<<include>>/ <<include>>/
<<include>>
Admin
Current/Password Confirm/Password
New/Password
Table/37:Use/Case/Diagram/of/Change/Password
Use/ID UC-17
Use/Name Change/the/password
Description This/allows/admin/to/change/password/of/his/account
Actor(s) Admin
Assumption  We/assume/admin/already/login/into/the/system.
Primary-Condition  Admin/must/be/login
Post/-Condition  Change/the/ Password/Successfully
Pre-Pathway  Click/the/change/password
 Enter/ current/password
 Enter/ new/password
 Enter/confirm/password
Left/Pathway  It/might/be/possible/us/admin/entered/the/wrong/curren
t/password.
 It/might/be/possible/that/new/and/confirm/password/does/no
t/match.
 It/might/be/possible/user/do/not/fill/any/fields.
Table/38:Use/Case/Description/of/Change/Password

6.2.2 Sequence/Diagrams
 Sequence/Diagrams/for/User
 Sign/In
SQ-01
Custom er :Users Datab ase
1.0/Enter/Login/C redentials 1.1/Forw ard/D etails
1.2/Validate/Credentials( )
1.4/Login/Succ essful 1.3/Credentials/Matched
Table/39:Sign/In
 Register
SQ-02
Custom e r :Users Datab a s e
1.0/En ter /th e/d eta ils/of/the /use r
1.1/Ver ify/the /e m ail
1.2/Che c k/em a il/ID

1.3/Em ail/C onf irm a tion
1.4/Ver ify/pa ssw or dl
1.5/Che c k/pa sswo rd/le ngth

1.6/Pas swor d /V er ifie d
1.6/Re gistra tion( )
1.8/Che c k/all/de tails

1.9/All/de ta ils/c he c ke d
2.1/Re gistra tion /S uc c essf ull 2.0/Deta ils/sav ed
Table/40:Register

 View/Profile
SQ-03
User :P rofile Database
1.0/View/P rofile
F orward/details
1.1/S elect/im age/t o/upl oa d
1.3/Im age/Vali dat ed 1.2/Validate/the/i m a ge/ siz e( )
1.4/Upload/Im ag e
1.7/Im age/Uplo ad ed 1.6/Im age/S av ed 1.5/C heck/intern et/ co nn ectivit y
Table/41:View/Profile
 Change/Password
SQ-04
User Database
1.0 Change/Password
Forward/details
1.1 Enter/current/pass word
1.3 Password/matched 1.2/Validate/the/current/pass word
1.4 New/password
1.6 Password/verified 1.5/Check/password/length
1.7 Confirm/Password
2.0/Password/Changed 1.9/Password/verified 1.8/Match/password()
Table/42:Change/Password

 Sequence/Diagrams/for/Book/Package
 View/Profile
SQ-01
TTE :P rofile Database
1.0/View/Profil e
Forward/details
1.1/Select/image/to/upl oad
1.2/Validate/the/image/size()
1.3/Image/Vali dated
1.4/Upload/Image
1.7/Image/Uploaded 1.5/Check/internet/connecti vity

1.6/Image/Saved
Table/43:Sequence/Diagrams/of/View/Profile
 Add/Balance
SQ-2
TTE :Ticket Database
1.0/ Rechar g e/ Us er/ Ac c ount

1.1/Enter/Us e r// I D
1.3/Email/ E xists 1./2/Chec k/ E m ail( )
1.4/Enter/ A mou nt
1.5/ check/ wall et/ mo ne y( )
1.6/ Amount/ Av aila bl e
1.7/ Account/ Re c ha rg ed/ S uc c es fully
Table/44:Add/Balance

 Change/Password
SQ-3
TTE Data b a s e
1 . 0 Chan g e /Pa s s w or d
Forw ar d / d e tails
1 . 1 Enter/c u rr e n t /p a s s w o r d
1 . 3 Passw o r d /m a tc h e d 1.2/V a lid a te /th e /c u r re n t /p a s s w or d
1 . 4 New/pa s s w o r d
1 . 6 Passw o r d /v er if ie d 1.5/ Ch ec k /pa s s w o r d /le n g th
1 . 7 Conf ir m /P a s s w o r d
2.0/Pa s s w o r d /C h a n g e d 1.9/Pa s s w o r d /v er if ie d 1.8/ M a tc h /pa s s w o r d( )
 Sequence/Diagrams/for/Admin
 View/Profile
SQ-1
Admin :Profil e Data b a s e
1.0/View/Profil e
Forward/details
1.1/Select/image/to/upl oad
1.2/Validate/the/image/size()
1.3/Image/Vali dated
1.4/Upload/Image
1.5/Check/internet/connecti vity
1.7/Image/Uploaded 1.6/Image/Saved

 Register/User
SQ-2
Admin :Users Database
1.0/Enter/th e/ det ail s/o f/th e/ us e r
1.1/Verify/t h e/ em ail
1.3/Em ail/C on fi rm ati on 1.2/C heck/ em ail/ I D
1.4/Verify/ p ass w or dl
1.5/C heck/p as s wo rd/l e ngt h

1.6/P asswor d/ V eri fi e d
1.6/R egistrati on ( )
1.9/All/details/ c h e ck e d 1.8/C heck/ all/d et ail s
2.1/R egistrati on/ S u c c ess ful l 2.0/Details/s a ve d
Table/47:Register/User
 Register/TTE
SQ-3
Admi n TTE Dat a b a s e
1.0/En te r /the /d et ai ls/of /th e/u se r
1.1/V e rif y/th e /e m a il
1.2/C h e ck /e m a il/I D
1.3/Em a il/C o nf ir m a tio n
1.4/V e rif y/p a ssw o r dl
1.6/P a ssw o r d/V e ri fie d 1.5/C h ec k /pa ss w or d/le n gth
1.6/R e gis tra ti on ()
1.8/C h e ck /a ll/de ta ils

1.9/A ll/de ta ils/c h e c ke d
2.1/R e gis tra ti on /S u c c e ssf u ll 2.0/D e ta ils/sa v e d
Table/48:Register/TTE

 Change/Password
SQ-4
Admin Database
1.0 Change/ P assword
Forward/details
1.1 Enter/current/ password
1.3 P assword/ matched 1.2/Validate/the/ cur rent/ pass word
1.4 New/password
1.6 P assword/ verified 1.5/ Check/ password/ length
1.7 Confirm/ P ass word
2.0/P assword/Changed 1.9/P assword/verifie d 1.8/Match/passwor d()
 Active/User’s
SQ-5
Admin User Databas e
1.0/Clic k/Active/User 1.1/De tail/Pass

1.3 All/Use r/Displayed 1.2/fe tc h/data()
1.4 Clic k/User 1.5/De tail/Pass
1.6/fe tc h/data()
1.7 de ta ils/displayed
1.8Upda te /User 1.9/ De ta il/Pass
2.1/User/Details/Updated 2.0/Update/User/Details()
Table/50:Active/User’s

 Search/User’s
SQ-6
Admin :User Database
1.0/Search/User 1.1/Detail/Pass
1.3 All/ticket/Displayed 1.2/fetch/data()
1.4 Click/User 1.5/Detail/Pass
1.6/fetch/data()
1.7 details/displayed
1.8Update/User 1.9/ Detail/Pass
2.1/User/Details/Updated 2.0/Update/User/Details()
Table/51:Search/User’s
6.2.3 Activity/Diagram
 Register
AD-01
[Check/if/det ails/
are/correct]
Click/New/USer Registation/activity/open Enter/registration/details
[NO]
[Yes]
[No] Check/if/email
Registration/done/successfully
already/exists
[Yes]
Re-enter/email/ID
Table/52:Register

 Login
AD-02
[Check/if/details/
are/correct]
Click/login Login/activity/open Enter/login/credentials
[NO]
[Yes]
Registration/done/successfully
Table/53:Login
 Forgot/Password
AD-03
[E nte r/e m a il]

Forgot/password Forgot/password/activity/open Enter/email
[Ye s]
[NO]
[NO]
[Ye s] [E m a il/e xists/or/not]

Submit
Table/54:Forgot/Password
 Activity/Diagrams/for/User
 View/Profile
AD-04
[Va lida te/the/
im a ge /siz e ]
//////////////Click/Profile View/profile/activity/open Select/ Image
[Ye s]
[NO]
Upload/Pic

CHAPTER/7:/ IMPLEMENTATION
7.1 Introduction
Following/the/end/of/the/design/phase,/the/developer/determined/that/the/needs/listed/mu
st/conform/to/the/system/development/schema/suggested./The/developer/works/to/turn/the
/system/design/into/a/real/system/during/the/implementation/phase,/which/is/one/of/the/mo
st/c rucial/stages/of/any/project./The/implementation/phase/entails/the/creative/application/
of/tools/to/turn/design/modules/into/a/fully/functional/system./A/programming/language/
and/a/programming/tool/would/be/required/for/working/on/the/real/system/by/the/develo
per./The/developer/decides/to/work/using/the/Android/SDK/and/JAVA/as/the/programmi
ng/language./A/succession/of/failures/plagued/the/developer,/slowing/down/the/impleme
ntation/process./This/chapter/also/contains/some/additional/information.
7.2 Tools/for/imple mentation

Followings/are/the/tools/used/for/the/development/of/the/system:
Tools Purpose
Windows/10 It/is/used/as/an/operating/system/which/helps/in/running
the/tools
Java/development/kit building/applications,/applets,/and/components/using/the
Java/programming/language
Microsoft/project Used/to/prepare/the/chart
Microsoft/word Used/to/document/the/project
Microsoft/PowerPoint Used/to/present/the/presentation/slide
MySQL Used/as/a/database
Netbeans JVM languages designed to maximize developer

productivity

7.3 Implementation/plan
7.3.1 Implementation/Approach
This/plan/would/give/the/developer/an/overview/of/the/procedures/required/in/constructin
g/t he/real/system./A/strategic/strategy/is/required/to/successfully/finish/a/system./The/'divi
de/a nd/conquer'/method/splits/the/system/into/separate/components,/making/it/easier/to/de
tect/a nd/correct/errors./The/aim/is/to/priorities/various/modules/depending/on/their/difficu
lty,/with/the/most/complicated/modules/being/generated/first,/so/that/each/one/can/be/comp
leted/on/time.
7.3.2. Implementation/Approach/Steps
1. There/is/only/one/app/in/the/system,/and/it/has/only/three/phases./User,/TTE,/an
d/t he/most/recent/Admin./TTE/version/can/only/work/if/any/user/has/booked/a/tic
ket/a nd/the/information/have/been/saved/to/the/server./So,/first,/the/app's/user/pha
se/must/be/constructed,/followed/by/the/TTE/phase.
2. The/first/stage/is/to/build/the/app's/registration/and/login/sections/so/that/anyon
e/can/log/in/and/fulfil/their/functions.
3. The/next/step/is/to/add/a/forget/password/option/so/that/if/a/user/forgets/his/pa
ssword,/he/or/she/can/recover/it.
4. After/logging/in/and/registering,/we/must/move/on/to/the/system's/user/functio
nality./Then/we/must/first/develop/the/dashboard,/which/will/allow/users/to/access
/to/various/sections/of/their/module.
5. After/constructing/the/dashboard,/we/must/complete/the/tasks/that/are/dependin
g/o n/it./We/can't/check/the/booking/history/without/completing/the/book/ticket/pr
ocess,/for/example./As/a/result,/we/must/first/book/a/ticket.
6. After/finishing/the/book/ticket,/we/must/develop/the/generate/QR/code/functio
n/so/that/when/we/create/the/TTE/functionality,/he/may/scan/the/QR/code/to/valid
ate/the/ticket./As/a/result,/the/next/step/is/to/create/the/QR/Code/functionality.
7. After/producing/the/QR/code,/we/must/proceed/to/the/user's/history/section,/wher
e/we/must/construct/the/ticket's/history/so/that/the/user/may/examine/it.
8. Finally,/in/order/for/the/user/to/access/his/profile,/we/must/implement/the/view
/profile/functionality.

7.3.3 Implementation/of/complex/modules
 Login
Login
Description
This/is/one/of/the/ most/important/modules/of/the/system/because/ without/ this/no/one/can
access/the/system.
Pseudocode
BEGIN.
Input/Email/In
put/Password
IF/(Email/Match/with/Password)/THEN/Displ
Login ay/Respective/User/Type/Homepage
ELSE
Please/Enter/Valid/Email/and/Passwor
d/END/IF
END
 Add/Balance
Tour/&/Travel//Management/
System
Description
This/feature/allows/the/TTE/to/recharge/the/user/account/using/the/wallet/money/present/in
his/account./It/will/provide/users/a/hassle-
free/booking/as/they/will/not/have/to/go/through/t he/queue/at/the/payment/counter/to/book
/the/ticket
Pseudocode
BEGIN.
Enter/Email/E
Add/Balance nter/Amount

7.4 Technical/Quality/and/other/features
7.4.1 Memory/Utilization
7.4.2 Performance
 The/built/software/is/adaptable/enough/to/function/on/any/Android-
based/phone/with/minimal/specifications/while/maintaining/the/same/level/o
f/performance./Because/the/app/is/compatible/with/the/least/recent/SDK/versi
on/14,/it/covers/around/95%/of/the/Android/market.
 The/performance/of/the/app/is/unaffected/by/the/mobile/device's/CPU/speed.
 The/programmer/is/adaptable/to/slower/internet/connections.
7.4.3 User/interface
 The/user/interface/adheres/to/the/HCIU/concepts/discussed/before.
 The/text-
field/sizes/are/based/on/the/Gmail/and/Facebook/apps,/which/are/ the/ most/popular/
among/mobile/users.
 For/a/better/comprehension/of/menu/items,/buttons,/and/text/displays,/metaphors/ar
e/employed.
 The/app's/settings/and/menu/icons/are/internationally/recognisable.
 On/GUI/and/Usability/testing,/more/user/interface/aspects/will/be/discussed.

CHAPTER/8:/TESTING
The/work/method/for/generating,/developing,/and/enhancing/the/prototype/for/each/test/itera
tion/is/described/in/this/chapter.
8.1 Tasks/to/be/analysed
The/following/tasks/were/chosen/for/testing:
Pay/via/manual/input
Manually/enter/payment/details/to/transfer/money.
Via/QR
///Transfer/money/by/QR
/
Exchange
Exchange/of/currency.
These/challenges/were/selected/because/they/put/the/app's/most/important/features/to/the/test
./These/were/the/most/difficult/jobs,/as/well/as/the/ones/with/the/most/room/for/improvement
.
Instructional/and/scene/cards/were/prepared/and/delivered/to/users/on/paper/to/indicate/what/
job/should/be/completed/and/what/objective/they/attempted/to/attain./It/ contains/the/instructio
n/a nd/scene/cards/that/were/shown/to/the/users/for/each/activity./As/previously/indicated,/the/j
ob/was/assigned/to/test/individuals/in/a/random/sequence./This/is/to/ensure/that/the/education
/in/order/of/one/activity/do/not/impact/the/outcome/of/the/others./The/work/instructions/were
/slightly/amended/to/adhere/to/the/new/prototype/design/when/the/prototype's/design/change
d.
8.2 Test/group
Table,/which/is/displayed/below,/lists/the/testing/group/and/their/characteristics./As/shown/in
/the/first/column/of/the/table,/each/test/participant/was/assigned/a/number/to/represent/them./
The/second/column/depicts/their/impressions/of/mobile/payment/applications,/and/the/third/c
olumn/depicts/their/impressions/of/software/development/as/measured/by/a/five-
point/Likert/scale.

On/the/amount/of/agreement/between/the/two/assertions,/the/Likert/scale/spans/from/1:/Disa
gree/strongly,/2:/Disagree,/3:/Both/agree/nor/disagree,/4:/Agree,/and/5:/Strongly/agree./(1)/Yo
u've/used/mobile/payment/apps/before,/and/(2)/you've/worked/with/software/development/be
fore.
Table/4.1:/The/test/subjects/and/their/perceived/experience/using/mobile/payment/apps/and/e
xperience/of/software/development.
SUBJECTS ROOM/BOOKING//APP DEVELOPMENT
1 4 5
2 2 4
3 4 3
4 3 4
5 3 4
6 5 1
7 2 5
8.3 Testing
Cent/globe/provided/the/specifications/for/the/prototype./Appendix/E/contains/all/of/the/prot
otypes./Before/they/began/engaging/with/the/prototype/and/after/reading/the/task/instructions
,/the/test/subjects/were/asked/if/they/had/any/questions./The/concept/of/the/app/was/acknowle
dged/as/being/difficult/to/grasp/for/the/test/subjects/based/just/on/the/task/instructions.
White/Box/Testing/(Conceptual/Testing)
White/box/testing,/also/known/as/Code-
Based/Test/or/Logical/Testing,/is/a/software/testing/approach/that/exposes/the/system's/or/co
de's/fundamental/implementation/or/structure./Somebody/who/is/a/hard/coder/or/a/programm
er/will/execute/the/tests./It/is/a/step/ahead/of/the/ui/since/it/is/concerned/with/the/internal/desi
gn/structure/or/implementation/rather/than/the/exterior/structure/or/interface./The/testing/is/u
sed/to/check/the/proposed/system's/or/application's/internal/workings.

Justification/for/Integration/Testing
When/the/developer/has/individually/tested/all/of/the/system's/components,/integration/testin
g/may/be/used./Following/the/testing/of/separate/modules,/the/modules/are/combined/and/eva
luated/to/see/if/they/perform/properly.
System/Testing
System/testing/is/a/technique/for/determining/if/a/system/works/properly/and/executes/correctl
y/when/all/of/its/modules/are/combined/into/a/single/system./The/mapping/of/the/requirement
s/given/with/the/output/data/or/application/created/is/also/part/of/the/testing.
Justification/for/System/Testing
After/all/of/the/modules/have/been/integrated/and/tested,/this/type/of/testing/is/conducted/on/
the/proposed/system/to/ensure/that/the/system/as/a/whole/fit/the/criteria/and/has/no/errors/or/
weaknesses./After/all/of/the/system's/modules,/such/as/the/view/profile/and/book/ticket/mod
ules,/have/been/implemented/and/tested/individually,/one/module/is/integrated/with/the/other
/and/tested/for/integration,/and/after/all/of/the/modules/have/been/completed/with/integration
/testing/individually,/system/testing/is/performed/to/test/the/system/as/a/whole.
Compatibility/Testing
The/testing/procedure/is/a/type/of/quasi-
testing/that/determines/whether/the/hardware/and/software/platforms/of/a/system/are/compati
ble./The/testing/ensures/that/the/final/programme/or/s ystem/runs/smoothly/across/a/variety/of/
platforms,/taking/into/consideration/the/operating/system,/software,/and/hardware./The/purpo
se/of/this/testing/is/to/check/if/the/proposed/system/works/in/a/specific/environment/that/com
prises,/among/other/things,/hardware,/software,/a/network,/and/an/operating/system.
Conclusion
The/proper/approaches/are/used/depending/on/the/goal/of/testing/and/the/software/require
ments,/such/as/the/bottom-
up/methodology/for/testing/phase./At/various/levels,/various/testing/methodologies/have/
been/utilized/to/test/the/systems/functionally/and/conceptually./Black/box/testing/was/use
d/to/evaluate/the/system's/functionality,/whereas/white/box/testing/was/used/to/test/the/sy
stem's/logic.

Unit/testing/is/the/initial/step/in/the/testing/process,/and/it/involves/evaluating/each/Capul
et/o f/the/system,/both/functionally/and/conceptually./Test/Cases/have/been/created/to/test/
the/functionality/of/the/module/as/well/as/the/code/flow/of/the/modules/in/order/to/find/an
d/fix/a ny/faults/or/issues/that/may/have/occurred.

CHAPTER/9:/CRITICAL/EVALUTION
9.1////// Critical/Evaluation
Following/the/developer's/completion/of/the/project,/it's/time/to/critically/evaluate/it/by/map
ping/the/project/and/its/needs/to/the/specifications/provided/in/the/project/specification/form.
/Because/the/developer/conducted/considerable/study/into/the/system's/capabilities,/he/condu
cted/a/thorough/examination/of/the/same./Following/study/and/analysis,/the/developer/create
d/the/system/to/define/the/goals,/which/were/then/implemented/and/tested/to/recover/any/fault
s/that/may/have/occurred/in/the/system,/resulting/in/a/bug-
free/system./Now/is/the/moment/to/critically/review/the/system,/which/involves/a/comprehens
ive/examination./The/critical/assessment/is/not/carried/out/module/by/module,/but/rather/as/a
/full/system/to/identify/the/quality,/importance,/and/effectiveness.
9.2. Factors/of/Benefit/(Usefulness/of/System/to/Target/Audience)
Because/the/constructed/system/can/handle/the/difficulties/listed/in/CHAPTER/2's/problem/d
escription/section,/it/is/extremely/valuable/to/the/target/consumers./The/system's/utility/was/e
xplored/in/section/tangible/and/intangible/advantages./The/following/are/some/of/the/advanta
ges/and/benefits:
Cost/efficiency/profits:
 Since,/the/app/targets/to/remove/the/limitations/of/a/dedicated/scanner/or/QR/Code/r
eader/and/clunky/PC./Thus,/it/will/save/ample/amount/of/retailer’s/money.
The/creator/created/this/software/so/that/it/could/be/used/for/free/and/that/it/could/be/accessibl
e/from/anywhere./However,/this/programme/would/need/a/small/amount/of/Internet/connectivit
y,/which/would/be/inexpensive.
Mobility:
 The/entire/POS/has/been/melded/to/a/mobile/phone;/thus,/users/will/get/a/great/adva
ntage/of/mobility.
The/whole/application/will/work/on/mobile/for/a/user/so/user/has/a/great/advantage/of/mobilit
y/while/using/application.

9.3////// Degree/of/Success
The/mappings/of/the/requirements/defined/for/the/proposed/model/in/the/requirement/specifi
cation/form/determines/the/rate/of/success/of/the/project./The/system/should/meet/project/devel
opment/quality/criteria/and/deployment/should/be/possible..
Figure/2:Degree/of/success
9.3.1
Critical/Appraisal
All/of/the/recommended/features/were/attempted/to/be/incorporated/into/the/final/product/by
/the/developer./The/proposed/specs/were/successfully/implemented/in/a/real-
world/system./A/secure/app/is/now/ready/to/be/deployed/once/the/implementation/and/testin
g/steps/have/been/completed./Several/obstacles/occurred/throughout/the/system's/developme
nt./There/were/several/QR/Code/scanning/issues/that/the/developer/had/to/overcome./Rootin
g/an/Android/phone/might/result/in/issues/with/the/phone's/normal/functionality,/as/well/as/h
arm/to/the/CPU/a nd/RAM./There/were/server/issues/since/the/developer/couldn't/work/on/a/lar
ge/server/because/it/would/be/too/expensive/and/inappropriate/for/the/project's/scale.
The/creator/made/every/attempt/to/complete/this/component/as/intended,/but/due/to/technical
/and/software/obstacles,/he/was/unable/to/do/so./The/developer/has/finished/his/part/of/the/pr
oject/and/is/now/working/on/the/same/topic/as/his/study./Apart/from/that,/the/developer/has/
complied/with/all/functional/and/non-
functional/criteria,/including/quality,/usability,/and/user/interface./Apart/from/that,/the/progra
m/is/put/to/the/test/in/a/range/of/real-
world/test/situations/to/ensure/a/realistic/outcome,/evaluation,/and/feedback./The/intended/syst
em/is/now/operational/a nd/ready/for/usage./"E-Wallet/Management/System"/is/a/one-of-a-
kind/programme/built/by/the/developer;/no/other/app/like/it/exists/on/the/market.

CHAPTER/10:/CONCLUSION
The/suggested/system,/dubbed/"TOUR/&/TRAVEL/MANAGEMENT/SYSTEM,"/is/extrem
ely/beneficial/to/the/user/since/it/meets/all/of/the/user's/needs/and/meets/all/of/the/quality/an
d/success/criteria./The/suggested/system's/success/is/complete/since/it/satisfied/the/success/cr
iteria/and/accomplished/what/it/was/designed/to./The/system/has/addressed/the/concerns/high
lighted/in/Chapter/2/in/terms/of/the/issues/raised/and/the/solutions/supplied./After/assessmen
t,/the/suggested/system/was/determined/to/successfully/ensure/the/end-
booking/user's/and/checking/in/a/real-
time/context,/thereby/solving/the/problem/as/envisioned.
10.1 Limitation/and/Error/in/the/Developed/System:
 The/project/is/strictly/mobile/based/and/all/the/features/are/for/Android/based/mobile/
only.
 For/some/of/the/features/the/mobile/should/have/internet/&/GPS/enabled.
 A/user/must/login/into/the/system/for/accessing/all/the/features.
10.2 Future/Enhancement
 The/app/can/be/improved/in/future/by/implementing/personalization/features/to/allo
w/users/to/personalize/the/app/as/per/their/requirements.
 The/app/can/be/implemented/to/provide/the/users/with/multi- language/support.
 The/app/can/be/enhanced/in/ future/with/adding/the/money/ in/ his/her/wallet/throug

h/Paytm,/FreeRechrge,/Mobikwik/to/perform/transaction.
 The/app/can/be/enhanced/to/have/a/facility/to/see/the/ticket/history/after/selecting/th
e/particular/dater/from/calendar.
 The/application/will/be/turned/into/a/hybrid/application,/so/it/runs/on/windows,/iOS/an
d/all/other/OS.
10.3 What/would/have/done/if/given/time/redo/the/project?
 If/the/programmer/is/given/a/second/chance/to/complete/this/project,/he/will/almo
st/surely/improve/it.

 Connect/with/IRCTC/server/and/Google/Map:/The/developer/would/like/to/connec
t/with/IRCTC/server/to/show/the/all/train/list./Also,/time/and/distance/of/destination/fro
m/the/user’s/location/can/be/displayed/on/the/map/itself.
10.4 Computational/Challenges
The/biggest/computational/problem/in/the/system/was/using/handlers,/services,/and/auto/refr
eshing/of/data/in/a/single/activity,/as/the/developer/had/to/accomplish/numerous/tasks/in/a/si
ngle/activity,/such/as:/Getting/the/user's/real- time/position/via/GPS/device/takes/5-
10/seconds,/a nd/the/developer/has/no/way/of/knowing/how/long/it/will/take/to/retrieve/the/GP
S/location.
10.5 Learning/Experience/Gathered
 Research/work/taught/me/a/lot:/During/the/early/stages/of/the/project,/the/develope
r/was/unsure/of/what/features/to/put/in/the/system./As/a/result,/the/developer/conducte
d/secondary/research/by/examining/the/research/works/of/other/writers/and/pointing/
out/any/errors/they/made./It/aided/in/the/acquisition/of/in-
depth/knowledge/of/the/subject/domain/as/well/as/the/critical/analysis/of/similar/syste
ms/in/terms/of/their/benefits/and/limitations./Finally,/the/developer/carried/out/primar
y/research/to/acquire/current/user/requirements.
 Developed/stress/and/time/manage ment/skills:/Throughout/the/SDLC,/the/develope
r/took/on/several/tasks/such/as/analyst,/researcher,/database/and/mobile/app/developer
,/and/tester./This/equipped/the/developer/with/the/ability/to/effectively/manage/both/s
tress/and/time./The/programmer/was/able/to/finish/the/project/on/time,/despite/all/of/t
he/stress/and/time/restrictions/that/arose/throughout/the/development/phase.
 Technical/expe rtise:/The/system's/implementation/necessitated/not/just/the/applicatio
n/o f/academic/learning/objectives,/but/also/a/thorough/grasp/of/numerous/mobile/tech
nologies./To/grasp/the/principles/of/android/app/development,/different/services,/My
SQL/database/concepts,/Web/Services,/and/other/topics,/it/was/necessary/to/read/a/va
riety/of/books/and/articles./It/finally/aided/in/broadening/technical/knowledge/and/ma
stery/of/many/languages/and/technologies/such/as/Java,/XML,/JSON,/Android/SDK,/a
nd/others.
 Had/project/manage ment/experience:/The/project/provided/a/good/experience/and/
a/sense/of/working/in/a/corporate/environment./By/completing/the/project/on/schedu
le,

delivering/a/quality/system,/meeting/user/needs,/and/employing/fact-
finding/procedures/to/acquire/requirements,/the/developer/also/performed/an/importan
t/role/as/a/project/manager./The/divide/and/conquer/method/was/used/to/break/down/t
he/entire/project/into/manageable/jobs/and/complete/them/according/to/the/Gantt/char
t's/timeline.
 How/to/fix/problems/and/learn/from/the m:/During/the/implementation/of/the/syste
m,/t he/programmer/encountered/several/faults/and/exceptions,/which/were/resolved/us
ing/a /variety/of/approaches./This/provided/insight/into/how/to/diagnose/and/correct/is
sues/utilizing/a/top-
down/approach./In/addition,/the/developer/learned/how/to/discover/and/rectify/mistak
es,/which/is/a/highly/unique/talent/required/to/create/an/error-free/system.
 Developed/a/high/level/of/confidence:/Initially,/the/developer/struggled/to/create/the
/system's/class./However,/after/doing/research/in/each/phase/of/development,/things/g
rew/simpler/over/time,/demonstrating/a/method/to/design/the/logic/and/circulation/of/t
he/e-
wallet/system./It/took/tenacity/and/a/lot/of/effort,/but/the/team/was/certain/in/one/t hin
g:/if/we/put/in/the/effort/in/the/correct/way,/things/will/get/easier./This/knowledge/ha
s/caused/the/developer/to/become/more/competitive,/as/he/now/believes/that/there/is/a
/solution/to/every/difficulty.

Chapter/11:/References
1. K./P./Prawirasasra,/‘Financial/Technology/in/Indonesia:/Disruptive/or/Collaborative’,
/Report/on/Economics/and/Finance,/vol./4,/no./2,/pp./83–
90,/2018,/doi:/10.12988/ref.2018.818.
2. Deloitte,/‘Cleared/for/Take-off/–
/Five/Megatrends/That/Will/Change/Financial/Services’,/2015./[Online].
3. McWaters/R.J,/Bruno/G.,/Lee/A.,/Blake/M.,/‘The/Future/of/Financial/Services-
How/disruptive/innovations/are/reshaping/the/way/financial/services/are/structured,/p
rovisioned/and/consumed’,/World/Economic/Forum,/2015.
4. B./R./Pachpande/and/A./A./Kamble,/‘Study/of/E-
wallet/Awareness/and/Its/Usage/in/Mumbai’,/Journal/of/Commerce/&/Management/T
hought,/vol./9,/no./1,/pp./33–45,/2018,/doi:/10.5958/0976-/478X.2018.00004.6.
5. [Asosiasi/Penyelenggara/Jasa/Internet/Indonesia,/‘Penetrasi/&/Perilaku/Pengguna/I nte
rnet/Indonesia/2017’,/2017,/2017.
6. ‘The/Little/Data/Book/2018/on/Financial/Inclusion’,/World/Bank,/2018.
7. N./Pranata,/A./Uluwiyah,/A./S./R./Sinaga,/A./Mockler,/and/K./Ringrod,/‘Assessing/th
e/I mpact/of/Digital/Opportunity/on/Financial/Inclusion’,/The/Eighth/Research/Dive/o
n/Financial/Inclusion,/p./19,/2018.
8. H./Pradibta,/‘Acceptance/of/Mobile/Payment/Application/in/Indonesia’.
9. Y./U./Chandra,/‘Bank/vs/telecommunication/E-
Wallet:/System/analysis,/purchase,/and/payment/method/of/GO-
mobile/CIMB/Niaga/and/T-
Cash/Telkomsel’,/in/2017/International/Conference/on/Information/Management/and/
Technology/(ICIMTech),/2017,/pp./165–170.
10. N./Azizah,/P./W./Handayani,/and/F./Azzahro,/‘Factors/Influencing/Continuance/Usag
e/o f/Mobile/Wallets/in/Indonesia’,/in/2018/International/Conference/on/Information/
Management/and/Technology/(ICIMTech),/2018,/pp./92–97.

11. [W.H.DeloneandE.R.McLean,‘TheDeLoneandMcLeanmodelof/information/systems/s
uccess:/a/ten-
year/update’,/Journal/of/management/information/systems,/vol./19,/no./4,/pp./9–
30,/2003.
12. V./Venkatesh,/M./G./Morris,/G./B./Davis,/and/F./D./Davis,/‘User/acceptance/of/infor
mation/technology:/Toward/a/unified/view’,/MIS/quarterly,/pp./425–478,/2003.
13. A./Omarini,/‘The/digital/transformation/in/banking/and/the/role/of/FinTechs/in/the/ne
w/financial/intermediation/scenario’,/2017.
14. K./N./Lemon/and/P./C./Verhoef,/‘Understanding/customer/experience/throughout/the
/customer/journey’,/Journal/of/marketing,/vol./80,/no./6,/pp./69–96,/2016.
15. F./Mohsan,/M./M./Nawaz,/M./S./Khan,/Z./Shaukat,/and/N./Aslam,/‘Impact/of/custome
r/satisfaction/on/customer/loyalty/and/intentions/to/switch:/Evidence/from/banking/sect
or/o f/Pakistan’,/International/Journal/of/Business/and/Social/Science,/vol./2,/no./16,/20
11.
16. K./Das,/T./Tamhane,/B./Vatterott,/P./Wibowo,/and/S./Wintels,/‘The/digital/archipelago
:/How/online/commerce/is/driving/Indonesia’s/economic/development’,/McKinsey/&/
Company,/August,/2018.
17. Snapcart,/‘Indonesian/Consumer/Insights:/The/Growing/Price/of/Maintaining/Custome
r/Loyalty’,/Snapcart/website,/2017.
18. Deloitte,‘EmbracingBricksandClicksinIndonesia.’,Deloitte,2017,/2017./ Retrieved/fro

m
19. W./H./Delone/and/E./R./Mclean,/‘Measuring/e-
commerce/success:/Applying/the/DeLone/&/McLean/information/systems/success/m
odel’,/International/Journal/of/electronic/commerce,/vol./9,/no./1,/pp./31–47,/2004.
20. E.M.Rogers,‘DiffusionofInnovations:modificationsofamodelfor/telecommunications’,/
in/Die/diffusion/von/innovationen/in/der/telekommunikation,/Springer,/1995,/pp./25–
/38.
21. L.-Y./Leong,/T.-S./Hew,/K.-
B./Ooi,/and/J./Wei,/‘Predicting/mobile/wallet/resistance:/A/two-
staged/structural/equation/modeling-
artificial/neural/network/approach’,/International/Journal/of/Information/Management
,/p./102047,/2019.

22. A./Seetharaman,/K./N./Kumar,/S./Palaniappan,/and/G./Weber,/‘Factors/Influencing/B
ehavioural/Intention/to/Use/the/Mobile/Wallet/in/Singapore.’,/Journal/of/Applied/Eco
nomics/&/Business/Research,/vol./7,/no./2,/2017.
23. P./Intarot/and/C./Beokhaimook,/‘Influencing/Factor/in/E-Wallet/Acceptant/and/Use’.
24. M./Saunders,/P./Lewis,/and/A./Thornhil,/Research/Method/for/Business,/7th/ed./Engl
and:/Pearson,/2016.
25. M./R./Ab/Hamid,/W./Sami,/and/M./M./Sidek,/‘Discriminant/validity/assessment:/Use
/of/Fornell/&/Larcker/criterion/versus/HTMT/criterion’,/in/Journal/of/Physics:/Confe
rence/Series,/2017,/vol./890,/p./012163.
26. ‘Partial/least/Squares/Structural/Equation/Modeling/(PLS-
SEM)/Techniques/Using/SmartPLS’,/Marketing/Bulletin,/p./Marketing/Bulletin,/24(1
),/1–32.
27. Bank/Indonesia,/‘Payment/System/Statistics’,/Bank/Indonesia,/2019,/2019.
28. M./Fuksa,/‘Mobile/Technologies/and/Services/Development/impact/on/Mobile/Interne
t/Usage/in/Latvia’,/presented/at/the/ICTE/in/Regional/Development,/Latvia,/2003,/doi
:/10.1016/j.procs.2013.12.006.
29. Gunadi,/S.,/‘Waspadai/Selalu/Dompet/Elektronik/Anda’,/kompasiana.com,/Mar./27,/
2019.
30. H.-
M./Lee/and/T./Chen,/‘Perceived/quality/as/a/key/antecedent/in/continuance/intention/o n
/mobile/commerce’,/International/Journal/of/Electronic/Commerce/Studies,/vol./5,/no
./2,/pp./123–142,/2014.
31. M./M./Ayyash,/‘Scrutiny/of/Relationship/between/E-
Banking/Information/Quality/Dimensions/and/Customer/Satisfaction.’,/JCS,/vol./13,/
no./4,/pp./78–90,/2017.
32. A./Saleem,/A./Ghafar,/M./Ibrahim,/M./Yousuf,/and/N./Ahmed,/‘Product/perceived/qu
ality/and/purchase/intention/with/consumer/satisfaction’,/Global/journal/of/managem
ent/and/business/research,/2015.
33. BCC/Research,/‘Mobile/Wallet/and/Payment/Technologies:/Global/Markets’,/2019./[
Online].

Final Tour & Travel Final Project Report, Aman, 2819154

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Tour & Travel Final Project Report, Aman, 2819154

Uploaded by

Copyright:

Available Formats

/Tour//&/Travel///Management/System

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-1

1.1 Topic/of/the/System .................................................................................................... 9

2.1 Current/Problem/Description .................................................................................... 18

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-2

2.5.2 Economic/Feasibility ......................................................................................... 22

3.1 Introduction/to/Literature/Review ............................................................................. 24

4.1.1 Primary/Research ............................................................................................... 30

5.1 Analysis/of/Questionnaire ......................................................................................... 37

6.1 Introduction ............................................................................................................... 38

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-3

7.1 Introduction ................................................................................................................. 62

10.1 Limitation/and/Error/in/the/Developed/System: ....................................................... 72

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-4

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-5

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-6

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-7

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-8

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-9

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

S./No. Tangible/Benefits Description

S./No. Intangible/Benefits Description

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

This/system/ensures/ that/ user/gets/ the/ value/of/their

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

2.1 Current/Proble m/Description

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-30

 Because/ statistical/approaches/may/be/applied/to/it,/the/ questionnaire/ analysis/is/e ffi

 Because/users/can/answer/questions/anonymously,/ there's/a/better/chance/of/ gettin

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-31

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-32

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-33

 It/will/aid/ in/ the/ gathering/of/detailed/ information/regarding/the/proposed/system'

 A/person's/sentiments,/ ideas,/and/ gestures/can/be/seen/ in/addition/to/ what/ they/sa

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-34

2016 85% 13% 1% 0.6% 0.4%

2015 81.8% 14.9% 2.3% 0.600% 0.4%

2014 86.8% 9.6% 2.5% 0.5% 0.7%

2013 80.8% 11.9% 2.4% 3.8% 1.2%

2012 65.3% 20.6% 3.1% 4.9% 6.1%

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-35

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-36

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-37

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-38

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-39

Login <<include>> OTP/verifi cation

Group-4 PANIPAT/INSTITUTE/ ENGINEERING/&/TECHNOLOGY P-40