BIS 360 – Lecture Six (Part 2) Conceptual Data Modeling (Chapter 10 and partial Chapter 12)

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Entity Relationship (E-R) Modeling Hachim Haddouti
Concepts of Database Management Seventh Edition Chapter 6 Database Design : ERD Model.
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.
Systems Development Life Cycle
Data Modeling is an Analysis Activity
1 © Prentice Hall, 2002 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred.
Modeling the Data: Conceptual and Logical Data Modeling
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Entity-Relation Modeling Hun Myoung Park, Ph.D., Public Management and Policy Analysis Program Graduate School of International Relations International.
ISMT221 Information Systems Analysis and Design Entity-Relationship Diagram Lab 4 Tony Tam.
MIS 210 Fall 2004Sylnovie Merchant, Ph. D. Lecture 4: Data Modeling Process Modeling MIS 210 Information Systems I.
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.
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.
Database Systems: Design, Implementation, & Management, 5 th Edition, Rob & Coronel 1 Data Models: Degrees of Data Abstraction l Modified ANSI/SPARC Framework.
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
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 3 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Importance of data modeling Importance of data modeling Write good.
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.
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.
1 © Prentice Hall, 2002 CMIS564: E/R Modeling Dr. Bordoloi Based on Chapter 3; Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
3.1 CSIS 3310 Chapter 3 The Entity-Relationship Model Conceptual Data Modeling.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Data Modeling ERM ERD.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
Business Process Modeling
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Structuring System Requirements: Conceptual Data Modeling 7.1.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
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.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Data Modeling Using the Entity-Relationship (ER) Model.
Data modeling using the entity-relationship model Chapter 3 Objectives How entities, tuples, attributes and relationships among entities are represented.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
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.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Modeling the Data: Conceptual and Logical Data Modeling.
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.
IS 4420 Database Fundamentals Chapter 3: Modeling Data in the Organization Leon Chen.
C_ITIP211 LECTURER: E.DONDO. Unit 4 : DATA MODELING.
Entity Relationship Modeling
Business System Development
TMC2034 Database Concept and Design
Tables and Their Characteristics
Database Design – Lecture 4
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
Database Systems: Design, Implementation, and Management Tenth Edition
Review of Week 1 Database DBMS File systems vs. database systems
Chapter 4 Entity Relationship (ER) Modeling
Entity-Relationship Diagram (ERD)
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

BIS 360 – Lecture Six (Part 2) Conceptual Data Modeling (Chapter 10 and partial Chapter 12)

1. Determine system requirements (ch. 7) 2. Structure system requirements (ch. 8-10) 3. Generate alternative for selection (ch. 11) SDLC Where are we? Project ID and Selection Project Initiation & Planning Analysis Logical Design Physical Design Implementation Maintenance Data Modeling Processing Modeling Logic Modeling

Differences between Modeling Data Modeling - Using Entity-Relationship Diagram (ER diagram or ERD) –identify What (types of data) needed in the system Process Modeling - Using Data Flow Diagram (DFD) –identify Where and How (which pieces of data) to be used Logic Modeling - Using Structured English, Decision Table, and Decision Tree –detail System Logic and Functional Structure

ERD and DFD Data Model (ER Diagram) Data Modeling (ER Diagramming) Process Modeling (Data Flow Diagramming) Process Model (Data Flow Diagram) (more static) (more dynamic)

Some Basic Jargons Model: An abstract representation of “reality” Data Model: An organization of data to represent the “reality.” Data Modeling: a technique used to create a “Data Model.” Conceptual Data Modeling: a technique to capture both “data” and its “meaning” required by an organization

Conceptual Data Modeling It is: presenting what data are needed in the system independent from “how” data are stored Independent from which DBMS to be used Its deliverables: A preliminary ER model (address only Entities and Relationships) A refined ER diagram (with detailed attributes for each entity)

An Example -- A Preliminary Entity-Relationship Model

An Example -- A Refined Entity-Relationship Diagram

ERD - basic concepts Entity A thing (tangible/intangible) that can be uniquely identified -- indicated by a noun, it could be a(n): –Person –Object (e.g., machine, tool, equipment, document) –Concept (e.g., position, movie, etc.) Symbol: a symbol for an Entity

ERD - basic concepts Relationship: An association between one or more entities -- described by a verb phrase; it is bi-directional Symbol: A Line (with Crow’s foot)

Entity Type - the object set that shares a common group of characteristics, e.g., STUDENT (SID, Name, Phone, Major) Entity instance - an occurrence of an Entity Type, e.g., (1234, Mike Taylor, , CIS) ERD - basic concepts Entity Type vs. Entity Instance

ERD - Extended Concepts Associative Entity: a special relationship that contains its characteristics to associate instances of one or more entity types. Symbol: EMPLOYEECOURSE completes Date

Weak Entity: an “entity” depends on another entity for its existence. Symbol: Weak Entity EMPLOYEE SPOUSE ERD - Extended Concepts

How to Characterize a Relationship? Cardinality: The number of occurrences (instances) involved at each side of a relationship –zero or One –one and only one –zero or many –one or many (Optional one) (Mandatory one) (Optional Many) (Mandatory Many)

Relationship: Extended Concepts Degree of a Relationship: The number of entity types involved in a relationship. Unary - a R within an entity itself Binary - a R between two different entity types Ternary - a R exists among three entity types

1 to 1 (1:1) 1 to many (1:M) many to many (M:N) Binary Relationships EmployeeSpouse is a spouse of has Vehicle Type Model is of registers Course is registered by Student is married to

Unary Relationships Person is a spouse of is married to 1 to 1 manages 1 to M Employee is managed by consists of M to N Part is a component of

Unary Relationships (a complete graph) Person is a spouse of is married to 1 to 1 consists of M to N Part is a component of is managed by 1 to M Employee manages

Unary Relationships Each Employee may manage one or more Employees. Each Employee must be managed by one and only one Employee. manages is manages by 1 to M Employee

More Unary Relationship! Course has a prerequisite is a prerequisite of Q. What is the cardinality for the above unary relationship?

More Unary Relationship! (A complete graph) Course has a prerequisite is a prerequisite of Why? Can you explain the above diagram?

Ternary Relationship A relationship that simultaneously involves 3 entities!

How to Characterize an Entity? Attribute A characteristic (property) of an entity or a relationship –Key (identifier) –Candidate key –Non-key attribute Examples: EMP (EmpID, Name, Address, DOB) DEPT (DeptID, DeptName, DeptAddress)

Foreign Key Foreign key: It is an attribute ( or a set of attributes) that is used as a Primary Key in some other entity. EMPDEPT EMP (EmpID, Name, Address, DOB) DEPT (DeptID, DeptName, DeptAddress)

How to Resolve a M:N Relationship? It is quite common to encounter a M:N relationship - which needs to be represented as an “Associative entity”. Most DBMS can not represent a M:N relationship, we need to... Use the two PKs as the PK and FKs in the associative entity Sup_PART SUPPLIERPART SID PID

An Example for an M:N Relationship  Associative Entity SUPPLIER(SID, Name, SSN, Phone, Addr) PART (PID, Description) SUPPLIER SID NameSSNPhone Addr PART PID Descrip Associative Entity Price Sup_PART (SID, PID, Price)

How to Conduct the ER Diagramming? Step 1 - Identify all interested Entities Step 2 - Identify proper relationships between entities Step 3 - identify the Key and non-key attributes for each entity Step 4 - Verify the validity of the final ER diagram

Validation of ERD Rules: The entity name must be a noun The entity name must be unique The entity must have an identification or primary key Each relationship is described by a verb (phrase)