A

PROJECT REPORT
ON

“IMPLEMENTATION OF CLOUD
COMPUTING TECHNOLOGY FOR M-
TICKET BOOKING”

SUBMITTED IN PARTIAL FULFILLMENT OF

THE REQUIREMENTS OF THE DEGREE OF
THIRD YEAR IN
COMPUTER ENGINEERING

BY
RAUL DIVYA DINESH(42)
JADHAV RIYA VISHWAS(16)
SABALE ROHIT MADHAV(45)
KOKANE SHUBHAM DHANANJAY(26)
GUIDE
[Link]

DEPARTMENT
OF
COMPUTER ENGINEERING

INDALA COLLEGE OF ENGINEERING,

KALYAN-421103

UNIVERSITY OF MUMBAI
ACADEMIC YEAR: 2023-2024

1|P ag e
 CERTIFICATE

This is certified that the Project report entitled “IMPLEMENTATION OF CLOUD COMPUTING
TECHNOLOGY FOR M-TICKRT BOOKING SYSTEM” submitted by KOKANE SHUBHAM
(26) ,RAUL DIVYA(42),JADHAV RIYA(16),SABALE ROHIT(45) Isa Bonafede work carried out by
us under guidance of PROF.V .KHANDAGALE, and it is approved for the for the partial fulfillment of
the requirement of the University of Mumbai for the award of the Master of Computer Engineering.

This Project report has not been earlier submitted to any other Institute of University for the award of Third
Year Computer Engineering

Place: Kalyan,

Date: 30/04/2024

[Link]
GUIDE EXTERNAL EXAMINAR

PROF. R. SINGH
HEAD OF DEPARTMENT PRINCIPAL

2
 PROJECT REPORT APPROVAL FOR
TE COMPUTER

This Project report entitled “IMPLEMENTATION OF CLOUD COMPUTING TECHNOLOGY

FOR M-TICKRT BOOKING SYSTEM” by [Link] is approved for the partial fulfillment
of the requirement of the University of Mumbai for the award of the Degree of Third Year in
Computer Engineering

External Examiner

……………………

……………………

[Link]
GUIDE

Date: 30/04/2024

Place: Kalyan

3
 DECLARATION
We declare that this written submission represents my ideas in my own words and where others'
ideas or words have been included, we have adequately cited and referenced the original sources.
We also declare that We have adhered to all principlesof academic honesty and integrity and have not
misrepresented or fabricated or falsified any idea/data/fact/source in my submission. We understand
that any violation of the above will cause disciplinary action by the Institute and can also evoke penal
action from the sources which have thus not been properly cited or from whomproper permission
has not been taken when needed.

1- SABALE ROHIT(45)_
2- KOKANE SHUBHAM(25)
3- RAUL DIVYA(41)
4- JADHAV RIYA(16)

Date:30/04/2024

4
 CONTENTS

ACKNOWLEDGEMENT I

ABSTRACT II

LIST OF FIGURES III

TITLE PAGE NO.

CHAPTERNO.
1 INTRODUCTION
INTRODUCTION 2
EXISTING SYSTEM 3
KEY FEATURES 4

2 CLOUD COMPUTING
SAAS 5
PROJECT MODULES 6
AMAZON WEB SERVICES (AWS) 8

3 LITERATURE SURVEY
SURVEY OF EXISTING SYSTEM 9
PROBLEM STATEMENT 10
OBJECTIVE 10

4 PROPOSED SYSTEM
FLOWCHART 11
SYSTEM STUDY 12
SYSTEM ANALYSIS 12

5 ANALYSIS AND DESIGN

FUNCTIONAL REQUIREMENTS 13

5
 NON-FUNCTIONAL REQUIREMENT 13
SYSTEM DESING 14
E-R DIAGRAM 14
SOFTWARE REQUIREMENTS 20

6 SNAPSHOTS
21
Aplication Home Page
User Home Page 22
Traine Ticket Booking Page 22
Cheakout Page 23
Payment Gateway Page 24
Booking Info And Print Ticket Page 25
AWS Elastic Compute Cloud 25
WS Elastic IP 26
AWS SES Sending Statistics 27

