Моделирование бизнес-процессов / Моделирование бизнес-процессов / ER-диаграмы / 0849315484 Entity-Relationship Diagrams

Index

T

Table(s), 7, 13, 100, 193, 236 attributes in, 210 candidate key in, 45 composition of, 42 derived, 18

intersection, 208 key of, 16, 17

mapping of entities to, 206 primary key of, 158, 206 problem with putting data in, 15 relational, 42, 50, 205 two-dimensional, 7, 8, 42 weak, 206

Ternary and higher-order ER diagrams, 165-185 binary versus ternary relationships, 166-169 example of n-ary relationship, 171 exercises, 185

mapping ternary diagrams to relational database, 182-184 methodology and grammar for n-ary relationship, 172-176 n-ary relationships, 171-172

n-ary relationships resolved into binary relationships, 179-181 structural constraints for ternary relationships, 169-170

ternary relationships from relationship-relationship situations, 176-179

Ternary relationship, 165, 166 example, 171

structural constraints for, 169 Thinking before action, 2

Third normal form, 16, 236 Transitivity rule of FD inference, 10 Tuple, 42, 208, 234, 235

Index

U-V

Unary relationships, 145 Union rule, 12

Unique identifier, 13, 17, 33, 34, 225, 236

Index

W-Z

Waterfall model, 2, 236

Weak entity(ies), 35, 115-132, 178, 206, 220, 225, 234, 236 definition of, 145

example of weak entity and identifying owner, 121 exercises, 127

grammar, 124-125

identifying owner and, 119, 121

mapping of weak entities to relational database, 125-126 methodology revisited, 123-124

attribute information, 124 drawing of entity, 124

examination of attributes in primary entity, 123 relationship, 189

reverse-engineering, 214

weak entities connected to, 121

List of Figures

Chapter 2: The Basic ER Diagram—A Data Modeling

Schema

Figure 2.1: An ER Diagram with Three Attributes

Figure 2.2: An ER Diagram with One Entity and Five Attributes, Alternate Models (Batini, Ceri, Navathe)

Figure 2.3: An ER Diagram with One Entity and Five Attributes Figure 2.4: An ER Diagram with a Composite Attribute — name Figure 2.5: An ER Diagram with a Multi-Valued Attribute Figure 2.5A: An ER Diagram with a Derived Attribute — age

Figure 2.6: An ER Diagram with a Primary Key or Unique Identifier Attribute

Figure 2.7: A Strong and a Weak AUTOMOBILE Entity

Figure 2.8: An ER Diagram of the STUDENT-AUTOMOBILE Database Figure 2.9: The MALL Entity

Chapter 3: Beyond the First Entity Diagram

Figure 3.1: A STUDENT Entity with a Multi-Valued Attribute

Figure 3.2: Two ER Diagrams: One of STUDENT and One of SCHOOL

Figure 3.3: The STUDENT Entity with a Relationship to the SCHOOL Entity

Figure 3.4: A STUDENT Entity with an Attribute Called AUTOMOBILE Figure 3.5: An ER Diagram of the STUDENT–AUTOMOBILE Database

Figure 3.6: An ER Diagram of the STUDENT–AUTOMOBILE Database with an "Unknown," "Yet-To-Be-Determined" Relationship

Figure 3.7: An ER Diagram of the Mall Database Thus Far

Figure 3.8: An ER Diagram of West Florida Mall Database Developing Figure 3.9: An ER Diagram of West Florida Mall with Four Entities

Chapter 4: Extending Relationships/Structural

Constraints

Figure 4.1: An ER Diagram of the STUDENT-AUTOMOBILE Database with the Relationship Name, drive, and Showing the Cardinality Ratios

Figure 4A: A One-to-One Relationship STUDENT:AUTOMOBILE::1:1 Figure 4B: Many-to-One Relationship STUDENT:AUTOMOBILE::M:1 Figure 4C: One-to-Many Relationship STUDENT:AUTOMOBILE::1:M

Figure 4D: Many-to-Many Relationship STUDENT:AUTOMOBILE::M:N

Figure 4.2: An ER Diagram of the STUDENT-AUTOMOBILE Database with the Relationship Name, drive

Figure 4.3: An ER Diagram of the STUDENT-AUTOMOBILE Database. Translating the Diagram into English

Figure 4E: Chen Model of 1(full):1 Relationship — Pattern 1 Figure 4F: Chen Model of M(full):1 Relationship — Pattern 1 Figure 4G: Chen Model of 1(partial):1 Relationship — Pattern 2 Figure 4H: Chen Model of M(partial):1 Relationship — Pattern 2 Figure 4I: Chen Model of 1(full):M Relationship — Pattern 3 Figure 4J: Chen Model of M(full):N Relationship — Pattern 3 Figure 4K: Chen Model of 1(partial):M Relationship — Pattern 4 Figure 4L: Chen Model of M(partial):N Relationship — Pattern 4

Figure 4.4: An ER Diagram (without Attributes) of a 1:M Relationship Figure 4.5: An ER Diagram (without Attributes) of a M:1 Relationship Figure 4.6: An ER Diagram (without Attributes) of a M:N Relationship Figure 4.7: The PASSENGER Entity Diagram

Figure 4.8: Sample Problem

Figure 4.9: Sample Problem: Alternate Presentation of Attributes with Explanation and Sample Data

Figure 4.10

Figure 4.11: An ER Diagram of West Florida Mall with Four Entities and Structural Constraints

Chapter 5: The Weak Entity

Figure 5.1: The EMPLOYEE Entity Showing DEPENDENT Name as a Multi-Valued Attribute

Figure 5.2: The EMPLOYEE–DEPENDENT ER Diagram — First Pass Figure 5.3: The EMPLOYEE–DEPENDENT ER Diagram

Figure 5.4: A Weak Entity with Two Relationships

Figure 5.5: The PERSON–PET–VET ER Diagram

Figure 5.6: The EMPLOYEE–DEPENDENT–HOBBY ER Diagram Figure 5.7: An ER Diagram of West Florida Mall Developed Thus Far

Chapter 6: Further Extensions for ER Diagrams with Binary Relationships

Figure 6.1: An ER Diagram of an M:N Relation with an Attribute of a

Relationship

Figure 6.2: An ER Diagram of an M:N Relationship that Has Been Replaced with Two 1:M Relationships

Figure 6.3: An ER Diagram (with Only Primary Keys) Showing a STUDENT/COURSE/INSTRUCTOR Database

Figure 6.4: An ER Diagram (with Only Primary Keys) Showing a STUDENT/COURSE/INSTRUCTOR Database with "Building" as an Attribute

Figure 6.5: An ER Diagram (with Only Primary Keys) Showing a STUDENT/ COURSE/INSTRUCTOR/BUILDING Database

Figure 6.6: An ER Diagram Showing a

STUDENT/COURSE/INSTRUCTOR/BUILDING Database

Figure 6.7: An ER Diagram Showing a STUDENT/COURSE/INSTRUCTOR/ BUILDING Database with the "room number" for the Three Relations

Figure 6.8: An ER Diagram with COURSE Entity in a Database

Figure 6.9: An ER Diagram of the COURSE–INSTRUCTOR Database

Figure 6.10: An ER Diagram of the COURSE–INSTRUCTOR Database

Figure 6.11: A Classic Recursive Relationship PERSONNEL–

SUPERVISOR

Figure 6A: One-to-One Recursive Relationship (Partial Participation on Both Sides)

Figure 6B: Instances of One-to-One Recursive Relationship (Partial Participation on Both Sides)

Figure 6.C: One-to-Many Recursive Relationship (Partial Participation on Both Sides)

Figure 6.D: Instances of One-to-Many Recursive Relationship (Partial Participation on Both Sides)

Figure 6.E: Many-to-Many Recursive Relationship (Partial Participation on Both Sides)

Figure 6.12: An ER Diagram with Two Entities and Two Relationships

Figure 6.12A: An ER Diagram with Two Entities and Two Relationships and Some Intersection Attributes

Figure 6.13: An ER Diagram Showing a STUDENT/COURSE/INSTRUCTOR Database with a "Redundant" Relationship

Figure 6.14: An ER Diagram Showing a STUDENT/COURSE/INSTRUCTOR Database with a "Redundant" Relationship

Figure 6.15: Recursive Relationship with (min, max) Ratios

Figure 6.16: An ER Diagram Showing an Alternative ER Notation for Specifying Structural Constraints

Figure 6.17: An ER Diagram of West Florida Mall Developed Thus Far

Chapter 7: Ternary and Higher-Order ER Diagrams

Figure 7.1A: A Binary Relationship of PRODUCT and SUPPLIER and an Intersection Attribute, wholesale_price

Figure 7.1B: A Binary Relationship of PRODUCT and CUSTOMER and an Intersection Attribute, retail_price

Figure 7.2: An ER Diagram (with Only Primary Keys) Showing a ThreeWay Relationship

Figure 7A: An ER Diagram Showing a Ternary Many-to-Many-to-Many Relationship (Partial Participation on All Sides)

Figure 7B: Instances of a Ternary Many-to-Many-to-Many for CUSTOMER:PRODUCT:SUPPLIER Relationship

Figure 7.3: An ER Diagram Showing an n-ary Relationship

Figure 7.4: An ER Diagram (with Only Primary Keys) Showing a ThreeWay and a Two-Way Relationship

