Concert Digital Ticketing System

Project Description

Concert Digital Ticketing System, would allow people to purchase

tickets to concerts more easily and efficiently. The system would help the
event promoter, the ticketing agencies, and the concert venue
promoters market the concert and easily sell their tickets and other items.
Therefore, it is more economical to buy and sell the tickets than to obtain
it directly from the physical stores.

Project Scope and Limitations

Purchasing ticket online availability is only for those who has

supported online payment account like paypal and active debit/credit
card.
The system will have features for reservation and payment of tickets
processed by staffs for customers who is not capable of paying online.
During the event validation of tickets will be based on payment
only.

Functional Requirements and Non-Functional Requirements (refer to Chapter 3:

Requirements Determination)
Functional Requirements

1. User Account Management

1.1 The system will allow managers to add new staffs
1.2 The system will allow managers to modify staffs info
1.3 The system will allow managers to create a user login account
for staffs

2. New Event Concert Management

2.1 The system will allow managers to create new instance of
Concert
2.2 The system will allow managers to create a schedule of a
concert
2.3 The system will allow managers to modify schedule of a concert
event
2.4 The system will allow managers to set maximum number of seats
of a concert event

1|Page
 2.5 The system will allow managers to modify maximum number of
seats of a concert event
2.6 The system will allow managers create sets of tickets for the
concert event
2.7 The system will allow managers to create types of tickets for the
concert event
2.8 The system will allow manager to generate automatic sets of
ticket number for tickets of a certain concert event.
2.9 The system will allow managers to set ticket price
2.10 The system will allow managers to modify ticket price
2.11 The system will allow managers to create staffing of a concert
event
2.12 The system will allow managers to modify staffing of a concert
event

3. Concert Ticket Sales Management

3.1 The system will allow customer to view ticket categories and
ticket price
3.2 The system will allow customer to reserve concert ticket event
online
3.3 The system will allow customer to reserve concert ticket event
via walk-in.
3.4 The system will allow customer to reserve concert ticket event
via phone calls
3.5 The system will allow clerk to reserve concert ticket event for
the customer.
3.6 The system will record reservation of concert ticket online
3.7 The system will allow payment of ticket online.
3.8 The system will allow clerk to record a customer payment.
3.9 The system will allow admin to view actual sales of concert
ticket

4 Concert Ticket Validation

4.1 The system will allow the checker to validate tickets during the
event

2|Page
Non-Functional Requirements

1. Operational
1.1 The system will run different smart phone devices

2. Performance
3. Security
4. Cultural and Political
4.1 Customer personal information is protected in compliance
with the Data Privacy Act Law.

Use Case Analysis

Use case name: Create Concert Event ID: UC001 Priority: High
Actor: Owner or Managers
Description: This use case describes how admin creates a concert event in the
system
Trigger: New Concert Event was successfully planned and organize and needed to
be recorded in the system.
Type: ☑ External ☐Temporal
Preconditions:
1. Admin user is authenticated through account login
Normal Course:
1. The system will show toolbars or menu
2. Admin goes to the concert event management menu
3. Admin then creates a new concert event
4. Admin inputs the venue of the concert
5. Admin inputs the number of seat
6. Admin setups the ticket #generator
7. Admin setups the ticket pricing
8. Admin setups staffing (different staffs that will compose the event concert)
9. Admin saves the transaction
Postconditions:
1. System will store all the data
2. System will do an audit trail of the transaction
Exceptions:

3|Page
Use case name: Phone Call Reservation ID: UC002 Priority: High
Actor: Customer
Description: This use case describes how customers reserves ticket via phone call
Trigger: Customer wants to reserves ticket via phone call
Type: ☑ External ☐Temporal
Preconditions:
1. Land Line phone is online
2. Cellular phone is online
Normal Course:
1. The customer will call and inquire about availability of ticket
2. Clerk will inform the customer about the availability of the ticket
3. The customer will reserve the ticket
4. The clerk will gather necessary data and input into the system
5. The clerk will inform the customer about the due date of payment.
6. The customer agrees.
Postconditions:
1. System will store all the data
2. System will lock the ticket and give it a status “reserved”
3. System will do an audit trail of the transaction
Exceptions:

Use case name: Walk In Reservation ID: UC003 Priority: High

Actor: Customer
Description: This use case describes how customers reserves ticket via walk in
Trigger: Customer wants to reserves ticket via walk in
Type: ☑ External ☐Temporal
Preconditions:
1. Office is open
Normal Course:
1. The customer comes in and inquire about availability of ticket
2. Clerk will inform the customer about the availability of the ticket
3. The customer will reserve the ticket
4. The clerk will gather necessary data and input into the system
5. The clerk will inform the customer about the due date of payment.
6. The customer agrees.
Postconditions:
1. System will store all the data
2. System will lock the ticket and give it a status “reserved”
3. System will do an audit trail of the transaction
Exceptions:

4|Page
Use case name: Online Payment ID: UC004 Priority: High
Actor: Customer
Description: This use case describes how customers pays reserved ticket online
Trigger: Customer wants to pay ticket online
Type: ☑External ☐Temporal
Preconditions:
1. Customer has paypal account or active debit/credit card.
2. The customer already sign up in the site and did a ticket reservation
Normal Course:
1. Customer goes to the billing section of the site
2. The system will give a payment choices
3. Customer will click online payment option
4. Customer inputs the necessary data
5. Customer click agrees and pays
6. System will generate proof of ticket purchase
Postconditions:
1. System will store all the data
2. System will lock the ticket and give it a status “paid”
3. System will do an audit trail of the transaction
Exceptions:

5|Page
Use case name: Money Courier Payment ID: UC005 Priority: High
Actor: Customer
Description: This use case describes how customers pays reserved ticket through
money courier
Trigger: Customer wants to pay reserved ticket through money courier
Type: ☑ External ☐Temporal
Preconditions:
1. The customer already sign up in the site and did a ticket reservation process
Normal Course:
1. Customer goes to the billing section of the site
2. The system will give a payment choices
3. Customer will choose payment through money courier
4. System will display different choices and details of available money courier
5. Customer will get the details and pay selected money courier
6. Customer will call the clerk and give details of payment / Customer will scan
or picture the proof of payment and email.
7. Account officer will confirm the payment
8. Account officer will give the details of payment to the cashier
9. Cashier accepts the payment and does the necessary recording transaction
of payment in the system
10. System generates proof of payment
Postconditions:
1. System will store all the data
2. System will lock the ticket and give it a status “paid”
3. System will do an audit trail of the transaction
Exceptions:

6|Page
Use case name: Walk In Payment ID: UC006 Priority: High
Actor: Customer
Description: This use case describes how customers pays reserved ticket through
walk in
Trigger: Customer wants to pay reserved tickets via walk in
Type: ☑ External ☐Temporal
Preconditions:
1. The customer already sign up in the site and did a ticket reservation process
Normal Course:
1. Customer comes and goes to cashier section with the billing statement.
2. Cashier pulls the data using the billing statement id number
3. Cashier confirms to the customer the amount to be paid
4. Customer pays the amount
5. Cashier accepts the payment and does the necessary recording transaction
of payment in the system
6. System generates proof of payment
7. Cashiers hands the proof of payment to the customer
Postconditions:
1. System will store all the data
2. System will lock the ticket and give it a status “paid”
3. System will do an audit trail of the transaction
Exceptions:

7|Page
Use case name: Concert Ticket Validation ID: UC007 Priority: High
Actor: Customer
Description: This use case will describe how tickets are validated during the event
Trigger: Customer comes to the concert with ticket details on hand.
Type: ☑ External ☐Temporal
Preconditions:
2. The customer already sign up in the site and did a ticket reservation process
1. Customer goes to the event and presents the ticket
2. Clerk pulls out the ticket number from the system
3. System generates validation details
4. Clerk signals the guard that validation of ticket is successful
5. Clerk then inputs the ticket number into the system.
Postconditions:
1. System will store all the data
2. System will lock the ticket and give it a status “used”
3. System will do an audit trail of the transaction
Exceptions:

8|Page
 MIT 202

Phase 1:
Requirements
Determination

Prepared by:
KUNNIG, JERWIN
GALLENO, EDEN
REMOLANO, JULIE DARE

9|Page