7 CONCLUSION 28

8 REFRENCES 29

6
 ACKNOWLEDGEMENT

We would sincerely like to thank our guide for this project [Link] for providing
us his/her valuable time and support throughout the [Link] would also like to extend my
gratitude to [Link].(Head of Department of Computer Engineering) and all the other
faculty members for helping us generously. We would like to thank Teaching & Non-teaching
staff of Computer Department who helped me time to time in all respects. And Librarian for
providing me all the reference books and material needed for project. Special thanks to my
parents and my friends for all the laughs and mood boosters without whom Computer
Engineering wouldn’t have been so pleasant for a memory.

7
 ABSTRACT
The current railway or bus ticket booking system is human dependent and tedious with regards to the
ticket booking process. The core objective of our project is to develop the web-application which will serve
as a medium for students/employees/anyone to book the tickets to travel through trains or bus. The principle
motive force of this web-application is to ease the process of ticket booking by avoiding the hecticand
boisterous process to stand in a queue and book the ticket for the short distance for travelling in the trains.
Several applications are available in the market which give information about the travelling destinations
and their fares. However, none of these applications incorporate the ticket booking process coordinated for
both train and bus. Our application contrasts from such a lot of existing applications as it would book the
ticket as well as save the ticket in the cloud database for both train and bus.

This website is for railway and bus ticket booking and one can easily validate those booked tickets
using mobile. Ticket can be bought with the help of smart phone, laptop using the web-application where
your railway tickets can be carried in your phone. The ticketing information of the user is securely stored in
the cloud database. Additionally, the ticket checker is given the checker application which is utilized for the
approval of the ticket appeared by the user. This framework gives the ticket checker web-applicationto
look for the user's ticket with the ticket number or other appropriate information in the cloud database for
checking purposes. Consider that the user's display is being damaged and not able to show the ticket due to
other reasons like battery failure we have another safeguard alternative to check the ticket by searching in
the ticket database with the ticket number or user’s other relevant information for validation purpose.

8
 LIST OF FIGURES

Figure Number Figure Name Page no

2.1 Cloud computing Service Modules 5

2.2 AWS EC-2 6
2.3 AWS SESFig 6
2.4 AWS SNS 6
4.1 E-R Diagram 15
4.2 Use Case Diagram 16
4.3 User Activity Flow Diagram 17
4.4 Admin Activity Flow Diagram 18
4.5 Data Flow Diagram 19

1|Pa ge
 CHAPTER1
INTRODUCTION

1.1. INTRODUCTION

There has been no advancement in Indian public transport system particularly railways and bus, still follows
the regular old pattern of ticket booking and checking. With the growing population, the number of travellers ready
to travelday by day is expanding abruptly and now the circumstances are deteriorating that individuals
don’t bother whether they have a ticket or not, they knowingly or sometimes because of some issue they are entered
in the train or bus without a ticket. Indian public transport system and IT are loosely bounded.
Presently the use of Information Technology is only limited to online checking of schedules and fares of
public transport. The main motive of this web-application is to easethe process of ticket booking by avoiding the
hectic process to stand in long queues and book the ticket for the short distance travelling in the trains and bus.
Users can purchase the ticket over the Internet, 24 hours a day throughout the year, this solves the issue of bus
ticket being misplaced or stolen in a real-life scenario. The application may get overloaded due to a huge number
of users visiting at once. Thus to solve the issue this system is built up using cloud infrastructure for improved
performance.

1.2. Existing system

To implement cloud computing technology for an existing M-ticket booking system, you'll need to assess the
current architecture and functionalities of the system. Here's a step-by-step guide to transitioning the existing system
to a cloud-based infrastructure:

1. Assessment of Current System:

2|Pa ge
 - Evaluate the current architecture, including hardware infrastructure, software components, and data storage.
- Identify any scalability bottlenecks, performance issues, or reliability concerns.
- Determine the technologies and frameworks used in the existing system.

2. Cloud Migration Strategy:

