Copyright  Oracle Corporation, 1999. All rights reserved. 11 ® Introduction to Entities, Attributes, and Relationships Section 02 – Lessons 1,2,3 Use.

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Database Design Lessons 2 & 3 Database Models, Entities, Relationships.
Entity-Relationship (ER) Modeling
Entity Relationship (ER) Modeling
Systems Analysis and Design with UML Version 2.0, Second Edition
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Data Modeling and Entity- Relationship Model II. IST2102 I want a database to maintain departments in my company. Store information about my employees,
System Analysis - Data Modeling
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 8 Structuring System Data Requirements
Database Design Concepts Lecture 7 Introduction to E:R Modelling Identifying Entities.
Modern Systems Analysis and Design Third Edition
APPENDIX C DESIGNING DATABASES
Oracle Academy -Week 1-.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas.
Entity Relationship Modeling Objectives: To illustrate how relationships between entities are defined and refined. To know how relationships are incorporated.
Data Modeling Using the Entity-Relationship Model
IT 244 Database Management System Data Modeling 1 Ref: A First Course in Database System Jeffrey D Ullman & Jennifer Widom.
Module 2: Conceptual Data Modeling with ERD
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Entity Relationship Diagrams
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
Overview of Database Development
Chapter 5 Entity Relationship (ER) Modelling
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 3/1 Copyright © 2004 Please……. No Food Or Drink in the class.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj ER Model Lecture 1 © Akhilesh Bajaj, 2000, 2002, 2003, 2004.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Plug-In T5: Designing Database Applications Business Driven Technology.
© Pearson Education Limited, Chapter 9 Logical database design – Step 1 Transparencies.
1.  An introduction to data modelling  The purpose of data modelling  Modelling data relationships 2.
Chapter 4 Entity Relationship (ER) Modeling.  ER model forms the basis of an ER diagram  ERD represents conceptual database as viewed by end user 
Next Back A-1 Management Information Systems for the Information Age Second Canadian Edition Copyright 2004 The McGraw-Hill Companies, Inc. All rights.
Overview of Database Development Data Modeling and Relational Database Design.
C-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Extended Learning Module.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
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.
IT 21103/41103 System Analysis & Design. Chapter 04 Data Modeling.
Part4 Methodology of Database Design Chapter 07- Overview of Conceptual Database Design Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
Section 04 Lesson 01 Introduction to the Database
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
CS311 Database Management system Somchai Thangsathityangkul 1.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
INTRODUCTION TO DATA MODELING CS 260 Database Systems.
11 Introduction to Entities, Attributes, and Relationships.
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
1 CS 430 Database Theory Winter 2005 Lecture 3: A Fifty Minute Introduction to Data Modeling.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
Data Modeling Using the Entity- Relationship (ER) Model
Business System Development
Introduction to Entities, Attributes, and Relationships
© The McGraw-Hill Companies, All Rights Reserved APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Entity-Relationship Model
CS311 Database Management system
Database Management system
ERD’s REVIEW DBS201.
Chapter 4 Entity Relationship (ER) Modeling
MIS2502: Data Analytics Relational Data Modeling
Presentation transcript:

Copyright  Oracle Corporation, All rights reserved. 11 ® Introduction to Entities, Attributes, and Relationships Section 02 – Lessons 1,2,3 Use the student note section below for further explanation of the slide content.Use the student note section below for further explanation of the slide content. Use your mouse to resize the content pane and read all of the student note section.Use your mouse to resize the content pane and read all of the student note section.

1-2 Copyright  Oracle Corporation, All rights reserved. ® Overview Why conceptual modeling? Introduction of the Key role players: –Entities –Attributes –Relationships Why conceptual modeling? Introduction of the Key role players: –Entities –Attributes –Relationships

1-3 Copyright  Oracle Corporation, All rights reserved. ® Why Create a Conceptual Model? It describes exactly the information needs of the business It describes exactly the information needs of the business It facilitates discussion It facilitates discussion It helps to prevent mistakes, misunderstanding It helps to prevent mistakes, misunderstanding It forms important “ideal system” documentation It forms important “ideal system” documentation It forms a sound basis for physical database design It forms a sound basis for physical database design It is a very good practice with many practitioners It is a very good practice with many practitioners It describes exactly the information needs of the business It describes exactly the information needs of the business It facilitates discussion It facilitates discussion It helps to prevent mistakes, misunderstanding It helps to prevent mistakes, misunderstanding It forms important “ideal system” documentation It forms important “ideal system” documentation It forms a sound basis for physical database design It forms a sound basis for physical database design It is a very good practice with many practitioners It is a very good practice with many practitioners

1-4 Copyright  Oracle Corporation, All rights reserved. ® Between Dream and Reality...

