SlideShare a Scribd company logo
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 7- 1
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Mapping Conceptual Design into a Logical
Design
Relational Database Design using
ER-to-Relational Mapping
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
ER-to-Relational Mapping Algorithm
 ER-to-Relational Mapping Algorithm

Step 1: Mapping of Regular Entity Types

Step 2: Mapping of Weak Entity Types

Step 3: Mapping of Binary 1:1 Relation Types

Step 4: Mapping of Binary 1:N Relationship Types.

Step 5: Mapping of Binary M:N Relationship Types.

Step 6: Mapping of Multivalued attributes.

Step 7: Mapping of N-ary Relationship Types.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 1: Mapping of Regular Entity Types.
 For each regular (strong) entity type E in the ER schema,
create a relation R that includes all the simple attributes of
E.

Choose one of the key attributes of E as the primary key for
R.

If the chosen key of E is composite, the set of simple
attributes that form it will together form the primary key of R.
 Example: We create the relations EMPLOYEE,
DEPARTMENT, and PROJECT in the relational schema
corresponding to the regular entities in the ER diagram.

SSN, DNUMBER, and PNUMBER are the primary keys for
the relations EMPLOYEE, DEPARTMENT, and PROJECT
as shown.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 7- 5
The ER conceptual schema diagram for the COMPANY database.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
FIGURE 7.2
Result of mapping the COMPANY ER schema into a relational schema.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 2: Mapping of Weak Entity Types

For each weak entity type W in the ER schema with owner entity
type E, create a relation R & include all simple attributes (or
simple components of composite attributes) of W as attributes of
R.
 Also, include as foreign key attributes of R the primary key
attribute(s) of the relation(s) that correspond to the owner entity
type(s).

The primary key of R is the combination of the primary key(s) of
the owner(s) and the partial key of the weak entity type W, if any.
 Example: Create the relation DEPENDENT in this step to
correspond to the weak entity type DEPENDENT.
 Include the primary key SSN of the EMPLOYEE relation as a
foreign key attribute of DEPENDENT (renamed to ESSN).

The primary key of the DEPENDENT relation is the combination
{ESSN, DEPENDENT_NAME} because DEPENDENT_NAME is
the partial key of DEPENDENT.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 3: Mapping of Binary 1:1 Relation Types

For each binary 1:1 relationship type R in the ER schema, identify the
relations S and T that correspond to the entity types participating in R.
 There are three possible approaches:
1. Foreign Key approach: Choose one of the relations-say S-and include a
foreign key in S the primary key of T. It is better to choose an entity type
with total participation in R in the role of S.

Example: 1:1 relation MANAGES is mapped by choosing the participating
entity type DEPARTMENT to serve in the role of S, because its participation
in the MANAGES relationship type is total.
2. Merged relation option: An alternate mapping of a 1:1 relationship type
is possible by merging the two entity types and the relationship into a
single relation. This may be appropriate when both participations are
total.
3. Cross-reference or relationship relation option: The third alternative
is to set up a third relation R for the purpose of cross-referencing the
primary keys of the two relations S and T representing the entity types.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 4: Mapping of Binary 1:N Relationship Types.
 For each regular binary 1:N relationship type R, identify the
relation S that represent the participating entity type at the
N-side of the relationship type.
 Include as foreign key in S the primary key of the relation T
that represents the other entity type participating in R.
 Include any simple attributes of the 1:N relation type as
attributes of S.
 Example: 1:N relationship types WORKS_FOR,
CONTROLS, and SUPERVISION in the figure.
 For WORKS_FOR we include the primary key DNUMBER
of the DEPARTMENT relation as foreign key in the
EMPLOYEE relation and call it DNO.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 5: Mapping of Binary M:N Relationship
Types.

For each regular binary M:N relationship type R, create a new
relation S to represent R.

Include as foreign key attributes in S the primary keys of the
relations that represent the participating entity types; their
combination will form the primary key of S.

