1. Database Management Systems Chapter 2 The Entity-Relationship Data Model Instructor: Li Ma Department of Computer Science Texas Southern University, Houston August, 2007

2. Entity-Relationship Model Diagrams Class hierarchies Weak entity sets

3. Jeffrey Ullman3 Purpose of E/R Model uThe E/R model allows us to sketch database designs. wWhat kinds of data and how they connect. wNot how data changes. uDesigns are pictures called entity- relationship diagrams. uLater: convert E/R designs to relational DB designs.

4. Jeffrey Ullman4 Entity Sets uEntity = “thing” or object. uEntity set = collection of similar entities. wSimilar to a class in object-oriented languages. uAttribute = property of (the entities of) an entity set. wAttributes are simple values, e.g. integers or character strings.

5. Jeffrey Ullman5 E/R Diagrams uIn an entity-relationship diagram: wEntity set = rectangle. wAttribute = oval, with a line to the rectangle representing its entity set.

6. Jeffrey Ullman6 Example uEntity set Beers has two attributes, name and manf (manufacturer). uEach Beers entity has values for these two attributes, e.g. (Bud, Anheuser-Busch) Beers name manf

7. Jeffrey Ullman7 Relationships uA relationship connects two or more entity sets. uIt is represented by a diamond, with lines to each of the entity sets involved.

8. Jeffrey Ullman8 Example Drinkers addrname Beers manfname Bars name license addr Sells Bars sell some beers. Likes Drinkers like some beers. Frequents Drinkers frequent some bars.

9. Jeffrey Ullman9 Relationship Set uThe current “value” of an entity set is the set of entities that belong to it. wExample: the set of all bars in our database. uThe “value” of a relationship is a set of lists of currently related entities, one from each of the related entity sets.

10. Jeffrey Ullman10 Example uFor the relationship Sells, we might have a relationship set like: BarBeer Joe’s BarBud Joe’s BarMiller Sue’s BarBud Sue’s BarPete’s Ale Sue’s BarBud Lite

11. Jeffrey Ullman11 Multiway Relationships uSometimes, we need a relationship that connects more than two entity sets. uSuppose that drinkers will only drink certain beers at certain bars. wOur three binary relationships Likes, Sells, and Frequents do not allow us to make this distinction. wBut a 3-way relationship would.

12. Jeffrey Ullman12 Example Bars Beers Drinkers name addr manf name addr license Preferences

13. Jeffrey Ullman13 A Typical Relationship Set BarDrinkerBeer Joe’s BarAnnMiller Sue’s BarAnnBud Sue’s BarAnnPete’s Ale Joe’s BarBobBud Joe’s BarBobMiller Joe’s BarCalMiller Sue’s BarCalBud Lite

14. Jeffrey Ullman14 Many-Many Relationships uFocus: binary relationships, such as Sells between Bars and Beers. uIn a many-many relationship, an entity of either set can be connected to many entities of the other set. wE.g., a bar sells many beers; a beer is sold by many bars.

15. Jeffrey Ullman15 In Pictures: many-many

16. Jeffrey Ullman16 Many-One Relationships uSome binary relationships are many - one from one entity set to another. uEach entity of the first set is connected to at most one entity of the second set. uBut an entity of the second set can be connected to zero, one, or many entities of the first set.

17. Jeffrey Ullman17 In Pictures: many-one

18. Jeffrey Ullman18 Example uFavorite, from Drinkers to Beers is many-one. uA drinker has at most one favorite beer. uBut a beer can be the favorite of any number of drinkers, including zero.

19. Jeffrey Ullman19 One-One Relationships uIn a one-one relationship, each entity of either entity set is related to at most one entity of the other set. uExample: Relationship Best-seller between entity sets Manfs (manufacturer) and Beers. wA beer cannot be made by more than one manufacturer, and no manufacturer can have more than one best-seller (assume no ties).

20. Jeffrey Ullman20 In Pictures: one-one

21. Jeffrey Ullman21 Representing “Multiplicity” uShow a many-one relationship by an arrow entering the “one” side. uShow a one-one relationship by arrows entering both entity sets. uRounded arrow = “exactly one,” i.e., each entity of the first set is related to exactly one entity of the target set.

22. Jeffrey Ullman22 Example DrinkersBeers Likes Favorite

23. Jeffrey Ullman23 Example uConsider Best-seller between Manfs and Beers. uSome beers are not the best-seller of any manufacturer, so a rounded arrow to Manfs would be inappropriate. uBut a beer manufacturer has to have a best-seller.

24. Jeffrey Ullman24 In the E/R Diagram ManfsBeers Best- seller

25. Jeffrey Ullman25 Attributes on Relationships uSometimes it is useful to attach an attribute to a relationship. uThink of this attribute as a property of tuples in the relationship set.

26. Jeffrey Ullman26 Example BarsBeers Sells price Price is a function of both the bar and the beer, not of one alone.

27. Jeffrey Ullman27 Equivalent Diagrams Without Attributes on Relationships uCreate an entity set representing values of the attribute. uMake that entity set participate in the relationship.

28. Jeffrey Ullman28 Example BarsBeers Sells price Prices Note convention: arrow from multiway relationship = “all other entity sets together determine a unique one of these.”

29. Jeffrey Ullman29 Convert Multiway Relationship to Binary uSome data models limit relationships to be binary uMultiway relationship could be converted to a collection of binary, many-one relationships wIntroduce a new connecting entity set replacing with the relationship

30. Jeffrey Ullman30 Example BarsBeers Prices Entity set “Sells” records sale Information. Each record has: bar name, beer name, price, sale number, date, … bar_of Sells beer_of price_of

31. Jeffrey Ullman31 Roles uSometimes an entity set appears more than once in a relationship. uLabel the edges between the relationship and the entity set with names called roles.

