1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Chapter 6: Entity-Relationship Model (part I)
Analysis Modeling.
1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.
Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.
Chapter 6 Methodology Logical Database Design for the Relational Model Transparencies © Pearson Education Limited 1995, 2005.
LIS 557 Database Design and Management William Voon Michael Cole Spring '04.
Databases Revision.
Modeling Data The Entity Relationship Model (ER) For Database Design.
CS34311 The Entity- Relationship Model Part II.. CS34312 Database Design Stages Application Requirements Conceptual Design Logical Design Physical Design.
Slides adapted from A. Silberschatz et al. Database System Concepts, 5th Ed. Entity-Relationship Model Database Management Systems I Alex Coman, Winter.
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 8 Structuring System Data Requirements
1 Data Modelling Which data to include in the database.
Murali Mani The Entity- Relationship Model. Murali Mani Database Design Stages Application Requirements Conceptual Design Logical Design Physical Design.
Modeling & Designing the Database
Class Number – CS 304 Class Name - DBMS Instructor – Sanjay Madria Instructor – Sanjay Madria Lesson Title – ER Model.
Oracle Academy -Week 1-.
ER Modeling Case Studies
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 3 Data Modeling Using the Entity-Relationship (ER) Model.
ICOM 5016 – Introduction to Database Systems Lecture 4 Dr. Manuel Rodriguez Department of Electrical and Computer Engineering University of Puerto Rico,
Data Modeling ERM ERD.
Dr. Mohamed Osman Hegaz1 Conceptual data base design: The conceptual models: The Entity Relationship Model.
Entities and Attributes
1 Introduction to modeling Relational modelling Slides for this part are based on Chapters 11 from Halpin, T. & Morgan, T. 2008, Information Modeling and.
Database Management System Lecture 6 The Relational Database Model – Keys, Integrity Rules.
1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.
Principles of Database Systems With Internet and Java Applications Today’s Topic Chapter 2: Representing Information with Data Models The lecture notes.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
Concepts and Terminology Introduction to Database.
Principles Graphical Languages Modeling Constraints
Database Systems Lecture # 7 8 th Feb, Conceptual and Logical Design Person buys Product name pricenamessn Conceptual Model: Relational Model: (plus.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
Methodology - Conceptual Database Design
1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.
CS 3630 Database Design and Implementation. Assignment 1 2 What is 3630?
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Database Application Design and Data Integrity AIMS 3710 R. Nakatsu.
Database Management Systems MIT Lesson 02 – Database Design (Entity Relationship Diagram) By S. Sabraz Nawaz.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
1 Introduction to modeling Object-role modelling (ORM) Slides for this part are based on Chapters 3-7 from Halpin, T. & Morgan, T. 2008, Information Modeling.
1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT.
Data Modelling Using Entity-Relationship (ER) Model
DES715 – Database Design Conceptual design. Database Life Cycle Database initial study Database design Implementation Testing Operation Maintenance.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
Methodology - Logical Database Design. 2 Step 2 Build and Validate Local Logical Data Model To build a local logical data model from a local conceptual.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
ENTITY RELATIONSHIP DIAGRAM. Objectives Define terms related to entity relationship modeling, including entity, entity instances, attribute, relationship.
The interplay of mandatory role and set-comparison constraints Dr. Peter Bollen School of Business and Economics Maastricht University, the Netherlands.
Lecture # 11 & 12 (First Exam) Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
COP Introduction to Database Structures
Databases (CS507) CHAPTER 7.
Data Modeling Using the ERD
Methodology Logical Database Design for the Relational Model
Entity-Relationship Model
CS 3630 Database Design and Implementation
Conceptual data modeling
Guidelines Towards Good Design
The Entity-Relationship Model
Entity Relationship Diagrams
Objective Solve equations in one variable that contain variable terms on both sides.
Kindergarten Lessons 5-8
Objective Solve equations in one variable that contain variable terms on both sides.
From conceptual to relational data model
Database Management system
Presentation transcript:

1 CONCEPTUAL SCHEMA DESIGN PROCESS Information Processing and Technology, 2001 Yr 12 IPT

Last Lesson §Value and Cardinality constraints limit the value an entity type can have. §Frequency constraints limit the number of times a role can be played by its associated entities. §Roles are either mandatory or optional.

Add other constraints: value, cardinality, frequency and mandatory. Design Cycle State Elementary Facts Entity types that should be combined and derivation Draw Conceptual Schema Diagram Add Uniqueness Constraints

Step 4. Add Uniqueness Constraints §Uniqueness constraints are specified in a conceptual schema to avoid data redundancy. §The relations are: l one to one l one to many l many to one l many to many

One to one §Does each friend have only one phone number? §Does each phone number have only one friend? Phone (number) Friend (name) has One friend has one phone number Yes

One to many §Does each party have only one minister? §Does each minister have only one party? Minister (name) Party (name) has One Party has many ministers Yes No

Many to one §Does each student have only one house? §Does each house have only one student? House (name) Student (name) has Many students have one house Yes No

Many to many §Does each teacher have only one subject? §Does each subject have only one teacher? Subject (name) Teacher (name) has Many teachers have many subjects. No

Ternary relationships (check this is always true) Subject (name) Student (name) stud ies Grade (letter) received

Design Cycle 1.State Elementary Facts 3.Entity types that should be combined and derivation. 5.Add other constraints: value, cardinality, frequency and mandatory. 6.Perform Population and Final Checks. 4.Add Uniqueness Constraints. 2.Draw Conceptual Schema Diagram

6. Perform Population and Final Checks. §The final Step of the CS Design Phase. §This step must check that the schema is: l internally consistent (no contradicting constraints) l externally consistent (population check) l free of redundancy (undetected derivations) l complete (fulfils original requirements and represents the UoD)

The End.