Model & Prediksi Data | Model data berdasarkan objek [2.1/3]

Kholid One
19 Sept 202006:50

Summary

TLDRThis script discusses data models, which are methods to represent data, its constraints, and relationships with the real world. It introduces two types of data models: object-based and record-based. Object-based models include entity-relationship models, semantic models, and object-oriented models. The entity-relationship model uses symbols like rectangles for entities, diamonds for relationships, and ovals for attributes. It also covers cardinality, such as one-to-one, one-to-many, many-to-one, and many-to-many relationships, using examples like citizens and ID cards. The object-oriented model views the real world as objects, with classes and attributes, and functions as methods of classes. The script concludes with a comparison to record-based models, emphasizing the object-oriented approach's focus on real-world objects as classes.

Takeaways

  • πŸ˜€ Data models represent data structures, constraints, and relationships with the real world.
  • πŸ“š There are two main types of data models: object-based and record-based.
  • πŸ” Object-based data models include entity-relationship models, semantic models, and object-oriented models.
  • 🏒 In entity-relationship models, entities are represented by rectangles, relationships by diamonds, attributes by ovals, and connections by lines.
  • πŸ”‘ Cardinality in entity-relationship models describes the possible relationships between entities, such as one-to-one, one-to-many, many-to-one, and many-to-many.
  • πŸ› Semantic models are similar to entity-relationship models but use words instead of symbols to describe relationships.
  • πŸš— Object-oriented models view the real world as a set of objects, each with attributes and methods.
  • 🌐 Object-oriented models use classes to represent real-world objects, with attributes as characteristics of the class and methods as functions of the class.
  • πŸ”— Relationships in object-oriented models are not represented by symbols but are implied through class interactions.
  • πŸ“Š Record-based data models focus on the structure of records and how they are organized and related within a database.

Q & A

  • What is a data model?

    -A data model is a way to represent data, its constraints, and relationships with the real world.

  • How many types of data models are mentioned in the script?

    -The script mentions two types of data models: one based on objects and the other based on records.

  • What are the components of an Entity-Relationship (ER) model?

    -The components of an ER model include entities, relationships, attributes, and cardinalities.

  • What does the term 'entity' represent in an ER model?

    -In an ER model, 'entity' represents an object in the real world.

  • What is the meaning of 'relationship' in the context of an ER model?

    -A 'relationship' in an ER model refers to the connection between entities.

  • What are the symbols used to represent entities and relationships in an ER model?

    -In an ER model, rectangles are used for entities, diamonds for relationships, ovals for attributes, and lines for connections.

  • What are the different cardinalities described in the script?

    -The script describes four cardinalities: one-to-one, one-to-many, many-to-one, and many-to-many.

  • Can you provide an example of a one-to-one cardinality as mentioned in the script?

    -An example of one-to-one cardinality is that one citizen can only have one ID card, and one ID card can only be owned by one citizen.

  • What is a semantic data model?

    -A semantic data model is similar to an ER model but uses words instead of symbols to describe the relationships between objects.

  • What is an object-oriented data model?

    -An object-oriented data model treats the real world as a set of objects, where each object is isolated and does not have relationships with other objects.

  • How are classes and attributes defined in an object-oriented data model?

    -In an object-oriented data model, classes represent the blueprint of objects, and attributes are the characteristics of the class.

Outlines

00:00

πŸ“Š Understanding Data Models

This paragraph introduces the concept of data models as a way to represent data, constraints, and relationships with the real world. It explains that data models are divided into two types: object-based and record-based. The object-based model includes entity-relationship (ER) models, which consist of entities, relationships, attributes, and mappings using basic symbols like rectangles for objects, diamonds for relationships, ovals for attributes, and lines for connections. The paragraph also discusses cardinality in ER models, including one-to-one, one-to-many, many-to-one, and many-to-many relationships, providing examples for each. Additionally, it touches on the semantic model, which is similar to ER but uses words instead of symbols to describe relationships.

05:03

🏦 Object-Oriented Data Modeling