- Choose a suitable cloud provider (e.g., AWS, Azure, Google Cloud) based on factors such as compatibility,
pricing, and service offerings.
- Decide on the migration approach:
- Lift and shift: Migrate existing infrastructure and applications to the cloud with minimal changes.
- Re-platform: Optimize applications for cloud-native services while retaining core functionality.
- Refactor: Restructure and modernize applications to take full advantage of cloud capabilities.
- Replace: Replace certain components with cloud-native alternatives if necessary.

3. Data Migration:

- Plan and execute the migration of data from on-premises or existing data centers to cloud storage solutions.
- Ensure data consistency, integrity, and security during the migration process.
- Use tools provided by the cloud provider or third-party migration services to streamline the data migration
process.

4. Application Migration:
- Containerize existing applications using Docker or similar containerization technologies to ensure portability
and compatibility with cloud environments.
- Deploy containerized applications to cloud-based container orchestration platforms such as Kubernetes for easier
management and scalability.
- Reconfigure application settings, environment variables, and dependencies to align with cloud platform
requirements.
- Test the migrated applications thoroughly to validate functionality, performance, and interoperability with other
components.

5. Integration with Cloud Services:

- Integrate the M-ticket booking system with cloud-based services for compute, storage, database, messaging, and
other functionalities.
- Replace or augment existing components with cloud-native alternatives to leverage advanced features and
scalability.

3|Pa ge
6. Security and Compliance:
- Implement security best practices recommended by the cloud provider, including network security, identity and
access management (IAM), encryption, and compliance controls.
- Configure firewalls, security groups, and access control policies to protect cloud resources from unauthorized
access and cyber threats.
- Ensure compliance with relevant regulatory requirements and industry standards for data protection and privacy
(e.g., GDPR, PCI DSS).

7. Monitoring and Management:

- Set up monitoring and alerting mechanisms using cloud-native tools such as CloudWatch, Azure Monitor, or
Google Cloud Monitoring.
- Monitor system performance, resource utilization, and application health to identify issues proactively and
optimize resource allocation.
- Implement automated scaling policies to dynamically adjust resources based on demand and workload patterns.

8. Training and Documentation:

- Provide training sessions for IT staff and stakeholders on cloud computing concepts, best practices, and tools.
- Document the migration process, architecture diagrams, configuration settings, and operational procedures for
future reference and knowledge sharing.

9. Testing and Validation:

- Conduct comprehensive testing of the migrated system, including functional testing, performance testing,
security testing, and user acceptance testing.
- Validate system reliability, scalability, and resilience under different scenarios and workloads.
- Address any issues or discrepancies identified during testing and refine the system accordingly.

10. Go-Live and Post-Migration Support:

- Plan and execute the cutover to the cloud environment during a scheduled maintenance window or off-peak
hours to minimize disruption to users.
- Monitor system performance and user feedback closely during the initial post-migration phase to address any
issues or concerns promptly.
de ongoing support and maintenance for the cloud-based M-ticket booking system, including software updates,

4|Pa ge
 CHAPTER 2
[Link]

2.1. CLOUD COMPUTING

Cloud Computing [1] is a form of distributed computing which has been evolving recently. Typically, the
cloud symbol is used to represent the Internet. Cloud computing is now widely used to describe the delivery of
software, infrastructure and storage services over the internet. Cloud computing provides tools and technologies
for various parallel applications with far more affordable prices compared to traditional parallel computing
techniques.

The main purpose of cloud computing is to profit from all of these technologies without the necessity for
deepknowledge or expertise with each of them. At present, whether large or small, all companies depend on
public cloud platforms to host and implement applications because they supply flexibility, mobility, scalability,
sustainability and it is cost-effective cloud Computing Service Models can be mainly placed into three types:
SaaS (Software as a Service), IaaS (Infrastructure as a Service) and PaaS (Platform as a Service). Each of the
cloud models has its collection of benefits that will meet the wants of assorted companies.

2.2. Software as a Service (SaaS):

Software as a Service (SaaS) [2] is a software distribution model in which applications are hosted by a
third- party provider and made available to users over the Internet. The SaaS model enables your business to