Also include any simple attributes of the M:N relationship type (or
simple components of composite attributes) as attributes of S.
 Example: The M:N relationship type WORKS_ON from the
ER diagram is mapped by creating a relation WORKS_ON
in the relational database schema.

The primary keys of the PROJECT and EMPLOYEE relations are
included as foreign keys in WORKS_ON and renamed PNO and
ESSN, respectively.
 Attribute HOURS in WORKS_ON represents the HOURS attribute of
the relation type. The primary key of the WORKS_ON relation is the
combination of the foreign key attributes {ESSN, PNO}.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 6: Mapping of Multivalued attributes.
 For each multivalued attribute A, create a new relation R.
 This relation R will include an attribute corresponding to A, plus the
primary key attribute K-as a foreign key in R-of the relation that
represents the entity type of relationship type that has A as an
attribute.
 The primary key of R is the combination of A and K. If the
multivalued attribute is composite, we include its simple
components.
 Example: The relation DEPT_LOCATIONS is created.
 The attribute DLOCATION represents the multivalued attribute
LOCATIONS of DEPARTMENT, while DNUMBER-as foreign key-
represents the primary key of the DEPARTMENT relation.
 The primary key of R is the combination of {DNUMBER,
DLOCATION}.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Step 7: Mapping of N-ary Relationship
Types.
 For each n-ary relationship type R, where n>2, create a new
relationship S to represent R.
 Include as foreign key attributes in S the primary keys of the
relations that represent the participating entity types.
 Also include any simple attributes of the n-ary relationship
type (or simple components of composite attributes) as
attributes of S.
 Example: The relationship type SUPPY in the ER on the
next slide.
 This can be mapped to the relation SUPPLY shown in the
relational schema, whose primary key is the combination of the
three foreign keys {SNAME, PARTNO, PROJNAME}
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
FIGURE 4.11
Ternary relationship types. (a) The SUPPLY relationship.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
FIGURE 7.3
Mapping the n-ary relationship type SUPPLY from Figure 4.11a.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Summary of Mapping constructs and
constraints
Table 7.1 Correspondence between ER and Relational Models
ER Model Relational Model
Entity type “Entity” relation
1:1 or 1:N relationship type Foreign key (or “relationship” relation)
M:N relationship type “Relationship” relation and two foreign keys
n-ary relationship type “Relationship” relation and n foreign keys
Simple attribute Attribute
Composite attribute Set of simple component attributes
Multivalued attribute Relation and foreign key
Value set Domain
Key attribute Primary (or secondary) key

More Related Content

Similar to Module_2_ER_to_relational_mapping_algorithm.pptx (20)

PPT
Mapping EER Model Constructs to Relations ADB_05_BRvs.ppt
SenzotaSemakuwa
 
PPT
Mapping
Samir Sabry
 
PPT
Er & eer to relational mapping
saurabhshertukde
 
PDF
Web app development_database_design_er-mapping_12
Hassen Poreya
 
PPTX
ERD_to_Rel2.PPThhhhhhhhhhhhhhhhhhhh.pptx
PreetiAggarwal52
 
PDF
Mapping example
Samir Sabry
 
PDF
Mapping example
Samir Sabry
 
PPTX
Logical database design and the relational model(database)
welcometofacebook
 
PDF
Pokok Bahasan 06 ER-EER to Relational Mapping (1).pdf
jefrifrans
 
PPT
Ch 6 Logical D B Design
guest8fdbdd
 
PPTX
ER model to Relational model mapping
Shubham Saini
 
PPT
Kul 2
sw pitara
 
PPT
The Database Environment Chapter 5
Jeanie Arnoco
 
PDF
Unit 2 DBMS
DhivyaSubramaniyam
 
PPT
chapter number 05Corrected local database.ppt
AzarHamid
 
PPTX
logical data base design ,data base , .pptx
mahnoorasif905
 
PDF
7. ER Model to Relational Model copy.pdf
RaksaMa1
 
