1 / 44

Chapter 7: ER – Entity Relationship Diagram

Chapter 7: ER – Entity Relationship Diagram. Major components of ER diagram Practices. ER. 1976 proposed by Peter Chen ER diagram is widely used in database design Represent conceptual level of a database system Describe things and their relationships in high level. Basic Concepts.

duff
Download Presentation

Chapter 7: ER – Entity Relationship Diagram

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Chapter 7: ER – Entity Relationship Diagram • Major components of ER diagram • Practices Yan Huang -CSCE4350 - ER

  2. ER • 1976 proposed by Peter Chen • ER diagram is widely used in database design • Represent conceptual level of a database system • Describe things and their relationships in high level Yan Huang -CSCE4350 - ER

  3. Basic Concepts • Entity set – an abstraction of similar things, e.g. cars, students • An entity set contains many entities • Attributes: common properties of the entities in a entity sets • Relationship – specify the relations among entities from two or more entity sets Yan Huang -CSCE4350 - ER

  4. An Example Yan Huang -CSCE4350 - ER

  5. Relationship • A relationship may be thought as a set as well • For binary relationship, it enumerates the pairs of entities that relate to each other • For example, entity set M = {Mike, Jack, Tom} entity set F = {Mary, Kate}. The relationship set married between M and F may be {<Mike,Mary>,<Tom, Kate>} Yan Huang -CSCE4350 - ER

  6. Relationship • A relationship set is a mathematical relation among n 2 entities, each taken from entity sets {(e1, e2, … en) | e1  E1, e2  E2, …, en  En}where (e1, e2, …, en) is a relationship • Example: (Hayes, A-102)  depositor Yan Huang -CSCE4350 - ER

  7. Relationship Example Yan Huang -CSCE4350 - ER

  8. Attribute of A Relationship Set Yan Huang -CSCE4350 - ER

  9. Relationship • The degree of a relationship = the number of entity sets that participate in the relationship • Mostly binary relationships • Sometimes more • Mapping cardinality of a relationship • 1 –1 • 1 – many • many – 1 • Many-many Yan Huang -CSCE4350 - ER

  10. One-One and One-Many Yan Huang -CSCE4350 - ER

  11. Many-one and many-many Yan Huang -CSCE4350 - ER

  12. 1- many Yan Huang -CSCE4350 - ER

  13. Many - 1 Yan Huang -CSCE4350 - ER

  14. Many - many Yan Huang -CSCE4350 - ER

  15. Alternative Cardinality Specification Yan Huang -CSCE4350 - ER

  16. Note on Mapping Cardinality • Both many and 1 include 0 • Meaning some entity may not participate in the relationship Yan Huang -CSCE4350 - ER

  17. Total Participation • When we require all entities to participate in the relationship (total participation), we use double lines to specify Every loan has to have at least one customer Yan Huang -CSCE4350 - ER

  18. Self Relationship • Sometimes entities in a entity set may relate to other entities in the same set. Thus self relationship • Here employees mange some other employees • The labels “manger” and “worker” are called roles the self relationship Yan Huang -CSCE4350 - ER

  19. More examples on self-relationship • People to people • Parent – children • Manager – employee • Husband – wife • Word to word • Root – synonym Yan Huang -CSCE4350 - ER

  20. Attributes • Both entity sets and relationships can have attributes • Attributes may be • Composite • Multi-valued (double ellipse) • Derive (dashed ellipse) Yan Huang -CSCE4350 - ER

  21. Another Example Yan Huang -CSCE4350 - ER

  22. Keys • A super key of an entity set is a set of one or more attributes whose values uniquely determine each entity. • A candidate key of an entity set is a minimal super key • Although several candidate keys may exist, one of the candidate keys is selected to be the primary key. Yan Huang -CSCE4350 - ER

  23. Key Examples • Suggest super keys for the following entity? • What are the candidate keys? • Primary key? author death name birthday description Yan Huang -CSCE4350 - ER

  24. Ternary Relationship Yan Huang -CSCE4350 - ER

  25. Can We Decompose a Ternary Relationship? Yan Huang -CSCE4350 - ER • Some relationships that appear to be non-binary may be better represented using binary relationships • E.g. A ternary relationship parents, relating a child to his/her father and mother, is best replaced by two binary relationships, father and mother • Using two binary relationships allows partial information (e.g. only mother being know) • But there are some relationships that are naturally non-binary • E.g. works-on, why?

  26. Converting Ternary to binary • In general, any non-binary relationship can be represented using binary relationships by creating an artificial entity set. • Replace R between entity sets A, B and Cby an entity set E, and three relationship sets: 1. RA, relating E and A 2.RB, relating E and B 3. RC, relating E and C • Create a special identifying attribute for E • Add any attributes of R to E • For each relationship (ai , bi , ci) in R, create 1. a new entity eiin the entity set E 2. add (ei , ai ) to RA 3. add (ei , bi) to RB 4. add (ei , ci ) to RC Yan Huang -CSCE4350 - ER

  27. Converting Ternary to binary Yan Huang -CSCE4350 - ER

  28. Design an ER Diagram • Design a database for an on-line reservation system for microscopes in material science lab • There are two types of users: microscope administrators and microscope end users • Each microscope is located in a specific lab • Each request is assigned to an administrator who can authorize or deny the request • Using of some microscope requires the presence of an administrator • Time is divided into 1 hour slots. Each reservation can only take one or more time slots Yan Huang -CSCE4350 - ER

  29. Weak Entity Set • Some entity sets in real world naturally depend on some other entity set • They can be uniquely identified only if combined with another entity set • Example: • section1, section2, … become unique only if you put them into a context, e.g. csce4350 Yan Huang -CSCE4350 - ER

  30. Weak Entity Set Notations Double rectangles for weak entity set Double diamond for weak entity relationship Dashed underscore for discriminator Yan Huang -CSCE4350 - ER

  31. Specialization • A lower-level entity set inherits all the attributes and relationship participation of the higher-level entity set to which it is linked. • A lower-level entity set may have additional attributes and participate in additional relationships Yan Huang -CSCE4350 - ER

  32. Yan Huang -CSCE4350 - ER

  33. Specification • Disjoint • Completenessconstraint (use double lines) • total: an entity must belong to one of the lower-level entity sets • partial: an entity need not belong to one of the lower-level entity sets Yan Huang -CSCE4350 - ER

  34. Design Considerations • Use of entity sets vs. attributes • Whether we want to keep additional information • Use of entity sets vs. relationship sets • Actions among entities are usually represented by relationships • Binary versus n-ary relationship sets • N-nary relationships are usually more natural for actions among entity sets • Weak entity set vs. strong entity set • Generalization Yan Huang -CSCE4350 - ER

  35. Notations Yan Huang -CSCE4350 - ER

  36. Notations Yan Huang -CSCE4350 - ER

  37. ER Practice Again • Design an ER diagram for an online music store. The database will contain at least the following concepts: songs, artists, bands, albums, and genres. • State your design assumptions you make to support design decisions. Be sure your assumptions are reasonable. Yan Huang -CSCE4350 - ER

  38. Best Practice Guide for ER Design • Use of entity sets vs. attributes • Use of entity sets vs. relationship sets • Binary versus n-ary relationship sets • Weak entity set vs. strong entity set • Choose the natural one • Generalization • If specialized entities need to keep additional information and participate in additional relationships Yan Huang -CSCE4350 - ER

  39. ER for Banking Enterprise • Description P238 Yan Huang -CSCE4350 - ER

  40. Read ER Diagrams • Following are some ER diagrams grabbed from the web • Read to understand/criticize Yan Huang -CSCE4350 - ER

  41. ? ? ? ? ? ? ? ? ? Yan Huang -CSCE4350 - ER

  42. ? ? ? ? ? Yan Huang -CSCE4350 - ER

  43. ? Yan Huang -CSCE4350 - ER

  44. Yan Huang -CSCE4350 - ER

More Related