5|Pa ge
quickly access cloud-based web applications without committing to install a new infrastructure. Applications run
on the vendor cloud,which they can control and maintain. On-site hardware is not required for this model,which
keeps associated costs [Link] reduces the expense of equipment procurement, delivery and servicing,as well as
software licensing, deployment and service. Small businesses may find this cloud platform particularly attractive.
2.3 Infrastructure as a Service (IaaS):
Infrastructure as a service (IaaS) [2] is a type of cloud computing that delivers basic computing,
networking, and storage services to customers on-demand, over the Internet. IaaS allows end-users to scale up
and reduce resourceson an as-needed basis. Infrastructure as a Service (IaaS) is often referred to as Hardware as
a Service (HaaS).
IaaS [3] was born out of a wider shift from conventional data centres to virtualized and cloud-based infrastructure.
The on-demand service model makes it easy for the user to transfer workloads from one cloud instance
to another, ensuring that resources are still available when you need them. IaaS providers offer services on a pay-
as-you- use basis. Users are expected to pay for what they have been using.

a) Platform as a Service (PaaS):

Platform as a Service (PaaS) [3] is a full cloud-based development and delivery environment with tools
that allow you to deliver anything from simple cloud-based apps to sophisticated cloud-enabled enterprise
applications. User can buy the services from a cloud service provider on a pay-as-you-use basis and access them
through the Internet. PaaS vendors sell a spread of tools that are mainly required for software development,
including a source code editor, a debugger, a compiler, and other critical tools. Such methods can be provided
together as a platform. PaaS offers all the skills you need to support a full lifecycle of web applications that are
designing, reviewing, deploying, managing and upgrading within the same integrated environment.

Fig.2.1. Cloud Computing Service Models .

6|Pa ge
 [Link] MODULES:

A. Registration:
This module is meant to record user details on the website database. It collects general information about
the user such as name, mobile number, email address, etc. This module also includes a unique Email [Link]
Password that would allow the user to sign-in to the website. The information received by the user is recorded
in the 'Register' database. Once the user has given all the information needed for registration, the website redirects
the user to the sign-in page.
B. Sign-In and Authentication:
This module facilitates the user to sign-in on to the website. It collects user information, such as email
address and password, and compares the information against the entries in the database. If the user entered
information that matches the authentication parameters that is email address and password entered during the
registration process, the user shall be authenticated and will be redirected to the user homepage. If the user
entered information that does not satisfy the requirements for authentication, the user will not be authenticated
and cannot access the user homepage.

C. Booking and Allocation:

This module is available once the user has signed-in onto the website, our application displays two modes
of transport to the user that are the train and the bus. User can select any one mode according to his choice. If
the user selects train he is prompted with the form where he has to enter his desired selection for booking process,
that form includes source station, final destination, train class, train type, number of tickets, route.
Once the user selects these parameters the script code accepts the entries and checks for matching entries
in the server database and accordingly displays the fare amount. after that user can go forward and proceed to
checkout. Similarfunctionality is available for bus booking but form choices are different.

D. Transaction:
This module displays a confirmation message that the user has successfully booked the ticket. It also
makes anentry in the transaction database and the unique transaction id is allocated to the user in this module.
User can print a ticket in the next step.

E. Admin:
This module is designed for Ticket-Checker. Firstly, Ticket-Checker must sign-in to use the application.
Once he has singed-in, he is provided with the transaction database for both bus and train ticket.

7|Pa ge
The checker can select any one of this option to verify and validate the ticket. In this module the checker is
provided with an option to search a particular keyword this will help checker to save time if he has to select any
specific entry.

2.3 AMAZON WEB SERVICES (AWS):

Amazon Web Services (AWS) [8] is a division of Amazon that provides on-demand cloud services, tools
and Interfaces for users, companies and organizations. Amazon Web Services (AWS) is the most robust and
widely accepted cloud platform in the world, providing more than 175 fully integrated data center facilities
worldwide.

Fig.2.2. AWS EC-2 Fig.2.3. AWS SES Fig.2.4. AWS SNS

• Amazon Elastic Compute Cloud (Amazon EC2):

Amazon Elastic Compute Cloud (Amazon EC2) [9] is a web service that provides stable, resizable cloud
storagecapabilities. The basic cloud service interface of Amazon EC2 helps you to receive and customizea
minimal congestion capability. It provides a wide variety of instance forms tailored for various use cases. Types
of instances provide a range of combinations of CPU, memory, storage, and networking capacities, which give
you the flexibility to choose the bestmix of resources for your applications.