PDF
ch03-Data Modeling Using the Entity-Relationship (ER) Model.pdf
RounakSaha34
 
Mapping EER Model Constructs to Relations ADB_05_BRvs.ppt
SenzotaSemakuwa
 
Mapping
Samir Sabry
 
Er & eer to relational mapping
saurabhshertukde
 
Web app development_database_design_er-mapping_12
Hassen Poreya
 
ERD_to_Rel2.PPThhhhhhhhhhhhhhhhhhhh.pptx
PreetiAggarwal52
 
Mapping example
Samir Sabry
 
Mapping example
Samir Sabry
 
Logical database design and the relational model(database)
welcometofacebook
 
Pokok Bahasan 06 ER-EER to Relational Mapping (1).pdf
jefrifrans
 
Ch 6 Logical D B Design
guest8fdbdd
 
ER model to Relational model mapping
Shubham Saini
 
Kul 2
sw pitara
 
The Database Environment Chapter 5
Jeanie Arnoco
 
Unit 2 DBMS
DhivyaSubramaniyam
 
chapter number 05Corrected local database.ppt
AzarHamid
 
logical data base design ,data base , .pptx
mahnoorasif905
 
7. ER Model to Relational Model copy.pdf
RaksaMa1
 
ch03-Data Modeling Using the Entity-Relationship (ER) Model.pdf
RounakSaha34
 

Recently uploaded (20)

PPTX
265587293-NFPA 101 Life safety code-PPT-1.pptx
chandermwason
 
PDF
POWER PLANT ENGINEERING (R17A0326).pdf..
haneefachosa123
 
PDF
Introduction to Productivity and Quality
মোঃ ফুরকান উদ্দিন জুয়েল
 
PPTX
Introduction to Neural Networks and Perceptron Learning Algorithm.pptx
Kayalvizhi A
 
PPTX
drones for disaster prevention response.pptx
NawrasShatnawi1
 
PPTX
Innowell Capability B0425 - Commercial Buildings.pptx
regobertroza
 
PPTX
Types of Bearing_Specifications_PPT.pptx
PranjulAgrahariAkash
 
PDF
IoT - Unit 2 (Internet of Things-Concepts) - PPT.pdf
dipakraut82
 
PPTX
MobileComputingMANET2023 MobileComputingMANET2023.pptx
masterfake98765
 
PDF
BioSensors glucose monitoring, cholestrol
nabeehasahar1
 
PPTX
Presentation on Foundation Design for Civil Engineers.pptx
KamalKhan563106
 
PDF
PRIZ Academy - Change Flow Thinking Master Change with Confidence.pdf
PRIZ Guru
 
PPTX
MPMC_Module-2 xxxxxxxxxxxxxxxxxxxxx.pptx
ShivanshVaidya5
 
PPTX
The Role of Information Technology in Environmental Protectio....pptx
nallamillisriram
 
PPT
inherently safer design for engineering.ppt
DhavalShah616893
 
PDF
PORTFOLIO Golam Kibria Khan — architect with a passion for thoughtful design...
MasumKhan59
 
PPTX
Hashing Introduction , hash functions and techniques
sailajam21
 
PPTX
REINFORCEMENT AS CONSTRUCTION MATERIALS.pptx
mohaiminulhaquesami
 
PDF
Statistical Data Analysis Using SPSS Software
shrikrishna kesharwani
 
PPTX
Break Statement in Programming with 6 Real Examples
manojpoojary2004
 
265587293-NFPA 101 Life safety code-PPT-1.pptx
chandermwason
 
POWER PLANT ENGINEERING (R17A0326).pdf..
haneefachosa123
 
Introduction to Productivity and Quality
মোঃ ফুরকান উদ্দিন জুয়েল
 
Introduction to Neural Networks and Perceptron Learning Algorithm.pptx
Kayalvizhi A
 
drones for disaster prevention response.pptx
NawrasShatnawi1
 
