SlideShare a Scribd company logo
1 of 39
+
Database Design:
Conceptual Model to
Logical Model (ER
diagrams to tables)
+
Database Design Process
IS 257 – Fall 2006
Conceptual
Model
Logical
Model
External
Model
Conceptual
requirements
Conceptual
requirements
Conceptual
requirements
Conceptual
requirements
Application 1
Application 1
Application 2 Application 3 Application 4
Application 2
Application 3
Application 4
External
Model
External
Model
External
Model
Internal
Model
+
Developing a Conceptual Model
 Overall view of the database that integrates all
the needed information discovered during the
requirements analysis.
 Elements of the Conceptual Model are
represented by diagrams, Entity-Relationship or
ER Diagrams, that show the meanings and
relationships of those elements independent of
any particular database systems or
implementation details.
 Can also be represented using other modeling
tools (such as UML)
+
Developing a Conceptual Model
 We looked at the bus transportation system
 We identified key scenarios
 Limited our scope
 Made our initial ER diagram
 Identified Entities
 Indicated relevant attributes
 Specified unique identifiers
 Worked out relationships between entities (& cardinality)
 Still to do:
 Still needs to be integrated
 May be full of flaws!
IS 257 – Fall 2006
+
Normalization of ER Diagram
(expand repeating attributes)
DiveOrds
Orders
DiveCust
Customer No ship
ShipVia
Order No
Ship Via
DiveItem
Repeating
attribute
Customer No
+
Normalization
DiveCust Orders
Customer No
DiveOrds
Ship
ShipVia
Order No
Ship Via
DiveItem
Contains
Item No
Qty
Order No
Customer No
Rental/sale
5/22/2023
Some ER
Diagram
Styles
5/22/2023
Crow's Feet Notation is as follows:
Cardinality: maximum (1 or many)
Modality: minimum (0 or 1)
+
Notation used in the following slides
 http://www.philblock.info/hitkb/i/interpreting_entity-
relationship_diagrams.html
5/22/2023
+ Chapter 7
Logical
Database
Design
Fundamentals of Database
Management Systems
by
Mark L. Gillenson, Ph.D.
University of Memphis
John Wiley & Sons, Inc.
+ 7-11
Chapter Objectives
 Describe the concept of logical database design.
 Design relational databases by converting entity-relationship
diagrams into relational tables.
 Describe the data normalization process.
+ 7-12
Chapter Objectives
 Perform the data normalization process.
 Test tables for irregularities using the data normalization
process.
+ 7-13
Logical Database Design
 The process of deciding how to arrange the attributes of the
entities in the business environment into database structures,
such as the tables of a relational database.
 The goal is to create well structured tables that properly reflect
the company’s business environment.
+ 7-14
Logical Design of Relational
Database Systems
 (1) The conversion of E-R diagrams into relational tables.
 (2) The data normalization technique.
 (3) The use of the data normalization technique to test the
tables resulting from the E-R diagram conversions.
+ 7-15
Converting E-R Diagrams into
Relational Tables
 Each entity will convert to a table.
 Each many-to-many relationship or associative entity will
convert to a table.
 During the conversion, certain rules must be followed to ensure
that foreign keys appear in their proper places in the tables.
7-16
Converting a Simple Entity
 The table simply contains the attributes that were specified in
the entity box.
 Salesperson Number is underlined to indicate that it is the
unique identifier of the entity and the primary key of the table.
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
SALESPERSON
7-17
Converting Entities in Binary
Relationships: One-to-One
There are three options for designing tables to
represent this data.
7-18
One-to-One: Option #1
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year
of
Hire
Office
Number Telephone Size
SALESPERSON/OFFICE
The two entities are
combined into one
relational table.
7-19
One-to-One: Option #2
 Separate tables for the
SALESPERSON and
OFFICE entities, with
Office Number as a
foreign key in the
SALESPERSON table.
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year of
Hire
Office
Number
SALESPERSON
Office
Number Telephone Size
OFFICE
7-20
One-to-One: Option #3
 Separate tables for the
