EasyTicket Mobile Application: System Design Document

Verified

Added on  2025/09/03

|13
|1645
|372
AI Summary
Desklib provides solved assignments and past papers to help students succeed.
Document Page
Contents
System vision...................................................................................................................................2
Analysis of stakeholders..................................................................................................................3
Rich picture......................................................................................................................................6
Functional requirements..............................................................................................................6
Non functional requirements.......................................................................................................7
Table of events.................................................................................................................................8
Context diagram.............................................................................................................................11
Assumptions..................................................................................................................................12
References......................................................................................................................................13
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
System vision
The traditional way of booking tickets for event is not convenient enough. The system requires
adding latest technological advancements in the ticking system. EasyTicket Company provides
ticking services to its customers. The company sells tickets for various events that include sports-
related events, musical events, concerts, festivals, family functions, and exhibitions. Ticketing
services for premier venues of Australia are also offered by the company. The main issue with
the ticking system is that it is not easy to use, thus the company wants to redesign the system that
should support mobile-based platforms. This makes the use of application easy and convenient
for its users. As mobile is a portable device and enhances the accessibility to the services. this
will make it more user-friendly.
The new system of ticketing system should be able to make customers enable to use the services
and functionalities of application on the mobile platform. Services include browsing, purchasing
and receiving the tickets on mobile phones and applications. The system should provide various
options to collect the tickets. Customers should be able to ask queries from the mobile
application and the team should be able to provide solution on the same platform. Thus the
management team and representatives should also be able to access the system. The system
should also be able to support searching for the events through application. The user should be
able to purchase ticket from the mobile-based system also. In order to assure the security in the
application, unregistered users should not have permission to purchase ticket. To maintain the
customer’s trust and flexibility, system should be capable to send email and SMS tickets on the
mobile phone of user. The mobile-based system should be integrated with the services of cloud.
This will be helpful to improve the reliability and availability of services and resources.
Adoption of latest technologies like cloud computing and big data can help the company in the
process of decision making and the improvement of the business activities. This will also
enhance service quality. It is helpful to enhance customer satisfaction by providing flexibility
and improved availability of services. Implementation with cloud-based service also ensures easy
access to services as well as prepares a backup to ensure the high availability of the services in
case of any system failure or natural disaster.
Document Page
Analysis of stakeholders
The table given below shows the list of stakeholders of the EasyTicket Company:
Stakeholder Role type Influence level Importance
level
1 Ticketing manager Responsible
for listing of
tickets and
allocate the
tasks to the
team members.
Represents the
ticketing
company and
its services
Internal High High
2 Registered
Customers
Responsible
for ticket
purchasing, the
main source of
company
benefits. A
most essential
part of the
system.
External High High
3 Ticketing officer Responsible
for inventory
updating.
Internal Low High
4 Un-registered
customers
Responsible
for browsing
and searching
for the events.
Enhance the
number of
users of the
application.
External Moderate Moderate
5 Bank Responsible
for the smooth
transaction
between
clients and the
company.
External High Moderate
6 Event managers/
operators
They provide a
list of events
and
requirements
of the events
to the
EasyTicket
External High High
Document Page
company
7 Cloud service
providers
Provide online
resources to
the company
to ensure high
availability of
the services. it
also provides
backup
services
External High Low
8 A representative of
the call center
These are
responsible to
resolve the
issues and
queries of the
customers
related to the
delivery and
booking of
ticket.
Internal Moderate High
9 Social media
platforms
These are
responsible for
the marketing
of the
application by
displaying the
functionalities
and services of
the EasyTicket
system.
External Moderate Low
10 Big data service
provider
These are
responsible for
the
management
of the
application
data.
External Moderate Low
11 Maintenance team Responsible
for the
management
and
maintenance
of the system.
This is
responsible to
assure great
customer
experience.
Internal High High
12 Telecommunicatio
n service provider
This is
responsible to
External Least Moderate
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
provide SMS
services and
email services.
this is
important as it
provides a
medium for
the
connectivity
between
company and
clients
Document Page
Rich picture
Functional requirements
Event managers should be able to view the number of booked tickets and related information
Event managers should be able to list the tickets.
e- Ticket should include complete information like event name, venue, timing, number of
seats, type of ticket, holder name, number, bar code, etc.
Customer should be able to browse the services
Customers should be able to apply search filters like price, venue and event type in the
application.
Customer should be able to select the desired ticket.
Document Page
Un-register users should not be allowed to book the tickets.
Unregistered users should be able to register.
The system should be able to show an error message or notification.
The system should be able to store and validate the user information
Customers should be able to ask queries through the interface of the system
Customers should be allowed to collect tickets in different ways.
Tickets should be able to be delivered on the customer’s phone
A printable ticket should be generated.
An email should be sent to the user.
Nonfunctional requirements
The ticket should include bar include
Ticket type should be mentioned on the ticket.
Various communication protocols for ticket deliver
Selection of cloud service provider
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Table of events
Name of event Type of
event
Source of
event
Trigger Condition
for event
Activity
of event
Response of
event
Destinati
on of
event
Customer
login into the
system
external User Customer
should be
registered
user and
have login
credential
s
Customer
is entering
the
credentials
The user gets
into the
system
User conduct
search for the
ticket
External User Search
used by the
user
Tickets
should be
listed
User is
searching
for the
event and
tickets
The system
will show
results on the
basis of search
Customer
User book the
seat
External User User click
on the
available
seat
User must
be a
registered
user
The user
gets seat
in order to
book it.
Changes the
color of the
selected seat.
User
User registers
into the
system
External User User click
on the
register
button
User
should not
be a
registered
user
The user
enters
details
like name,
country
name,
address,
email id,
etc.
User get
registered into
the system
User
User make
payment
External Registered
user
Customer
click on
the
payment
button
User want
to make
payment
and had
credit card
details
Enters the
card
credentials
like CVV
etc.
Payment
process starts
and message
displays to do
not press back
button
System
Verification of
customer
credentials
State User User enter
eth login
details
User
should
have login
credential
s
System
matching
the
entered
details
from the
database
Get login into
the system
System
Invalid
credentials
State User User enter
the login
details
User
should
have login
System
matching
the
The system
generates an
error message
User
Document Page
credential
s
entered
details
from the
database
Generate
online tickets
State System Payment
successful
Payment
completed
Create a
printable
ticket
Send the
ticket to the
user through
different
options like
email or SMS
User
Successful
validation of
credit card
State Bank Successful
payment
Payment
process
completed
by filling
the credit
card
details
A
message
appears
for
successful
message
Display the
payment
receipt or send
a message to
the phone of
the user
User
Verification of
credit card
fails
State Bank Occurrence
of
transaction
All the
details are
filled
Check the
details of
credit card
Generate an
error message
and display it
User
Customer ask
queries
External User User click
on the help
section
User must
be a
registered
user
Customer
write a
query in
the
designated
section
The
representative
team receive
the user’s
query
Represent
ative team
The system
generates an
exception
message
State System Make a
ticket
purchase
ticket
procedure
User
completed
the
purchase
procedure
The
system
displays
an error
message
The system
displays an
error message
to customer
User
User purchase
ticket
External Unregistered
User
Select the
option to
receive a
ticket
User must
be a un-
registered
user
User
makes a
ticket
purchase
The user
receives an
exception
message
User
Representativ
e team solve
user queries
External Representative
team
Receive
notification
of user
query
Member
should be
logged
into the
system
Solve the
user
query
User receive
solution of the
query
User
User make a
search by
price or any
other filter
External User Click on
the search
button
Search
should be
conducted
by the
user
User is
searching
for the
tickets
according
to the
filter
System
display eth
results
according to
the filter
User
The company
needs a
backup of
State Company Go to the
cloud
services
The
company
must have
Ask for
the
backup of
Get the data
backup of the
data
Company
Document Page
data a cloud
service
provider
data
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Context diagram
The following image shows the context diagram of the EasyTicket system. This shows the basic
activities of eth system along with the system boundaries.
Document Page
Assumptions
The assumption is that the implementation of application on mobile will increase service
availability.
Assumptions are that the information of the tickets and events manually updated in the
system
The assumption is that the new system will ask same details as website for registration.
An assumption is that the system is secure enough to protect the credit card details of the
customer.
The assumption is that the system will save the history of booked tickets.
The assumption is that the system will improve the number of customers as well as the
satisfaction level of existing customers.
The assumption is that the system automatically saves the user details in database.
The assumption is that the system will provide notification about the success, error or
cancellation of the ticket.
The assumption is that cloud services will act as backup in case of any disaster.
The assumption is that the system automatically validates the user by matching the
credentials from database.
chevron_up_icon
1 out of 13
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]