1 / 33

Understanding ER Diagrams in Database Systems

This text elaborates on relationship degrees, including unary, binary, and ternary relationships, recursive relationships, and composite entities in database design. It also details the process of developing an ER diagram, using a Tiny College scenario to explain entity relationships.

laurad
Download Presentation

Understanding ER Diagrams in Database Systems

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. Relationship Degree • Indicates number of entities or participants associated with a relationship • Unary relationship • Association is maintained within single entity • Binary relationship • Two entities are associated • Ternary relationship • Three entities are associated Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  2. Relationship Degree (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  3. Relationship Degree (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  4. Recursive Relationships • Relationship can exist between occurrences of the same entity set • Naturally found within unary relationship Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  5. Recursive Relationships (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  6. Recursive Relationships (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  7. Recursive Relationships (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  8. Recursive Relationships (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  9. Recursive Relationships (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  10. Recursive Relationships (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  11. Composite Entities • Also known as bridge entities • Composed of primary keys of each of the entities to be connected • May also contain additional attributes that play no role in connective process Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  12. Composite Entities (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  13. Composite Entities (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  14. Composite Entities (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  15. Developing an ER Diagram • Database design is iterative rather than linear or sequential process • Iterative process • Based on repetition of processes and procedures Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  16. Developing an ER Diagram (continued) • Building an ERD usually involves the following activities: • Create detailed narrative of organization’s description of operations • Identify business rules based on description of operations • Identify main entities and relationships from business rules • Develop initial ERD • Identify attributes and primary keys that adequately describe entities • Revise and review ERD Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  17. Developing an ER Diagram (continued) • Tiny College • Tiny College is divided into several schools • Each school is composed of several departments • Each department may offer courses • Each department may have many professors assigned to it • Each professor may teach up to four classes; each class is section of course • Student may enroll in several classes, but (s)he takes each class only once during any given enrollment period Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  18. Developing an ER Diagram (continued) • Tiny College (continued) • Each department has several students • Each student has only a single major and is associated with a single department • Each student has an advisor in his or her department • Each advisor counsels several students • The relationship between class is taught in a room and the room in the building Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  19. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  20. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  21. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  22. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  23. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  24. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  25. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  26. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  27. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  28. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  29. Developing an ER Diagram (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  30. Database Design Challenges: Conflicting Goals • Database design must conform to design standards • High processing speeds are often a top priority in database design • Quest for timely information might be focus of database design Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  31. Database Design Challenges: Conflicting Goals (continued) Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  32. Summary • Entity relationship (ER) model • Uses ERD to represent conceptual database as viewed by end user • ERM’s main components: • Entities • Relationships • Attributes • Includes connectivity and cardinality notations Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

  33. Summary (continued) • Connectivities and cardinalities are based on business rules • In ERM, M:N relationship is valid at conceptual level • ERDs may be based on many different ERMs • Database designers are often forced to make design compromises Database Systems: Design, Implementation, & Management, 7th Edition, Rob & Coronel

More Related