Click here to load reader

Entity Relationship Model Chapter 6. Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier,

Embed Size (px)

Citation preview

  • Slide 1
  • Entity Relationship Model Chapter 6
  • Slide 2
  • Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier, etc. Attribute A description of an entity. Eg. Worker has name, worker number, department, address, etc. Relationship
  • Slide 3
  • Example of an Attribute
  • Slide 4
  • Type of Attribute Simple Attributes vs. Composite Attributes
  • Slide 5
  • Solitary Attribute vs. Multiple Value Attribute
  • Slide 6
  • Derived Attribute
  • Slide 7
  • Attribute Domain & Key Set of values for an attribute Character Numeric Date Attributes with one key/ two keys
  • Slide 8
  • Relationship Link between entities. Types of relationship: Unary Binary Ternary
  • Slide 9
  • Unary
  • Slide 10
  • Binary
  • Slide 11
  • Ternary
  • Slide 12
  • Cardinality One to one relationship (1:1) One to many relationship (1:M) Many to many relationship (M:N)
  • Slide 13
  • 1:1 Relationship
  • Slide 14
  • 1:M Relationship
  • Slide 15
  • M:N Relationship
  • Slide 16
  • Relationship Participation Compulsory Optional
  • Slide 17
  • Guidelines and Steps in ER Model No system environment insertion.
  • Slide 18
  • Slide 19
  • Slide 20
  • Slide 21
  • Wrap-up on ERD Determine entities, relationship. Determine attributes. Determine attributes related to relationship (if any). Choose the keys for the entities. Determine the domain for each attribute. Combine the diagrams. Check and refine.
  • Slide 22
  • Tutorial 1 Prepare an ERD for the following case study: A university database contains information about lecturers (identified by staff number) and courses (identified by course code). Lecturers teach courses; each of the following situations concerns the Teaches relationship set. For each situation, create an Entity Relationship (ER) diagram that describes it (assuming no further constraints hold). 1. Lecturers can teach the same course in several semesters, and each course offering must be recorded. 2. Every lecturer must teach some course. 3. Every lecturer teaches exactly one course (no more, no less). 4. Every lecturer teaches exactly one course (no more, no less), and every course must be taught by some lecturer. 5. Now suppose that certain courses can be taught by a team of lecturers jointly, but it is possible that no one lecturer in a team can teach the course. Model this situation, introducing additional entity sets and relationship sets if necessary.
  • Slide 23
  • -Thank You-