1 / 45

Chapter # 4 Entity Relationship (ER) Modeling

Chapter # 4 Entity Relationship (ER) Modeling. ER model forms the basis of an ER diagram ERD represents conceptual database as viewed by end user ERDs depict database’s main components: Entities Attributes Relationships. Entity Relationship (ER) Modeling.

behm
Download Presentation

Chapter # 4 Entity Relationship (ER) Modeling

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 # 4 Entity Relationship (ER) Modeling

  2. ER model forms the basis of an ER diagram ERD represents conceptual database as viewed by end user ERDs depict database’s main components: Entities Attributes Relationships Entity Relationship (ER) Modeling

  3. Refers to entity set and not to single entity occurrence Corresponds to table and not to row in relational environment In Chen and Crow’s Foot models, entity represented by rectangle with entity’s name Entity name, a noun, written in capital letters Entities …

  4. Characteristics of entities Chen notation: attributes represented by ovals connected to entity rectangle with a line Each oval contains the name of attribute it represents Crow’s Foot notation: attributes written in attribute box below entity rectangle Attributes …

  5. Required attribute:must have a value Optional attribute:may be left empty Domain: set of possible values for an attribute Attributes may share a domain Attributes (3) …

  6. Attributes (4) …

  7. Composite attributecan be subdivided Simple attributecannot be subdivided Single-value attributecan have only a single value Multivalued attributescan have many values Attributes (5) …

  8. Attributes (6) … • Identifiers:one or more attributes that uniquely identify each entity instance • Composite identifier:primary key composed of more than one attribute

  9. M:N relationships and multivalued attributes should not be implemented Create several new attributes for each of the original multivalued attributes components Create new entity composed of original multivalued attributes components Splitting multivalued Attributes

  10. Derived attribute:value may be calculated from other attributes Need not be physically stored within database For example, an employee’s age, EMP_AGE, may be found by computing the integer value of the difference between the current date and the EMP_DOB. Derived Attribute

  11. Attributes (8) …

  12. Association between entities Participants are entities that participate in a relationship Relationships between entities always operate in both directions Relationship can be classified as 1:M Relationships …

  13. Connectivity Describes the relationship classification Cardinality Expresses minimum and maximum number of entity occurrences associated with one occurrence of related entity Established by very concise statements known as business rules Connectivity and Cardinality

  14. Connectivity and Cardinality (2) • the cardinality (1,4) written next to the CLASS entity in the “PROFESSOR teaches CLASS” relationship indicates that each professor teaches up to four classes, • the cardinality (1,1) written next to the PROFESSOR entity indicates that each class is taught by one and only one professor.

  15. Existence dependence Entity exists in database only when it is associated with another related entity occurrence Existence independence Entity can exist apart from one or more related entities Sometimes such an entity is referred to as a strong or regular entity Existence Dependence

  16. Weak (non-identifying) relationships Exists if PK of related entity does not contain PK component of parent entity Relationship Strength COURSE(CRS_CODE, DEPT_CODE, CRS_DESCRIPTION, CRS_CREDIT) CLASS(CLASS_CODE, CRS_CODE, CLASS_SECTION, CLASS_TIME, ROOM_CODE, PROF_NUM) In this case, a weak relationship exists between COURSE and CLASS because the CLASS_CODE is the CLASS entity’s PK, while the CRS_CODE in CLASS is only an FK.

  17. Relationship Strength (2)

  18. Strong (identifying) relationships Exists when PK of related entity contains PK component of parent entity Relationship Strength COURSE(CRS_CODE, DEPT_CODE, CRS_DESCRIPTION, CRS_CREDIT) CLASS(CRS_CODE, CLASS_SECTION , CLASS_TIME, ROOM_CODE, PROF_NUM) indicate that a strong relationship exists between COURSE and CLASS, because the CLASS entity’s composite PK is composed of CRS_CODE + CLASS_SECTION.

  19. Relationship Strength (3)

  20. Weak entitymeets two conditions The entity is existence-dependent; that is, it cannot exist without the entity with which it has a relationship. The entity has a primary key that is partially or totally derived from the parent entity in the relationship. Database designer determines whether an entity is weak based on business rules Weak Entities

  21. Weak Entities (2) DEPARTMENT DEPARTMENT

  22. Weak Entities (3) DEPARTMENT

  23. Optional participation One entity occurrence does not require corresponding entity occurrence in particular relationship Mandatory participation One entity occurrence requires corresponding entity occurrence in particular relationship Relationship Participation

  24. Relationship Participation (2)

  25. Relationship Participation (3)

  26. 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 Relationship Degree

  27. Relationship Degree (2)

  28. Relationship Degree (3)

  29. Relationship can exist between occurrences of the same entity set Naturally found within unary relationship Recursive Relationships

  30. Also known as bridge entities Used to transform M:N relationships into 1:M. Composed of primary keys of each of the entities to be connected May also contain additional attributes that play no role in connective process Associative (Composite) Entities

  31. Associative (Composite) Entities (2)

  32. Associative (Composite) Entities (3)

  33. Database design is an iterative process Create detailed narrative of organization’s 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 Developing an ER Diagram

  34. To illustrate the use of the iterative process that ultimately yields a workable ERD, let’s start with an initial interview with the Tiny College administrators. The Tiny College Example

  35. Developing an ER Diagram (2)

  36. Developing an ER Diagram (3)

  37. Developing an ER Diagram (4)

  38. Developing an ER Diagram (5)

  39. Developing an ER Diagram (6)

  40. Developing an ER Diagram (7)

  41. Developing an ER Diagram (8)

  42. Developing an ER Diagram (9)

  43. Developing an ER Diagram (11)

  44. THE END

More Related