1. 1 Entity Relationship Approach u Top-down approach to data modeling u Uses diagrams u Normalization - confirms technical soundness u Entity Relationship - reflects business requirements

2. 2 Using Diagrams u Define a procedure for representing existing models u Develop diagrams directly from business requirements u Business-oriented terminology based on... –Entities (things of interest to business) –Relationships between entities

3. 3 Hospital Example u Graphic 2-13 u Format does not encourage a quick appreciation of the main concepts and rules –e.g. Each operation can be performed by only one surgeon but this is not immediately apparent u This is a very simple model, as we progress to more complex models the problem of presentation becomes more serious

4. 4 Data Model Diagram u Sometimes called data structure diagram, they are based on two symbols –A "box" represents a table (a rounded rectangle is usually used) –A line drawn between two boxes represents a foreign key pointing back to the table that has the primary key

5. 5 Existing Tables u Simply draw a box for every table in the model with the name of it inside u Graphic 3-2

6. 6 Existing Relationships u Draw a line between the two boxes and indicate the direction of the link by putting a "crows foot" at the foreign key end –Think of the crows foot as an arrow pointing back to the table with the primary key u Graphic 3-3

7. 7 Interpreting the Diagram u The model specifies a Surgeon table (data about surgeons) u The model specifies an Operation table (data about operations) u Each Operation can be associated with only one surgeon u Each Surgeon can be associated with many Operations

8. 8 Summarizing Relationships u This represents the relationship between tables (implied by the primary and foreign keys) without having to list any column names at all

9. 9 Asking Questions u We could now ask the business specialist –Is it true that each operation is performed by one surgeon only? –Can we count on this in the future? u We can make changes now (in the model) while the cost is still low u Question: If more than one Surgeon is allowed, how would we handle it?

10. 10 Another Solution u We could choose to track only the surgeon who managed the operation u Record decisions like this in the diagram –Avoids the question being revisited –Specifies precisely what data will be held u Cannot answer question - "In how many operations did surgeon number 12 at hospital number 18 participate?"

11. 11 Annotated Relationship u Graphic 3-4 u As well as annotating the diagram, we should change the column name from Surgeon Number to Managing Surgeon Number

12. 12 Optionality u What if there are no surgeons required for an operation? –e.g. a small cut with antibiotics given u Operation table may have a NULL value for Surgeon Number u To show the difference between optional or mandatory relationships use the convention shown in Graphic 3-5

13. 13 Exercise u Draw the relationships for the rest of the model

14. 14 First Pass u Graphic 3-6 u Checking the diagram will often reveal unsound assumptions and misunderstandings u Conversely, it may increase confidence in the model for both user and designer

15. 15 Operation and Operation Type u Are we sure that each operation can be of only one type? u How would we represent a gall bladder removal and appendectomy operation? –1. Allow only "simple" operations - need a new table for repeating group –2. Allow complex operation types such as "Combined Gall Bladder removal and Appendectomy"

16. 16 Both will Work u Option 2 will be easier to implement u Option 1 will be more elegant –Can ask "list all operations that involved appendectomies"

17. 17 Redundant Lines u Note the Lines connecting Hospital, Operation, and Surgeon tables –line from Hospital to Surgeon –line from Surgeon to Operation –line from Operation to Hospital »Does this line add anything to our knowledge of the business rules?

18. 18 Rules for Removing Lines u Graphic 3-7 u If A derives B and B derives C than an A derives C connecting line is not needed –If B is optional, than we cannot remove the A derives C line –If A derives C provides different information than A derives B we can not remove A derives C

19. 19 Exercise u Remove the remaining Redundant lines from Graphic 3-7

20. 20 Solution u Graphic 3-8

21. 21 Top-Down Approach u Why Normalize at all? Why not just use this Top-down E-R approach? u In practice this is what is most often done, with Normalization being a final check u Using E-R first... –we can start with "What data do we need to keep information about –no need to start with a single overly complex table