32. Jeffrey Ullman32 Example Drinkers Married husbandwife Relationship Set HusbandWife BobAnn JoeSue…

33. Jeffrey Ullman33 Example Drinkers Buddies 12 Relationship Set Buddy1 Buddy2 Bob Ann Joe Sue Ann Bob Joe Moe …

34. Jeffrey Ullman34 Subclasses uSubclass = special case = fewer entities = more properties. uExample: Ales are a kind of beer. wNot every beer is an ale, but some are. wLet us suppose that in addition to all the properties (attributes and relationships) of beers, ales also have the attribute color.

35. Jeffrey Ullman35 Subclasses in E/R Diagrams uAssume subclasses form a tree. wI.e., no multiple inheritance. uIsa triangles indicate the subclass relationship. wPoint to the superclass.

36. Jeffrey Ullman36 Example Beers Ales isa namemanf color

37. Jeffrey Ullman37 E/R Vs. Object-Oriented Subclasses uIn OO, objects are in one class only. wSubclasses inherit from superclasses. uIn contrast, E/R entities have representatives in all subclasses to which they belong. wRule: if entity e is represented in a subclass, then e is represented in the superclass.

38. Jeffrey Ullman38 Example Beers Ales isa namemanf color Pete’s Ale

39. Jeffrey Ullman39 Keys uA key is a set of attributes for one entity set such that no two entities in this set agree on all the attributes of the key. wIt is allowed for two entities to agree on some, but not all, of the key attributes. uWe must designate a key for every entity set.

40. Jeffrey Ullman40 Keys in E/R Diagrams uUnderline the key attribute(s). uIn an Isa hierarchy, only the root entity set has a key, and it must serve as the key for all entities in the hierarchy.

41. Jeffrey Ullman41 Example: name is Key for Beers Beers Ales isa namemanf color

42. Jeffrey Ullman42 Example: a Multi-attribute Key Courses dept number hoursroom Note that hours and room could also serve as a key, but we must select only one key.

43. Jeffrey Ullman43 Weak Entity Sets uOccasionally, entities of an entity set need “help” to identify them uniquely. uEntity set E is said to be weak if in order to identify entities of E uniquely, we need to follow one or more many- one relationships from E and include the key of the related entities from the connected entity sets.

44. Jeffrey Ullman44 Example uname is almost a key for football players, but there might be two with the same name. unumber is certainly not a key, since players on two teams could have the same number. uBut number, together with the team name related to the player by Plays-on should be unique.

45. Jeffrey Ullman45 In E/R Diagrams Double diamond for supporting many-one relationship. Double rectangle for the weak entity set. PlayersTeams Plays- on name number city

46. Jeffrey Ullman46 Weak Entity-Set Rules uA weak entity set has one or more many-one relationships to other (supporting) entity sets. wNot every many-one relationship from a weak entity set need be supporting. uThe key for a weak entity set is its own underlined attributes and the keys for the supporting entity sets. wE.g., (player) number and (team) name is a key for Players in the previous example.

47. Jeffrey Ullman47 Design Principles (1) uFaithfulness: relationships make sense, reflect reality uAvoiding redundancy: say everything once only uSimplicity count: necessary elements only

48. Jeffrey Ullman48 Design Principles (2) uChoosing the right relationships: don’t add every possible relationship uPicking the right kind of elements: choose a right design element to represent a real-world concept wUse attributes wUse entity set/relationship combination

49. Jeffrey Ullman49 Design Techniques 1.Avoid redundancy. 2.Don’t use an entity set when an attribute will do. 3.Limit the use of weak entity sets.

50. Jeffrey Ullman50 Avoiding Redundancy uRedundancy occurs when we say the same thing in two or more different ways. uRedundancy wastes space and (more importantly) encourages inconsistency. wThe two instances of the same fact may become inconsistent if we change one and forget to change the other.

51. Jeffrey Ullman51 Example: Good BeersManfs ManfBy name This design gives the address of each manufacturer exactly once. nameaddr

52. Jeffrey Ullman52 Example: Bad BeersManfs ManfBy name This design states the manufacturer of a beer twice: as an attribute and as a related entity. name manf addr

53. Jeffrey Ullman53 Example: Bad Beers name This design repeats the manufacturer’s address once for each beer and loses the address if there are temporarily no beers for a manufacturer. manfmanfAddr

54. Jeffrey Ullman54 Entity Sets Versus Attributes uAn entity set should satisfy at least one of the following conditions: wIt is more than the name of something; it has at least one nonkey attribute. or wIt is the “many” in a many-one or many- many relationship.

55. Jeffrey Ullman55 Example: Good BeersManfs ManfBy name Manfs deserves to be an entity set because of the nonkey attribute addr. Beers deserves to be an entity set because it is the “many” of the many-one relationship ManfBy. nameaddr

56. Jeffrey Ullman56 Example: Good Beers name There is no need to make the manufacturer an entity set, because we record nothing about manufacturers besides their name. manf

57. Jeffrey Ullman57 Example: Bad BeersManfs ManfBy name Since the manufacturer is nothing but a name, and is not at the “many” end of any relationship, it should not be an entity set. name

58. Jeffrey Ullman58 Don’t Overuse Weak Entity Sets uBeginning database designers often doubt that anything could be a key by itself. wThey make all entity sets weak, supported by all other entity sets to which they are linked. uIn reality, we usually create unique ID’s for entity sets. wExamples include social-security numbers, automobile VIN’s etc.

59. Jeffrey Ullman59 When Do We Need Weak Entity Sets? uThe usual reason is that there is no global authority capable of creating unique ID’s. uExample: it is unlikely that there could be an agreement to assign unique player numbers across all football teams in the world.