ERM – A Worked Example. Objectives We will use a simple scenario to: identify the entities involved Identify the relationships between the entities (if.

Slides:



Advertisements
Similar presentations
Banking Business Scenario
Advertisements

Complex entities and relationships Case examples are from the book: Lars Fank Databaser Teori og Praksis ISBN
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Chapter 4 Entity Relationship (E-R) Modeling
Entity Relationship (ER) Modeling
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Database design concepts info1408 Lecture 8 Worked example of E:R Modelling.
Database design concepts info1408 Lecture 8 Worked example of E:R Modelling.
Lecture 10 Conversion to tables Database Design Concepts INFO1408.
Data modelling uses two main techniques Entity relationship (E-R) modelling: a top- down approach Normalisation: a bottom-up approach.
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Database Design Concepts Lecture 7 Introduction to E:R Modelling Identifying Entities.
Entity-Relationship Design
Entity-Relationship modeling Transparencies
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
2.3 Organising Data for Effective Retrieval
Chapter 5 Entity Relationship (ER) Modelling
Conceptual Design Lecture - 2 Database Development.
Chapter 5 Entity–Relationship Modeling
Principles of Database Systems With Internet and Java Applications Today’s Topic Chapter 2: Representing Information with Data Models The lecture notes.
Data Modelling – ERD Entity Relationship Diagram’s Entity Relationship Diagrams and how to create them. 1.
Concepts and Terminology Introduction to Database.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model.
Database Design Principles – Lecture 3
1.  An introduction to data modelling  The purpose of data modelling  Modelling data relationships 2.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Chapter 4 Entity Relationship (ER) Modeling.  ER model forms the basis of an ER diagram  ERD represents conceptual database as viewed by end user 
1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis activity Janice Regan,
DeSiamorePowered by DeSiaMore1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
1 A Demo of Logical Database Design. 2 Aim of the demo To develop an understanding of the logical view of data and the importance of the relational model.
3 & 4 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Keys Consists of one or more attributes that determine other.
Entity-Relationship (E-R) Diagrams
An Entity Relationship (ER) Diagram is a graphic that shows the interrelationship between entities in a database.
Description and exemplification of entity-relationship modelling.
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
In this session, you will learn to: Map an ER diagram to a table Objectives.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 4 ENTITY RELATIONSHIP (ER) MODELING Instructor Ms. Arwa Binsaleh 1.
Database Design & Implementation Workshop 4 – Drawing ER Diagrams
Database Design – Lecture 4 Conceptual Data Modeling.
Information Access Mgt09/12/971 Entity-Relationship Design Information Level Design.
Multiplication Facts. 9 6 x 4 = 24 5 x 9 = 45 9 x 6 = 54.
HNDComputing – DeMontfort University  DeMontfort University 2011 Entity Relationship Modelling (continued) wk4 Database Design ConceptsDatabase Design.
Data Flow Diagrams. A diagram which shows the movement of data in a system.
EntityRelationshipDiagrams. Entity Relationship Models The E-R (entity-relationship) data model views the real world as a set of basic objects (entities)
Multiplication Facts. 2x2 4 8x2 16 4x2 8 3x3.
Multiplication Facts Review: x 1 = 1 10 x 8 =
Database -Entity-Relationship Model 2012/03/05.
Data Flow Diagrams Level 1 and Level 0 System Design.
Multiplication Facts All Facts. 0 x 1 2 x 1 10 x 5.
Chapter 3: Modeling Data in the Organization
Data Modeling Using the Entity- Relationship (ER) Model
Entity-Relationship Model
COP Introduction to Database Structures
Multiplication Facts.
Tables and Their Characteristics
Entity-Relationship Modelling
Multiplication Facts.
Order Database – ER Diagram
Data Modelling Introduction
Database Systems: Design, Implementation, and Management Tenth Edition
Entity-Relationship Modelling
Multiplication Facts.
Chapter 4 Entity Relationship (ER) Modeling
What about −(−6) ? What quantity is in the box?.
Presentation transcript:

ERM – A Worked Example

Objectives We will use a simple scenario to: identify the entities involved Identify the relationships between the entities (if any) Identify the multiplicity (or degree) Determine the optionality of the relationships between entities

To create an E:R Model You would use the results of your fact finding to identify the entities In this case we will use a scenario Identify the entities from the scenario

The Scenario A small Cinema club runs a number of cinemas throughout the region. Each cinema can show various films at several daily showings over several days/weeks/months depending on the popularity of the film. Members book tickets for a particular showing Identify the entities

A small Cinema club runs a number of cinemas throughout the region. Each cinema can show various films at several daily showings. Members book tickets for a particular Showing.

Each entity is represented as a Box

Refer back to the scenario and identify the relationships The cinema shows films. Therefore there is a relationship between cinema and film Shown by a line- named shown at

Identify the properties of the relationship How many cinemas can a film be shown at? How many films can a cinema show? Does a cinema have to show a film in order to be on our database as a cinema? Does a film have to be shown at a cinema in order to be on our database?

How many cinemas can a film be shown at? Many How many films can a cinema show? Many So the relationship is many to many Does a cinema have to show a film in order to be on our database as a cinema? No- optional Does a film have to be shown at a cinema in order to be on our database? Yes- mandatory

Each cinema can show various films at several daily showings..

Showing and film Relationship name-screens A showing shows how many films? A film can have how many a showings? A film must have a showing to be on database? A showing must have a film to show to be on the database?

A showing shows how many films? 1 A film can have how many a showings? Many A film must have a showing to be on database? Yes-mandatory A showing must have a film to show to be on the database? Yes -Mandatory

Add to existing diagram

Members book tickets for a particular showing How many bookings can a member make for a showing? A Showing has bookings made by how many members? A showing must have a booking ? A member must have made a booking?

How many bookings can a member make for a showing? many A Showing has bookings made by how many members? many A showing must have a booking ? No- Optional A member must have made a booking? No -optional

Add to diagram

Important! The diagram that has been produced contains many to many relationships Many to many relationships cannot be implemented in a relational database How to deal with this problem will be addressed in the next session.

References Data Analysis for database Design By D R Howe