Text:

Modern Database Management 11th Edition

Jeffrey A. Hoffer, V. Ramesh, Heikki Topi

© 2013 Pearson Education, Inc.  Publishing as Prentice Hall 1

© 2013 Pearson Education, Inc.  Publishing as Prentice Hall 2
 Define terms
 Understand importance of data modeling
 Write good names and definitions for entities,
relationships, and attributes
 Distinguish unary, binary, and ternary relationships
 Model different types of attributes, entities,
relationships, and cardinalities
 Draw E-R diagrams for common business
situations
 Convert many-to-many relationships to associative
entities
 Model time-dependent data using time stamps

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

3
  A database must mirror the real world if it is
to answer questions about the real world
 Data Modeling is a design technique for
capturing reality

STUDENT

Social_Security_No
Name
Major

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

  Related to business, not technical,
characteristics
 Meaningful and self-documenting
 Unique
 Readable
 Composed of words from an approved list
 Repeatable
 Written in standard syntax

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

5
 Explanation of a term or fact
 Term–word or phrase with specific meaning
 Fact–association between two or more terms
 Guidelines for good data definition
 A concise description of essential data meaning
 Gathered in conjunction with systems requirements
 Accompanied by diagrams
 Achieved by consensus, and iteratively refined

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

6
 Entities:
 Entity instance–person, place, object, event, concept
(often corresponds to a row in a table)
 Entity Type–collection of entities (often corresponds to a
table)
 Relationships:
 Relationship instance–link between entities (corresponds
to primary key-foreign key equivalencies in related tables)
 Relationship type–category of relationship…link between
entity types
 Attributes:
 Properties or characteristics of an entity or relationship
type (often corresponds to a field in a table)

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

7
 Sample E-R Diagram (Figure 2-1)

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

88
Basic E-R notation (Figure 2-2)

Entity Attribute
symbols symbols

A special entity
that is also a Relationship
relationship symbols

Relationship
degrees specify
number of
entity types Relationship
involved cardinalities
specify how
many of each
entity type is
allowed
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
99
 WEAK ASSOCIATIVE
ENTITY
ENTITY ENTITY

MULTIVALUED DERIVED
ATTRIBUTE ATTRIBUTE
ATTRIBUTE

RELATIONSHIP INDENTIFYING
RELATIONSHIP

*Actually somewhat modified Chen.

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

  Are statements that define or constrain
some aspect of the business
 Are derived from policies, procedures,
events, functions
 Assert business structure
 Control/influence business behavior
 Are expressed in terms familiar to end
users
 Are automated through DBMS software

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

11
  Declarative–what, not how
 Precise–clear, agreed-upon meaning
 Atomic–one statement
 Consistent–internally and externally
 Expressible–structured, natural
language
 Distinct–non-redundant
 Business-oriented–understood by
business people

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

12
  Entity – a person, a place, an
object, an event, or a concept in
the user environment about which
the organization wishes to
maintain data
 Entity type – a collection of
entities that share common
properties or characteristics
 Entity instance – A single
occurrence of an entity type

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

13
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
14
  SHOULD BE:
 An object that will have many instances in the
database
 An object that will be composed of multiple
attributes
 An object that we are trying to model
 SHOULD NOT BE:
 A user of the database system
 An output of the database system (e.g., a report)

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

15
Figure 2-4 Example of inappropriate entities

System System
user Inappropriate output
entities

Appropriate
entities

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

16
 Strong entity
 exists independently of other types of entities
 has its own unique identifier
 identifier underlined with single line
 Weak entity
 dependent on a strong entity (identifying owner)…cannot exist
on its own
 does not have a unique identifier (only a partial identifier)
 entity box and partial identifier have double lines
 Identifying relationship
 links strong entities to weak entities

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

17
Figure 2-5 Example of a weak identity and its identifying relationship

Strong entity Weak entity

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

18
 Attribute–property or characteristic of
an entity or relationship type
 Classifications of attributes:
 Required versus Optional Attributes
 Simple versus Composite Attribute
 Single-Valued versus Multivalued
Attribute
 Stored versus Derived Attributes
 Identifier Attributes

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

19
Required – must have a value for every Optional – may not have a value for
entity (or relationship) instance with every entity (or relationship) instance
which it is associated with which it is associated

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

20
 Composite attribute – An attribute that has
meaningful component parts (attributes)

The address is
broken into
component parts

Figure 2-7 A composite attribute

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

21
 Multi-valued and Derived
Attributes
Multivalued – may take on more than Derived – values can be calculated from
one value for a given entity (or related attribute values (not physically
relationship) instance stored in the database)

Figure 2-8 Entity with multivalued attribute (Skill) and derived attribute
(Years Employed)

Multivalued Derived
an employee can Calculated
have more than one from date
skill employed
and current
date
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
22
22
  Identifier (Key)–an attribute (or
combination of attributes) that
uniquely identifies individual
instances of an entity type
 Simple versus Composite Identifier
 Candidate Identifier–an attribute that
could be a key…satisfies the
requirements for being an identifier

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

23
  Choose Identifiers that
 Will not change in value
 Will not be null
 Avoid intelligent identifiers (e.g.,
containing locations or people that might
change)
 Substitute new, simple keys for long,
composite keys

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

24
 Figure 2-9 Simple and composite identifier attributes

The identifier
is boldfaced
and underlined

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

25
25
 Name should be a singular noun or noun
phrase
 Name should be unique
 Name should follow a standard format
 e.g. [Entity type name { [ Qualifier ] } ] Class
 Similar attributes of different entity types
