Detailed Data Modeling. Outline Data Modeling Modeling Constructs –Entities –Relationships –Cardinality Model Basic Rules Advanced Rules Prototyping Process.

Slides:



Advertisements
Similar presentations
More Diagramming & Practice with Relationship Modeling
Advertisements

Entity Relationship (ER) Modeling
Entity Relationship (ER) Modeling
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.
IT420: Database Management and Organization
Systems Development Life Cycle
Modeling the Data: Conceptual and Logical Data Modeling
FIS 431/631 Financial Information Systems: Analysis and Design REA Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
Entity Relationship (E-R) Modeling
Systems Development Life Cycle
© 2005 by Prentice Hall Chapter 3a Database Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
1 © Prentice Hall, 2002 Chapter 5: Logical Database Design and the Relational Model Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B.
Entity Relationship Diagrams
Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.
A Quick Review of Analysis Stages of the Systems Development Life Cycle Planning Analysis Design Construction.
FIS 431/631 Financial Information Systems: Analysis and Design ERD & Normalization Joe Callaghan Oakland University Department of Accounting & Finance.
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
CS424 PK, FK, FD Normalization Primary and Foreign Keys Primary and foreign keys are the most basic components on which relational theory is based. Primary.
Chapter Five Data Modeling with the Entity-Relationship Model.
CSCI 242 Relational Data Modeling Copyright 2011, David C. Roberts, all rights reserved.
Michael F. Price College of Business Chapter 6: Logical database design and the relational model.
Hall, Accounting Information Systems, 7e ©2011 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Class Agenda – 04/04/2006 Discuss database modeling issues
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke’s Chapter Five: Data Modeling with the Entity-Relationship.
3 Chapter 3 Entity Relationship (E-R) Modeling Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
1. 2 Data Modeling 3 Process of creating a logical representation of the structure of the database The most important task in database development E-R.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 9.1.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Concepts and Terminology Introduction to Database.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
10/3/2012ISC329 Isabelle Bichindaritz1 Logical Design.
Database Design Principles – Lecture 3
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.
1 © Prentice Hall, 2002 Chapter 5: Logical Database Design and the Relational Model Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B.
IT 21103/41103 System Analysis & Design. Chapter 04 Data Modeling.
Description and exemplification of entity-relationship modelling.
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.
Chapter 10 Designing Databases. Objectives:  Define key database design terms.  Explain the role of database design in the IS development process. 
Logical Database Design and the Relational Model.
EntityRelationshipDiagrams. Entity Relationship Models The E-R (entity-relationship) data model views the real world as a set of basic objects (entities)
Logical Design 12/10/2009GAK1. Learning Objectives How to remove features from a local conceptual model that are not compatible with the relational model.
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.
Database Design, Application Development, and Administration, 6 th Edition Copyright © 2015 by Michael V. Mannino. All rights reserved. Chapter 5 Understanding.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
TMC2034 Database Concept and Design
SEEM3430: Information Systems Analysis and Design
Database Design – Lecture 4
ERD’s REVIEW DBS201.
Database Systems: Design, Implementation, and Management Tenth Edition
Review of Week 1 Database DBMS File systems vs. database systems
CHAPTER 2 - Database Requirements and ER Modeling
Chapter 4 Entity Relationship (ER) Modeling
Entity-Relationship Diagram (ERD)
Guide to Modeling Keys to E-R diagrams.
Guide to Modeling Keys to E-R diagrams.
Entity-Relationship Design
Presentation transcript:

Detailed Data Modeling

Outline Data Modeling Modeling Constructs –Entities –Relationships –Cardinality Model Basic Rules Advanced Rules Prototyping Process Modeling Homework

Data Modeling Why model data? –Data needs are relatively constant over time, as is the nature of data needed in a particular enterprise –Data is necessary for present and future decision making –Strategies for collecting data into a system have changed radically 1850 all manual, face to face, post (mail) 1900 still manual, telephone 1950 early computer applications and storage 2000 little manual, web-interface, enterprise systems –Data is static

Modeling Constructs Entity Relationship Attribute –Primary Key –Foreign Key –Simple –Composite –Derivable Cardinality –Broad business rules of min/max association Abstraction –Grouping by type, generalization, class (IS-A), super and subtypes

Entity Types –Persons - AGENT –Places - Locations –Objects - RESOURCES –Events - EVENTS –Concepts – Artifacts Instance –Single occurrence of any specific Entity

Attribute Broad Characteristics Classification for each specific entity type Descriptive property –Element, property, field –Compound attributes Domain – restricted values – validation rules, look-up tables Identification –Single value key –Compound key –Concatenated key

Relationship Natural organizational association –Registered in; Purchase of; Sale of; Receipt of; Payment for; Typically related to an event –Assigned to a department; Declared major; –Detail of natural organizational association Items purchased; Time worked; Repairs made;

Cardinality Minimum/maximum associations between entities –Agent sells/buys many products –Employee works on many projects –Employee works in ONE department Mandatory –At least one instance per each association must exist Parent (Mandatory dual relationship based on …) Optional –An instance per association may not exist Marriage Different representations –Crowsfoot, Chen, others

Types of Relationships Recursive –Exists with same entity type Ex: Bill of Materials (inventory/products); Marriage (People) Non-Identifying –Entity exists on its own Identifying –Entity exists because of another entity (also called ‘Dependent’, ‘Attributive’ One to Many Many to Many

Associative Entity Entity with a base in an association Inherits primary (Compound) key from more than one entity –Purchase/Sales order detail (Order#, Item #) –Shipping detail (Shipping Doc#, Item #) –Time Card detail (esp. projects/jobs) (Time Card#, Project/Job #) Second Normal Form

Generalization Also known as IS A relationship, CLASS –Supertype Attributes used by other entity (subtype) –People –Subtype Inherits attributes from supertype Has additional set of attributes –Student, Employee May or may not be multiple subtypes –Student, Employee, Alumni (inclusive) –Salaried, hourly (exclusive)

Conceptual Modeling Summary Entity Relationship Model –Chen, 1976 Entity –Noun, Attributes Relationship –Verb, Cardinality –Natural business association –Duality Set Theory Notation –See Table 4-1; Figure 8-3 (Whitten, 316/299) REA Model CASE Tool (Visible Analyst) Visio

Normalization Strategy used in evolving data model First Normal Form (1NF) –Remove repeating groups – no more than one value for a single instance of that entity Second Normal Form (2NF) –All non-key attributes dependent upon full primary key (Compound Key) and in 1NF Third Normal Form (3NF) –All non-key attributes not dependent on another non-key attribute and in 2NF REMEMBER – All values to be dependent upon the primary key, and ONLY the primary key

ERD and REA REA derived from ERD REA reflects duality of event, critical for enterprise modeling REA supplements ERD –Add duality Accounts as artifacts –Organizational rules –Queries

ERD to Data Design (Access) Entities correspond to tables in RDBMS; Stores in Data Flow Diagram Convert ERD to Relational Model (Design Phase), Tables for Physical Design Access - Associate (in Relationship screen) Primary Key Attribute (field) of ONE side to Foreign Key Attribute (field) of MANY side –Enforce Referential Integrity Rules, if desired

Homework Chapter 9 Problems and Exercises –1 –6 –7 –17