10/10/16

Overview  of  Database  D esign ►

► What

are the entities and relationships in the enterprise? information about these entities and relationships should we store in the database? ► First step, from an informal description to a more precise description ► What are the integrity constraints or business rules that hold? ► A database `schema’ in the ER Model can be represented pictorially (ER diagrams). ► Can map an ER diagram into a relational schema.

BBM371-­‐ Data  Management

► What

Lecture 2: Entity-Relation (ER) Diagrams 11.10.2016

ER  Model  Basics

Keys

►

Entity: Real-world object distinguishable from other objects. An

►

Attribute: Entities have attributes

►

Entity Set: A collection of similar entities.

entity is described (in DB) using a set of attributes. ►

►

Conceptual design: (ER Model is used at this stage.)

►

Underline the key attributes.

e.g. Ali, Ayşe, CS, 371, 201 etc. e.g. Ayşe has an address,Ali has a phone number etc.

e.g., all employees, the set of students, the set of courses etc. entities in an entity set have the same set of attributes. (Until we consider ISA hierarchies, anyway!) name ssn lot ► Each entity set has a key. ► Each attribute has a domain. ►

► All

Employees

1

10/10/16

Keys ►

ER  Model  Basics  ( cont.)

A candidate key is a minimal set of attributes that uniquely identifies each instance of an entity type. For example, the number attribute uniquely identifies an Employee and is a candidate key for the Employee entity type. ►

►

A primary key is a candidate key that is selected to identify each instance of an entity type. The primary key is chosen from a set of candidate keys. For instance, an employee may also have SSN as an attribute.The primary key may be either SSN or number as both are candidate keys. ►

►

A composite key is a key that consists of two or more attributes. For example, a course is uniquely identified only by the department code (22C) and the course number within the department (144). ►

Entity  Sets  in  Relational  D atabases

Attributes ►

custom er _id

An entity is represented by a set of attributes

custom er _str eet

custom er _city

custom er _nam e

2

10/10/16

ER  Model  Basics  ( Contd.)

Relationship  Set  b orrower nam e lot

dnam e did

lot Em ployees

ssn

since

nam e ssn

budget Em ployees

Wor ks_In

Depar tm ents

super -­ visor

subor -­ dinate

Repor ts_To

►

►

Relationship: Association among two or more entities. E.g., Ayşe works in Pharmacy department, Ali takes 371, etc. Relationship Set: Collection of similar relationships. ► An

►

n-ary relationship set R relates n entity sets E1 ... En Same entity set could participate in different relationship sets, or in different “roles” in same set as in Reports_To relationship

Example

Key Constraints ►

►

Consider Works_In: An employee can work in many departments; a dept can have many employees. In contrast, each dept has at most one manager, according to the key constraint on Manages.

since nam e ssn

dnam e lot

Em ployees

1-­to-­1

did Manages

1-­to   Many

budget

Depar tm ents

Many-­to-­1

Many-­to-­Many

3

10/10/16

Match the constraints

Cardinality

3)

I)

1-­to-­1 2)

Many-­to-­1 4)

1-­to   Many

a)

E

R

F

b)

E

R

F

c)

E

R

F

d )

E

R

F

Many-­to-­1

Making  ER  Models ►

To make an ER model you need to identify: ► ► ► ►

Entities Attributes Relationships Cardinality ratios

Entities are things or objects. They are often nouns. Attributes are facts or properties. They are also often nouns. ► Verbs often describe relationships between entities. ►

Example

►

A university consists of a number of departments. Each department offers several courses. A number of modules make up each course. Students enrol in a particular course and take modules towards the completion of that course. Each module is taught by a lecturer from the appropriate department, and each lecturer tutors a group of students

►

E x amp l e b y Natash a Al ech i n a

4

10/10/16

Example  -­‐ entities

Example  -­‐ relationships

A university consists of a number of departments. Each department offers several courses. A number of modules make up each course. Students enrol in a particular course and take modules towards the completion of that course. Each module is taught by a lecturer from the appropriate department, and each lecturer tutors a group of students

►

A university consists of a number of departments. Each department offers several courses. A number of modules make up each course. Students enrol in a particular course and take modules towards the completion of that course. Each module is taught by a lecturer from the appropriate department, and each lecturer tutors a group of students

Example  – ER  D iagram

Example  – ER  D iagram

Entities:   Department,  

Each   department  

Course,   Module,   Lecturer,   Student

Department

Course

Module

Student

Lecturer

offers   several   courses

Offers

Department

Course

Module

Lecturer

Student

5

10/10/16

Example  -­‐ ER  D iagram

Example  -­‐ ER  D iagram

A  number   of   modules   make   up each   courses

Course

Students   enrol   in a   particular   course

Department

Offers

Includes

Module

Department

Offers

Lecturer

Student

Course

Includes

Module

Student

Enrols  In

E n ti ty Rel ati o n sh i p Mo d el l ni g

E n ti ty Rel ati o n sh i p Mo d el l ni g

Example  -­‐ ER  D iagram

Example  -­‐ ER  D iagram

Students   …   take modules

Course

Each   module   is   taught   by a  lecturer

Department

Offers

Includes

Module

E n ti ty Rel ati o n sh i p Mo d el l ni g

Student

Department

Offers

Lecturer

Course

Takes

Enrols  In

Lecturer

Includes

Module

Teaches

Lecturer

Takes

Enrols  In

Student

E n ti ty Rel ati o n sh i p Mo d el l ni g

6

10/10/16

Example  -­‐ ER  D iagram a   lecturer   from   the appropriate  

department

each   lecturer   tutors a  group   of   students

Department

Offers

Course

Example  -­‐ ER  D iagram

Includes

Module

Teaches

Department

Employs

Offers

Lecturer

Course

Takes

Module

Lecturer

Teaches

Takes

Student

Enrols  In

Includes

Employs

Enrols  In

Student

Tutors

E n ti ty Rel ati o n sh i p Mo d el l ni g

E n ti ty Rel ati o n sh i p Mo d el l ni g

Example  -­‐ ER  D iagram

Ternary relationship with Constraint Star s

Department

Offers

Contr acts

Movies

Employs Studios

Course

Includes

Module

Teaches

Lecturer

Can a star be contracted by multiple studios? Can a movie have multiple contracts with a studio? ► Can a star act in multiple movies? ► What is constrained? ► ►

Takes

Enrols  In

Student

Tutors

E n ti ty Rel ati o n sh i p Mo d el l ni g

7

10/10/16

Participation Constraints ►

Weak  Entities

Does every department have a manager?

►

► If

so, this is a participation constraint: the participation of Departments in Manages is said to be total (vs. partial). ► Every Departments entity must appear in an instance of the Manages relationship. since

nam e ssn Em ployees

Manages

► Owner

entity set and weak entity set must participate in a one-to-many relationship set (one owner, many weak entities). ► Weak entity set must have total participation in this identifying relationship set. nam e

dnam e did

lot

A weak entity can be identified uniquely only by considering the primary key of another (owner) entity.

budget

ssn

cost

lot

pnam e

age

Depar tm ents Policy

Em ployees

Dependents

Wor ks_In

since

IS-­‐A  Hierarchy As in C++, or other PLs, attributes are inherited. v If we declare A ISA B, every A entity is also considered to be a B entity. ► Overlap constraints: Can Joe be an Hourly_Emps as well as a Contract_Emps entity? (Allowed/disallowed) ► Covering constraints: Does every Employees entity also have to be an Hourly_Emps or a Contract_Emps entity? (Yes/no) ► Reasons for using ISA: ► To add descriptive attributes specific to a subclass. ► To identify entitities that participate in a relationship.

Aggregation

v

na m e ssn

lot

Em ploy e e s

hourly _ wa ge s

hours _ work e d ISA c ontra c tid

Hourly _ Em ps

Contra c t_ Em ps

►

Used when we have to model a relationship involving (entitity sets and) a relationship set.

ssn

► Aggregation

allows us to treat a relationship set as an entity set for purposes of participation in (other) relationships.

nam e

Monitor s

until

since pbudget

Pr ojects

lot

Em ployees

star ted_on pid

☛ Aggregation vs. ternary relationship: v Monitors is a distinct relationship, with a descriptive attribute. vAlso, can say that each sponsorship is monitored by at most one employee.

dnam e did

Sponsor s

budget Depar tm ents

8

10/10/16

Conceptual  D esign  Using  t he  ER  Model ►

Design choices:

Entity  vs.  Attribute ►

►Should

a concept be modeled as an entity or an attribute? ►Should a concept be modeled as an entity or a relationship? ►Identifying relationships: Binary or ternary? Aggregation? ►

►

Constraints in the ER Model: ►A

lot of data semantics can (and should) be captured. some constraints cannot be captured in ER diagrams.

►But

Entity vs.  Attribute (Contd.) ►

Works_In4 does not allow an employee to work in a department for two or more periods. fr om

nam e ssn

budget Depar tm ents

Wor ks_In4

Em ployees ►

Similar to the problem of wanting to record several addresses for an employee: We want to record several values of the descriptive attributes for each instance of this relationship. Accomplished by introducing new entity set, Duration. ssn

nam e

lot

Em ployees

fr om

►

dnam e

did

did Wor ks_In4

Dur ation

dnam e budget Depar tm ents

to

Depends upon the use we want to make of address information, and the semantics of the data: ► If we have several addresses per employee, address must be an entity (since attributes cannot be set-valued). ► If the structure (city, street, etc.) is important, e.g., we want to retrieve employees in a given city, address must be modeled as an entity (since attribute values are atomic).

Entity  vs.  Relationship

to

lot

Should address be an attribute of Employees or an entity (connected to Employees by a relationship)?

►

First ER diagram OK if a manager gets a separate discretionary budget for each dept. What if a manager gets a discretionary budget that covers all managed depts? ► Redundancy: dbudget stored for each dept managed by manager. ► Misleading: Suggests dbudget associated with departmentmgr combination.

since

nam e ssn

dbudget

lot Em ployees

did

dnam e budget Depar tm ents

Manages2

nam e ssn

lot since Em ployees ISA

Manager s

Manages2

dbudget

did

dnam e budget Depar tm ents

This fixes the pr oblem!

9

10/10/16

Binary  vs.  Ternary  Relationships If each policy is owned by just 1 employee, and each dependent is tied to the covering policy, first diagram is inaccurate. ► What are the additional constraints in the 2nd diagram? ►

ssn

pnam e

lot Em ployees

►

cost pnam e

lot

age

Em ployees

Policies cost

Summary  of  C onceptual  D esign Conceptual design follows requirements analysis, a high-level description of data to be stored

ER model popular for conceptual design ► Constructs

are expressive, close to the way people think about their applications.

Basic constructs: entities, relationships, and attributes (of entities and relationships). ► Some additional constructs: weak entities, ISA hierarchies, and aggregation. ► Note: There are many variations on ER model. ►

“can-supply” P, D “needs” P, and D “deals-with” S does not imply that D has agreed to buy P from S. do we record qty?

Beneficiar y

policyid

►

An example in the other direction: a ternary relation Contracts relates entity sets Parts, Departments and Suppliers, and has descriptive attribute qty. No combination of binary relationships is an adequate substitute: ► How

Better design

► Yields

Previous example illustrated a case when two binary relationships were better than one ternary relationship.

►S

Dependents Pur chaser

►

►

Policies policyid

nam e

age

Dependents

Cover s

Bad design

ssn

Binary  vs.  Ternary  Relationships  ( Contd.)

nam e

Summary  of  ER  (Contd.) ►

Several kinds of integrity constraints can be expressed in the ER model: key constraints, participation constraints, and overlap/covering constraints for ISA hierarchies. Some foreign key constraints are also implicit in the definition of a relationship set. ► Some

constraints (notably, functional dependencies) cannot be expressed in the ER model. ► Constraints play an important role in determining the best database design for an enterprise.

10

10/10/16

Summary  of  ER  (Contd.) ►

ER design is subjective. There are often many ways to model a given scenario! Analyzing alternatives can be tricky, especially for a large enterprise. Common choices include: ► Entity

vs. attribute, entity vs. relationship, binary or n-ary relationship, whether or not to use ISA hierarchies, and whether or not to use aggregation.

►

Ensuring good database design: resulting relational schema should be analyzed and refined further. FD information and normalization techniques are especially useful.

Homework  – cont.   ►

►

Homework ►

“A database will be made to store information about patients in a hospital. On arrival, each patient’s personal details (name, address, and telephone number) are recorded where possible, and they are given an admission number. They are then assigned to a particular ward (Accident and Emergency, Cardiology, Oncology, etc.). In each ward there are a number of doctors and nurses. A patient will be treated by one doctor and several nurses over the course of their stay, and each doctor and nurse may be involved with several patients at any given time.”

End  of  the  second  lecture…

Identify the entities, attributes, relationships, and cardinality ratios from the description. Draw an entity-relationship diagram showing the items you identified.

11