FUTSAL ARENA 1CC5 THORIQ MUHAMMAD NAUFAL AULIA MUHAMMAD FAHRUL ROZI Faculty of Engineering University of Indonesia PROJECT ON Futsal Arena Developed By Name : Thoriq Muhammad Naufal Aulia Muhammad Fahrul Rozii Reg. No : NIIT FUTSAL ARENA Batch Code : Start Date : December End Date : December Name Of The Coordinator : Kevin Harada Name Of Developer : Thoriq Muhammad Naufal Aulia Muhammad Fahrul Rozi : December Date Of Submission NIIT CERTIFICATE This is to certify that this report, titled Futsal Arena, embodies the original work done by Thoriq Muhammad Naufal Aulia, Muhammad Fahrul Rozi in partial fulfillment of his course Requitment at NIIT. Coordinator: MR. Kevin Harada ACKNOWLEDGEMENT We have benefited a lot from the feedback and suggestions given to us by Kevin Harada and other faculty members. The Project presentation opportunity we have with CCIT-FTUI is a greatchance for learning and professional development. Therefore, we consider ourselves very lucky as we are provided with an opportunity to be a part of it. We are also grateful for having a change to meet so many wonderful people and professionals who led us through this project period. Bearing in mind, we would like to express our deepest gratitude and special thanks to Mr.Kevin Harada of CCIT-FTUI faculty who is spite of being extraordinarily busy with his duties, took time out to hear, guide and keep us on the correct path and allowing us to carry out our project until completion. Our Project assignment won’t be as good as it is now without any help, feedback and suggestion that were given to us by our friends within the campus. So, we would also like to say thank you to all of them. We will strive to use gained skills and knowledge in the best possible way, and we will continue to work on the improvements, in order to attain desired carrer objective. SYSTEM ANALYSIS Rental Futsal Arena is a large event management company of Depok City. The company organizes various types of rented. The management of Futsal Arena have realized that it is dificult to maintain so much data manually. Therefore, they invented some data systems to facilitate the work. Features provided is a function and many functions as a provider of output data that has been processed by the system. So that all activity in the company can be conveyed easily and reduce the risk of data error. ENTITIES Number Of Entities: 5 Names Of Entities: 1. Customer 2. Employee 3. Transaction 4. Field 5. Schedule ATTRIBUTES Attributes: The Various Entitles and their attributes are listed in the following table: Entities Customer Employee Tansaction Field Schedule Attributes ID_Customer Customer_Name Team_Name No_Phone ID_Employee Employee_Name Address Gender No_Phone_Employee ID_Transaction Date_Transaction ID_Field Price Quantity_(Hours) Total ID_Field Field_Type Price ID_Schedule ID_Field Date_Play Hour E/R DIAGRAM TABLES Number Of Tables: 5 Structure of Tables: The Table Structures are shown here. COSTUMER (Entity) CUSTOMER ID_Customer Name_Customer Name_ Team NO_Phone TRANSACTION (Entity) TRANSACTION ID_Transaction Date_Transaction ID_Customer ID_Employee ID_Field Price Quantity Total EMPLOYEE (Entity) EMPLOYEE ID_Employee Employee_Name Gender Address Employee_Phone SCHEDULE (Entity) SCHEDULE ID_Schedule ID_Field Date_Play Hour FIELD (Entity) FIELD ID_Field Type_Field Price The Transaction Details table is formed because of a many-to-many relationship between Event Table and Payment Table. TABLES 1 NF Number Of Tables: 5 Structure of Tables: The Table Structures are shown here. COSTUMER CUSTOMER ID_Customer Name_Customer Name_ Team NO_Phone TRANSACTION TRANSACTION ID_Transaction Date_Transaction ID_Customer ID_Employee ID_Field Price Quantity Total FIELD FIELD ID_Field Type_Field Price EMPLOYEE EMPLOYEE ID_Employee Employee_Name Gender Address Employee_Phone SCHEDULE SCHEDULE ID_Schedule ID_Field Date_Play Hour TABLES 1 NF Example: Table 1 NF Before ID_Transaction Date_Transaction ID_Customer Name_Customer TR001 10/12/2015 C001 Bokir TR002 10/12/2015 C002 Ridwan TR003 11/12/2015 C003 Hudaya Name_ Team NO_Phone ID_Employee Employee_Name PalaKubang 08968779990 E001 Akbar Aw Squad 081277778989 E002 Akromul Nestrie fc 081231324546 E003 Noorman ID_Field Lap001 Synthetic Rp200.000 2 Rp400.000 12/12/2015 Hour 19.00-20.00 20.00-21.00 Lap003 Rubber Rp150.000 3 Rp450.000 13/10/2015 14.00-15.00 Lap002 Type_Field Board Price Rp175.000 Quantity Total 2 Rp350.000 Date_Play 14/10/2015 15.00-16.00 16.00-17.00 09.00-10.00 10.00-11.00 TABLE 1 NF After ID_Transaction Date_Transaction ID_Customer Name_Customer TR001 TR001 TR002 TR002 TR002 TR003 10/12/2015 10/12/2015 10/12/2015 10/12/2015 10/12/2015 11/12/2015 C001 C001 C002 C002 C002 C003 Bokir Bokir Ridwan Ridwan Ridwan Hudaya TR003 11/12/2015 C003 Hudaya Name_ Team NO_Phone ID_Employee Employee_Name ID_Field PalaKubang PalaKubang Aw Squad Aw Squad Aw Squad Nestrie fc 08968779990 08968779990 081277778989 081277778989 081277778989 081231324546 E001 E001 E002 E002 E002 E003 Akbar Akbar Akromul Akromul Akromul Noorman Lap001 Lap001 Lap003 Lap003 Lap003 Lap002 Nestrie fc 081231324546 E003 Noorman Lap002 Type_Field Price Quantity Total Date_Play Hour Synthetic Synthetic Rubber Rubber Rubber Board Rp200.000 Rp200.000 Rp150.000 Rp150.000 Rp150.000 Rp175.000 2 2 3 3 3 2 Rp400.000 Rp400.000 Rp450.000 Rp450.000 Rp450.000 Rp350.000 12/12/2015 12/12/2015 13/12/2015 13/12/2015 13/12/2015 14/12/2015 19.00-20.00 Board Rp175.000 2 Rp350.000 14/12/2015 10.00-11.00 20.00-21.00 14.00-15.00 15.00-16.00 16.00-17.00 09.00-10.00 TABLES 2 NF The table are already in 2NF as the attributes in each table depend on primary key. The table structure as shown here. COSTUMER CUSTOMER ID_Customer Name_Customer Name_ Team NO_Phone TRANSACTION TRANSATION ID_Transaction Date_Transaction ID_Customer ID_Employee ID_Field Price Quantity Total ID_Employee Employee_Name Gender Address Employee_Phone ID_Field Type_Field Price ID_Schedule ID_Field Date_Play Hour TABLES 3 NF The table are already in 3NF as the attributes in each table depend on primary key. The table stucture as shown here. COSTUMER CUSTOMER ID_Customer Name_Customer Name_ Team NO_Phone EMPLOYEE EMPLOYEE ID_Employee Employee_Name Gender Address Employee_Phone SCHEDULE SCHEDULE ID_Schedule ID_Field Date_Play Hour FIELD FIELD ID_Field Type_Field Price TRANSACTION TRANSACTION ID_Transaction Date_Transaction ID_Customer ID_Employee ID_Field Price Quantity Total TABELS AFTER DENORMALIZATION When are we going to find out about when the payment transactions and by whom, there is attribute involved is taken from the table before the process of denormalization such as transactions done. We also look at how to find out about how the transactions by customer and how much. In this case, we separate the several attributes that are taken off the table before the denormalization process such transactions. TRANSACTION ID_Transaction Date_Transaction ID_Customer ID_Employee ID_Field Price Quantity Total PRIMARY AND FOREIGN KEYS The Primary and Foreign Keys (Wherever Applicable) for each table are listed with their respective table name: Customer Primary Key: ID_Customer Employees Primary Key: ID_Employee Transaction Primary Key: ID_Transaction Foreign Keys: ID_Field ID_Employee, ID_Customer Field Primary Key: ID_Field Foreign Keys: ID_Schedule Schedule Primary Key: ID_Schedule Foreign keys: ID_Field PROBLEMS ENCOUNTERED Some of the problems experienced in the writing of the inventor of this project are as follows: We have just learned of Data Table Relation and E/R Diagrams We have not had experience in doing the project as given at this time Difficulties when looking for Relation at each data CONFIGURATION Hardware: IntelR DualCoreTM @ 2,20GHz 2,20 GHz, 2.00GB RAM, 500 GB HDD, Operating System: Windows 10 Home Singel Language Software: Microsoft Visio 2016, Microsoft Word 2016 PROJECT FILE DETAILS S.No File Name Remarks 1 FutsalArena.word Word Document contain Relation
