modul 4

MODULE 4 

DESIGN E-R DIAGRAM 

USING DBDesigner 

A. Purpose
1. Students are able to design a database through its design stages.
2. Students are able to realize the results into a database design using ER diagrams DBDesigner.
B. Basic Theory
1. Basis Theory in Module 3.
C. Equipment and Materials
1. The computer with the Windows 7 operating system.
2. DBDesigner application program.
3. Practical Module System Database.
D. Step Work
1. Draw ER diagram using DB Designer:
a. Run the application program DB Designer.
b. Click the new button and then click on the table so that the work area will result in a new table.

c. Double click on the new table to open the table editor, change the name of the table name with the name of the customer, then fill the attribute table with data like the next step is as follows:

d. Click on coloumn name id_nasabah id_nasabah to set the primary key to be turned into. 

e. Click the check icon to close the table editor so that the customer table becomes:

f. Perform steps b through e to create the account table, cabang_bank and transactions. 

g. After all the tables are created, connect each table to another table with a button as follows:

h. Rename the relationship open relationship with the editor, so that after completion of the final result to be as follows:

E. Analysis
From the experiments above , I can conclude that DB Designer is an application program that is created specifically to design a database design that includes the entities and their attributes and relationships that occur between these entities . For the relation of one to one ( 1:1 ) pictured with white diamond -shaped wake , a relation one to many ( 1 : n ) is described by the wake -shaped diamond white and black , and many to many relationships ( n : m ) is described by black diamond -shaped wake . To many to many relationships will appear in the new table between the two entities are connected .
F. Duties

Of the task on the module 3 Question 1 and 2 , make a design database from stage 1 to stage 4 . Use the DB program to create ER Diagram Designer .
1 . Make design a database to handle data lectures . The data will be handled are : personal data about students , faculty personal data concerning the data subject and the data classrooms . Students may take more than one course , and one course may be taken by more than one student at a time ( joint account ) .
Draw ER Diagram manual for the case of stage 1 to stage 4 !
Design steps :
1 ) Determine the entity :
· Student : store all the personal data of all students .
· Faculty : store all personal data arbitrarily lecturer .
· Mata_kuliah : store information about all the existing courses .
· Ruang_kelas : store information about all classrooms are used .
2 ) Determine the attributes :
· Student :

•  nama_mahasiswa : student 's full name ( varchar ( 50 ) )
•  NIM : student registration number ( char ( 10 ) ) PK
•  address : student residential address ( varchar ( 255 ) )
•  tempat_lahir : place of birth of students ( varchar ( 20 ) )
•  tgl_lahir : date , month and year of birth of students ( varchar ( 20 ) )

· Faculty :

•  nama_dosen : full name lecturers ( varchar ( 50 ) )
•  NIK : faculty personnel identification numbers ( varchar ( 20 ) ) PK

•  address : home address lecturer ( varchar ( 255 ) )
•  no_HP : lecturers phone number ( integer )

· Mata_kuliah :

•  nama_mk : course name ( varchar ( 40 ) )
•  kode_mk : the course code ( varchar ( 15 ) ) PK
•  jumlah_sks : the number of course credits ( integer )
•  classes : classes and hours in a course ( varchar ( 2 ) )
•  schedule : college course schedule includes days and hours ( varchar ( 20 ) )

· Ruang_kelas :

•  id_kelas : class identities such as building , floor and room number ( char ( 5 ) ) PK
•  capacity : the number of seats or the maximum capacity that can be accommodated ( integer )

3 ) Determine the relationship between entities :

relationship:
· Students are guided by faculty:

•  Table main: professor 
•  Table two: student 
•  Relationship: many to one (n: 1) 
•  Attribute liaison: NIK (NIK in faculty FK) 

· Students take mata_kuliah:

