Database design concepts info1408 Lecture 8 Worked example of E:R Modelling.

Slides:



Advertisements
Similar presentations
Database Design: ER Modelling (Continued)
Advertisements

ENTITY RELATIONSHIP MODELLING
Concepts of Database Management Seventh Edition
Chapter 6 Review Questions
Lecture Eleven Entity-Relationship Modelling
Database design concepts info1408 Lecture 8 Worked example of E:R Modelling.
Lecture 10 Conversion to tables Database Design Concepts INFO1408.
Lecture Fourteen Methodology - Conceptual Database Design
Chapter 4 ENTITY-RELATIONSHIP MODELLING.
Data modelling uses two main techniques Entity relationship (E-R) modelling: a top- down approach Normalisation: a bottom-up approach.
Copyright © 2007 Ramez Elmasr and Shamkant B. Navathei Week 3 Outline Overview of Database Design Process Example Database Application (COMPANY) ER Model.
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Enhanced ER modeling techniques Transparencies
Database Design Concepts Info1408
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Database Design Concepts Lecture 7 Introduction to E:R Modelling Identifying Entities.
Chapter 4 Entity-Relationship modeling Transparencies © Pearson Education Limited 1995, 2005.
Relational Databases What is a relational database? What would we use one for? What do they look like? How can we describe them? How can you create one?
CSC271 Database Systems Lecture # 21. Summary: Previous Lecture  Phases of database SDLC  Prototyping (optional)  Implementation  Data conversion.
Entity-Relationship modeling Transparencies
Entity-relationship Modeling Transparencies 1. ©Pearson Education 2009 Objectives How to use ER modeling in database design. The basic concepts of an.
2.3 Organising Data for Effective Retrieval
Conceptual Design Lecture - 2 Database Development.
Chapter 5 Entity–Relationship Modeling
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model.
Database Design Principles – Lecture 3
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Data Modeling IST210 Class Lecture.
Entity-Relationship (ER) Modelling ER modelling - Identify entities - Identify relationships - Construct ER diagram - Collect attributes for entities &
CSC271 Database Systems Lecture # 25. Summary: Previous Lecture  Structural constraints  Multiplicity  Cardinality  Participation  Connection traps.
Initial Design of Entity Types for the COMPANY Database Schema Based on the requirements, we can identify four initial entity types in the COMPANY database:
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
ERM – A Worked Example. Objectives We will use a simple scenario to: identify the entities involved Identify the relationships between the entities (if.
Database Design – Lecture 4 Conceptual Data Modeling.
Lecture 03 Entity-Relationship Diagram. Chapter Outline.
Multiplication Facts. 9 6 x 4 = 24 5 x 9 = 45 9 x 6 = 54.
MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj ER Model Lecture 2 © Akhilesh Bajaj, 2000, 2002, 2003, 2004,
Data Modeling Using the Entity- Relationship (ER) Model.
HNDComputing – DeMontfort University  DeMontfort University 2011 Entity Relationship Modelling (continued) wk4 Database Design ConceptsDatabase Design.
CSC271 Database Systems Lecture # 23. Summary: Previous Lecture  Database design using ER modeling  Concepts of ER model  Entities  Relationships.
© Shamkant B. Navathe CC Enhanced Entity-Relationship Copyright © 2004 Ramez Elmasri and Shamkant Navathe.
Data Flow Diagrams. A diagram which shows the movement of data in a system.
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.
BIS 245 OUTLET Peer Educator/ bis245outlet.com FOR MORE CLASSES VISIT
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Lecture # 16 July 26,2012 Data Modeling using the Entity Relationship.
Data Modeling Using the Entity- Relationship (ER) Model
Week 03 – ER Diagram INFOSYS 222.
Entity-Relationship Model
Chapter # 3 Data Modeling Using the Entity-Relationship (ER) Model
Session 2 Welcome: The sixth learning sequence
Week 02 - Introduction to Data Modelling
Enhanced ER Modeling Transparencies
Entity-Relationship Modelling
Chapter 7 Entity-Relationship Model
BIS 245 Possible Is Everything/snaptutorial.com
Order Database – ER Diagram
Data Modelling Introduction
Entity-Relationship Modeling "Extended"
Entity-Relationship Modelling
IST 318 Database Administration
Initial Design of Entity Types: EMPLOYEE, DEPARTMENT, PROJECT, DEPENDENT Gender.
CHAPTER 2 - Database Requirements and ER Modeling
Entity-Relationship Modeling "Extended"
Entity-Relationship Modeling "Extended"
Presentation transcript:

Database design concepts info1408 Lecture 8 Worked example of E:R Modelling

Objectives We will use a simple scenario We will identify the entities Identify the relationships between the entities ( if any) For each relationship the multiplicity ( or degree) and optionality will be determined

To create an E:R Model You would use the results of your fact finding to identify the entities ( as we did last week) 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. The cinema show films. A film is shown several times over a week ( or more) known as a showing. Each film can have several showings. Members book tickets for a particular showing Identify the entities

Each entity is represented as a Box

Refer back to the scenario and identify the relationships The cinema show 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?

A film is shown several times over a week ( or more) and in several of the clubs cinemas. Each film can have several 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?

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?

Add to diagram

Summary The many to many relationships are not appropriate to the final design- we will look at what to do with them next week. We have taken entities and identified the relationships between the entities. Relationships have been described and recorded using the prescribed notation.

References Data Analysis for database Design By D R Howe