Fernandha Dzaky

Final Project Report

January 8th, 2020

II. Table of Contents

Table of content
Background / Problem description
Aims and benefits
Problem Formulation
Solution design
Database Security
Screenshots
Link to Git, Demo Video and References

II. Background & Problem description

Big campus like Bina Nusantara International of course has so many events. There are so many types of events as well, such as , music events, charity events, championship and many more.

Let us take an example on one of the biggest event on BINUS International, Fuse Experience. Fuse Experience is a music and art festival held by Binus International Music Club. This event sure attracts many audience, because of the big shot and upcoming top artists that are coming to this event such as Elephant Kind, Kunto Aji, and Sal Priadi and many more.Those big names capable of being a breakthrough for the event.

But after we sat down and talk with the committee, turns out that Fuse Experience does not have their own sites , where people can buy tickets online. They use third party sites such as Go-Tix and Loket.com for selling their event ticket. Hence they don’t own their customer’s database and also the financial traffic.

III. Aims and benefits

As a big event, we are expecting Fuse to have a simple yet effective Event Ticketing system that can help the audience / customer to buy their tickets online. We intend to create a System and Database for Fuse, where it does not only help the audience to secure the ticket availability but also plays a very big role for the Fuse itself in terms of Customer Data , Ticketing, and Financial Management.

IV. Problem Formulation

Before we start executing the project, there are some tricky problems and obstacles that we had to face in order for this System runs just fine. These problems are not that easy to be solved because we didn’t have any experience in any of the problems that faced. Down below are the 6 main problems that we encountered before the making of this System :

1. What programming Language should be used ? There are multiple options of programming languages , but we have to pick the most suitable one for this project

2. How should we design the database ? There are multiple ways to create a database for event ticketing, but we have to choose the best and suitable ways and design because this database will be later ( hopefully ) used by Fuse Experience.

3. How the system flows or works ? We want the programme to be as ‘user friendly’ as possible, there are couple ways to visualize but we have to pick the most suitable one for this project.

V. Solution design

We decided to go with Website Application because Websites it’s the most universal platform in the universe, and its more convenient for the admin to manage the customer databases. The WebApp not only can be used by Customers ( Buying Event Ticket Online ) but also can be used by Admin to manage the Order History, monitor the Financial Traffic, and etc.

1. What programming Language should be used ? There are multiple options of programming languages but we decided to go with HTML for its Front End ( UI / UX ) and PHP for the communication between the websites and database. Database security is very important for Fuse Experience because it contains a lot of private information, that is why we go with PHP. People cannot inspect or see the code directly from websites, because PHP Codes are executed directly in the server, not in the websites.

2. How should we design the database ? We use My SQL Database for this project, and we have 11 Tables in total namely Address , Customer , Ticket_Detail , Ticket ,Bill , Payment , Payment_Type, Staff , Artist , Schedule and Position. Rest assured, this Database is already in a 3NFormat so all of the tables has been normalized. Down below Screen Shot of the ERD, along with the Relationships.

** Screenshot of ERD and Relationships **

3. How the system flows or works ? What’s good about this system, is the user / customer don’t have to register in order to buy their tickets, because after we pay attention to the behaviour of the customer who buys event ticket online, they tend to buy their ticket once , and they won’t open the sites anymore

That’s why with the system that we designed, customers don’t have to sign up in order to buy a ticket, they just have to write their biodata, select their ticket class and quantity, their payment method, and that’s it.

VI. Database Security

Customers data are very important, not only for Fuse, but also for the customer itself. That’s why the security of the database is very important. We used 2 ways to protect the database from malicious hacker.

The first attempt to secure the database is by creating an admin login page, where the admin who knows the user and password can login to the back End or the Customer Data Storage. The credentials and passwords for the admin to login and stored in PHP file , where people can’t see the code directly from the website inspect or the database. The second attempt that we do to secure the database is by using PHP Language. As stated above, we use PHP for the communication between the websites and database. People cannot inspect or see the code directly from websites, because PHP Codes are executed directly in the server, not in the websites.

VII. Screenshots