• Amazon Simple Email Service (Amazon SES):

Amazon Simple Email Service (Amazon SES) [11] is a cloud-based email delivery service designedto
help digital marketers and software developers submit advertising, confirmation and transactional emails. This
is a secure, price-effective tool for enterprises of all sizes that use email to keep in touch with their users.
• Amazon Simple Notification Service (Amazon SNS):
Amazon Simple Notification Service (Amazon SNS) [10] is a highly accessible, reliable, stable, fully
managedmessaging service that lets you to decouple microservices, distributed systems, and serverless
applications.
Amazon SNS provides high-throughput, push-based, multi-to-many messaging topics. It offers alow-
costinfrastructure for the mass distribution of messages, mainly to smartphone users.
• RESULTS AND DISCUSSIONS:
The web application M-Ticket booking system was developed using Hypertext Markup Language

8|Pa ge
 CHAPTER.3
LITERATURE SURVEY

3.1. Survey of Existing system

A Study by Mohezar et. al. [5] identified trends in e-tickets among urban communities, especially in
Kuala Lumpur. This research explores the trends and patterns of use of e-tickets. The study also focused on
consumer perspectives for e-tickets in terms of their usability, reliability, protection, convenience and
performance. The research also explores the effect of demographic variables on e-ticket acceptance of e- tickets.
A survey was conducted amongst Internet users in Kuala Lumpur. Questionnaires were randomly distributed to
5,000 individuals. Kuala Lumpur was selected to have the largest number of Internet users.

The study found that e-tickets are not a new trend, as an almost good number of respondents have been
purchasing online tickets for the past two years and the purchase of rail and bus tickets seems to have dominated
online ticketing services. It was also found that comfort and ease of use were among the factors that inspired
respondents to buy tickets online

The study [5] also found that online ticket purchasers are young, qualified and with a higher income
bracket, Sahney et al. found that the modus operandi of the online ticket booking system needs particular
attention to factors such as the functionality of online search information, website design, and the capacity of

9|Pa ge
 all time network availability for online booking. We propose that the flexibility of the Internet should be
combined with the convenience of a simplified decision making and collaborative booking from traditional travel
agents. The expertise of travel agents should help online customers to find the best travel option under given
constraints and provide efficient support for impulsive decision

3.2. Problem Statement

The need to build this website was the technological development of almost everything around us.
The user needs all the tasks to be accomplished in an effective and relaxed manner. In such a time, there was a
desperate need toconstruct a website for the convenience of the user. Also, this website will aim to solve the
tiresome task of managing the crowd easy, without confusion, during ticket booking times. Cloud Technology
will help to add flexibility and [Link] an effective solution where users can view doctors available and
select the preferred date and time

3.3. Objective

Certainly! Let’s explore the implementation of cloud computing technology for M-Ticket booking. This project
aims to revolutionize the ticket booking process by leveraging cloud infrastructure and web-based applications
The existing railway or bus ticket booking system is human-dependent and tedious with regards to the ticket
booking process. Passengers often face challenges such as long queues, manual processes, and the need to
physically visit booking counters. The core objective of our project is to develop a web application that serves as
a medium for students, employees, or anyone to book tickets for train or bus travel.

10 | P a g e
 CHAPTER 4
PROPOSED SYSTEM

[Link] SYSTEM

The implementation of cloud computing technology for M-Ticket booking can be seen in various systems and
proposals. The system allows users to book tickets for trains or buses and store the ticketing information securely
in the cloud database. This eliminates the need for physical tickets and provides a more convenient andaccessible
way of ticket booking.

The cloud-based system can also provide real-time monitoring of train or bus movements, which can aid in
fixing crossing or precedence of two or more trains or buses at the best location based on conflict protocols.
Additionally, the system can provide an opportunity to overcome human dependence and related errors in
information collection from the field.

11 | P a g e
In the case of ticket checking, the system can provide a ticket checker web-application to look for the user's
ticket with the ticket number or other relevant information in the cloud database for checking purposes. This
ensures a more efficient and accurate ticket checking process.