Figure 7.5: An ER Diagram (with Only Primary Keys) Showing a ThreeWay Relationship with Partial Participations, and a 1-Relationship

Figure 7.6A: A Binary Relationship of BOOK_PUBLISHER and

MANUSCRIPT

Figure 7.6B: A Relationship of a Relationship

Figure 7.6C: A Relationship of a Relationship

Figure 7.6D: A Relationship of a Relationship Resolved into a Ternary Relationship

Figure 7.7: An ER Diagram of an M:N Relationship That Has Been Replaced with Two 1:M Relationships

Figure 7.8: An ER Diagram (with Only Primary Keys) Showing a ThreeWay Relationship "Decomposed" into Three Binary Relationships

Chapter 8: Generalizations and Specializations

Figure 8.1: The Student-Athlete with an Attempt to Add a Variant Attribute

Figure 8.2: The Student–Athlete Shown as a Strong–Weak Relationship Variant Attribute

Figure 8.3: The Student–Athlete Shown as a Strong–Weak Relationship Variant Attribute

Figure 8.3A: The Student—Athlete Shown in a Superclass/Subclass

Relationship

Figure 8.4: An Office Database with Specialization Entities, Full Participation and Disjoint

Figure 8.5: An ER Diagram of West Florida Mall Developed Thus Far

Chapter 9: Relational Mapping and Reverse-

Engineering ER Diagrams

Figure 9.1: Reverse-Engineering Strong Entities

Figure 9.2: Reverse-Engineering 1:N Relationships

Figure 9.3: An ER Diagram Showing the Relationship between R and S Figure 9.4: Reverse-Engineering Weak Entities

Figure 9.5: Reverse-Engineering Multi-Valued Attributes

Figure 9.6: Reverse-Engineering M:N Relationships

Figure 9.7: Reverse-Engineering n-ary Cases

Chapter 10: A Brief Overview of the Barker/Oracle-

Like Model

Figure 10.1: Barker/Oracle-Like Notation: An ER Diagram with One Entity and Five Attributes

Figure 10.1A: Barker/Oracle-Like Notation: An ER Diagram with One Entity and Five Attributes (Data Types Added)

Figure 10.2: Barker/Oracle-Like Notation: An ER Diagram with a Composite Attribute — name

Figure 10.3: Barker/Oracle-Like Notation: An ER Diagram with a Primary Key or Unique Identifier Attribute and Optional and Mandatory Attributes

Figure 10.4: Barker/Oracle-Like Notation: The STUDENT Entity with a Relationship to the SCHOOL Entity

Figure 10.5: 1:1 Relationship in the Barker/Oracle-Like Notation

Figure 10.6: 1:M Relationship in the Barker/Oracle-Like Notation

Figure 10.7: Unique Identifier Shown by Placing Bar across Contributing Relationship Line(s)

Figure 10.8: Unique Identifier Shown by Placing Bar across Contributing Relationship Line(s) [Note: "*" shows a foreign key.]

Figure 10.9: Barker/Oracle-Like Notation Showing Foreign Key

Figure 10.10: Barker/Oracle-Like Notation: Recursive Relationships

Figure 10.11: An ER Diagram of an M:N Relationship in the Chen-Like Model

Figure 10.12: Barker/Oracle-Like Notation: M:N Relationship Broken into Two 1:M Relationships

List of Examples

Chapter 1: The Software Engineering Process and

Relational Databases

Checkpoint 1.1

Checkpoint 1.2

Checkpoint 1.3

Checkpoint 1.4

Chapter 2: The Basic ER Diagram—A Data Modeling

Schema

Checkpoint 2.1

Checkpoint 2.2

Checkpoint 2.3

Chapter 3: Beyond the First Entity Diagram

Checkpoint 3.1

Checkpoint 3.2

Chapter 4: Extending Relationships/Structural

Constraints

Checkpoint 4.1

Checkpoint 4.2

Checkpoint 4.3

Checkpoint 4.4

Chapter 5: The Weak Entity

Checkpoint 5.1

Checkpoint 5.2

Checkpoint 5.3

Chapter 6: Further Extensions for ER Diagrams with Binary Relationships

Checkpoint 6.1

Checkpoint 6.2

Checkpoint 6.3 (Optional)

Checkpoint 6.4

Chapter 7: Ternary and Higher-Order ER Diagrams

Checkpoint 7.1

Checkpoint 7.2

Checkpoint 7.3

Chapter 8: Generalizations and Specializations

Checkpoint 8.1

Checkpoint 8.2

Chapter 9: Relational Mapping and Reverse-

Engineering ER Diagrams

Checkpoint 9.1

Checkpoint 9.2

Chapter 10: A Brief Overview of the Barker/Oracle-

Like Model

Checkpoint 10.1

Checkpoint 10.2

Checkpoint 10.3

Checkpoint 10.4