SALESPERSON and
OFFICE entities, with
Salesperson Number as a
foreign key in the OFFICE
table.
Salesperson
Number
Salesperson
Name
Commission
Percentage
Year of
Hire
SALESPERSON
Office
Number Telephone
Salesperson
Number Size
OFFICE
7-21
Converting Entities in Binary
Relationships: One-to-Many
 The unique identifier of the entity on the “one side” of the
one-to-many relationship is placed as a foreign key in the table
representing the entity on the “many side.”
 So, the Salesperson Number attribute is placed in the
CUSTOMER table as a foreign key.
7-22
Converting Entities in Binary
Relationships: One-to-Many
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
SALESPERSON
Customer
Number
Customer
Name HQ City
Salesperson
Number
CUSTOMER
7-23
Converting Entities in Binary
Relationships: Many-to-Many
E-R diagram with the many-to-many binary
relationship and the equivalent diagram using an
associative entity.
+ 7-24
Converting Entities in Binary
Relationships: Many-to-Many
 An E-R diagram with two entities in a many-to-many
relationship converts to three relational tables.
 Each of the two entities converts to a table with its
own attributes but with no foreign keys (regarding
this relationship).
 In addition, there must be a third “many-to-many”
table for the many-to-many relationship.
7-25
Converting Entities in Binary
Relationships: Many-to-Many
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
SALESPERSON
Product
Number
Product
Name Unit Price
PRODUCT
Salesperson
Number
Product
Number Quantity
SALE
 The primary key of SALE
is the combination of the
unique identifiers of the
two entities in the many-
to-many relationship.
Additional attributes are
the intersection data.
Product
Number
Product
Name Unit Price
PRODUCT
7-26
Converting Entities in Unary
Relationships: One-to-One
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
Backup
Number
SALESPERSON
 With only one entity type
involved and with a one-to-
one relationship, the
conversion requires only one
table.
7-27
Converting Entities in Unary
Relationships: One-to-Many
Very similar to the one-
to-one unary case.
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire Manager
SALESPERSON
7-28
Converting Entities in Unary
Relationships: Many-to-Many
Product
Number
Product
Name Unit Price
PRODUCT
This relationship requires two tables in the
conversion.
The PRODUCT table has no foreign keys.
Product
Number
Sub-Assembly
Number Quantity
COMPONENT
7-29
Converting Entities in Unary
Relationships: Many-to-Many
Product
Number
Product
Name Unit Price
PRODUCT
 A second table is created since in the conversion of a
many-to-many relationship of any degree — unary,
binary, or ternary — the number of tables will be equal to
the number of entity types (one, two, or three,
respectively) plus one more table for the many-to-many
relationship.
Product
Number
Sub-Assembly
Number Quantity
COMPONENT
7-30
Converting Entities in
Ternary Relationships
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
SALESPERSON
 The primary key of the SALE
table is the combination of the
unique identifiers of the three
entities involved, plus the Date
attribute.
Customer
Number
Customer
Name HQ City
CUSTOMER
Product
Number
Product
Name Unit Price
PRODUCT
Salesperson
Number
Customer
Number
Product
Number Date Quantity
SALE
7-31
Designing the
General Hardware
Company Database
7-32
Designing the General Hardware
Company Database
Salesperson
Number
Salesperson
Name
Commission
Percentage Year of Hire
Office
Number
SALESPERSON
Customer
Number
Customer
Name
Salesperson
Number HQ City
CUSTOMER
Customer
Number
Employee
Number
Employee
Name Title
CUSTOMER EMPLOYEE
Product
Number
Product
Name Unit Price
PRODUCT
Salesperson
Number
Product
Number Quantity
SALES
Office
Number Telephone Size
OFFICE
7-33
Designing the Good Reading
Bookstores Database
7-34
Designing the Good Reading
Bookstores Database
Publisher
Name City Country Telephone
Year
Founded
PUBLISHER
Author
Number
Author
Name
Year
Born
Year
Died
AUTHOR
Book
Number
Book
Name
Publication
Year Pages
Publisher
Name
BOOK
Customer
Number
Customer
Name Street City State Country
CUSTOMER
Book
Number
Author
Number
WRITING
Book
Number
Customer
Number Date Price Quantity
SALE
7-35
Designing the World Music Association
Database
7-36
Designing the World Music Association
Database
Orchestra
Name City Country
Music
Director
ORCHESTRA
Musician
Number
Musician
Name Instrument
Annual
Salary
Orchestra
Name
MUSICIAN
Musician
Number Degree University Year
DEGREE
Composer
Name Country
Date Of
Birth
COMPOSER
Composition
Name
Composer
Name Year
COMPOSITION
Orchestra
Name
Composition
Name
Composer
Name Year Price
RECORDING
7-37
Designing the
Lucky
Rent-A-Car
Database
7-38
Designing the Lucky
Rent-A-Car Database
Manufacturer
Name
Manufacturer
Country
Sales Rep
Name
Sales Rep
Telephone
MANUFACTURER
Car Serial
Number Model Year Class
Manufacturer
Name
CAR
Repair
Number
Car Serial
Number Date Procedure Mileage
Repair
Time
MAINTENANCE
Customer
Number
Customer
Name
Customer
Address
Customer
Telephone
CUSTOMER
Car Serial
Number
Customer
Number
Rental
Date
Return
Date
Total
Cost
RENTAL
+ 7-39
Next up: The Data Normalization
Process
 A methodology for organizing attributes into tables so that