1-5 Copyright  Oracle Corporation, All rights reserved. ® Dream and Reality - Activity Directions: Working in pairs, one student describes his/her "dream house" while the other student attempts to draw it. The pairs can discuss specific details but, the student describing the house is not allowed to see what is being drawn until after time is called. Assessment: Ask volunteer student pairs to describe the discrepancies between what they thought was being described and what was actually drawn. Directions: Working in pairs, one student describes his/her "dream house" while the other student attempts to draw it. The pairs can discuss specific details but, the student describing the house is not allowed to see what is being drawn until after time is called. Assessment: Ask volunteer student pairs to describe the discrepancies between what they thought was being described and what was actually drawn.

1-6 Copyright  Oracle Corporation, All rights reserved. ® Entity Relationship Modeling Models business, not implementation Is a well-established technique Has a robust syntax Results in easy-to- read diagrams…...although they may look rather complex at first sight Models business, not implementation Is a well-established technique Has a robust syntax Results in easy-to- read diagrams…...although they may look rather complex at first sight

1-7 Copyright  Oracle Corporation, All rights reserved. ® Goals of Entity Relationship Modeling Capture all required information Information appears only once Model no information that is derivable from other information already modeled Information is in a predictable, logical place Capture all required information Information appears only once Model no information that is derivable from other information already modeled Information is in a predictable, logical place

1-8 Copyright  Oracle Corporation, All rights reserved. ® Database Types Hierarchical Relational Network ER Model

1-9 Copyright  Oracle Corporation, All rights reserved. ® Entity An Entity is: –“Something” of significance to the business about which data must be known. –A name for the things that you can list. –Usually a noun. Examples: objects, events Entities have instances. An Entity is: –“Something” of significance to the business about which data must be known. –A name for the things that you can list. –Usually a noun. Examples: objects, events Entities have instances.

1-10 Copyright  Oracle Corporation, All rights reserved. ® Entities and Instances PERSON PRODUCT PRODUCT TYPE EMPLOYMENT CONTRACT JOB SKILL LEVEL TICKET RESERVATION PURCHASE ELECTION PRINTER PREFERENCE DOCUMENT VERSION PERSON PRODUCT PRODUCT TYPE EMPLOYMENT CONTRACT JOB SKILL LEVEL TICKET RESERVATION PURCHASE ELECTION PRINTER PREFERENCE DOCUMENT VERSION Mahatma Gandhi 2.5 x 35 mm copper nail nail my previous contract violinist fluent tonight: Hamlet in the Royal the CD I bought yesterday for parliament next fall …...

1-11 Copyright  Oracle Corporation, All rights reserved. ® Entities and Sets dish washer JOB waiter cook waitress manager financial controller porter piano player An entity represents a set of instances that are of interest to a particular business.

1-12 Copyright  Oracle Corporation, All rights reserved. ® Attribute Also represents something of significance to the business Is a single valued property detail of an entity Is a specific piece of information that: –Describes –Quantifies –Qualifies –Classifies –Specifies an entity. Also represents something of significance to the business Is a single valued property detail of an entity Is a specific piece of information that: –Describes –Quantifies –Qualifies –Classifies –Specifies an entity.

1-13 Copyright  Oracle Corporation, All rights reserved. ® Attribute Examples Entity EMPLOYEE CAR ORDER JOB TRANSACTION EMPLOYMENT CONTRACT Entity EMPLOYEE CAR ORDER JOB TRANSACTION EMPLOYMENT CONTRACT Attribute Family Name, Age, Shoe Size, Town of Residence, ,... Model, Weight, Catalog Price, … Order Date, Ship Date, … Title, Description,... Amount, Transaction Date, … Start Date, Salary,...

1-14 Copyright  Oracle Corporation, All rights reserved. ® Practice Exercises Complete the following Practice Exercises in class: 1-1 "Instance or Entity" 1-2 "Guest" Complete the following Practice Exercises in class: 1-1 "Instance or Entity" 1-2 "Guest"

1-15 Copyright  Oracle Corporation, All rights reserved. ® Relationships Also represent something of significance to the business Express how entities are mutually related Always exist between two entities (or one entity twice) Always have two perspectives Are named at both ends Also represent something of significance to the business Express how entities are mutually related Always exist between two entities (or one entity twice) Always have two perspectives Are named at both ends

1-16 Copyright  Oracle Corporation, All rights reserved. ® Relationship Examples EMPLOYEES have JOBS JOBS are held by EMPLOYEES EMPLOYEES have JOBS JOBS are held by EMPLOYEES PRODUCTS are classified by a PRODUCT TYPE PRODUCT TYPE is a classification for a PRODUCT PRODUCTS are classified by a PRODUCT TYPE PRODUCT TYPE is a classification for a PRODUCT PEOPLE make TICKET RESERVATIONS TICKET RESERVATIONS are made by PEOPLE PEOPLE make TICKET RESERVATIONS TICKET RESERVATIONS are made by PEOPLE