The second paragraph delves into object-oriented data modeling, which views the real world as a collection of objects. It contrasts this with the entity-relationship model, where objects are isolated and do not have relationships with each other. The paragraph uses the example of a 'class' to illustrate how objects are mapped to classes, with attributes representing characteristics and functions or procedures representing the behaviors of a class. It provides a specific example of a 'car' class, detailing attributes such as the number of seats, transmission type, and engine type, and functions like moving forward and backward. The summary emphasizes the object-oriented approach to data modeling, where the focus is on the objects and their interactions.

Mindmap

Keywords

πŸ’‘Model Data

A model data is a conceptual structure used to describe the organization, logical and semantic aspects of data and standardize how the data is represented, stored, and used. In the video, model data is central to understanding how data is represented and its relationship to the real world. It is divided into two types: object-based and record-based, which are essential for database design and data analysis.

πŸ’‘Entity-Relationship Model (ER Model)

The Entity-Relationship Model is a high-level, graphical representation of the data in a database. It shows the entities, their attributes, and the relationships that exist between them. In the script, the ER Model is used to illustrate how objects in the real world are interconnected, with rectangles representing entities, diamonds for relationships, and ovals for attributes.

πŸ’‘Cardinality

Cardinality in the context of the ER Model refers to the number of relationships that can exist between entities. It defines the possible number of associations between instances of two entities. The script mentions different cardinalities such as one-to-one, one-to-many, many-to-one, and many-to-many, which are crucial for defining the constraints and rules of data relationships.

πŸ’‘Entity

An entity is a thing or object about which information is to be stored or retrieved. In the video script, entities are represented as objects in the real world, such as 'penduduk' (resident) or 'BPKB' (vehicle registration), and they are the primary components of the ER Model, having attributes and participating in relationships.

πŸ’‘Relationship

A relationship in the ER Model defines the kind of association between two entities. It describes how entities are connected. The script uses examples like a resident owning a vehicle registration certificate, illustrating the many-to-one relationship where one entity (resident) can be associated with many instances of another entity (vehicle registration).

πŸ’‘Attribute

An attribute is a characteristic or property of an entity that describes the entity. In the script, attributes are represented by ovals and are used to detail the features of each entity, such as a 'nomor rekening' (account number) for a bank account or 'alamat' (address) for a customer.

πŸ’‘Object-Oriented Data Model

The Object-Oriented Data Model treats the real world as a set of objects, where each object is an instance of a class with its attributes and methods. This model is mentioned in the script as an alternative to the ER Model, focusing on the encapsulation of data and operations into objects, which is fundamental in object-oriented programming and systems design.

πŸ’‘Class

In the context of object-oriented models, a class is a blueprint for creating objects, defining the properties (attributes) and methods (functions or behaviors) that the objects will have. The script refers to classes as the conceptual categories for grouping similar objects, such as different types of vehicles in a database.

πŸ’‘Semantic Data Model

A Semantic Data Model focuses on the meaning of the data, its relationships, and constraints, rather than just its structure. The script contrasts this with the ER Model, where relationships are represented with words rather than symbols, emphasizing the importance of understanding the semantics of data in database design.

πŸ’‘Record-Based Data Model

A Record-Based Data Model organizes data in records, which are collections of related data items treated as a single unit. This model is mentioned in the script as a way to represent data that is more focused on the record as a whole, rather than individual objects or entities.

πŸ’‘Normalization

Normalization is a process used in database design to organize the columns (attributes) and tables (entities) of a relational database to reduce redundancy and improve data integrity. While not explicitly mentioned in the script, normalization is a key concept related to the design of data models and the prevention of anomalies in database usage.

Highlights

Data models can be considered as ways to represent data, constraints, and relationships with the real world.

Data models are divided into two types: based on objects and based on records.

Entity-Relationship (ER) model is characterized by four main components: entities, attributes, relationships, and mappings.

In ER models, entities are represented by rectangles, relationships by diamonds, attributes by ovals, and connections by lines.

Cardinality in ER models indicates the possible number of entities involved in a relationship, such as one-to-one, one-to-many, many-to-one, and many-to-many.

An example of one-to-one cardinality is a citizen having only one ID card, and an ID card being owned by only one citizen.

