Database Systems: Design, Implementation, and Management Ninth Edition

/ 50 []
Download Presentation
(1110) |   (0) |   (0)
Views: 500 | Added:
Rate Presentation: 1 0
Database Systems: Design, Implementation, and Management Ninth Edition. Chapter 4 Entity Relationship (ER) Modeling. Objectives. In this chapter, students will learn: The main characteristics of entity relationship components
Database Systems: Design, Implementation, and Management Ninth Edition

An Image/Link below is provided (as is) to

Download Policy: Content on the Website is provided to you AS IS for your information and personal use only and may not be sold or licensed nor shared on other sites. SlideServe reserves the right to change this policy at anytime. While downloading, If for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Database systems design implementation and management ninth edition l.jpgSlide 1

Database Systems: Design, Implementation, and ManagementNinth Edition

Chapter 4

Entity Relationship (ER) Modeling

Objectives l.jpgSlide 2


  • In this chapter, students will learn:

    • The main characteristics of entity relationship components

    • How relationships between entities are defined, refined, and incorporated into the database design process

    • How ERD components affect database design and implementation

    • That real-world database design often requires the reconciliation of conflicting goals

Database Systems, 9th Edition

The entity relationship model erm l.jpgSlide 3

The Entity Relationship Model (ERM)

  • ER model forms the basis of an ER diagram

  • ERD represents conceptual database as viewed by end user

  • ERDs depict database’s main components:

    • Entities

    • Attributes

    • Relationships

Database Systems, 9th Edition

Entities l.jpgSlide 4


  • Refers to entity set and not to single entity occurrence

  • Corresponds to table and not to row in relational environment

  • In Chen and Crow’s Foot models, entity is represented by rectangle with entity’s name

  • Entity name, a noun, written in capital letters

Database Systems, 9th Edition

Attributes l.jpgSlide 5


  • Characteristics of entities

  • Chen notation: attributes represented by ovals connected to entity rectangle with a line

    • Each oval contains the name of attribute it represents

  • Crow’s Foot notation: attributes written in attribute box below entity rectangle

Database Systems, 9th Edition

Slide6 l.jpgSlide 6

Database Systems, 9th Edition

Attributes cont d l.jpgSlide 7

Attributes (cont’d.)

  • Required attribute: must have a value

  • Optional attribute: may be left empty

  • Domain: set of possible values for an attribute

    • Attributes may share a domain

  • Identifiers: one or more attributes that uniquely identify each entity instance

  • Compositeidentifier: primary key composed of more than one attribute

Database Systems, 9th Edition

Slide8 l.jpgSlide 8

Database Systems, 9th Edition

Attributes cont d9 l.jpgSlide 9

Attributes (cont’d.)

  • Composite attribute can be subdivided

  • Simple attribute cannot be subdivided

  • Single-value attribute can have only a single value

  • Multivalued attributes can have many values

Database Systems, 9th Edition

Slide10 l.jpgSlide 10

Database Systems, 9th Edition

Attributes cont d11 l.jpgSlide 11

Attributes (cont’d.)

  • M:N relationships and multivalued attributes should not be implemented

    • Create several new attributes for each of the original multivalued attributes’ components

    • Create new entity composed of original multivalued attributes’ components

  • Derivedattribute: value may be calculated from other attributes

    • Need not be physically stored within database

Database Systems, 9th Edition

Slide12 l.jpgSlide 12

Database Systems, 9th Edition

Relationships l.jpgSlide 13


  • Association between entities

  • Participants are entities that participate in a relationship

  • Relationships between entities always operate in both directions

  • Relationship can be classified as 1:M

  • Relationship classification is difficult to establish if only one side of the relationship is known

Database Systems, 9th Edition

Connectivity and cardinality l.jpgSlide 14

Connectivity and Cardinality

  • Connectivity

    • Describes the relationship classification

  • Cardinality

    • Expresses minimum and maximum number of entity occurrences associated with one occurrence of related entity

  • Established by very concise statements known as business rules

Database Systems, 9th Edition

Slide15 l.jpgSlide 15

Database Systems, 9th Edition

Existence dependence l.jpgSlide 16

Existence Dependence

  • Existencedependence

    • Entity exists in database only when it is associated with another related entity occurrence

  • Existenceindependence

    • Entity can exist apart from one or more related entities

    • Sometimes such an entity is referred to as a strong or regular entity

Database Systems, 9th Edition

Relationship strength l.jpgSlide 17

Relationship Strength

  • Weak (non-identifying) relationships

    • Exists if PK of related entity does not contain PK component of parent entity

  • Strong (identifying) relationships

    • Exists when PK of related entity contains PK component of parent entity