redundancy among the nonkey attributes is eliminated.
 The output of the data normalization process is a properly
structured relational database.

More Related Content

Similar to ER Diagrams to Relational Tables: Conceptual to Logical Database Design

2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx
2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx
2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptxBigBoss599305
 
Kevin Fahy Bi Portfolio
Kevin Fahy   Bi PortfolioKevin Fahy   Bi Portfolio
Kevin Fahy Bi PortfolioKevinPFahy
 
Preparing for BIT – IT2301 Database Management Systems 2001d
Preparing for BIT – IT2301 Database Management Systems 2001dPreparing for BIT – IT2301 Database Management Systems 2001d
Preparing for BIT – IT2301 Database Management Systems 2001dGihan Wikramanayake
 
William Canning Portfolio Annotated
William Canning Portfolio AnnotatedWilliam Canning Portfolio Annotated
William Canning Portfolio Annotatedcanningw
 
SSIS_SSRS_PPS_SP_SSAS_Hong_Bing Li
SSIS_SSRS_PPS_SP_SSAS_Hong_Bing LiSSIS_SSRS_PPS_SP_SSAS_Hong_Bing Li
SSIS_SSRS_PPS_SP_SSAS_Hong_Bing LiHong-Bing Li
 
Ch 6 Logical D B Design
Ch 6  Logical D B  DesignCh 6  Logical D B  Design
Ch 6 Logical D B Designguest8fdbdd
 
SSIS_SSAS_SSRS_SP_PPS_HongBingLi
SSIS_SSAS_SSRS_SP_PPS_HongBingLiSSIS_SSAS_SSRS_SP_PPS_HongBingLi
SSIS_SSAS_SSRS_SP_PPS_HongBingLiHong-Bing Li
 
Ssis Ssas Ssrs Sp Pps Hong Bing Li
Ssis Ssas Ssrs Sp Pps Hong Bing LiSsis Ssas Ssrs Sp Pps Hong Bing Li
Ssis Ssas Ssrs Sp Pps Hong Bing LiHong-Bing Li
 
Fundamentals of BI Report Testing - Module 10
Fundamentals of BI Report Testing - Module 10Fundamentals of BI Report Testing - Module 10
Fundamentals of BI Report Testing - Module 10MichaelCalabrese20
 
Ais Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The ReaAis Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The ReaSharing Slides Training
 
Ais Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The ReaAis Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The Reasharing notes123
 
X rec extened reconciliation using excel vba
X rec   extened reconciliation using excel vbaX rec   extened reconciliation using excel vba
X rec extened reconciliation using excel vbasenthilsundaresan
 
Project Portfolio
Project PortfolioProject Portfolio
Project PortfolioArthur Chan
 
Tony Von Gusmann & MS BI
Tony Von Gusmann & MS BITony Von Gusmann & MS BI
Tony Von Gusmann & MS BIvongusmann
 