A one-to-many cardinality example is a citizen owning multiple vehicle registration documents, but each document belonging to only one citizen.

Many-to-one cardinality is illustrated by a student enrolling in one high school, while a high school can have many students.

Many-to-many cardinality is where multiple entities can relate to multiple other entities, such as a student participating in multiple extracurricular activities, and each activity being joined by many students.

Semantic models are similar to ER models but use words instead of symbols to describe relationships between objects.

An example of a semantic model is a simple representation of the relationship between banks, savings accounts, and customers.

Attributes in semantic models describe characteristics of entities, such as account numbers and balances for savings accounts.

Object-oriented data models view the real world as a set of objects, with each object encapsulated and having no relationships with other objects.

In object-oriented models, objects are mapped to classes, with attributes representing characteristics of the class and functions or procedures representing the class's behavior.

An example of an object-oriented model is a 'Car' class representing various types of cars in the real world, each with attributes like the number of seats and transmission type.

Functions in object-oriented models define the behavior of objects, such as moving forward and braking for a 'Car' class.

Record-based data models focus on the structure and organization of data records, rather than the relationships between objects.

Transcripts

play00:03

twicsy Setelah mempelajari jenis-jenis

play00:14

data Sekarang kita akan sama-sama

play00:16

belajar tentang model data model data

play00:23

dapat dikatakan sebagai cara untuk

play00:26

merepresentasikan data batasan serta

play00:29

hubungannya dengan dunia nyata model

play00:37

data dibagi dua jenis untuk representasi

play00:40

data yang pertama berdasarkan objek dan

play00:42

kedua berdasarkan record model data

play00:48

berbasis objek diantaranya model entity

play00:51

relationship model semantik dan model

play00:53

berorientasi objek karakteristik dan

play00:57

istilah untuk model er adalah 1

play01:00

dengan objek sebagai entitas yang kedua

play01:06

adalah set entitas adalah kumpulan

play01:08

entitas yang sama yang ketiga atribut

play01:11

adalah karakteristik dari suatu entitas

play01:15

yang keempat Relasi adalah hubungan

play01:17

antar entitas yang satu dengan etiket

play01:19

yang lain yang lima pemetaan entitas

play01:21

dengan menggunakan simbol-simbol dasar

play01:26

yang biasa digunakan pada model Ir

play01:28

adalah persegi panjang untuk

play01:29

menggambarkan objek di dunia nyata belah

play01:32

ketupat untuk menghubungkan entitas

play01:33

dengan entitas lain oval untuk mendapat

play01:36

mendeskripsikan karakteristik tiap

play01:38

entitas dan garis untuk penghubung set

play01:40

entitas ada gambar ini kita lihat bahwa

play01:43

persegi panjang itu disebut sebagai

play01:46

handset entitas setan di Trans digunakan

play01:50

untuk menggambarkan objek objek di dunia

play01:52

nyata lalu ini adalah belah ketupat ini

play01:56

disebut sebagai set relasi yang

play01:58

digunakan untuk

play02:00

yang sehat entitas dengan set entitas

play02:02

lainnya selanjutnya adalah oval nah

play02:05

gambar oval ini disebut sebagai atribut

play02:08

digunakan untuk mendeskripsikan

play02:09

karakteristik setiap entitas selanjutnya

play02:13

adalah garis-garis digunakan untuk

play02:16

sebagai penghubung antara set relasi

play02:18

dengan set entitas ataupun menghubungkan

play02:21

set entitas dengan atribut Selain itu

play02:26

entity-relationship memiliki

play02:28

kabinet-kabinet litas untuk menunjukkan

play02:30

jumlah entitas yaitu pertama one-to-one

play02:34

One atau satu ke-10 merupakan

play02:39

kardinalitas dimana satu entitas hanya

play02:42

dapat berelasi dengan satu entitas

play02:45

lainnya dan berlaku sebaliknya contohnya

play02:48

adalah satu penduduk hanya boleh

play02:50

memiliki satu KTP atau satu KTP boleh

play02:56

dimiliki hanya oleh satu penduduk

play03:00