Database Systems, 9th Edition

Slide18 l.jpgSlide 18

Database Systems, 9th Edition

Slide19 l.jpgSlide 19

Database Systems, 9th Edition

Weak entities l.jpgSlide 20

Weak Entities

  • Weakentity meets two conditions

    • Existence-dependent

    • Primary key partially or totally derived from parent entity in relationship

  • Database designer determines whether an entity is weak based on business rules

Database Systems, 9th Edition

Slide21 l.jpgSlide 21

Database Systems, 9th Edition

Slide22 l.jpgSlide 22

Database Systems, 9th Edition

Relationship participation l.jpgSlide 23

Relationship Participation

  • Optionalparticipation

    • One entity occurrence does not require corresponding entity occurrence in particular relationship

  • Mandatoryparticipation

    • One entity occurrence requires corresponding entity occurrence in particular relationship

Database Systems, 9th Edition

Slide24 l.jpgSlide 24

Database Systems, 9th Edition

Slide25 l.jpgSlide 25

Database Systems, 9th Edition

Relationship degree l.jpgSlide 26

Relationship Degree

  • Indicates number of entities or participants associated with a relationship

  • Unaryrelationship

    • Association is maintained within single entity

  • Binaryrelationship

    • Two entities are associated

  • Ternaryrelationship

    • Three entities are associated

Database Systems, 9th Edition

Slide27 l.jpgSlide 27

Database Systems, 9th Edition

Slide28 l.jpgSlide 28

Database Systems, 9th Edition

Recursive relationships l.jpgSlide 29

Recursive Relationships

  • Relationship can exist between occurrences of the same entity set

    • Naturally found within unary relationship

Database Systems, 9th Edition

Slide30 l.jpgSlide 30

Database Systems, 9th Edition

Slide31 l.jpgSlide 31

Database Systems, 9th Edition

Associative composite entities l.jpgSlide 32

Associative (Composite) Entities

  • Also known as bridge entities

  • Used to implement M:N relationships

  • Composed of primary keys of each of the entities to be connected

  • May also contain additional attributes that play no role in connective process

Database Systems, 9th Edition

Slide33 l.jpgSlide 33

Database Systems, 9th Edition

Slide34 l.jpgSlide 34

Database Systems, 9th Edition

Developing an er diagram l.jpgSlide 35

Developing an ER Diagram

  • Database design is an iterative process

    • Create detailed narrative of organization’s description of operations

    • Identify business rules based on description of operations

    • Identify main entities and relationships from business rules

    • Develop initial ERD

    • Identify attributes and primary keys that adequately describe entities

    • Revise and review ERD

Database Systems, 9th Edition

Slide36 l.jpgSlide 36

Database Systems, 9th Edition

Slide37 l.jpgSlide 37

Database Systems, 9th Edition

Slide38 l.jpgSlide 38

Database Systems, 9th Edition

Slide39 l.jpgSlide 39

Database Systems, 9th Edition

Slide40 l.jpgSlide 40

Database Systems, 9th Edition

Slide41 l.jpgSlide 41

Database Systems, 9th Edition

Slide42 l.jpgSlide 42

Database Systems, 9th Edition

Slide43 l.jpgSlide 43

Database Systems, 9th Edition

Slide44 l.jpgSlide 44

Database Systems, 9th Edition

Slide45 l.jpgSlide 45

Database Systems, 9th Edition

Slide46 l.jpgSlide 46

Database Systems, 9th Edition

Database design challenges conflicting goals l.jpgSlide 47

Database Design Challenges: Conflicting Goals

  • Database designers must make design compromises

    • Conflicting goals: design standards, processing speed, information requirements

  • Important to meet logical requirements and design conventions

  • Design is of little value unless it delivers all specified query and reporting requirements

  • Some design and implementation problems do not yield “clean” solutions

Database Systems, 9th Edition

Slide48 l.jpgSlide 48

Database Systems, 9th Edition

Summary l.jpgSlide 49


  • Entity relationship (ER) model

    • Uses ERD to represent conceptual database as viewed by end user

    • ERM’s main components:

      • Entities

      • Relationships

      • Attributes

    • Includes connectivity and cardinality notations

Database Systems, 9th Edition

Summary cont d l.jpgSlide 50

Summary (cont’d.)

  • Connectivities and cardinalities are based on business rules

  • M:N relationship is valid at conceptual level

    • Must be mapped to a set of 1:M relationships

  • ERDs may be based on many different ERMs

  • UML class diagrams are used to represent the static data structures in a data model

  • Database designers are often forced to make design compromises

Database Systems, 9th Edition

Copyright © 2015 SlideServe. All rights reserved | Powered By DigitalOfficePro