Innowell Capability B0425 - Commercial Buildings.pptx
regobertroza
 
Types of Bearing_Specifications_PPT.pptx
PranjulAgrahariAkash
 
IoT - Unit 2 (Internet of Things-Concepts) - PPT.pdf
dipakraut82
 
MobileComputingMANET2023 MobileComputingMANET2023.pptx
masterfake98765
 
BioSensors glucose monitoring, cholestrol
nabeehasahar1
 
Presentation on Foundation Design for Civil Engineers.pptx
KamalKhan563106
 
PRIZ Academy - Change Flow Thinking Master Change with Confidence.pdf
PRIZ Guru
 
MPMC_Module-2 xxxxxxxxxxxxxxxxxxxxx.pptx
ShivanshVaidya5
 
The Role of Information Technology in Environmental Protectio....pptx
nallamillisriram
 
inherently safer design for engineering.ppt
DhavalShah616893
 
PORTFOLIO Golam Kibria Khan — architect with a passion for thoughtful design...
MasumKhan59
 
Hashing Introduction , hash functions and techniques
sailajam21
 
REINFORCEMENT AS CONSTRUCTION MATERIALS.pptx
mohaiminulhaquesami
 
Statistical Data Analysis Using SPSS Software
shrikrishna kesharwani
 
Break Statement in Programming with 6 Real Examples
manojpoojary2004
 
Ad