22. 22 Terminology u The Relational Models (used with Normalization) were built on three basic concepts: tables, columns, and keys u The E-R Models: Entities, Attributes, and Relationships u Easier to say, "The relationship between a hospital and surgeon", then "the existence of the primary key of Hospital as a foreign key in the Surgeon table"

23. 23 Entities u An entity is the "real world" class of things that a table represents –entities: St. John's Hospital –entity type: Hospital u In practice: Entity means Entity type and Entity Instance (row) for Entity

24. 24 Entities - continued u Some things will need to be represented by more than one entities –e.g. Invoices would be represented by two entities: Invoice Header and Invoice Item –e.g. Quarterly Profit would be derived from sales and expense figures from other entities

25. 25 Multiple "Things" as One Entity u Example... –Preferred Customer –Corporate Customer –Becomes a Customer Type with a Customers Table

26. 26 Entity Naming u The name of an entity must be in the singular. (Exactly the opposite of what it says in the SQL book!) –e.g. Account instead of Accounts u Three reasons: –Consistency - standards –Communication - an 'entity is something we need to keep information about –Compatibility with Relationship Name - (we'll look at this later)

27. 27 Relationships u The lines between the boxes are the relationships between the entities u We name relationships in both directions –"Each company may issue one or more shares" –"Each share must be issued by one company" u Graphic 3-9 show notation were using u Graphic 3-10 shows alternative diagramming notations

28. 28 Exercise u Draw the E-R model that would represent the relationship between a Manager and Departments within his company. A Manager may be in charge of more than one department

29. 29 Solution and More Examples u Graphic 3-11 u Graphic 3-12

30. 30 Suggested Diagramming Tips u Orient your diagram so that the Crows feet are nearer to the bottom of the page u Place Crow's feet on the right u Eliminate crossing lines where possible (but clarity is most important u Duplicate Entities to avoid long relationship lines –Can use a dotted-line to connect the same entity

31. 31 Many-to-Many Relationships u Many-to-Many Relationships are frequently modeled u Graphic 3-13 u How would we implement the relationship using foreign keys?

32. 32 We Can't u We can't hold the key to Qualification in the Employee table because an Employee could have several qualifications u Like wise the Qualification table would need to support multiple Employee Keys u A Normalized model cannot represent many-to-many relationships with foreign keys, yet such relationships certainly exist

33. 33 Representing Many-to-Many u Can't use foreign keys u Can use a table

34. 34 Normalized Many-to-Many u Graphic 3-16 u Whenever we encounter a many-to-many relationship between two entities we represent it with a new entity linked to the two original entities. u The Primary keys of each original table become together become the Primary Key of the new entity ("the resolution entity")

35. 35 Choice of Representation u Conceptual vs. Physical Model u Conversion is not totally mechanical –New Non-key attributes in the resolution entity? –Different Name for the resolution entity? »e.g. instead of Employee-Qualification table we might use "Certifications" table

36. 36 One-to-One Relationships u Should not automatically combine the entities into a single entity u When to split –distinct real-world concepts (e.g. Person- Passport) –Separating attribute groups (e.g. Detail vs. default) –Transferables (e.g. Part type -stored in-Bin)

37. 37 Self-Referencing Relationships u Graphic 3-18 u Each employee may manage one or more employees u Each employee may be managed by one employee –carry the foreign key in the same table as the Primary key –e.g. Manager Id -> Employee Id

38. 38 Attributes u Sometimes show a few attributes to clarify meaning (e.g. Primary, Foreign keys) u Don't show all the attributes, because we want the big picture u Keep in separate lists for each entity

39. 39 More Normalization u If in the process of listing attributes, we find repeating groups or lookup tables –Normalize the design –Update the E-R model

40. 40 Summary u Data models can be presented diagrammatically by using a box to represent each table and a line for each foreign key relationship u This provides a language for "top-down" data models; prior to developing attributes u Many-to-Many relationships are resolved with a "resolution entity"

41. 41 Last Slide - Entity Relationship u Assignment #10 due next week