Colin\'s BI Portfolio
Colin\'s BI PortfolioColin\'s BI Portfolio
Colin\'s BI Portfoliocolinsobers
 

Similar to ER Diagrams to Relational Tables: Conceptual to Logical Database Design (20)

2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx
2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx
2020.11.10 SISTEM BASIS DATA PERTEMUAN 12 - Normalization_new.pptx
 
Kevin Fahy Bi Portfolio
Kevin Fahy   Bi PortfolioKevin Fahy   Bi Portfolio
Kevin Fahy Bi Portfolio
 
Preparing for BIT – IT2301 Database Management Systems 2001d
Preparing for BIT – IT2301 Database Management Systems 2001dPreparing for BIT – IT2301 Database Management Systems 2001d
Preparing for BIT – IT2301 Database Management Systems 2001d
 
William Canning Portfolio Annotated
William Canning Portfolio AnnotatedWilliam Canning Portfolio Annotated
William Canning Portfolio Annotated
 
Kul 2
Kul 2Kul 2
Kul 2
 
ER to Relational Mapping
ER to Relational MappingER to Relational Mapping
ER to Relational Mapping
 
SSIS_SSRS_PPS_SP_SSAS_Hong_Bing Li
SSIS_SSRS_PPS_SP_SSAS_Hong_Bing LiSSIS_SSRS_PPS_SP_SSAS_Hong_Bing Li
SSIS_SSRS_PPS_SP_SSAS_Hong_Bing Li
 
Ch 6 Logical D B Design
Ch 6  Logical D B  DesignCh 6  Logical D B  Design
Ch 6 Logical D B Design
 
SSIS_SSAS_SSRS_SP_PPS_HongBingLi
SSIS_SSAS_SSRS_SP_PPS_HongBingLiSSIS_SSAS_SSRS_SP_PPS_HongBingLi
SSIS_SSAS_SSRS_SP_PPS_HongBingLi
 
Ssis Ssas Ssrs Sp Pps Hong Bing Li
Ssis Ssas Ssrs Sp Pps Hong Bing LiSsis Ssas Ssrs Sp Pps Hong Bing Li
Ssis Ssas Ssrs Sp Pps Hong Bing Li
 
Dimensional modeling
Dimensional modelingDimensional modeling
Dimensional modeling
 
Fundamentals of BI Report Testing - Module 10
Fundamentals of BI Report Testing - Module 10Fundamentals of BI Report Testing - Module 10
Fundamentals of BI Report Testing - Module 10
 
Ais Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The ReaAis Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The Rea
 
Ais Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The ReaAis Romney 2006 Slides 15 Database Design Using The Rea
Ais Romney 2006 Slides 15 Database Design Using The Rea
 
DBMS - ER Model
DBMS - ER ModelDBMS - ER Model
DBMS - ER Model
 
X rec extened reconciliation using excel vba
X rec   extened reconciliation using excel vbaX rec   extened reconciliation using excel vba
X rec extened reconciliation using excel vba
 
Project Portfolio
Project PortfolioProject Portfolio
Project Portfolio
 
Tony Von Gusmann & MS BI
Tony Von Gusmann & MS BITony Von Gusmann & MS BI
Tony Von Gusmann & MS BI
 
PHP/MySQL Programming Class Lecture 03
PHP/MySQL Programming Class Lecture 03PHP/MySQL Programming Class Lecture 03
PHP/MySQL Programming Class Lecture 03
 
Colin\'s BI Portfolio
Colin\'s BI PortfolioColin\'s BI Portfolio
Colin\'s BI Portfolio
 

Recently uploaded

Organic Name Reactions for the students and aspirants of Chemistry12th.pptx
Organic Name Reactions  for the students and aspirants of Chemistry12th.pptxOrganic Name Reactions  for the students and aspirants of Chemistry12th.pptx
Organic Name Reactions for the students and aspirants of Chemistry12th.pptxVS Mahajan Coaching Centre
 
Crayon Activity Handout For the Crayon A
Crayon Activity Handout For the Crayon ACrayon Activity Handout For the Crayon A
Crayon Activity Handout For the Crayon AUnboundStockton
 
