marathon class psbd

Marathon class

Marathon classEdi Purnomo PutraLecture Code : D5386

NormalisasiTujuan NormalisasiUpdate anomalisinsert, update, deleteFunctional dependencyFull functional dependencynilainim, KdMtkPartial dependencynamabarangidbarang

Normalisasinormalisasi adalah suatu teknik Formal Dalam Menentukan atribut dan menghasilkan kumpulan relasi yang bertujuan untuk menyediakan kebutuhan data yang diperlukan oleh perusahaan

A technique for producting a set of relation with desirable properties, given data reqruirements of an enterprise

Tujuan Normalisasi1)Menjamin struktur data yang konsisten.2)Kerangkapan data yang minimal.3)Stabilitas struktur data yang maksimal1) Meminimalkan Jumlah Kapasitas Penyimpanan Yang Diperlukan Untuk menyimpan data.2)Meminimalkan resiko data yang tidak konsisten dalam suatu basis data.3)Meminimalkan kemungkinanupdatedandeleteanomaly.4)Memaksimalkan stabilitas dari struktur dataManfaat Normalisasi

DatawarehouseKarakteristik DWHETL(Extract, transform, loading)Datamart vs DWH

Karakteristik Subject orientedCustomer, product, salesIntegratedData konsistenMale, M, Ma MaleNonvolatileTidak bisa diubah refresh scd(Slow Changing Dimension)Time variantMingguna, bulanan, tahunandimensi waktu

ETL ExtractEkstract data dari ODS /OLTP(OPERASIONAL DATA SOURCE)TransformPenyamaan data JL, jalan, JLN JLMelakukan kalkulasi aggregateLoadMasukan data ke DWH/Data Mart

Datamart VS DWHData mart1 subjectBagian dari data warehouseRelative SebentarDWHBeberapa subjectImplementasi waktu lama

ERFan trapChasm trapParticipant disjointStrong entity Weak entityDegree relationRecursiveSingle value atributeMultivalue attribute

Prticiapant DisjointParticipantAnd / orJoin disjoin Optional and mandatory

Participant Disjoint

Participant Disjoint

Optional OR

Mandatory Or

DegreeDegree of a RelationshipNumber of participating entities in relationship.

Relationship of degree :two is binary three is ternaryfour is quaternary.

Binary relationship called POwns

Ternary relationship called Registers

Quaternary relationship called Arranges

Recursive relationship called Supervises with role names

AttributesAttributeProperty of an entity or a relationship type.

Attribute DomainSet of allowable values for one or more attributes.

AttributesSimple AttributeAttribute composed of a single component with an independent existence.

Composite AttributeAttribute composed of multiple components, each with an independent existence.

AttributesSingle-valued AttributeAttribute that holds a single value for each occurrence of an entity type.

Multi-valued AttributeAttribute that holds multiple values for each occurrence of an entity type.

AttributesDerived AttributeAttribute that represents a value that is derivable from value of a related attribute, or set of attributes, not necessarily in the same entity type.

Entity TypeStrong Entity TypeEntity type that is not existence-dependent on some other entity type.

Weak Entity TypeEntity type that is existence-dependent on some other entity type.

Fan TrapWhere a model represents a relationship between entity types, but pathway between certain entity occurrences is ambiguous.

Chasm TrapWhere a model suggests the existence of a relationship between entity types, but pathway does not exist between certain entity occurrences. Trap

An Example of a Fan Trap

Semantic Net of ER Model with Fan Trap

At which branch office does staff number SG37 work?

Restructuring ER model to remove Fan Trap

Semantic Net of Restructured ER Model with Fan Trap Removed

SG37 works at branch B003.

An Example of a Chasm Trap

Semantic Net of ER Model with Chasm Trap

At which branch office is property PA14 available? Mengawasi, mengatur

ER Model restructured to remove Chasm Trap

Semantic Net of Restructured ER Model with Chasm Trap Removed

Key TypePrimary key NIM, KDMataKuliahComposite key KdMatakuliah+NIMForeign key Candidate keyAlternate key

AggregateSumAvgMinMaxCount

Intersect, except,union