Table Design CALL FOR PAPER 2010 MUNAS APTIKOM.

Seminar dan Call For Paper Munas Aptikom Politeknik Telkom Bandung, 9 Oktober 2010 229 Columns Data type Atrribute F_merek Varchar20 Brand F_min Int Minimum price F_maks Int Maximum price Table tbl_mp_npm represents company entity. The following table is a relation between the column and data type column in the tbl_mp_npm table with the attributes of company entity. Table 4. Columns of tbl_mp_npm table. Columns Data type Atrribute F_industri Varchar30 Industrial sector F_npm Float Average NPM Table tbl_mp_pidato represents announcement entity. The following table is a relation between the column and data type column in the tbl_mp_pidato table with the attributes of announcement entity. Table 5. Columns of tbl_mp_pidato table. Columns Data type Atrribute F_tanggal Datetime Time F_owner Varchar20 Player F_isi Varchar100 Content Table tbl_mp_player represents player entity. The following table is a relation between the column and data type column in the tbl_mp_player table with the attributes of player entity. Table 6. Columns of tbl_mp_player table. Columns Data type Atrribute F_nama Varchar{20} Name F_password Varchar20 Password F_validasi Varchar20 - F_nomor Smallint - F_level Tinyint Level F_status Tinyint Status F_firstlogin Datetime - F_lastlogin Datetime - F_peluru Tinyint Audit F_salah Tinyint Mistakes Table tbl_mp_pns represents tax official entity. The following table is a relation between the column and data type column in the tbl_mp_pns table with the attributes of tax official entity. Table 7. Columns of tbl_mp_pns table. Columns Data type Atrribute F_pangkat Varchar10 Grade F_golongan Varchar3 Class F_gaji Int Income 230 Seminar dan Call For Paper Munas Aptikom Politeknik Telkom Bandung, 9 Oktober 2010 Table tbl_mp_rekor represents performance record entity. The following table is a relation between the column and data type column in the tbl_mp_rekor table with the attributes of performance record entity. Table 8. Columns of tbl_mp_rekor table. Columns Data type Atrribute F_nama Varchar20 Player F_level Tinyint Level F_counter Smallint Amount F_waktu Datetime Time F_status Tinyint Status Table tbl_mp_soal represents case entity. The following table is a relation between the column and data type column in the tbl_mp_soal table with the attributes of case entity. Table 9. Columns of tbl_mp_soal table. Columns Data type Atrribute F_nomor Smallint Case number F_kasus Varchar200 Case F_jawaban Smallint Answer F_alasan Varchar130 Reason F_owner Varchar20 Player

5.2 Table Relationship Design

As an RDBMS, there are relationship among tables in the database design of Mafia Pajak. The relation between these tables will be described with the image below. Figure 1. Table relationship design.

6. Testing

Testing is conducted by collecting Mafia Pajak database size data on August 21, 2010. The collected data is number of records and data size which is measured in kilobytes. Tables are grouped into two, namely the master tables and transaction tables. Master table is a table whose size is not affected by the number of players. Transaction table is the table whose size is affected by a number of players. Master tables include tbl_mp_karyawan, tbl_mp_mobil, tbl_mp_npm, and tbl_mp_pns. Here is the data size of the tables. Table 10. Data on master tables. Table size record size KB Tbl_mp_karyawan 54 2,8 Tbl_mp_mobil 58 2,5 Tbl_mp_npm 59 2,4 Tbl_mp_pns 27 1,5 Seminar dan Call For Paper Munas Aptikom Politeknik Telkom Bandung, 9 Oktober 2010 231 Transaction tables include tbl_mp_aktivitas, tbl_mp_pidato, tbl_mp_player, tbl_mp_rekor, and tbl_mp_soal. Here is the data size of the tables. Table 11. Data on transaction tables. Table size record size KB Tbl_mp_aktivitas 11.405 886,3 Tbl_mp_pidato 67 5,3 Tbl_mp_player 519 34,9 Tbl_mp_rekor 1.557 50,9 Tbl_mp_soal 4.936 1.100 From the data above can be seen that the master data size is much smaller than the transaction data. Overall size of the master data is 9.2 kilobytes. Overall size of the transaction data is 2,077 kilobytes or 2.077 megabytes. Transaction data is relative to 519 players. Thus, the ratio of master data on the amount of transaction data for as many as 519 players is 0.44. The value of this ratio will further decrease when the players getting a lot. The size of the data which is required by one player is four kilobytes. This value is obtained by dividing the size of transaction data with the number of players. Thus, to facilitate the needed space for 1000 players is 4 MB of data. The system requires space for 4 GB of data to facilitate a million players.

7. Conclusion

Through this research, the following conclusions are as follows. • Database design for the game Mafia Pajak is being made and match with the game scenario. • The ratio of master data to the transaction data is very small for the number of players is more than 500. • Size of data needed by one player is four kilobytes. References [1] Gertz, Michael., OracleSQL Tutorial, Database and Information System Group, Department of Computer Science, University of California, Davis. [2] “Survei Gaji 2010”, SwaSembada July 14, 2010. [3] Indonesia Car Price Guide, http:www.autocarprices.com, July 18, 2010 [4] Tabel Remunerasi Depkeu, http:remunerasipns.wordpress.com20100105tabel- remunerasi-depkeu-2 July 18, 2010 [5] Yahoo Industry Browser, http:finance.yahoo.commarketupdateoverview, July 18, 2010