Database Technology. Topic 4: Enhanced Entity- Relationship (EER) Modeling

Size: px

Start display at page:

Download "Database Technology. Topic 4: Enhanced Entity- Relationship (EER) Modeling"

Lucas Wells
5 years ago
Views:

1 Topic 4: Enhanced Entity- Relationship (EER) Modeling Olaf Hartig

2 Example A taxi company needs to model their activities. There are two types of employees in the company: drivers and operators. For drivers it is interesting to know the date of issue and type of the driving license, and the date of issue of the taxi driver s certificate. For all employees it is interesting to know their personal number, address and the available phone numbers. The company owns a number of cars. For each car there is a need to know its type, year of manufacturing, number of places in the car and date of the last service. The company wants to have a record of car trips. A taxi may be picked on a street or ordered through an operator who assigns the order to a certain driver and a car. Departure and destination addresses together with times should also be recorded. 2

3 Recall: DB Design Process 3

4 Entity-Relationship (ER) Model High-level conceptual data model An overview of the database Easy to discuss with non-database experts Easy to translate to data model of DBMS ER diagram Diagrammatic notation associated with the ER model 4

5 Entities and Entity Types Entity: a thing in the real world with an independent existence Attributes: Properties that describe an entity Entity type: A collection of entities that have the same set of attributes SS ame Regumber Model Year Owner Car 5

6 Attributes simple versus composite single-valued versus multivalued stored versus derived Street City SS ame Address Owner Phoneumber Age 6

7 Constraints on Attributes Value sets (domains) of attributes Key attributes Street City SS ame Address Owner Phoneumber Age 7

8 Relationship Types Relationship type: Association among entity types Model SS ame Regumber Year Owner 1 owns Car 8

9 Constraints on Relationship Types Cardinality ratio: Maximum number of relationships an entity can participate in Possible cardinality ratio: 1:1, 1:, :1, and :M Owner 1 owns Car Owner 1 owns Car Owner owns M Car 9

10 Constraints on Relationship Types Participation constraint Total participation: Every entity participates in at least one relationship with another entity SS Every car must be owned by at least one owner. M Owner owns Car Regumber 10

11 Attributes of Relationship Types Store information on who owned which car and during which period of time SS ame Owner SellDate BuyDate owns Regumber M Car Model Year 11

12 n-ary Relationships Example: A person works as an engineer at one company and as a gym instructor at another company Company works at M Employee works as M JobType Employee M works as K Company JobType Ternary 12

13 Weak Entity Types Identified by their relationship to a specific entity from another entity type Do not have key attributes of their own Only partial key The identifying entity has the rest of the key name name Team 1 plays_in Player number 13

14 ER otation 14

15 Enhanced Entity-Relationship (EER) Model

16 Enhanced ER (EER) Model Why more? To support more complex data requirements Example: Only some employees can use a company car, only managers have to write a monthly report, but all employees have assigned personal number, salary account and a place in the office. What more? Specialization / generalization Subtype / supertype Union subtypes Attribute and relationship inheritance 16

17 Subtype / Supertype Surname P ame Firstame specialization generalization Employee process of defining types Commission U d U U o Salesman Engineer Manager ProjectLeader 1 1 uses writes 1 Car MonthlyReport Regumber ReportID 17

18 Constraints on Subtypes Disjointness constraint Specifies that the subclasses of the specialization must be disjoint Otherwise overlapping Completeness constraint (or totalness constraint) Specifies that every superclass entity must be in a subclass Otherwise partial Disjointness and completeness are independent constraints i.e., four cases are possible disjoint and total disjoint and partial overlapping and total overlapping and partial 18

19 Example

20 Example A taxi company needs to model their activities. There are two types of employees in the company: drivers and operators. For drivers it is interesting to know the date of issue and type of the driving license, and the date of issue of the taxi driver s certificate. For all employees it is interesting to know their personal number, address and the available phone numbers. The company owns a number of cars. For each car there is a need to know its type, year of manufacturing, number of places in the car and date of the last service. The company wants to have a record of car trips. A taxi may be picked on a street or ordered through an operator who assigns the order to a certain driver and a car. Departure and destination addresses together with times should also be recorded. 22

21 Example Street Postumber Address Town P Employee Phone TaxiCertifDate Uo U DrivingLicenseDate Driver Operator DrivingLicenseType 1 1 drives assign DeparturePlace Destination DepTime DestTime ID Trip made_by Type Regumber 1 Car YearOfManuf ServiceDate Places 23

22 Example (cont'd) A driver may have many driving licenses (types) TaxiCertifDate DrivingLicenseDate DrivingLicenseType Driver Date Type Id TaxiCertifDate DrivingLicense Körkort belongsto 1 Driver TaxiCertifDate Type DrivingLicense belongsto M Driver Date 24

23 Summary

24 Summary Entity-relationship (ER) model: a graphical way to model the world Main concepts: Entity type Relationship type Attributes Different types of constraints Enhanced ER model 26

Topic 5: Mapping of EER Diagrams to Relations

Topic 5: Mapping of EER Diagrams to Relations Olaf Hartig olaf.hartig@liu.se Recall: DB Design Process 2 Running Example 3 Algorithm for Mapping from the ER Model to the Relational Model Step 1: Map Regular