Moreover, the system can also utilize big data strategy to analyze the data gathered from smart cards used intrain
travel. This can help in predicting consumer count and behavior, which can be used to improve railway
infrastructure and provide customized services for travelers.
Overall, the implementation of cloud computing technology for M-Ticket booking provides a more efficient,
convenient, and innovative way of ticket booking and travel management.

3.1. System Study

The next step for implementing Cloud Computing Technology for M-Ticket Booking could be to design the
system architecture. This would involve identifying the components of the system, such as the user interface, the
database, and the cloud infrastructure, and determining how they will interact with each other. The system
architecture should also take into account the security and scalability requirements of the system. Once the system
architecture has been designed, the development team can begin building the system according to the
specifications outlined in the architecture.j

3.2. System Analysis

The system can be designed to provide a seamless and efficient ticket booking experience for users. The cloud-
based system can offer several benefits, such as real-time monitoring of train or bus movements, which can aidin
fixing crossing or precedence of two or more trains or buses at the best location based on conflict protocols.
Additionally, the system can provide an opportunity to overcome human dependence and related errors in
information collection from the field.

12 | P a g e
 CHAPTER 5
ANALYSIS AND DESIGN

5.1. Functional requirements

● View Traine Information

● Search traine or Bus

● View Ticket

● Search bus or traine

● Ticket Booking

● Check-in form Submitting

● Ticket management

● Schedule a timing

5.2. Non-functional requirements

● Responsive and user friendly UI

● Speed
● Less weight
● Reliability
13 | P a g e
5.3. System Design
The system design for the implementation of cloud computing technology for M-Ticket booking involves
several components, including:
1. User Interface: A user-friendly interface that allows users to book tickets, view ticket history, and accessother
relevant information.

1. Cloud Database: A secure and scalable cloud database that stores ticketing information, user data, andother
relevant data.

2. Real-time Monitoring System: A real-time monitoring system that tracks train or bus movements andprovides
information on train or bus crossing and precedence.
Ticket Checker Web-Application: A web-application that allows ticket checkers to verify tickets andaccess
relevant information…

5.4. Entity Relationship Diagram (ER Diagram)

ER diagram is a graphical representation of entities and their relationship to each other, typically used
in computing regarding the organization of data within database or information systems. Entity is a piece of
data, object or concept which described which data should store. Relationship is how data is shared between
entities.
• Entity
Which are represented by rectangle. An entity is an object or concept that has its existence in the real
world. It includes all those things about which data is collected. A weak entity is an entity that must defined
by a foreign key relationship with another entity as it cannot be uniquely identified by its own attributes alone.
• Attributes

Which are represented by ovals. A key attribute is the unique, distinguishing characteristic of the
[Link] example, an employee's social security number might be the employee's key attribute.

14 | P a g e
Figure 4:1ER diagram

15 | P a g e
 • Use Case Diagram

Figure 4:2Use case Diagram

⚫ User: Open web-application in the appropriate browser. Enter desired information to book the ticket.
⚫ Admin: Manipulate and manage the system database by adding new bus stops or train stations,removing
[Link] new Verifier if required.
⚫ Server: Takes the desired entries from the user. Calculates the fare by checking in the [Link]
theticket in a valid format. Post the details of user on cloud with its ticket.
⚫ Verifier: Open the web application in the appropriate browser Takes booking id or other relevant
information ofthe user and verifies.

16 | P a g e
• User Activity Flow of M-Ticket Booking System:

User can buy our ticket with the help of a mobile phone or a laptop or any other device which can access
a web- application where your tickets are transported on your computer. Firstly, the user has to set up an account
to book a ticket. After an account has been established, the user can sign-in using his or her credential.
Our application shows two modes of transportation to the user that are train and bus. Once the user selects
oneof the options, he has to enter his desired source and destination address. For train, In our system user has to
input whether he has to book a ticket for first class, second class. Enter the total number of passengers and type
of journey whether single or return. After that our system display the fares. User has to confirm all the details
and then he is forwarded to payment gateway. Once the payment process is completed our system prints a ticket
and that will be uploaded on the cloud in users account. Similar process for bookingbus ticket.