Module_2_ER_to_relational_mapping_algorithm.pptx

  • 1. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 7- 1
  • 2. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Mapping Conceptual Design into a Logical Design Relational Database Design using ER-to-Relational Mapping
  • 3. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe ER-to-Relational Mapping Algorithm  ER-to-Relational Mapping Algorithm  Step 1: Mapping of Regular Entity Types  Step 2: Mapping of Weak Entity Types  Step 3: Mapping of Binary 1:1 Relation Types  Step 4: Mapping of Binary 1:N Relationship Types.  Step 5: Mapping of Binary M:N Relationship Types.  Step 6: Mapping of Multivalued attributes.  Step 7: Mapping of N-ary Relationship Types.
  • 4. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 1: Mapping of Regular Entity Types.  For each regular (strong) entity type E in the ER schema, create a relation R that includes all the simple attributes of E.  Choose one of the key attributes of E as the primary key for R.  If the chosen key of E is composite, the set of simple attributes that form it will together form the primary key of R.  Example: We create the relations EMPLOYEE, DEPARTMENT, and PROJECT in the relational schema corresponding to the regular entities in the ER diagram.  SSN, DNUMBER, and PNUMBER are the primary keys for the relations EMPLOYEE, DEPARTMENT, and PROJECT as shown.
  • 5. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 7- 5 The ER conceptual schema diagram for the COMPANY database.
  • 6. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe FIGURE 7.2 Result of mapping the COMPANY ER schema into a relational schema.
  • 7. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 2: Mapping of Weak Entity Types  For each weak entity type W in the ER schema with owner entity type E, create a relation R & include all simple attributes (or simple components of composite attributes) of W as attributes of R.  Also, include as foreign key attributes of R the primary key attribute(s) of the relation(s) that correspond to the owner entity type(s).  The primary key of R is the combination of the primary key(s) of the owner(s) and the partial key of the weak entity type W, if any.  Example: Create the relation DEPENDENT in this step to correspond to the weak entity type DEPENDENT.  Include the primary key SSN of the EMPLOYEE relation as a foreign key attribute of DEPENDENT (renamed to ESSN).  The primary key of the DEPENDENT relation is the combination {ESSN, DEPENDENT_NAME} because DEPENDENT_NAME is the partial key of DEPENDENT.
  • 8. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 3: Mapping of Binary 1:1 Relation Types  For each binary 1:1 relationship type R in the ER schema, identify the relations S and T that correspond to the entity types participating in R.  There are three possible approaches: 1. Foreign Key approach: Choose one of the relations-say S-and include a foreign key in S the primary key of T. It is better to choose an entity type with total participation in R in the role of S.  Example: 1:1 relation MANAGES is mapped by choosing the participating entity type DEPARTMENT to serve in the role of S, because its participation in the MANAGES relationship type is total. 2. Merged relation option: An alternate mapping of a 1:1 relationship type is possible by merging the two entity types and the relationship into a single relation. This may be appropriate when both participations are total. 3. Cross-reference or relationship relation option: The third alternative is to set up a third relation R for the purpose of cross-referencing the primary keys of the two relations S and T representing the entity types.
  • 9. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 4: Mapping of Binary 1:N Relationship Types.  For each regular binary 1:N relationship type R, identify the relation S that represent the participating entity type at the N-side of the relationship type.  Include as foreign key in S the primary key of the relation T that represents the other entity type participating in R.  Include any simple attributes of the 1:N relation type as attributes of S.  Example: 1:N relationship types WORKS_FOR, CONTROLS, and SUPERVISION in the figure.  For WORKS_FOR we include the primary key DNUMBER of the DEPARTMENT relation as foreign key in the EMPLOYEE relation and call it DNO.
  • 10. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 5: Mapping of Binary M:N Relationship Types.  For each regular binary M:N relationship type R, create a new relation S to represent R.  Include as foreign key attributes in S the primary keys of the relations that represent the participating entity types; their combination will form the primary key of S.  Also include any simple attributes of the M:N relationship type (or simple components of composite attributes) as attributes of S.  Example: The M:N relationship type WORKS_ON from the ER diagram is mapped by creating a relation WORKS_ON in the relational database schema.  The primary keys of the PROJECT and EMPLOYEE relations are included as foreign keys in WORKS_ON and renamed PNO and ESSN, respectively.  Attribute HOURS in WORKS_ON represents the HOURS attribute of the relation type. The primary key of the WORKS_ON relation is the combination of the foreign key attributes {ESSN, PNO}.
  • 11. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 6: Mapping of Multivalued attributes.  For each multivalued attribute A, create a new relation R.  This relation R will include an attribute corresponding to A, plus the primary key attribute K-as a foreign key in R-of the relation that represents the entity type of relationship type that has A as an attribute.  The primary key of R is the combination of A and K. If the multivalued attribute is composite, we include its simple components.  Example: The relation DEPT_LOCATIONS is created.  The attribute DLOCATION represents the multivalued attribute LOCATIONS of DEPARTMENT, while DNUMBER-as foreign key- represents the primary key of the DEPARTMENT relation.  The primary key of R is the combination of {DNUMBER, DLOCATION}.
  • 12. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Step 7: Mapping of N-ary Relationship Types.  For each n-ary relationship type R, where n>2, create a new relationship S to represent R.  Include as foreign key attributes in S the primary keys of the relations that represent the participating entity types.  Also include any simple attributes of the n-ary relationship type (or simple components of composite attributes) as attributes of S.  Example: The relationship type SUPPY in the ER on the next slide.  This can be mapped to the relation SUPPLY shown in the relational schema, whose primary key is the combination of the three foreign keys {SNAME, PARTNO, PROJNAME}
  • 13. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe FIGURE 4.11 Ternary relationship types. (a) The SUPPLY relationship.
  • 14. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe FIGURE 7.3 Mapping the n-ary relationship type SUPPLY from Figure 4.11a.
  • 15. Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Summary of Mapping constructs and constraints Table 7.1 Correspondence between ER and Relational Models ER Model Relational Model Entity type “Entity” relation 1:1 or 1:N relationship type Foreign key (or “relationship” relation) M:N relationship type “Relationship” relation and two foreign keys n-ary relationship type “Relationship” relation and n foreign keys Simple attribute Attribute Composite attribute Set of simple component attributes Multivalued attribute Relation and foreign key Value set Domain Key attribute Primary (or secondary) key