How to Make a Pirate ship Primary Education.pptx
How to Make a Pirate ship Primary Education.pptxHow to Make a Pirate ship Primary Education.pptx
How to Make a Pirate ship Primary Education.pptxmanuelaromero2013
 
Presiding Officer Training module 2024 lok sabha elections
Presiding Officer Training module 2024 lok sabha electionsPresiding Officer Training module 2024 lok sabha elections
Presiding Officer Training module 2024 lok sabha electionsanshu789521
 
mini mental status format.docx
mini    mental       status     format.docxmini    mental       status     format.docx
mini mental status format.docxPoojaSen20
 
Paris 2024 Olympic Geographies - an activity
Paris 2024 Olympic Geographies - an activityParis 2024 Olympic Geographies - an activity
Paris 2024 Olympic Geographies - an activityGeoBlogs
 
18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf
18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf
18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdfssuser54595a
 
A Critique of the Proposed National Education Policy Reform
A Critique of the Proposed National Education Policy ReformA Critique of the Proposed National Education Policy Reform
A Critique of the Proposed National Education Policy ReformChameera Dedduwage
 
The Most Excellent Way | 1 Corinthians 13
The Most Excellent Way | 1 Corinthians 13The Most Excellent Way | 1 Corinthians 13
The Most Excellent Way | 1 Corinthians 13Steve Thomason
 
Contemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptx
Contemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptxContemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptx
Contemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptxRoyAbrique
 
Accessible design: Minimum effort, maximum impact
Accessible design: Minimum effort, maximum impactAccessible design: Minimum effort, maximum impact
Accessible design: Minimum effort, maximum impactdawncurless
 
Mastering the Unannounced Regulatory Inspection
Mastering the Unannounced Regulatory InspectionMastering the Unannounced Regulatory Inspection
Mastering the Unannounced Regulatory InspectionSafetyChain Software
 
PSYCHIATRIC History collection FORMAT.pptx
PSYCHIATRIC   History collection FORMAT.pptxPSYCHIATRIC   History collection FORMAT.pptx
PSYCHIATRIC History collection FORMAT.pptxPoojaSen20
 
Grant Readiness 101 TechSoup and Remy Consulting
Grant Readiness 101 TechSoup and Remy ConsultingGrant Readiness 101 TechSoup and Remy Consulting
Grant Readiness 101 TechSoup and Remy ConsultingTechSoup
 
Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991
Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991
Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991RKavithamani
 
Incoming and Outgoing Shipments in 1 STEP Using Odoo 17
Incoming and Outgoing Shipments in 1 STEP Using Odoo 17Incoming and Outgoing Shipments in 1 STEP Using Odoo 17
Incoming and Outgoing Shipments in 1 STEP Using Odoo 17Celine George
 

Recently uploaded (20)

Organic Name Reactions for the students and aspirants of Chemistry12th.pptx
Organic Name Reactions  for the students and aspirants of Chemistry12th.pptxOrganic Name Reactions  for the students and aspirants of Chemistry12th.pptx
Organic Name Reactions for the students and aspirants of Chemistry12th.pptx
 
Crayon Activity Handout For the Crayon A
Crayon Activity Handout For the Crayon ACrayon Activity Handout For the Crayon A
Crayon Activity Handout For the Crayon A
 
How to Make a Pirate ship Primary Education.pptx
How to Make a Pirate ship Primary Education.pptxHow to Make a Pirate ship Primary Education.pptx
How to Make a Pirate ship Primary Education.pptx
 
Presiding Officer Training module 2024 lok sabha elections
Presiding Officer Training module 2024 lok sabha electionsPresiding Officer Training module 2024 lok sabha elections
Presiding Officer Training module 2024 lok sabha elections
 
mini mental status format.docx
mini    mental       status     format.docxmini    mental       status     format.docx
mini mental status format.docx
 
Paris 2024 Olympic Geographies - an activity
Paris 2024 Olympic Geographies - an activityParis 2024 Olympic Geographies - an activity
Paris 2024 Olympic Geographies - an activity
 
Código Creativo y Arte de Software | Unidad 1
Código Creativo y Arte de Software | Unidad 1Código Creativo y Arte de Software | Unidad 1
Código Creativo y Arte de Software | Unidad 1
 
