32
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi

© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Embed Size (px)

Citation preview

Page 1: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

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

Chapter 3:The Enhanced E-R Model

Modern Database Management10th Edition

Jeffrey A. Hoffer, V. Ramesh, Heikki Topi

Page 2: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

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

Objectives Define terms Understand use of supertype/subtype

relationships Understand use of specialization and

generalization techniques Specify completeness and disjointness constraints Develop supertype/subtype hierarchies for

realistic business situations Develop entity clusters Explain universal (packaged) data model Describe special features of data modeling

project using packaged data model

Page 3: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 3

Supertypes and Subtypes Enhanced ER model: extends original

ER model with new modeling constructs Subtype: A subgrouping of the entities in an

entity type that has attributes distinct from those in other subgroupings

Supertype: A generic entity type that has a relationship with one or more subtypes

Attribute Inheritance: Subtype entities inherit values of all

attributes of the supertype An instance of a subtype is also an instance

of the supertype

Page 4: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 4

Figure 3-1 Basic notation for supertype/subtype notation

a) EER notation

Page 5: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 5

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

b) Microsoft

Visio Notation

Figure 3-1 Basic notation for supertype/subtype notation (cont.)

Page 6: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 6

Figure 3-2 Employee supertype with three subtypes

All employee subtypes will have employee number, name, address, and date hired

Each employee subtype will also have its own attributes

Page 7: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 7

Relationships and Subtypes

Relationships at the supertype level indicate that all subtypes will participate in the relationship

The instances of a subtype may participate in a relationship unique to that subtype. In this situation, the relationship is shown at the subtype level

Page 8: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 8

Figure 3-3 Supertype/subtype relationships in a hospital

Both outpatients and resident patients are cared for by a responsible physician

Only resident patients are assigned to a bed

Page 9: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 9

Generalization and Specialization

Generalization: The process of defining a more general entity type from a set of more specialized entity types. BOTTOM-UP

Specialization: The process of defining one or more subtypes of the supertype and forming supertype/subtype relationships. TOP-DOWN

Page 10: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 10

Figure 3-4 Example of generalization

a) Three entity types: CAR, TRUCK, and MOTORCYCLE

All these types of vehicles have common attributes

Page 11: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 11

Figure 3-4 Example of generalization (cont.)

So we put the shared attributes in a supertype

Note: no subtype for motorcycle, since it has no unique attributes

b) Generalization to VEHICLE supertype

Page 12: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 12

Figure 3-5 Example of specialization

a) Entity type PART

Only applies to manufactured parts

Applies only to purchased parts

Page 13: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 13

b) Specialization to MANUFACTURED PART and PURCHASED PART

Note: multivalued attribute was replaced by an associative entity relationship to another entity

Created 2 subtypes

Figure 3-5 Example of specialization (cont.)

Page 14: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 14

Constraints in Supertype/ Completeness Constraint

Completeness Constraints: Whether an instance of a supertype must also be a member of at least one subtype Total Specialization Rule: Yes (double

line) Partial Specialization Rule: No (single

line)

Page 15: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 15

Figure 3-6 Examples of completeness constraints

a) Total specialization rule

Page 16: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 16

b) Partial specialization rule

Figure 3-6 Examples of completeness constraints (cont.)

Page 17: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 17

Constraints in Supertype/ Disjointness constraint

Disjointness Constraints: Whether an instance of a supertype may simultaneously be a member of two (or more) subtypes Disjoint Rule: An instance of the

supertype can be only ONE of the subtypes

Overlap Rule: An instance of the supertype could be more than one of the subtypes

Page 18: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 18

a) Disjoint rule

Figure 3-7 Examples of disjointness constraints

Page 19: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 19

b) Overlap ruleFigure 3-7 Examples of disjointness constraints (cont.)

Page 20: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 20

Constraints in Supertype/ Subtype Discriminators

Subtype Discriminator: An attribute of the supertype whose values determine the target subtype(s) Disjoint – a simple attribute with alternative

values to indicate the possible subtypes Overlapping – a composite attribute whose

subparts pertain to different subtypes. Each subpart contains a Boolean value to indicate whether or not the instance belongs to the associated subtype

Page 21: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 21

Figure 3-8 Introducing a subtype discriminator (disjoint rule)

Page 22: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 22

Figure 3-9 Subtype discriminator (overlap rule)

Page 23: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 23

Figure 3-10 Example of supertype/subtype hierarchy

Page 24: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 24

Entity Clusters

EER diagrams are difficult to read when there are too many entities and relationships

Solution: Group entities and relationships into entity clusters

Entity cluster: Set of one or more entity types and associated relationships grouped into a single abstract entity type

Page 25: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 25

Figure 3-13a Possible entity clusters for Pine Valley Furniture in Microsoft Visio

Related groups of entities could become clusters

Page 26: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 26

Figure 3-13b EER diagram of PVF entity clusters

More readable, isn’t it?

Page 27: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 27

Figure 3-14 Manufacturing entity cluster

Detail for a single cluster

Page 28: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 28

Packaged Data Models

Predefined data models Could be universal or industry-

specific Universal data model = a generic or

template data model that can be reused as a starting point for a data modeling project (also called a “pattern”)

Page 29: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 29

Advantages of Packaged Data Models

Use proven model components Save time and cost Less likelihood of data model errors Easier to evolve and modify over time Aid in requirements determination Easier to read Supertype/subtype hierarchies promote reuse Many-to-many relationships enhance model

flexibility Vendor-supplied data model fosters integration

with vendor’s applications Universal models support inter-organizational

systems

Page 30: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 30

Packaged data models are generic models that can be customized for a particular organization’s business rules

Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in a universal data model

(a) Basic PARTY universal data model

Page 31: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 31

Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in a universal data model

(b) PARTY supertype/subtype hierarchy

Page 32: © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,

Chapter 3 © 2011 Pearson Education, Inc.  Publishing as Prentice Hall 32

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic,

mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. Printed in the United States of America.

Copyright © 2011 Pearson Education, Inc.  Publishing as Prentice Hall