4.2. Database Building
4.2.1. Conceptual Design
The conceptual design of database is the result of the first understanding of the application and illustrates the application at its simplest. To answer the
question those arise during the need assessment, conceptual design will defines the objective of the database and the data need which required in the system.
Context Diagram
The context diagram is the highest level and represents the overall system, means context diagram shows all the external entities that interact with the system
through data or information flow over the system. The Context Diagram for this study shows three main entities and what they currently share in the way of
information; administrator, data source and user Figure 8.
Figure ext
aster Data
Maste ovided
ion that listed in the
Table 10. Th vided in
type abular data. The
spatial data a again i
ypes n and line.
8. Cont diagram
M List
r data list pr informat
based on the data e data are di
to two s, i.e. spatial and t
re subdivided nto two t
, i.e. polygo
39
Table 10. Master data list
Data Type Feature type
Entity Attribute
A00NDANA Polygon
id_kab, nm_kab, Kecamatan, Area, Perimeter
L00NDANA Line
id_shoreln, keterangan S00NDANA
Polygon id_settle, keterangan
QA0NDANA Polygon
id_lu, klas_lu RC0NDANA
Polygon id_slope, klas_slope
FA0NDANA Polygon
_lf id_lf, klas
OH0NDANA P
olygon id_sali, klas_sali
OB0NDANA Polygon
id_SST, klas_SST OI0NDANA
P olygon
id_current, klas_cv OE0NDANA
Polygon id_depth, klas_depth
OJ0NDANA P olygon
id_wcl, klas_wcl
OK0NDANA Polygon
id_ph, klas_ph GA0NDANA
Polygon id_geol, geologi, formasi
Spatial
OC0NDANA Polygon
id_coral, klas_coral Kab_indo
Table KodeBPS, Id_prop, NM_prop, id_kab,
NM_kab Tb_pulau
Table id_pul, id_kab, nm_pul, nm_lain,
gugusan, laut, desa, kecamatan, luas Tb_geogpul
Table d,
id_pul, lat, long, luas, altitude, reef, lagoon, shoreln, scale, coastal, low_lan
nearsl, jarak, depth
Tb_geolpul Table
u, iklim, ncam, ik_protek,
change, ps_bdaya, ps_kritis, ps_reef, ps_mrove, ek_darat,
ek_laut, ks_spes id_pul, jenis, geologi, hujan, suh
sd_air, ancaman, ik_a ekosis, ps_hutan, ps_
Tb_ekolpul Table
id_pul, sup_ksv, kws_ldg, jml_ldg, ldg_drt, ldg_laut, rel_data, referen, da_nil
Tb_demopul Table
id_pul, inhabit, human, popup, tahun, densitas, grade, mjr_act, mnr_act,
hm_imp, urb_pop, hab_type, port, airport, pop_agr, eco_prs, pop_tamb, pop_fish
Tb_indikator Table
id_pul, kls_TH, kd_np, kls_er, kls_sr, kls_ep, kls_pa_kls_da, nilai_sk
kls_ie_drt, kls_ie_laut, kls_inv, kls_ur,
2
Tabular
Tb_grafis Table
id_pul, Foto, Image
40
Entity Relationship Diagram
On Conceptual design, the master data list table would be follow by the design of Entity Relationship Diagram ERD of the database. ERD model
contains components of entity set including their relationship set with their attributes that represent all facts from part of the real world. This diagram also
describes cardinality, the number of possible relationship of each entity. There are three type of cardinality, namely one to one 1:1, one to many 1:M and many to
many M:N. Figure 9 show ERD of this system.
Figure 9. Entity Relationship Diagram
4.2.2. Logical Design
Kategori