Entity Relationship Diagrams Basic Elements and Rules.

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Copyright 2001 Prentice-Hall, Inc. Object Oriented Aproach to System Requirements: Process Modeling 7.1 Chapter 7.
Modern Systems Analysis and Design Third Edition
Systems Development Life Cycle
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
ISMT221 Information Systems Analysis and Design Entity-Relationship Diagram Lab 4 Tony Tam.
System Analysis - Data Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 10 Structuring System Requirements: Conceptual Data Modeling.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Entity Relationship Diagrams
Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Chapter 8 Structuring System Data Requirements
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Modern Systems Analysis and Design Third Edition
Entity Relationship Diagrams
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Entity Relationship Modeling Objectives: To illustrate how relationships between entities are defined and refined. To know how relationships are incorporated.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Segment 5 Database Review International Islamic University Chittagong Campus.
Data Modeling ERM ERD.
Chapter 8 Structuring System Data Requirements
Business Process Modeling
Chapter 8 Structuring System Data Requirements
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 8 Structuring System Data Requirements
Copyright (c) 2014 Pearson Education, Inc. Introduction to Databases.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Structuring System Requirements: Conceptual Data Modeling 7.1.
Conceptual Data Modeling. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.
Chapter 9 Structuring System Data Requirements. Objectives:  Define key data modeling terms.  Draw entity-relationship (E-R) and class diagrams to represent.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Entity Relationship Diagram. Introduction Definition: Entity-relationship diagram is a data-modeling technique that visualises entities, the attributes.
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
CIS 210 Systems Analysis and Development Week 6 Part I Structuring Systems Data Requirements,
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
C_ITIP211 LECTURER: E.DONDO. Unit 4 : DATA MODELING.
Entity Relationship Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
Modern Systems Analysis and Design Third Edition
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Entity Relationship Diagrams
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 9 Structuring System Data Requirements
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Modern Systems Analysis and Design Third Edition
Review of Week 1 Database DBMS File systems vs. database systems
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Entity Relationship Diagrams Basic Elements and Rules

Introduction to Entity- Relationship (E-R) Modeling  Notation uses three main constructs Data entities Relationships Attributes  Entity-Relationship (E-R) Diagram A detailed, logical representation of the entities, associations and data elements for an organization or business 10.2

Entity-Relationship (E-R) Modeling Key Terms  Entity A person, place, object, event or concept in the user environment about which the organization wishes to maintain data Represented by a rectangle in E-R diagrams  Entity Type A collection of entities that share common properties or characteristics  Attribute A named property or characteristic of an entity that is of interest to an organization 10.3

Entity-Relationship (E-R) Modeling Key Terms  Candidate keys and identifiers Each entity type must have an attribute or set of attributes that distinguishes one instance from other instances of the same type Candidate key  Attribute (or combination of attributes) that uniquely identifies each instance of an entity type

Examples  Identify a few entity types, instances, attributes and candidate keys for: DePaul Campus Connect Registration System Illinois Bureau of Motor Vehicles System Amazon.com Product Information System

Depicting Entities and Attributes  Draw a portion of the ERD for each of these systems: DePaul Campus Connect Registration System Illinois Bureau of Motor Vehicles System Amazon.com Product Information System

Conceptual Data Modeling and the E-R Diagram  Goal Capture as much of the meaning of the data as possible  If you know the rules of normalization, referential integrity, foreign keys, etc., this is good but not as important now. It is much more important to get the organizational data model correct, i.e. to understand the actual data requirements for the organization.  Result A better design that is scalable and easier to maintain

Entity-Relationship (E-R) Modeling Key Terms  Identifier A candidate key that has been selected as the unique identifying characteristic for an entity type Selection rules for an identifier 1.Choose a candidate key that will not change its value 2.Choose a candidate key that will never be null 3.Avoid using intelligent keys 4.Consider substituting single value surrogate keys for large composite keys

Entity-Relationship (E-R) Modeling Key Terms  Relationship An association between the instances of one or more entity types that is of interest to the organization Association indicates that an event has occurred or that there is a natural link between entity types Relationships are always labeled with verb phrases

Cardinality  The number of instances of entity B that can be associated with each instance of entity A  Minimum Cardinality The minimum number of instances of entity B that may be associated with each instance of entity A This is also called “modality”.  Maximum Cardinality The maximum number of instances of entity B that may be associated with each instance of entity A

Naming and Defining Relationships  Relationship name is a verb phrase  Avoid vague names  Guidelines for defining relationships Definition explains what action is being taken and why it is important Give examples to clarify the action Optional participation should be explained Explain reasons for any explicit maximum cardinality

Naming and Defining Relationships  Guidelines for defining relationships Explain any restrictions on participation in the relationship Explain extent of the history that is kept in the relationship Explain whether an entity instance involved in a relationship instance can transfer participation to another relationship instance 10.12