yang selanjutnya adalah want to many

play03:03

many-to-one dan many-to-many one-to-many

play03:09

atau satu ke banyak kuantum ini

play03:13

merupakan kardinalitas dimana satu

play03:16

entitas a dapat berelasi dengan banyak

play03:19

entitas B lainnya dan satu entitas B

play03:22

hanya dapat berelasi dengan satu entitas

play03:25

a saja contohnya adalah satu penduduk

play03:29

boleh memiliki banyak BPKB tetapi satu

play03:36

BPKB hanya boleh dimiliki oleh satu

play03:40

penduduk

play03:42

yang selanjutnya adalah many-to-one atau

play03:46

dari banyak ke-1 many Tuan merupakan

play03:50

kardinalitas dimana satu entitas a dapat

play03:53

berelasi hanya dengan satu entitas B

play03:57

Adapun satu entitas b dapat berelasi

play04:00

dengan banyak entitas a contoh nya

play04:04

adalah seorang siswa dapat mendaftar di

play04:08

1 SMA sedangkan 1 SMA itu bisa memiliki

play04:15

banyak siswa yang selanjutnya adalah

play04:19

many-to-many atau banyak ke banyak yaitu

play04:24

kardinalitas dimana banyak entitas dapat

play04:27

berelasi dengan banyak entitas lainnya

play04:29

dan berlaku sebaliknya contohnya adalah

play04:33

seorang siswa bisa mendaftar di banyak

play04:37

ekskul sedangkan satu ekskul itu bisa

play04:42

di banyak siswa selanjutnya adalah model

play04:47

semantik modelnya mirip dengan entity

play04:50

relationship yaitu menggunakan relasi

play04:52

antar objek namun relasinya tidak

play04:54

digambarkan dalam simbol tetapi dengan

play04:56

kata-kata kita lihat bahwa ini adalah

play04:59

salah satu model semantik ya contoh

play05:03

model cantik semantik sederhana yang

play05:05

menggambarkan hubungan antar bank

play05:06

tabungan dan customer dimana sebuah bank

play05:11

melayani tabungan dan mempunyai customer

play05:14

dan customer yakni salah satunya bernama

play05:16

Amir ya Ini adalah atribut-atribut dari

play05:21

tabungan yaitu nomor rekening dan saldo

play05:23

sedangkan atribut dari Aamir adalah

play05:26

alamat dan nomor rekening yang c adalah

play05:31

model data berorientasi objek yaitu

play05:33

model data yang menganggap dunia nyata

play05:35

sebagai sebuah objek pada model data ini

play05:40

objek terisolasi dan tidak punya relasi

play05:43

yang dengan objek yang lain Jika pada

play05:49

entity relationship sebagai disebut

play05:52

sebagai entitas D model-model berantas

play05:55

objek setan tetap disebut sebagai class

play05:58

karakteristik dan lab istilah untuk

play06:00

model berotasi objek adalah memetakan

play06:02

objek supaya kelas atribut merupakan

play06:04

karakteristik dari kelas fungsi atau

play06:06

prosedur merupakan fungsi dari sebuah

play06:08

kelas contohnya adalah pada class mobil

play06:12

Berikut ini yang merupakan representasi

play06:14

dari berbagai jenis mobil dunia nyata

play06:17

setiap mobil memiliki beberapa atribut

play06:19

seperti jumlah kursi jenis transmisi

play06:22

otomatis ataupun manual dan jenis mesin

play06:25

yang digunakan dapat juga didefinisikan

play06:27

fungsi mobil secara umum pada tiap mobil

play06:30

seperti maju-mundur dan mengerem itulah

play06:33

penjelasan model data berdasarkan objek

play06:36

Thailand Jude ke model data yang kedua

play06:38

yaitu model data berdasarkan record of

play06:43

[Musik]

play06:48

badges0

Rate This
β˜…
β˜…
β˜…
β˜…
β˜…

5.0 / 5 (0 votes)

Related Tags
Data ModelingEntity RelationshipObject-OrientedDatabase DesignSemantic ModelCardinalityData RepresentationRecord ModelModeling TechniquesSoftware Development