Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.

Slides:



Advertisements
Similar presentations
Chapter # 4 BIS Database Systems
Advertisements

Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model Chapter Four DAVID M. KROENKE and DAVID J. AUER DATABASE CONCEPTS, 3 rd Edition.
Database Systems: Design, Implementation, and Management Tenth Edition
Alternative Approach to Systems Analysis Structured analysis
Chapters 7 & 9 System Scope
Copyright Irwin/McGraw-Hill Data Modeling Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
System Analysis - Data Modeling
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Entity Relationship Diagrams Basic Elements and Rules.
Fundamentals, Design, and Implementation, 9/e Chapter 3 Entity-Relationship Data Modeling: Process and Examples Instructor: Dragomir R. Radev Fall 2005.
Review Questions What is data modeling? What is the actual data model that is created called? Data modeling is a technique for organizing and documenting.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Entity Relationship Diagrams
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Copyright Irwin/McGraw-Hill Data Modeling Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 2.
Lesson-19 Data Modeling and Analysis
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 8 Structuring System Data Requirements
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Supplemental Material Data Modeling and Analysis.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
BIS310: Week 7 BIS310: Structured Analysis and Design Data Modeling and Database Design.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Trisha Cummings.  Most people involved in application development follow some kind of methodology.  A methodology is a prescribed set of processes through.
Class Agenda – 04/04/2006 Discuss database modeling issues
Copyright Irwin/McGraw-Hill Data Modeling Introduction  The presentation will address the following questions:  What is systems modeling and what.
Entity-Relationship modeling Transparencies
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.
Entity-relationship Modeling Transparencies 1. ©Pearson Education 2009 Objectives How to use ER modeling in database design. The basic concepts of an.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
1 CSE323 การวิเคราะห์และออกแบบระบบ (Systems Analysis and Design) Lecture 05: Data Modeling and Analysis.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
Copyright (c) 2014 Pearson Education, Inc. Introduction to Databases.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
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 
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Database Design – Lecture 5 Conceptual Data Modeling – adding attributes.
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
Databases Illuminated Chapter 3 The Entity Relationship Model.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 4 ENTITY RELATIONSHIP (ER) MODELING Instructor Ms. Arwa Binsaleh 1.
Database Design – Lecture 4 Conceptual Data Modeling.
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Levels of Database Modeling High degree of abstraction Conceptual model User view 1 User view 2 Implementa- tion model Physical model Medium degree of.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
MBI 630: Week 9 Conceptual Data Modeling and Designing Database 6/10/2016.
C_ITIP211 LECTURER: E.DONDO. Unit 4 : DATA MODELING.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
TMC2034 Database Concept and Design
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Lecture on Data Modeling and Analysis
Chapter 9 Structuring System Data Requirements
System Design (Relationship)
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Review of Week 1 Database DBMS File systems vs. database systems
Chapter 4 Entity Relationship (ER) Modeling
Entity-Relationship Diagram (ERD)
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Data Modeling Entity - Relationship Models

Models Used to represent unstructured problems A model is a representation of reality Logical models  show what a system ‘is’ or ‘does’.  implementation-independent;  depict business requirements Physical models –show not only what a system ‘is’ or ‘does’, but also how the system is physically and technically implemented. –implementation-dependent –depict technical requirements

Data modeling  is a technique for defining business requirements for a database. technique for organizing and documenting a system’s DATA. purpose of data modeling - organize data in a way that is flexible and adaptable to unanticipated business requirements

Entity Relationship Diagram (ERD). One method of data modeling Several notations –Chen –Martin –Bachman

Entities –A concept to abstractly represent all instances of a group of similar ‘things’ –class of persons, places, objects, events, or concepts about which we need to capture and store data. –entity instance is a single occurrence of an entity.

Attributes descriptive property or characteristic of an entity The values for each attribute are defined in terms of three properties: data type, domain, and default –data type for an attribute defines what class of data can be stored in that attribute –domain of an attribute defines what values an attribute can legitimately take on. –default value for an attribute is that value which will be recorded if not specified by the user.

Keys Every entity must have an identifier or key –An key is an attribute, or a group of attributes, which assumes a unique value for each entity instance –A group of attributes that uniquely identifies an instance of an entity is called a concatenated key A primary key is that candidate key which will most commonly be used to uniquely identify a single entity instance. Any candidate key that is not selected to become the primary key is called an alternate key.

Relationships Entities interact with, and impact one another via relationships to support the business mission. relationship is a natural business association that exists between one or more entities.  verb phrase describes the relationship. –All relationships are implicitly bidirectional, meaning that they can interpreted in both directions.

Cardinality: defines the minimum and maximum number of occurrences of one entity for a single occurrence of the related entity

Degree  The degree of a relationship is the number of entities that participate in the relationship. –A binary relationship has a degree = 2, because two different entities participated in the relationship  Relationships may also exist between different instances of the same entity. This is called a recursive relationship  :.

Associative Entity entity that inherits its primary key from more than one other entity (parents). Each part of that concatenated key points to one and only one instance of each of the connecting entities.

Generalization: technique wherein the attributes that are common to several types of an entity are grouped into their own entity, called a supertype. entity supertype will have one or more one-to-one relationships to entity subtypes. These relationships are sometimes called IS A relationships

Subtype An entity subtype is an entity whose instances inherit some common attributes from an entity supertype, and then add other attributes that are unique to an instances of the subtype. –The subtypes not only inherit the attributes, but also the data types, domains, and defaults of those attributes. –In addition to inheriting attributes, subtypes also inherit relationships to other entities.  An entity can be both a supertype and subtype.

CASE  Data models are stored in the repository.  In a sense, the data model is metadata – that is, data about the business’ data.  Computer-aided systems engineering (CASE) technology, provides the repository for storing the data model and its detailed descriptions.