•  The main tables: students, mata_kuliah 
•  The second table: mahasiswa_has_mata_kuliah 
•  Relationship: many to many (m: n) 
•  Attribute liaison: NIM, kode_mk (FK NIM, kode_mk in mahasiswa_has_mata_kuliah) 

· Faculty administer mata_kuliah:

•  The main table: mata_kuliah 
•  The second table: lecturer 
•  Relationship: many to one (n: 1) 
•  Attribute liaison: kode_mk (FK kode_mk in mata_kuliah) 

· Mata_kuliah occupy ruang_kelas:

• The main table: ruang_kelas 
•  The second table: mata_kuliah 
•  Relationship: many to one (n: 1) 
•  Attribute support: id_kelas (FK id_kelas in ruang_kelas) 

4) Draw ER diagram using DB Designer:

2 . Take for example any database ( should be different for each student ) . Make the design of the database manually ER Diagram from stage 1 to stage 4 , provided at least database contains 4 pieces entity .

I will create a database Mirai ( Private & Sistematic ) . Mirai is the institute courses ( les ) for levels kindergarten , elementary , junior high , and high school . Subjects provided are Mathematics and English . The system used is a private , one tutor a student . Additionally Mirai teach students according to their ability , to the existing levels divide students by ability level of each student . There are different , even though using the private system , Mirai require that students come to tutoring which has been provided by Mirai . For each student who took the course , students will receive tutoring hours right twice in a week with the designated day . Students are allowed to take the schedule as desired ( any subject area ) , but depending on tutor availability and place . Mirai has been an expert tutor in the two subjects at once ( Maths and English ) .

The data that will be addressed are : personal data about students Mirai , personal data about tentor , data about subjects , data on a schedule provided by Mirai . Database design steps Mirai :

1 . Determine the entity :

· Students : store all data about students Mirai .

· Tutor : store all data about Mirai tutor .

· Maple : store information about subjects in Mirai .

· Schedule : stores information about the tutoring schedule provided Mirai .

2 . Specifying attributes :

· Students :

•  nama_siswa : Mirai student 's full name ( varchar ( 50 ) )
•  id_siswa : Mirai student id number ( integer ) PK
•  alamat_siswa : student residence address ( varchar ( 255 ) )
• classes : a class of students at the school formal ( integer )
•  nama_ortu : the name of the parents or guardians of students ( varchar ( 50 ) )
•  no_HP : phone number / mobile students who could be contacted ( integer )

· Tutor :

•  nama_tentor : full name tentor Mirai ( varchar ( 50 ) )
•  id_tentor : Mirai tutor id number ( integer ) PK
•  address : tentor residential address ( varchar ( 255 ) )

· Maple :

•  kode_mp : subject code ( integer ) PK
•  nama_mp : subject name ( varchar ( 15 ) )
•  levels : level subjects in Mirai , ie from level 1-12 ( integer )
•  costs : the cost in dollars of subjects ( integer )

· Schedule :

•  hari_jam : days and hours of tutoring ( varchar ( 15 ) ) PK
•  tempat_les : Mirai tutoring place that symbolized with numbers ( integer )

3 . Determine relationships between entities :

relationship: 

 students mentored tutor: 

•  The main tables: students 
•  The second table: tentor 
•  Relationship: one to one (1:1) 
•  Attribute liaison: id_siswa (FK id_siswa in students) 

The students took the subject:

•  The main tables: students, maple 
•  The second table: siswa_has_mapel 
•  Relationship: many to many (m: n) 
• Attribute liaison: id_siswa, kode_mp (FK id_siswa, kode_mp in siswa_has_mapel) 

 The students choose the schedule:

•  The main tables: students, schedule 
•  The second table: siswa_has_jadwal 
•  Relationship: many to many (m: n) 
•  Attribute liaison: id_siswa, hari_jam (FK id_siswa, hari_jam in siswa_has_jadwal) 

4. Draw ER diagram using DB Designer:

source: http://millama-aryani.blogspot.com/