database_06.pptVIP

Copyright 2005 Radian Publishing Co. Chapter 6 E-R Diagrams Part B. Database Design Contents Chapter 6 E-R Diagrams 6.1 Relationships 6.1 A. Identifying entities and Relationships 6.1 B. Relationship Cardinality 6.1 C. Sample Relationships 6.1 D. Degree of Relationship 6.1 E. Multiple Relationships 6.2 E-R diagrams with Attributes Drawn 6.3 Relationships with Attributes 6.4 Resolving E-R Diagram for Relational DB 6.4 A. Resolving Binary M:N Relationship 6.4 B. Resolving Multi-valued Attribute 6.4 C. Resolving Unary M:N Relationship Chapter 6 E-R Diagrams An entity-relationship (E-R) diagram is a graphical representation of data for an organisation at conceptual level. 6.1 Relationships The requirements for an entity are: 1. one or more attributes 2. many possible distinct instances. A relationship is an association between two entities based on a key attribute. 6.1 A. Identifying Entities and Relationships (1/2) Identifying entities and relationships for a data model is a process of filtering and integrating. (Refer to Guides to Identifying Entities and Guides to Naming Relationships on textbook P. 74) 6.1 A. Identifying Entities and Relationships (2/2) 6.1 B. Relationship Cardinality (1/7) Cardinality specifies the maximum and minimum numbers of instances of an entity participating in an association with another entity. There are three basic types of relationships that specify the maximum number of instances: one-to-one (1:1), one-to-many (1:M) and many-to- many (M:N). 6.1 B. Relationship Cardinality (2/7) 6.1 B. Relationship Cardinality (3/7) 6.1 B. Relationship Cardinality (4/7) 6.1 B. Relationship Cardinality (5/7) 6.1 B. Relationship Cardinality (6/7) There are four possible cardinalities: Mandatory one Mandatory many An instance is mandatory if there exists at least one instance in the relationship. Optional one Optional many An instance is optional if the instance may or may not exist. 6.1 B. Relationship Cardinality (7/7) 6.1 C. Sample