18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf
18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf
18-04-UA_REPORT_MEDIALITERAСY_INDEX-DM_23-1-final-eng.pdf
 
A Critique of the Proposed National Education Policy Reform
A Critique of the Proposed National Education Policy ReformA Critique of the Proposed National Education Policy Reform
A Critique of the Proposed National Education Policy Reform
 
TataKelola dan KamSiber Kecerdasan Buatan v022.pdf
TataKelola dan KamSiber Kecerdasan Buatan v022.pdfTataKelola dan KamSiber Kecerdasan Buatan v022.pdf
TataKelola dan KamSiber Kecerdasan Buatan v022.pdf
 
Model Call Girl in Bikash Puri Delhi reach out to us at 🔝9953056974🔝
Model Call Girl in Bikash Puri  Delhi reach out to us at 🔝9953056974🔝Model Call Girl in Bikash Puri  Delhi reach out to us at 🔝9953056974🔝
Model Call Girl in Bikash Puri Delhi reach out to us at 🔝9953056974🔝
 
The Most Excellent Way | 1 Corinthians 13
The Most Excellent Way | 1 Corinthians 13The Most Excellent Way | 1 Corinthians 13
The Most Excellent Way | 1 Corinthians 13
 
Contemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptx
Contemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptxContemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptx
Contemporary philippine arts from the regions_PPT_Module_12 [Autosaved] (1).pptx
 
Accessible design: Minimum effort, maximum impact
Accessible design: Minimum effort, maximum impactAccessible design: Minimum effort, maximum impact
Accessible design: Minimum effort, maximum impact
 
Mastering the Unannounced Regulatory Inspection
Mastering the Unannounced Regulatory InspectionMastering the Unannounced Regulatory Inspection
Mastering the Unannounced Regulatory Inspection
 
PSYCHIATRIC History collection FORMAT.pptx
PSYCHIATRIC   History collection FORMAT.pptxPSYCHIATRIC   History collection FORMAT.pptx
PSYCHIATRIC History collection FORMAT.pptx
 
Grant Readiness 101 TechSoup and Remy Consulting
Grant Readiness 101 TechSoup and Remy ConsultingGrant Readiness 101 TechSoup and Remy Consulting
Grant Readiness 101 TechSoup and Remy Consulting
 
Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991
Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991
Industrial Policy - 1948, 1956, 1973, 1977, 1980, 1991
 
Model Call Girl in Tilak Nagar Delhi reach out to us at 🔝9953056974🔝
Model Call Girl in Tilak Nagar Delhi reach out to us at 🔝9953056974🔝Model Call Girl in Tilak Nagar Delhi reach out to us at 🔝9953056974🔝
Model Call Girl in Tilak Nagar Delhi reach out to us at 🔝9953056974🔝
 
Incoming and Outgoing Shipments in 1 STEP Using Odoo 17
Incoming and Outgoing Shipments in 1 STEP Using Odoo 17Incoming and Outgoing Shipments in 1 STEP Using Odoo 17
Incoming and Outgoing Shipments in 1 STEP Using Odoo 17
 

