Professional Documents
Culture Documents
PROJECT REPORT
ON
BY
Certificate
This is to certify that Ms. Rasika Pashilkar, who is pursuing her MCA from JSPM’s Rajarshi Shahu
College of Engineering, has successfully completed her project “Travel Desk Management Systems”
with us.
The project duration is from January 06, 2020 to June 22, 2020.
Regards,
For Harbinger Systems Pvt. Ltd.
Premlata Mangudkar
Associate General Manager – Talent Management
JAYAWANT SHIKSHAN PRASARAK MANDAL’s
RAJARSHI SHAHU COLEEGE OF ENGINEERING
(Approved by All India Council for Technical Education & Govt.of Maharashtra,)
Affiliated to Pune University I.D. No. - PU/ Engg. / 173 (2001)
Prof. T. J. Sawant Dr. R. K. Jain
D.E.E., B.E. (Elec.) MISTE M. E.(CIVIL Engg) Ph.D
Founder Secretary Principal
Date: 11/09/2020
CERTIFICATE
This is to certify that Ms./Mr. Rasika Pashilkar, is a bonafide student of
JSPM’s Rajarshi Shahu College of Engineering, Tathawade, Pune, has
successfully completed the project work as prescribed by the Savitribai
Phule Pune University, Pune, in the partial fulfillment of the Master of
Computer Applications (MCA) Program 2019-2020.
External Examiner:
Internal Examiner:
Date:
Place: Pune
Sr. No. 80, Pune- Mumbai Bypass Highway, Tathawade, Pune- 411 033.
Phone : +91-020-229334344/4084/4347 Telefax : +91-020-22933424
E-mail : rscoe@vsnl.net Website : www.jspmrscoe.edu.in
Declaration
To
The Principal,
Rajarshi Shahu College of Engineering,
Tathawade,
Pune-33.
Respected Sir,
The system presented here is my own work and has not been
duplicated from any other sources.
Thank You,
Yours Sincerely,
Rasika S. Pashilkar
Acknowledgement
I would like to express my gratitude and sincere regards to
the following people to whom I am grateful for their support
and help without which I would not have been able to do this
project entitled “Travel Management System”.
Rasika S. Pashilkar
Index
Sr.No Title Page No
1 Chapter 1: Introduction 1
1.1 Company Profile 2
1.2 Existing System and Need Of System 4
1.3 Scope of work 7
1.4 Operating Environment – Hardware and
9
Software
2 Chapter 2 : Proposed System 10
2.1 Proposed System 11
2.2 Objective Of System 15
2.3 User Requirements 16
2.4 Feasibility Study 17
3 Chapter 4: Analysis And Design 20
3.1 Use Case Diagram 21
3.2 Class Diagram 28
3.3 Activity Diagram 30
3.4 Sequence Diagram 35
3.5 Component Diagram 41
3.6 Deployment Diagram 42
4 Chapter 4: Implementation 43
4.1 Input Screens 44
4.2 Module Specifications 75
4.3 Table Specifications 79
5 Chapter 5: Testing 85
5.1 Test Procedures and Implementation 86
5.2 Test cases 90
6 Chapter 6: User Manual 102
7 Chapter 7: Drawbacks and Limitations 106
8 Chapter 8: Proposed Enhancements 108
9 Chapter 9: Conclusion 110
10 Chapter 10: Bibliography 112
11 Chapter 11: Annexure 114
11.1 Technology Used 115
11.2 Sample Code 120
Travel Management System
1
CHAPTER
INTRODUCTION
The purpose of this chapter is to provide an introduction to the company
profile and also define basic terminology used in our system that is Travel
Management System. Chapter-1 presents an overview of existing system
and need of system, scope of work and different operating environment.
❖
Company Profile
❖
Project Introduction
❖
Existing System and Need for System
❖
Scope of Work
❖
Operating Environment – Hardware and Software
Page - 1 -
Travel Management System
Page - 2 -
Travel Management System
➢ DEVELOPING PEOPLE
➢ MERITOCRACY
➢ AGILITY
➢ PROFESSIONALISM
➢ INCLUSIVITY
Page - 3 -
Travel Management System
❖ Existing System :
Many a times employees have to travel to client location
for some work, which may include travelling either domestically
or internationally.
➢ Iftravel.
the request is rejected then the employee has to cancel his/her
Page - 4 -
Travel Management System
➢ The admin head checks the travel request details and approves
or rejects the request considering the expense, the designation of
the employee, etc.
➢ Also, the admin head contacts the travel insurance agent and
asks the employee for the nominee details and share to be paid to
the nominee and accordingly takes the insurance for the
employee travelling.
Page - 5 -
Travel Management System
➢ After the entire tour is completed, the employee submits the hard
copy of all the bills like hotel bills, transport bills, stationery bills.
➢and easy
Filling a lot of details in excel sheet is not much convenient
as compared to an online form.
➢regarding
Admin needs to call the respective vendors for enquiry
the availability of bookings on desired dates.
➢manually
The validity of passport/visa expiry needs to be
checked.
Page - 6 -
Travel Management System
➢ This web application will use SSO for login, meaning that the
login credentials will be the same as the employee’s other
harbinger web applications credentials. All the basic employee
information will be fetched from an external API.
➢ The travel request will take the basic employee details like
company name, employee name, employee id, gender, date of birth,
designation, etc. automatically from the database.
➢ The employee will need to provide few details like project name,
delivery head, destination city, departure date, return date, client
address, mode of travel, meal preference, accommodation details.
➢need
Also, for international travel, travel insurance nominee details
to be provided by the employee.
Page - 7 -
Travel Management System
➢ Once the details are filled by employee and he/she submits the
form, all the details will be saved to the database and the request
status will be set to “pending” and an email will be sent to
Delivery Manager informing about the new request that is raised.
➢to Option will be given to the Delivery Manager and the admin head
send the request back for correction.
➢to After the entire tour is done, option will be given to the employee
upload all the bills associated with his/her tour.
➢anyAdmin head will be able to view all the bills of each travel that
employee has made.
Page - 8 -
Travel Management System
❖ Software Requirements:
➢
Operating System Server: Operating system like Windows
XP or later, Linux, Ubuntu, etc.
➢
Database Server : MongoDB 4.2
➢
Client : Mozilla Firefox, Google Chrome or any compatible
web browser
➢
Tools : Postman
➢
User Interface : React JS, Bootstrap, CSS
➢
Code Behind : Node Js 12.14.1 with Node Package
Manager 6.13.4
❖ Hardware Specifications:
➢
Processor: Intel Pentium or More
➢
Ram:2 GB Ram
➢
Hard Disk: PC with 20GB
➢
Output Devices : LCD Monitor, Printer
➢
Input Devices : Keyboard, Mouse
Page - 9 -
Travel Management System
2
CHAPTER
PROPOSED SYSTEM
This chapter gives you an idea about the project which I have undertaken.
It explains the user requirements of the system to be developed leading to
proposing a solution for the same from our side. User requirements we get
from our client so it’s totally based on client need.
❖
Proposed System
❖
Objectives of System
❖
User Requirements
Page - 10 -
Travel Management System
❖
Employee :
➢
Travel Details : o Trip type o
Travel type o
Source city
o Destination city
o Departure date
o Return date
o Mode of travel o
Meal Preference
o Frequent Flyer Number
o Accommodation requirement,etc
Page - 11 -
Travel Management System
➢ After filling these details and submitting the request, all the
details will be stored in the database and an acknowledgement
email will be sent to the employee. Also, email will be sent to
his/her Delivery Manager informing about the new request and
ask to approve or reject the request.
➢ Options will be given to view or edit the details he/she has filled.
➢ Also, after the trip he/she can upload all the bills associated
with his/her tour.
Page - 12 -
Travel Management System
❖ Delivery Manager :
➢ The delivery manager dashboard will have two tabs – one
to display his/her own travel requests, and another to display
the pending approvals that he/she has. In the pending
approvals tab, the details of the basic travel request details will
be displayed of each request that is received. Option will be
given to view the full travel request details that an employee
has filled.
❖ Admin Head :
➢ After viewing the travel request details and the
approximate expense required for the travel, the admin head
will either approve or reject the travel request. If the request
is approved then an email is sent to the requestor informing
him/her the request status.
❖
Email Module
❖
Dashboard
❖
File Upload Module :
Page - 14 -
Travel Management System
➢
The main objective of the system is to develop a user-friendly
system that automates the manual process of travel request.
➢
The employee should be able to create, edit, view and cancel all
the details of the travel request with information made by her as
well as status of travel requests such as approved, pending or
rejected.
➢
Travel Request will consist of in depth flow of details such as
passport, insurance, accommodation, visa, visa requirements
and other details.
➢
Information can be stored and retrieved as well as manipulated
as per requirement.
➢
Employees that are Managers or Admin will be able to make
their own request as well as view their directs’ requests and then
approve, reject or send request back for correction, as per the
requirement with appropriate message.
➢
Mails will be triggered to Mangers, Admin and Employees based
on flow of travel request that will notify Managers, Admin and
Employee about travel request.
➢
After the trip is completed, the employee should be able to
upload the bills associated with trip. This will help to charge the
expenses to specific company or client.
➢
Employees that are Admin will be able to view reports regarding
travel requests based on month, city, project etc.
➢
In case if an employee needs to have a business card on his
travel, he can select appropriate option that triggers mail to
facilities with employee details for business card printing.
Page - 15 -
Travel Management System
The client wants to have the following functionalities from the system
➢common
Any user should be able to log-in to the system using his/her
login credentials used for all other harbinger applications.
➢passport
Employee should be able to upload the scanned copy of his/her
and visa.
➢request.
Send email to respective vendors if the admin head approves the
➢passport.
Send email to employee 6 months before the expiry of his/her
➢request.
Employee should be able to track the status of his/her travel
Page - 16 -
Travel Management System
❖ Technical Feasibility
As we know that technical feasibility centers on the existing computer
system (hardware, software, etc.) and to what extent it can support the
proposed addition. But in this case the situation is different. Here there is
no existing system at all. Everything needs to be purchased. So each and
every office should have the following for their infrastructure
–
➢ Client/Server architecture.
➢ A good communication media-based network.
➢ Various System and Application Software installed the system.
➢ MongoDB.
➢ Node.Js
➢ On Server there should be Windows 10 as operating system.
➢ On clients Windows XP or later, Linux etc. running on them.
Page - 17 -
Travel Management System
❖ Behavioral Feasibility
As we know that people are inherently resistant to change and
computers have been known to facilitate change but in spite of these
Travel Management System is behaviorally feasible with its employee
users. On the introduction of new system it was required to educate
and explain the office staff on new way of doing the travel request.
Employees had shown interest in using the software. Nobody voiced
resistance to this idea of computerize the process of travel request.
❖ Legal Feasibility:
The system follows all the rule and regulation of our country and
world norms. Each active site individually and simultaneously commit
every change, or no site can commit the change. Such a solution is
obviously not feasible for large numbers of sites because of realities
such as network outages.
❖ Economic Feasibility
Page - 18 -
Travel Management System
❖ Operational Feasibility
Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s operating
requirements. Operational feasibility aspects of the project are to be taken
as an important part of the project implementation. Some of the
important issues raised are to test the operational feasibility of a project
includes the following:
Page - 19 -
Travel Management System
3
CHAPTER
ANALYSIS AND DESIGN
As we are using DOT NET framework for developing this application we are
designing our application by OOPS concept. So UML (Unified Modeling
Language) is the best way for represent this project. In this Chapter we will
explain this project by UML concepts and also database specifications.
Diagrams such as the Use Case Diagram, Class Diagram, and Module
Hierarchy Diagram etc. you will see in this chapter
❖
Use Case Diagram
❖
Class Diagram
❖
Activity Diagram
❖
Sequence Diagram
❖
Component Diagram
❖
Deployment Diagram
Page - 20 -
Travel Management System
➢ Actors:
Actor Name
➢ Association:
-------------------------->
Page - 21 -
Travel Management System
Page - 22 -
Travel Management System
Page - 23 -
Travel Management System
Page - 24 -
Travel Management System
Page - 25 -
Travel Management System
Page - 26 -
Travel Management System
Page - 27 -
Travel Management System
➢ Graphical Depiction:
A class icon is drawn as a 3-part box, with the class name in the top
part, a list of attributes (with optional types and values) in the
middle part, and a list of operations (with optional argument lists
and return types) in the bottom part
➢ Dependency:
Page - 28 -
Travel Management System
Page - 29 -
Travel Management System
Page - 30 -
Travel Management System
Page - 31 -
Travel Management System
Page - 32 -
Travel Management System
Page - 33 -
Travel Management System
Page - 34 -
Travel Management System
❖ Definitions
Page - 35 -
Travel Management System
Page - 36 -
Travel Management System
Page - 37 -
Travel Management System
Page - 38 -
Travel Management System
Page - 39 -
Travel Management System
Page - 40 -
Travel Management System
Page - 41 -
Travel Management System
Page - 42 -
Travel Management System
4
CHAPTER
IMPLEMENTATION
❖
Input Screens
❖
Module Specifications
❖
Table Specifications
Page - 43 -
Travel Management System
4.1input screen
Following are the employee interface screen shots of the system modules.
Page - 44 -
Travel Management System
Page - 45 -
Travel Management System
Fig 3.2 Employee Profile : Employee can edit his profile and update the
information
Page - 46 -
Travel Management System
Fig 4.1 : Travel Request - Employee Master Form : This is the initial form for
creation of new travel request. It consists of basic information of employee.
Page - 47 -
Travel Management System
Fig 4.2 : Travel Request - Travel Details Form : This form includes travel
details like type of travel, dates of travel, places of travel, other details like
meal preference, seat preference and accomodation details like hotel etc.
Page - 48 -
Travel Management System
Fig 4.2.1 : Travel Request - Travel Details Form : Fill the travel details
with releveant information for travel type : Round City
Page - 49 -
Travel Management System
Fig 4.2.1 : Travel Request - Travel Details Form : Fill the travel details
with releveant information for travel type : Multi City. In this, we can
number of cities we would visit in order to get to destination.
Page - 50 -
Travel Management System
Fig 4.3 : Travel Request - Passport Details Form : This form is used to
get passport details of Employee.
Fig 4.3.1 : Travel Request - Passport Details Form : Fill passport details
and upload passport front and back image.
Page - 51 -
Travel Management System
Fig 4.3.2 : Travel Request - Passport Details Form : File Upload (Utility
PopUp Window) : This is used to upload images of passport and visa.
Fig 4.3.2.1 : Travel Request - Passport Details Form : File Upload (Utility
PopUp Window) : Select Image Files to Upload and click on upload
Page - 52 -
Travel Management System
Fig 4.4 : Travel Request - Insurance Details Form : This form is used to
add nominees by employee to travel insurance. In case of any loss during
travel, this insurance will help to compensate for the loss.
Fig 4.4.1 : Travel Request - Insurance Details Form : Fill the details of
nominee for the insurance.
Page - 53 -
Travel Management System
Fig 4.5.1 : Travel Request – Visa Details Form : Enter valid visa details
and upload visa image using file upload utility like passport image
Page - 54 -
Travel Management System
Fig 5.1 Basic Validation : Basic validations are used to show that field is
compulsary
Fig 5.1 Basic Validation : Basic validations are used to show that field
has invalid data in it.
Page - 55 -
Travel Management System
Fig 2.4 : Employee Dashboard : It shows all travel requests with status
created by the empoyee.
Page - 56 -
Travel Management System
Fig 4.6 : Travel Request – View Travel Request : A modal is used to view
complete travel request with all travel details. It provides an edit button,
which redirects to travel details form, which will help to edit the travel
request.
Page - 57 -
Travel Management System
Fig 4.7 : Travel Request – Edit Travel Requests : Update the travel
request.
Page - 58 -
Travel Management System
Fig 6 : Travel Bill - Upload Bill : After the completion of trip, employee
can submit bills to the company using Upload Bill Form.
Fig 6.1 : Travel Bill - Upload Bill : Mentiion appropriate bill category and
usind file upload utility, upload the bill images.
Page - 59 -
Travel Management System
Fig 7.2 : Mail Notification : Mail template for travel request generated by
an employee sent to manager
Page - 60 -
Travel Management System
Page - 61 -
Travel Management System
Page - 62 -
Travel Management System
Fig 9.1: Manager Approval : Popup for manager approving travel request
made by Employee. Manager has to specify to whom the expenses that are
to be charged
Page - 63 -
Travel Management System
Fig 9.2: Manager Rejection : Popup for manager rejection travel request
made by Employee.
Page - 64 -
Travel Management System
Fig 9.3: Request Correction: Popup for manager to send travel request
back for correction to employee
Page - 65 -
Travel Management System
ss
Page - 66 -
Travel Management System
Page - 67 -
Travel Management System
Page - 68 -
Travel Management System
Page - 69 -
Travel Management System
Fig 12.2 : Report Generation - City-Wise Report : Admin can view city-
wise report in tabular format
Fig 12.2.1 : Report Generation - City-Wise Report : Admin can view city-
wise report in graphical format
Page - 70 -
Travel Management System
Page - 71 -
Travel Management System
Page - 72 -
Travel Management System
Fig 7.3 : Mail Notification : Mail template for successful approval of travel
request by manager sent to employee
Fig 7.4 : Mail Notification : Mail template for rejection of travel request
by manager sent to employee with appropriate rejection reason
Page - 73 -
Travel Management System
Fig 7.4 : Mail Notification : Mail template for bussiness card containing
employee details sent to facilities team
Page - 74 -
Travel Management System
❖
New Travel Request :
➢
Travel Details : o Trip type o
Travel type o
Source city
o Destination city
o Departure date
o Return date
o Mode of travel o
Meal Preference
o Frequent Flyer Number
o Accommodation requirement,etc
Page - 75 -
Travel Management System
➢ After filling these details and submitting the request, all the
details will be stored in the database and an acknowledgement
email will be sent to the employee. Also, email will be sent to
his/her Delivery Manager informing about the new request and
ask to approve or reject the request.
➢ Options will be given to view or edit the details he/she has filled.
➢ Also, after the trip he/she can upload all the bills associated
with his/her tour.
Page - 76 -
Travel Management System
❖ Admin Head :
➢ After viewing the travel request details and the
approximate expense required for the travel, the admin
head will either approve or reject the travel request.
Page - 77 -
Travel Management System
❖
Email Module
❖
Dashboard
❖
File Module :
Page - 78 -
Travel Management System
Page - 79 -
Travel Management System
Page - 80 -
Travel Management System
Page - 81 -
Travel Management System
Page - 82 -
Travel Management System
Page - 83 -
Travel Management System
Page - 84 -
Travel Management System
5
CHAPTER
TESTING
Page - 85 -
Travel Management System
❖ Objectives of Testing
❖ Methods of Testing
Page - 86 -
Travel Management System
UNIT TESTING
MODULE
TESTING
Component
Testing SUB-SYSTEM
TESING
SYSTEM TESTING
Integration Testing
ACCEPTANCE
TESTING
User
Testing
➢ Unit Testing
Page - 87 -
Travel Management System
➢ Integration Testing
Integration Testing is any type of software testing that seeks to verify the
interfaces between components against a software design. Software
components may be integrated in an interactive way or all together ("big
bang"). Normally the former is considered a better practice since it allows
interface issues to be localized more quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction
between integrated components (modules). Progressively user groups of
tested software components corresponding to elements of the architectural
design are integrated and tested until the software works as a software.
➢ System Testing
Page - 88 -
Travel Management System
➢ Acceptance Testing
➢ Alpha Testing
➢ Beta Testing
Beta testing comes after alpha testing and can be considered a form of
external user acceptance testing. Versions of the software, known beta
versions, are released to a limited audience outside of the programming
team. The software is released to groups of people so that further testing
can ensure the products have few faults or bugs.
Sometimes, beta versions are made available to the open public to increase
the feedback filled to a maximal number of future users.
➢ Usability Testing
➢ Security Testing
Page - 89 -
Travel Management System
Test cases list the specific items that will be tested and describe the
detailed steps that will be followed to verify the software. There are two
fundamental approaches to testing software: test-to-pass and test-to-fail,
when you test-to-pass, you really ensure only that the software minimally
works. You don’t push its capabilities. You don’t see what you can do to
break it. You treat it with kid gloves, applying the simplest and most
straightforward test cases.
You may be thinking that if your goal is to find bugs, why would you
test-to-pass? Wouldn’t you want to find bugs by any means possible? The
answer is no, not initially.
Think about an analogy with a newly designed car. You are assigned
to test the very first prototype that has just rolled off the assembly line and
has never been driven. You probably wouldn’t get in, start it up, head for
the test track, and run it wide open at full speed as hard you could. You
would probably crash and die. Use test-to-pass to reveal bugs before you
test-to-fail.
In Travel Management System market there are many test cases that
are applied. Some of them shown below like GUI testing, Login, Database
etc.
There are three main methods of manually implementing test cases. These
are building test cases into your classes, creating a test script and creating
a separate testing hierarchy. Building Test Cases into your Classes When
building test cases into your classes create test methods such as Test
Class; test Objects Foxx for verifying the workings of classes and its
instances. The test Class methods would test the associated class
methods, create instances of the class, put these objects into default or
specified states, and test the objects with related test cases. One can
inherit and reuse test cases from the super class for subclass testing.
Page - 90 -
Travel Management System
➢ Conclusions
Application software system has been developed to case out the problems
faced in the present system. The system described in this book have
designed, Tested and documented to same greater extent. This package is
expected to prove to be very useful to the “Online Shopping”.
The goals that are expected to achieve by the software are:
• Simplification of the operation.
• Less processing time and increasing the productivity.
Each transaction is updated and processed immediately.
• Avoiding errors by minimizing human interaction through user
friendly screens to enter data and Enquirers the information from
the tables on like message.
• Portable and flexible for further enhancement.
After developing the system, it has been tested with sample data and the
results are found to be in satisfaction. The system is user friendly are and
easy to use prescribed by the standards have been followed in designing the
input screens lending to consistency. Across forms and reduced user strains.
Page - 91 -
Travel Management System
Page - 92 -
Travel Management System
3.Travel Details
tab will open
,now click on
next.
Page - 93 -
Travel Management System
3.Travel
Details tab will open
3.Travel
Details tab will open.
4. Select
International from
Drop down Travel
Type. Fill all the
required details and
click next.
Page - 94 -
Travel Management System
4.Select International
from Drop down for
Travel Type. Fill all
the required details
And click next.
Page - 95 -
Travel Management System
Page - 96 -
Travel Management System
3.Click on next.
Page - 97 -
Travel Management System
Page - 98 -
Travel Management System
Page - 99 -
Travel Management System
Page - 100 -
Travel Management System
Page - 101 -
Travel Management System
6
CHAPTER
USER MANUAL
For any system to be successful it is important that the intended user find
the system easy to operate. The purpose of the user manual is to make
user acquainted with the system and help employee understand the
system and operate it conveniently. The manual contain several
screenshots that describes how to use the entire system.
❖ Application Description
Page - 102 -
Travel Management System
User Manual
For any system to be successful it is important that the intended
user find the system easy to operate. The purpose of the user manual is
to make user acquainted with the system and help user understand the
system and operate it conveniently. The User Manual is prepared
reflexively because it is an item that must accompany every system.
The manual contain several screenshots that describes how to
use the entire system. This Manual helps user to navigate efficiently
through the system and help user to solve issues wherever they occur.
➢
The system contains following users: o
Employee
o Manager
o Admin
➢
The system has following features: o
Employee Registration
o Creation of new travel request
o Approval/Rejection of travel requests
o Uploading of various documents like passport, visa, etc
o Editing of Master data tables
o Bill and Report generation
➢ Log in into the system using LDAP credentials. You are redirected
to dashboard after successful credential verification of Username
and Password.
Page - 103 -
Travel Management System
Page - 104 -
Travel Management System
Symbol Meaning
Denotes approval status: Request is pending.
Denotes approval status: Request is approved.
Used to view form or other details.
Used to edit form or other details.
Used to delete.
Used to upload bills.
❖
Buttons
Page - 105 -
Travel Management System
7
CHAPTER
DRAWBACKS
AND
LIMITATIONS
This part of documentation will explain drawbacks and limitation that
are in Travel Management System Market Application.
Page - 106 -
Travel Management System
❖ Drawbacks
➢ System requires a high speed broadband internet connection.
➢ Employee neither download nor print his/her travel request
application.
❖ Limitations
8
CHAPTER
PROPOSED
ENHANCEMENTS
The future enhancements of the Travel Management System are proposed
in this chapter. It gives us the insight about the area and field where these
enhancements can be made.
Page - 108 -
Travel Management System
Proposed Enhancements
➢ Option will be given to user to apply for new visa, in case if he/she
does not have a visa of the destination country.
Page - 109 -
Travel Management System
9
CHAPTER
CONCLUSIONS
This part concludes Travel Management System in brief explanation and
also specifies operation performed in the application.
Page - 110 -
Travel Management System
Conclusions
Page - 111 -
Travel Management System
10
CHAPTER
BIBLIOGRAPHY
The Bibliography chapter contains all the reference books, websites or other
reference material details used in order to make this report worthwhile.
Page - 112 -
Travel Management System
Bibliography
➢ Udemy Courses
o The Complete Node.js Developer Course (3rd Edition)
Created by Andrew Mead, Rob Percival
➢ Web reference:
o http://node.org /learn
o http://udemy.com
Page - 113 -
Travel Management System
11
CHAPTER
ANNEXURE
This section of report specifies Input and Output Forms as report and
also some sample code which is describes in this section.
❖ Technology used
❖ Sample Code
Page - 114 -
Travel Management System
➢
Declarative
React makes it painless to create interactive UIs. Design simple views for
each state in your application, and React will efficiently update and
render just the right components when your data changes. Declarative
views make your code more predictable and easier to debug.
➢ Component-Based
➢ A Simple Component
Page - 115 -
Travel Management System
➢ A Stateful Component
➢ An Application
Using props and state, we can put together a small Todo application.
This example uses state to track the current list of items as well as
the text that the user has entered. Although event handlers appear to
be rendered inline, they will be collected and implemented using
event delegation.
❖ Middleware : Node JS :
➢ As an asynchronous event-driven JavaScript runtime, Node.js is
designed to build scalable network applications.
Page - 116 -
Travel Management System
➢
Node.js takes the event model a bit further. It presents an event loop
as a runtime construct instead of as a library. In other systems,
there is always a blocking call to start the event-loop.
➢
Typically, behavior is defined through callbacks at the beginning of a
script, and at the end a server is started through a blocking call like
EventMachine::run().
➢
In Node.js, there is no such start-the-event-loop call. Node.js
simply enters the event loop after executing the input script.
Node.js exits the event loop when there are no more callbacks to
perform. This behavior is like browser JavaScript — the event loop
is hidden from the user.
➢
HTTP is a first-class citizen in Node.js, designed with streaming
and low latency in mind. This makes Node.js well suited for the
foundation of a web library or framework.
➢
Node.js being designed without threads doesn't mean you can't take
advantage of multiple cores in your environment. Child processes
can be spawned by using our child_process.fork() API, and are
designed to be easy to communicate with. Built upon that same
interface is the cluster module, which allows you to share sockets
between processes to enable load balancing over your cores.
❖ Backend : MongoDB :
➢
MongoDB is a document database with the scalability and flexibility
that you want with the querying and indexing that you need.
➢
MongoDB is a cross-platform document-oriented database
program. Classified as a NoSQL database program, MongoDB
uses JSON-like documents with schema. MongoDB is
developed by MongoDB Inc. and licensed under the Server
Side Public License (SSPL).
Page - 117 -
Travel Management System
➢ Ad hoc queries
➢ Indexing
Fields in a MongoDB document can be indexed with primary
and secondary indices.
➢ Replication
MongoDB provides high availability with replica sets. A replica set consists
of two or more copies of the data. Each replica set member may act in the
role of primary or secondary replica at any time. All writes and reads are
done on the primary replica by default. Secondary replicas maintain a
copy of the data of the primary using built-in replication. When a primary
replica fails, the replica set automatically conducts an election process to
determine which secondary should become the primary. Secondaries can
optionally serve read operations, but that data is only eventually
consistent by default.
➢ Load balancing
➢ Capped collections
Page - 118 -
Travel Management System
➢ File storage
MongoDB can be used as a file system, called GridFS, with load balancing
and data replication features over multiple machines for storing files.
This function, called grid file system, is included with MongoDB drivers.
MongoDB exposes functions for file manipulation and content to
developers. GridFS can be accessed using mongofiles utility or plugins
for Nginx and lighttpd. GridFS divides a file into parts, or chunks, and
stores each of those chunks as a separate document.
➢ Aggregation
➢ Transactions
Page - 119 -
Travel Management System
/**
* Mastertest : Master Data Controller-Retrieves data from
various collections of database of master tables.
* @param {object} data http req
* @returns {object} data http res,json
*/
Page - 120 -
Travel Management System
}catch(error){
Page - 121 -