Figure 4:3 User Activity Flow Diagram

17 | P a g e
• Admin Activity Flow of M-Ticket Booking System:
Ticket-Checker is equipped with the checker application used for validation of the train ticket or bus
ticket. Ticket information for users is stored in a cloud database for security purposes. This web application
provides the Ticket-Checker with checker application to search for the user’s ticket with the ticket number or
other valid credentialsin the cloud database for checking purposes.

Figure 4:4 Admin Activity Flow Diagram

18 | P a g e
DFD Diagram

Figure 4:5 Date Flow Diagram

19 | P a g e
4.5. Software Requirements

Software Hardware
• Microsoft Windows 10 Ultimate - 64bit Intel(R) Core(TM) i3-2670QM @ 2.20GHz
• XAMP Server 4 GB RAM
• MYSQL Server 500 GB Hard disk

• Sublime text
• Any browsers
• AWS CONCOLE EC2

20 | P a g e
 CHAPTER 6
SNAPSHOT

• Application Home Page:

The web application home page displays the ticket booking menu. It also displays the login page for
current users at the top of the application and a path for new users to register quickly onto the application.

• User Home Page (after the user has signed in):

The user home page has the header which has options such as Train Ticket, Bus Ticket, User Bookings
and displays users name and has log out and my profile options in drop down list. The body of user home page
has a menu which has two options which are Book Train Ticket, Book Bus Ticket, respectively.

21 | P a g e
• Train Ticket Booking Page:
The Train Ticket Booking page has the header which is similar to that of User Home Page, The body of
thispage has a form which has contents such as Source Station, Destination, Type and Class of Ticket,
Total Passengers. User can select these form variables according to his choice.

22 | P a g e
• Checkout Page:
The Checkout page has the header which is similar to that of User Home Page, The body of this
page displaysthe Route and Fare according to user choice, user can check out if he is satisfied by displayed
fare. The checkout page also has a Go Back option which will head the user to Train Ticket Booking Page.

• Payment Gateway Page:

The Payment Gateway Page has the form where user has to enter his card details to complete the
ticketbookingprocess.

23 | P a g e
• Booking Info and Print Ticket Page:

This page is displayed after payment is completed, it show- cases the ticket booking information
that theuserhas selected and allocates a unique transaction id which is known as Booking Id.

This page also has a print ticket optionwhich prints the ticket

24 | P a g e
• AWS Elastic Compute Cloud:
Launching Instance having UBUNTU Operating System.

25 | P a g e
 • WS Elastic IP:
Associating Elastic IP Address to an Instance

26 | P a g e
• AWS SES Sending Statistics :

Amazon SES provides methods for tracking the sending activity.

27 | P a g e
 CHAPTER 7
CONCLUSION

There are many issues in existing railways [6] and bus ticket booking system, To deal
over this issue, we are working towards a web-based platform. We have identified the
loopholes and started our systematic investigation. Our investigation focuses on these major
issues and have put forward a desired result for the same. We have introduced an application
on how to secure passenger information. With this experimental analysis, there will be an
increased usage of public transport systems, as everything can be done independently.
Thereis no need of any dependence on the conductor or ticket collector while entering into
the busor railways for collecting the ticket, all that we need to do is get a digital ticket by
using the web application available in the mobile device and verify it by using users
Booking Id or other credentials. This would eventually boost the will of the people and
people will use the transport very often. We can visualize that M-Ticket system will have
an application portfoliowith a mix of cloud-based services delivered across a combination
of private, hybrid, and public cloud-based infrastructure deployment models. Thus, using
cloud

28 | P a g e
 CHAPTER 8
REFERENCES

1. Grance T., and Mell P., NIST definition of cloud computing, National Institute of Standards and
Technology,January 2011.
2. Subashini S., and Kavitha V., A survey on security issues in service delivery models
3. of cloud computing. Journal of Network and Computer Applications, July 2010.
4. [Link]
5. [Link]
6. [Link]
7. [Link]
8. [Link]
9. [Link]
10. [Link]
11. [Link]
by=[Link]&[Link]-order=desc
12. [Link]

29 | P a g e