ER Diagrams to Relational Tables: Conceptual to Logical Database Design

  • 1. + Database Design: Conceptual Model to Logical Model (ER diagrams to tables)
  • 2. + Database Design Process IS 257 – Fall 2006 Conceptual Model Logical Model External Model Conceptual requirements Conceptual requirements Conceptual requirements Conceptual requirements Application 1 Application 1 Application 2 Application 3 Application 4 Application 2 Application 3 Application 4 External Model External Model External Model Internal Model
  • 3. + Developing a Conceptual Model  Overall view of the database that integrates all the needed information discovered during the requirements analysis.  Elements of the Conceptual Model are represented by diagrams, Entity-Relationship or ER Diagrams, that show the meanings and relationships of those elements independent of any particular database systems or implementation details.  Can also be represented using other modeling tools (such as UML)
  • 4. + Developing a Conceptual Model  We looked at the bus transportation system  We identified key scenarios  Limited our scope  Made our initial ER diagram  Identified Entities  Indicated relevant attributes  Specified unique identifiers  Worked out relationships between entities (& cardinality)  Still to do:  Still needs to be integrated  May be full of flaws! IS 257 – Fall 2006
  • 5. + Normalization of ER Diagram (expand repeating attributes) DiveOrds Orders DiveCust Customer No ship ShipVia Order No Ship Via DiveItem Repeating attribute Customer No
  • 6. + Normalization DiveCust Orders Customer No DiveOrds Ship ShipVia Order No Ship Via DiveItem Contains Item No Qty Order No Customer No Rental/sale
  • 8. 5/22/2023 Crow's Feet Notation is as follows: Cardinality: maximum (1 or many) Modality: minimum (0 or 1)
  • 9. + Notation used in the following slides  http://www.philblock.info/hitkb/i/interpreting_entity- relationship_diagrams.html 5/22/2023
  • 10. + Chapter 7 Logical Database Design Fundamentals of Database Management Systems by Mark L. Gillenson, Ph.D. University of Memphis John Wiley & Sons, Inc.
  • 11. + 7-11 Chapter Objectives  Describe the concept of logical database design.  Design relational databases by converting entity-relationship diagrams into relational tables.  Describe the data normalization process.
  • 12. + 7-12 Chapter Objectives  Perform the data normalization process.  Test tables for irregularities using the data normalization process.
  • 13. + 7-13 Logical Database Design  The process of deciding how to arrange the attributes of the entities in the business environment into database structures, such as the tables of a relational database.  The goal is to create well structured tables that properly reflect the company’s business environment.
  • 14. + 7-14 Logical Design of Relational Database Systems  (1) The conversion of E-R diagrams into relational tables.  (2) The data normalization technique.  (3) The use of the data normalization technique to test the tables resulting from the E-R diagram conversions.
  • 15. + 7-15 Converting E-R Diagrams into Relational Tables  Each entity will convert to a table.  Each many-to-many relationship or associative entity will convert to a table.  During the conversion, certain rules must be followed to ensure that foreign keys appear in their proper places in the tables.
  • 16. 7-16 Converting a Simple Entity  The table simply contains the attributes that were specified in the entity box.  Salesperson Number is underlined to indicate that it is the unique identifier of the entity and the primary key of the table. Salesperson Number Salesperson Name Commission Percentage Year of Hire SALESPERSON
  • 17. 7-17 Converting Entities in Binary Relationships: One-to-One There are three options for designing tables to represent this data.
  • 18. 7-18 One-to-One: Option #1 Salesperson Number Salesperson Name Commission Percentage Year of Hire Office Number Telephone Size SALESPERSON/OFFICE The two entities are combined into one relational table.
  • 19. 7-19 One-to-One: Option #2  Separate tables for the SALESPERSON and OFFICE entities, with Office Number as a foreign key in the SALESPERSON table. Salesperson Number Salesperson Name Commission Percentage Year of Hire Office Number SALESPERSON Office Number Telephone Size OFFICE
  • 20. 7-20 One-to-One: Option #3  Separate tables for the SALESPERSON and OFFICE entities, with Salesperson Number as a foreign key in the OFFICE table. Salesperson Number Salesperson Name Commission Percentage Year of Hire SALESPERSON Office Number Telephone Salesperson Number Size OFFICE
  • 21. 7-21 Converting Entities in Binary Relationships: One-to-Many  The unique identifier of the entity on the “one side” of the one-to-many relationship is placed as a foreign key in the table representing the entity on the “many side.”  So, the Salesperson Number attribute is placed in the CUSTOMER table as a foreign key.
  • 22. 7-22 Converting Entities in Binary Relationships: One-to-Many Salesperson Number Salesperson Name Commission Percentage Year of Hire SALESPERSON Customer Number Customer Name HQ City Salesperson Number CUSTOMER
  • 23. 7-23 Converting Entities in Binary Relationships: Many-to-Many E-R diagram with the many-to-many binary relationship and the equivalent diagram using an associative entity.
  • 24. + 7-24 Converting Entities in Binary Relationships: Many-to-Many  An E-R diagram with two entities in a many-to-many relationship converts to three relational tables.  Each of the two entities converts to a table with its own attributes but with no foreign keys (regarding this relationship).  In addition, there must be a third “many-to-many” table for the many-to-many relationship.
  • 25. 7-25 Converting Entities in Binary Relationships: Many-to-Many Salesperson Number Salesperson Name Commission Percentage Year of Hire SALESPERSON Product Number Product Name Unit Price PRODUCT Salesperson Number Product Number Quantity SALE  The primary key of SALE is the combination of the unique identifiers of the two entities in the many- to-many relationship. Additional attributes are the intersection data. Product Number Product Name Unit Price PRODUCT
  • 26. 7-26 Converting Entities in Unary Relationships: One-to-One Salesperson Number Salesperson Name Commission Percentage Year of Hire Backup Number SALESPERSON  With only one entity type involved and with a one-to- one relationship, the conversion requires only one table.
  • 27. 7-27 Converting Entities in Unary Relationships: One-to-Many Very similar to the one- to-one unary case. Salesperson Number Salesperson Name Commission Percentage Year of Hire Manager SALESPERSON
  • 28. 7-28 Converting Entities in Unary Relationships: Many-to-Many Product Number Product Name Unit Price PRODUCT This relationship requires two tables in the conversion. The PRODUCT table has no foreign keys. Product Number Sub-Assembly Number Quantity COMPONENT
  • 29. 7-29 Converting Entities in Unary Relationships: Many-to-Many Product Number Product Name Unit Price PRODUCT  A second table is created since in the conversion of a many-to-many relationship of any degree — unary, binary, or ternary — the number of tables will be equal to the number of entity types (one, two, or three, respectively) plus one more table for the many-to-many relationship. Product Number Sub-Assembly Number Quantity COMPONENT
  • 30. 7-30 Converting Entities in Ternary Relationships Salesperson Number Salesperson Name Commission Percentage Year of Hire SALESPERSON  The primary key of the SALE table is the combination of the unique identifiers of the three entities involved, plus the Date attribute. Customer Number Customer Name HQ City CUSTOMER Product Number Product Name Unit Price PRODUCT Salesperson Number Customer Number Product Number Date Quantity SALE
  • 32. 7-32 Designing the General Hardware Company Database Salesperson Number Salesperson Name Commission Percentage Year of Hire Office Number SALESPERSON Customer Number Customer Name Salesperson Number HQ City CUSTOMER Customer Number Employee Number Employee Name Title CUSTOMER EMPLOYEE Product Number Product Name Unit Price PRODUCT Salesperson Number Product Number Quantity SALES Office Number Telephone Size OFFICE
  • 33. 7-33 Designing the Good Reading Bookstores Database
  • 34. 7-34 Designing the Good Reading Bookstores Database Publisher Name City Country Telephone Year Founded PUBLISHER Author Number Author Name Year Born Year Died AUTHOR Book Number Book Name Publication Year Pages Publisher Name BOOK Customer Number Customer Name Street City State Country CUSTOMER Book Number Author Number WRITING Book Number Customer Number Date Price Quantity SALE
  • 35. 7-35 Designing the World Music Association Database
  • 36. 7-36 Designing the World Music Association Database Orchestra Name City Country Music Director ORCHESTRA Musician Number Musician Name Instrument Annual Salary Orchestra Name MUSICIAN Musician Number Degree University Year DEGREE Composer Name Country Date Of Birth COMPOSER Composition Name Composer Name Year COMPOSITION Orchestra Name Composition Name Composer Name Year Price RECORDING
  • 38. 7-38 Designing the Lucky Rent-A-Car Database Manufacturer Name Manufacturer Country Sales Rep Name Sales Rep Telephone MANUFACTURER Car Serial Number Model Year Class Manufacturer Name CAR Repair Number Car Serial Number Date Procedure Mileage Repair Time MAINTENANCE Customer Number Customer Name Customer Address Customer Telephone CUSTOMER Car Serial Number Customer Number Rental Date Return Date Total Cost RENTAL
  • 39. + 7-39 Next up: The Data Normalization Process  A methodology for organizing attributes into tables so that redundancy among the nonkey attributes is eliminated.  The output of the data normalization process is a properly structured relational database.