Project proposal - submission

 ­­Project proposal – Database Technology

Group members:

William Jonathan Mulyadi / 2502045683

Hansel Faren / 2501990350

Benedictus Filbert Federico / 2502005263

 

We are going to take topic number 7 which is the E-ticketing management system.

E-ticketing management system

1.       Background:

The reason why we decided to take this topic is because of our collective enjoyment watching music concerts/festivals. Some of the music festivals don't have a good e-ticketing management system yet. E-ticketing also helps reduce paper or plastic being used as it is compatible with countless devices. E-ticketing is an interaction of humans to interface resulting in a faster process while also promoting ease of use. In conclusion, this is why we decided to pick this topic.

2.       Aim:

           What we're aiming for in our topic is that we want to help other people who like music and the event organizer arranging a music festival by making an e-ticketing management system that will help the event organizer sell their tickets to the customer and the customer can buy the tickets early before the event.

3.       Target user:

           People who want to watch music festivals.

           Event organizer who wants to sell their music festival tickets.

4.       List of relations:

The first table is the location table (LT-TABLE) – this table shows the available location to hold the music concert. It contains the location ID, name of the building, location

(lID, bName, loc)

 

-          lID is primary key

The second table is the choose music festival (CMF-TABLE) – this table contains the name of the music festivals, the ID of the music festival, and the date of the music festival.

           (mID, mName, mD, lID)

-          The primary key will be the mID

-          The foreign key will be lID

The third table is the add customer (AC-TABLE) – this table allowed to save the details of the customers. This table contains the ID of the customers, name of the customers, gender, age, email, password.

           (cID, cName, cGender, cAge, cEmail, cPass)

-          The primary key will be the cID

The fourth table is the transaction ticket (TT- TABLE) – this table allowed the customers to choose the ID of the music festival that they want and how many tickets they want to buy. This table will contain transaction ID, the ID of the music festival, the name of the music festival, the ID of the customers, the number of tickets that they want.

           (tID, lID, mID, mName, cID, amt)

-          The primary key will be the tID

-          The lID is the foreign key

-          The mID is the foreign key

-          The cID is the foreign key

 

          

5.       There will be 2 roles here

           The first one is the customers

           The second one is the admin

The admin can add and edit the details of the music festivals, locations and also can edit the details of the customers.

For printing the ticket, we will use join.

 

6.       The Graph: