ENTITYRELATIONSHIP MODELLING 2 Objectives How to use EntityRelationship

ENTITY-RELATIONSHIP MODELLING

2 Objectives: • How to use Entity–Relationship (ER) modelling in database design. • Basic concepts associated with ER model. • Diagrammatic technique for displaying ER model using Unified Modelling Language (UML). • How to identify and resolve problems with ER models called connection traps. • How to build an ER model from a requirements specification.

3 ER diagram of Branch user views of Dream. Home

4 Concepts of the ER Model • Entity types • Relationship types • Attributes

5 Entity Type • Entity type ▫ Group of objects with same properties, identified by enterprise as having an independent existence. • Entity occurrence ▫ Uniquely identifiable object of an entity type.

6 Examples of Entity Types

7 ER diagram of Staff and Branch entity types

8 Relationship Types • Relationship type ▫ Set of meaningful associations among entity types. • Relationship occurrence ▫ Uniquely identifiable association, which includes one occurrence from each participating entity type.

9 Semantic net of Has relationship type

10 ER diagram of Branch Has Staff relationship

11 Relationship Types • Degree of a Relationship ▫ Number of participating entities in relationship. • Relationship of degree : ▫ two is binary ▫ three is ternary ▫ four is quaternary.

12 Binary relationship called POwns Ternary relationship called Registers

13 Quaternary relationship called Arranges

14 Relationship Types • Recursive Relationship ▫ Relationship type where same entity type participates more than once in different roles. • Relationships may be given role names to indicate purpose that each participating entity type plays in a relationship.

15 Recursive relationship called Supervises with role names

16 Entities associated through two distinct relationships with role names

17 Attributes • Attribute ▫ Property of an entity or a relationship type. • Attribute Domain ▫ Set of allowable values for one or more attributes.

18 Attributes types: • Simple Attribute ▫ Attribute composed of a single component with an independent existence. • Composite Attribute ▫ Attribute composed of multiple components, each with an independent existence. • Single-valued Attribute ▫ Attribute that holds a single value for each occurrence of an entity type.

19 • Multi-valued Attribute ▫ Attribute that holds multiple values for each occurrence of an entity type. • Derived Attribute ▫ Attribute that represents a value that is derivable from value of a related attribute, or set of attributes, not necessarily in the same entity type.

20 Keys • Candidate Key ▫ Minimal set of attributes that uniquely identifies each occurrence of an entity type. • Primary Key ▫ Candidate key selected to uniquely identify each occurrence of an entity type. • Composite Key ▫ A candidate key that consists of two or more attributes.

21 ER diagram of Staff and Branch entities and their attributes

22 Entity Type • Strong Entity Type ▫ Entity type that is not existence-dependent on some other entity type. • Weak Entity Type ▫ Entity type that is existence-dependent on some other entity type.

23 Strong entity type called Client and weak entity type called Preference

24 Relationship called Advertises with attributes

25 Structural Constraints • Main type of constraint on relationships is called multiplicity. • Multiplicity - number (or range) of possible occurrences of an entity type that may relate to a single occurrence of an associated entity type through a particular relationship. • Represents policies (called business rules) established by user or company.

26 Structural Constraints • The most common degree for relationships is binary. • Binary relationships are generally referred to as being: ▫ one-to-one (1: 1) ▫ one-to-many (1: *) ▫ many-to-many (*: *)

27 Semantic net of Staff Manages Branch relationship type

28 Multiplicity of Staff Manages Branch (1: 1) relationship

29 Semantic net of Staff Oversees Property. For. Rent relationship type

30 Multiplicity of Staff Oversees Property. For. Rent (1: *) relationship type

31 Semantic net of Newspaper Advertises Property. For. Rent relationship type

32 Multiplicity of Newspaper Advertises Property. For. Rent (*: *) relationship

33 Structural Constraints • Multiplicity for Complex Relationships ▫ Number (or range) of possible occurrences of an entity type in an n-ary relationship when other (n-1) values are fixed.

34 Semantic net of ternary Registers relationship with values for Staff and Branch entities fixed

35 Multiplicity of ternary Registers relationship

36 Summary of multiplicity constraints

37 Structural Constraints • Multiplicity is made up of two types of restrictions on relationships: cardinality and participation. ▫ Cardinality Describes maximum number of possible relationship occurrences for an entity participating in a given relationship type. ▫ Participation Determines whether all or only some entity occurrences participate in a relationship.

38 Multiplicity as cardinality and participation constraints

39 Problems with ER Models • Problems may arise when designing a conceptual data model called connection traps. • Often due to a misinterpretation of the meaning of certain relationships. • Two main types of connection traps are called fan traps and chasm traps.

40 Problems with ER Models • Fan Trap ▫ Where a model represents a relationship between entity types, but pathway between certain entity occurrences is ambiguous. • Chasm Trap ▫ Where a model suggests the existence of a relationship between entity types, but pathway does not exist between certain entity occurrences.

41 An Example of a Fan Trap • Occurred when two or more 1. . * relationship came from the same entity

42 Semantic Net of ER Model with Fan Trap • At which branch office does staff number SG 37 work?

43 Restructuring ER model to remove Fan Trap

44 Semantic Net of Restructured ER Model with Fan Trap Removed • SG 37 works at branch B 003.

45 An Example of a Chasm Trap

46 Semantic Net of ER Model with Chasm Trap • At which branch office is property PA 14 available?

47 ER Model restructured to remove Chasm Trap

48 Exercise • Given the following descriptions, create an appropriate ER diagram: Each company operates four departments, and each department belongs to one company. Each department employs one or more employees, and each employee is employed by one department. Each of the employees may or may not have one or more dependants, and each dependant belongs to one employee. Each employee may or may not have an employment history. • You are required to create ER model of the data requirements for a company that specializes in IT training. The Company has twelve instructors and can handle up to one hundred trainees per training session. The Company offers five advanced technology courses, each of which is taught by a teaching team of two or more instructors. Each instructor is assigned to a maximum of two teaching teams or may be assigned to do research. Each trainee undertakes one advanced technology course per training session.

49 Semantic Net of Restructured ER Model with Chasm Trap Removed