• Tidak ada hasil yang ditemukan

Staffsite STMIK PPKIA Pradnya Paramita DD_5_2

N/A
N/A
Protected

Academic year: 2017

Membagikan "Staffsite STMIK PPKIA Pradnya Paramita DD_5_2"

Copied!
13
0
0

Teks penuh

(1)
(2)

Database Design

5-2

(3)

Objectives

This lesson covers the following objectives:

• Recognize and give examples of a one-to-one relationship

• Recognize and give examples of a one-to-many relationship

• Recognize and give examples of a many-to-many relationship

• Recognize redundant relationships and remove them from

(4)

Purpose

• Can one PERSON own many DVDs, or only one ?

• Can one DVD be owned by many PERSONs?

• As we refine and improve our model, we want to make sure

our entity relationships correctly model our business rules.

(5)

One-to-Many (1:M) Relationships

• The various types of 1:M

relationships are most common in an ER Model.

• You have seen several examples already.

Relationship Types 1:M

1:M Relationship

EMPLOYEE assigned to DEPARTMENT

(6)

Many-to-Many (M:M) Relationships

• The various types of M:M relationships are common,

particularly in a first version of an ER model.

• In later stages of the modeling process, all M:M relationships will be resolved, and

disappear.

Relationship Types M:M

STUDENT learns from TEACHER

educates

(7)

One-to-One Relationships For Roles

• Usually you will find just a few of the

various types of 1:1 relationships in every ER model.

• Mandatory at one end

of the 1:1 relationship commonly occurs when roles are modeled.

(8)

One-to-One Relationships For Processes

• 1:1 relationships (of all three variations) also occur when some of the entities represent various stages in a process.

EXAM ANSWER KEY

RECIPE DISH

evaluated with

for

the basis for

the result

(9)

Redundant Relationships

• A redundant relationship can be derived from another relationship in the model.

• In this example, you can derive the relationship from PERSON to COUNTRY from the other two

relationships (COUNTRY to TOWN, TOWN to PERSON), so you should remove the direct relationship from COUNTRY to PERSON .

COUNTRY

TOWN

PERSON

location of

located in

location of

living in hometown of

(10)

Redundant Relationships

• However, be careful of

concluding that a relationship is redundant based on the structure alone.

• Read the relationships to check.

• The ERD shown here does not

reflect a redundant relationship.

the birthplace of location of

hometown

(11)

Terminology

Key terms used in this lesson included:

• Many-to-many (M:M)

• One-to-many (1:M)

• One-to-one (1:1)

(12)

Summary

In this lesson, you should have learned how to:

• Recognize and give examples of a one-to-one relationship

• Recognize and give examples of a one-to-many relationship

• Recognize and give examples of a many-to-many relationship

• Recognize redundant relationships and remove them from

(13)

Referensi

Dokumen terkait

It gives the probability of a normal random variable not being more than z standard deviations above its

• In order to accurately collect this data, a business must create a conceptual model of the data it considers important.. Copyright © 2015, Oracle and/or

• Some health clubs allow memberships to be transferred from one person to another, but other health clubs don’t.. • This business rule is normally determined by what is most

• Apply the rule of Second Normal Form to resolve a violation. in

• Distinguish between using date as an attribute and DAY as an entity in a data model, depending on business requirements. • Solve the problem of keeping characteristics of a date by

• Organize the final oral presentation content in logical outline order.. • Identify appropriate content for each part of

• State the implications for world businesses to be able to easily manipulate data stored in date format.. • Demonstrate the use of SYSDATE and

creation statement, the Oracle database will create a Check Constraint in the database to enforce a value in the NOT NULL column. • This constraint creation can be almost invisible