1-17 Copyright  Oracle Corporation, All rights reserved. ® JOB waiter cook waitress manager financial controller porter piano player Employees have Jobs Ahmed Jill Adam Maria EMPLOYEE Numerical observation: All EMPLOYEES have a JOB No EMPLOYEE has more than one JOB Not all JOBS are held by an EMPLOYEE Some JOBS are held by more than one EMPLOYEE Numerical observation: All EMPLOYEES have a JOB No EMPLOYEE has more than one JOB Not all JOBS are held by an EMPLOYEE Some JOBS are held by more than one EMPLOYEE Shintaro dish washer

1-18 Copyright  Oracle Corporation, All rights reserved. ® Entity Representation in Diagram Drawn as a “softbox” Name singular Name inside Neither size, nor position has a special meaning Drawn as a “softbox” Name singular Name inside Neither size, nor position has a special meaning EMPLOYEE TICKET RESERVATION JOB ASSIGNMENT JOB ORDER ELECTION During design, entities usually lead to tables.

1-19 Copyright  Oracle Corporation, All rights reserved. ® Attributes in Diagrams * o EMPLOYEE Family Name Address o Birth Date o Shoe Size o JOB Title o Description During design, attributes lead to columns. * * Mandatory attribute, that is, known and available for every instance Optional attribute, that is, unknown or unimportant to know for some instances

1-20 Copyright  Oracle Corporation, All rights reserved. ® Jobs are held by one or more employees An employee has exactly one job has Relationship in Diagrams EMPLOYEE JOB has held by exactly one one or more During design, relationships lead to foreign keys.

1-21 Copyright  Oracle Corporation, All rights reserved. ® has held by EMPLOYEE JOB Relationships in Diagrams

1-22 Copyright  Oracle Corporation, All rights reserved. ®mandatory:mandatory:optional:optional: Relationships in Diagrams

1-23 Copyright  Oracle Corporation, All rights reserved. ® EMPLOYEE JOB Two Perspectives has held by mandatory:mandatory:optional:optional:

1-24 Copyright  Oracle Corporation, All rights reserved. ® Every EMPLOYEE has one and only one JOB One Way has EMPLOYEE JOB held by mandatory:mandatory:optional:optional:

1-25 Copyright  Oracle Corporation, All rights reserved. ® The Other Way has EMPLOYEE JOB held by mandatory:mandatory:optional:optional: A JOB may be held by one or more EMPLOYEES

1-26 Copyright  Oracle Corporation, All rights reserved. ® ” “ Each P split into must be may be one or more Qs One and only one Q “ Each P may be split into one or more Qs ” Reading a Relationship End P split into Q part of

1-27 Copyright  Oracle Corporation, All rights reserved. ® “ Each Q part of ” must be may be one or more Ps One and only one P “ Each Q must be part of exactly one P ” Reading a Relationship End P split into Q part of

1-28 Copyright  Oracle Corporation, All rights reserved. ® “ Each P may be split into one or more Qs ” “ Each Q must be part of exactly one P ” Reading a Relationship End P split into Q part of

1-29 Copyright  Oracle Corporation, All rights reserved. ® Functions Drive Data Business functions are always present. –Explicit –Assumed Business functions need data. An entity, attribute, or relationship may be modeled because: –It is used by a business function. –The business need may arise in the near future. Business functions are always present. –Explicit –Assumed Business functions need data. An entity, attribute, or relationship may be modeled because: –It is used by a business function. –The business need may arise in the near future.

1-30 Copyright  Oracle Corporation, All rights reserved. ® Weather Forecast København Bremen Berlin München Amsterdam Bruxelles Paris Bordeaux 1/-5 7/2 3/-1 8/3 5/-3 4/0 4/1 0/-3 January * * * *

1-31 Copyright  Oracle Corporation, All rights reserved. ® ( Copenhagen ) Bremen Berlin ( Munich ) Bruxelles Paris Bordeaux Amsterdam UK FR DE DK CH NL BE IT LU IR København München ( Brussels )

1-32 Copyright  Oracle Corporation, All rights reserved. ® located in having referring to referred in about Weather Forecast, a Solution WEATHER TYPE * Icon * Description WIND DIRECTION * Icon * Description COUNTRY * Name o Geographical Position CITY * Name o Geographical Position FORECAST * Date o Minimum Temperature o Maximum Temperature o Wind Force referring to referred in subject of

1-33 Copyright  Oracle Corporation, All rights reserved. ® Graphical Elements of ER Diagram Subtype # # Unique identifier ArcArc NontransferabilityNontransferability * * * * o o EntityAttributeRelationship

1-34 Copyright  Oracle Corporation, All rights reserved. ® Summary ER Modeling models information conceptually Based on functional business needs ER Modeling focuses on “what” a business is doing. Not necessarily the “how” Diagrams provide easy means of communication Detailed, but not too much IN CLASS - Complete the Practice Exercises IN CLASS and ONLINE Complete the Quiz for this Chapter. ER Modeling models information conceptually Based on functional business needs ER Modeling focuses on “what” a business is doing. Not necessarily the “how” Diagrams provide easy means of communication Detailed, but not too much IN CLASS - Complete the Practice Exercises IN CLASS and ONLINE Complete the Quiz for this Chapter.