should use the same qualifiers and classes

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

26
 State what the attribute is and possibly why it is
important
 Make it clear what is and is not included in the
attribute’s value
 Include aliases in documentation
 State source of values
 Specify required vs. optional
 State min and max number of occurrences allowed
 Indicate relationships with other attributes

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

27
 Relationship Types vs. Relationship Instances
 The relationship type is modeled as lines between
entity types…the instance is between specific entity
instances
 Relationships can have attributes
 These describe features pertaining to the association between
the entities in the relationship
 Two entities can have more than one type of
relationship between them (multiple
relationships)
 Associative Entity–combination of relationship
and entity

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

28
Figure 2-10 Relationship types and instances

a) Relationship
type (Completes)

b) Relationship
instances

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

29
29
  Degree of a relationship is
the number of entity types
that participate in it
 Unary Relationship
 Binary Relationship
 Ternary Relationship

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

30
 Degree of relationships – from Figure 2-2

Entities of
One entity two different
related to types related Entities of three
another of to each other different types
the same
related to each
entity type
other
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
31
31
 One-to-One
 Each entity in the relationship will have exactly one
related entity
 One-to-Many
 An entity on one side of the relationship can have
many related entities, but an entity on the other side
will have a maximum of one related entity
 Many-to-Many
 Entities on both sides of the relationship can have
many related entities on the other side

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

32
Figure 2-12 Examples of relationships of different degrees

a) Unary relationships

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

33
33
Figure 2-12 Examples of relationships of different degrees (cont.)

b) Binary relationships

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

34
34
Figure 2-12 Examples of relationships of different degrees (cont.)

c) Ternary relationship

Note: a relationship can have attributes of its own

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
35
35
 Cardinality Constraints—the number of
instances of one entity that can or must
be associated with each instance of
another entity
 Minimum Cardinality
 If zero, then optional
 If one or more, then mandatory
 Maximum Cardinality
 The maximum number

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

36
Figure 2-17 Examples of cardinality constraints

a) Mandatory cardinalities

A patient history is A patient must have recorded

recorded for one and at least one history, and can
only one patient have many

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

37
37
Figure 2-17 Examples of cardinality constraints (cont.)

b) One optional, one mandatory

A project must be An employee can be assigned

assigned to at least one to any number of projects, or
employee, and may be may not be assigned to any
assigned to many at all

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

38
38
Figure 2-17 Examples of cardinality constraints (cont.)

c) Optional cardinalities

A person is
married to at most
one other person,
or may not be
married at all

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

39
39
Figure 2-21 Examples of multiple relationships

a) Employees and departments

Entities can be related to one another in more than one way

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

40
40
Figure 2-21 Examples of multiple relationships (cont.)

b) Professors and courses (fixed lower limit constraint)

Here, min cardinality constraint is 2. At least two

professors must be qualified to teach each course. Each
professor must be qualified to teach at least one course.

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

41
41
Figure 2-15a and 2-15b Multivalued attributes can be represented as relationships

simple

composite

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

42
42
 An entity–has attributes
 AND it’s a relationship–links entities together
 When should a relationship with attributes
instead be an associative entity?
 All relationships for the associative entity should be
many
 The associative entity could have meaning
independent of the other entities
 The associative entity preferably has a unique
identifier, and should also have other attributes
 The associative entity may participate in other
relationships other than the entities of the associated
relationship
 Ternary relationships should be converted to
associative entities
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
43
 Associative entity is like a relationship with an attribute, but it
is also considered to be an entity in its own right.

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

 Associative entity involves a rectangle with a diamond inside.
Note that the many-to-many cardinality symbols face toward the
associative entity and not toward the other entities

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

 Figure 2-13c An associative entity – bill of materials structure

This could just be a relationship with

attributes…it’s a judgment call.

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

46
46
 This is the Bill of Materials laid out a different
way. It could just be a relationship with
attributes…it’s a judgment call

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

Figure 2-11a A binary relationship with an attribute

Here, the date completed attribute pertains specifically to the

employee’s completion of a course…it is an attribute of the
relationship.

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

48
48
Figure 2-11b An associative entity (CERTIFICATE)

Associative entity is like a relationship with an attribute, but it is

also considered to be an entity in its own right.

Note that the many-to-many cardinality between entities in

Figure 2-11a has been replaced by two one-to-many relationships
with the associative entity.
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
49
49
 Figure 2-19 Simple example of time-stamping

The Price History

Time stamp – a time value that is attribute is both
associated with a data value, often multivalued and
indicating when some event occurred that composite.
affected the data value

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

50
50
 Figure 2-20c E-R diagram with associative entity for
product assignment to product line over time

The Assignment
Modeling time-dependent data has become associative entity shows
more important due to regulations such as the date range of a
HIPAA and Sarbanes-Oxley. product’s assignment to a
particular product line.
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
51
51
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
 Figure 2-22
Data model for Pine
Valley Furniture
Company in
Microsoft Visio
notation

Different modeling
software tools may have
different notation for the
same constructs.

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

53
53
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
 CUSTOMER ORDER

* Customer ID * Order ID
Customer name Order Date

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

 Customer ID
CUSTOMER
Customer name
1

SUBMITS

M
Order ID
ORDER
Order date

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

 CUSTOMER ORDER
#Customer_ID #Order_ID
*Customer Name *Order Date

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall
59
 Copyright © 2013 Pearson Education, Inc.  Publishing as Prentice Hall

Chapter 2 © 2013 Pearson Education, Inc.  Publishing as Prentice Hall 60