IDEF1X (Integrated Definition 1, Extended  IDEF1X narrows the definition of entities, attributes, and relationships  IDEF1X adds the notion of domains.

Slides:



Advertisements
Similar presentations
ER Model For a college DB
Advertisements

Relational Database Modeling II We dont live in a world of reality, we live in a world of perceptions. J. Gerald Simmons.
Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques
Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
E NTITY R ELATIONSHIP D IAGRAMS Joe Meehean 1. E NTITY R ELATIONSHIP M ODEL Entity type an object (noun) e.g., student attributes (e.g., last name) Relationship.
Chapter 4 Entity Relationship (E-R) Modeling
Database Processing: Fundamentals, Design, and Implementation, 9/e by David M. KroenkeChapter 5/1 Copyright © 2004 Please……. No Food Or Drink in the class.
IT420: Database Management and Organization
Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Chapter 5 Understanding Entity Relationship Diagrams.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 8.
Fundamentals, Design, and Implementation, 9/e Chapter 5 Database Design.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke Database Processing Tenth Edition Chapter 5 Data.
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.
Chapter Five Data Modeling with the Entity-Relationship Model.
Motivation for IDEF1X Simplicity Common Standard Useful when relational model is target Air Force 1985 or thereabouts.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 2.
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.
Data Modeling and the Entity-Relationship Model Chapter Four DAVID M. KROENKE and DAVID J. AUER DATABASE CONCEPTS, 5 th Edition.
Entity-Relationship Model
The (min,max) notation (1,1) (0,1) (1,N) (1,1). SUMMARY OF ER-DIAGRAM NOTATION FOR ER SCHEMAS Meaning ENTITY TYPE WEAK ENTITY TYPE RELATIONSHIP TYPE IDENTIFYING.
Chapter Five Data Modeling with the Entity-Relationship Model.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 7.
Slide 1 Chapter 05 – Part 1 Data Modeling with the Entity-Relationship Model.
CSCI 242 Relational Data Modeling Copyright 2011, David C. Roberts, all rights reserved.
Using ER/Studio.
COURSE REGISTRATION SYSTEM Case study IST2101. Case Study: Course Registration (1) IST2102 You are helping Penn State create a course registration system.
Ch5: ER Diagrams - Part 2 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Data Modeling and the Entity-Relationship Model Chapter Four DAVID M. KROENKE’S DATABASE CONCEPTS, 2 nd Edition.
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.
Chapter 5 1 © Prentice Hall, 2002 Chapter 5: Transforming EER Diagrams into Relations Mapping Regular Entities to Relations 1. Simple attributes: E-R attributes.
Module Title? Data Base Design 30/6/2007 Entity Relationship Diagrams (ERDs)
Entity Relationship Diagrams Objectives s Learn the Elements of the E-R model (entities, attributes, and relationships) s Show how to apply the E-R model.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
DATABASE DESIGN I IST 210: Organization of Data IST210 1.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Component 4: Introduction to Information and Computer Science Unit 6: Databases and SQL Lecture 2 This material was developed by Oregon Health & Science.
Database Design Using Entity-Relationship Models Transformation of Entity-Relationship Models into Relational Database Design Trees, Networks, and Bills.
1 5 Modeling Techniques A line manager states, “I know the Chinese say one picture is worth 1,000 words but these diagrams, there are so many that I’d.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall, modified by Dr. Lyn Mathis 5-1 David M. Kroenke’s, 10 th ed. Chapter.
Data Modeling IST210 Class Lecture.
 R EVIEW M ORE ON ERD’ S DBS201. Why ERDs What is an ERD What is represented by boxes What is the connection between boxes called.
Chapter 9: Logical Database Design and the Relational Model (ERD Mapping)
Component 4/Unit 6b Topic II Relational Databases Keys and relationships Data modeling Database acquisition Database Management System (DBMS) Database.
advanced data modeling
Lecture 03 Entity-Relationship Diagram. Chapter Outline.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall, modified by Dr. Lyn Mathis 5-1 David M. Kroenke’s, 10 th ed. Chapter.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
Ch 05. Basic Symbols ( manino ). Cardinalities Cardinality Notation.
Database vs File System Integrated Data Reduced Data Duplication Program/Data Independence Easier representation for user Separate/Isolated data Appl.
Chapter 5 Understanding Entity Relationship Diagrams.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix C: E-R Diagrams and The IDEF1X Standard.
Data Modeling and Entity-Relationship Model I
Database Design I IST 210: Organization of Data IST2101.
ERwin.
Chapter 5 Database Design
Requirements Become the E-R Data Model
IST 210: Organization of Data
Outline of the ER Model By S.Saha
IDEF1X Standard IDEF1X (Integrated Definition 1, Extended) was announced as a national standard in 1993 It defines entities, relationships, and attributes.
Practice of ER modeling
Weak Entity Sets An entity set that does not have a primary key is referred to as a weak entity set. The existence of a weak entity set depends on the.
Database Processing: David M. Kroenke’s Chapter Five:
Presentation transcript:

IDEF1X (Integrated Definition 1, Extended  IDEF1X narrows the definition of entities, attributes, and relationships  IDEF1X adds the notion of domains which is not present in the E-R model  IDEF1X introduces new symbology and hierarchy of views

IDEF1X vs. Extended E-R Extended E-RIDEF1XRemarks Entity Same Attribute Same Relationship Same 1:1 and 1:N Relationship Non-Identifying Connection Rel’ship HAS-A M:N RelationshipNon-Specific Rel’ship ID-Dependent Rel’shipIdentifying Rel’ship Weak Entity, ~ID-DepNone Supertype EntityGeneric EntityIS-A Subtype EntityCategory EntityCategories are mutually exclusive NoneDomain

IDEF1X RELATIONSHIPS  Non-Identifying Connection Relationship Equivalent to HAS-A relationships in E-R (1:1 or 1:N) DeptNameSerialNumber BudgetCode OfficeNumber Type Size Material DEPARTMENTFURNITURE DEPARTMENTFURNITURE 1:N A DEPARTMENT is not required to have any FURNITURE, but every piece of FURNITURE must belong to one, and only one, DEPARTMENT. Default relationship is 1:N as shown above

IDEF1X RELATIONSHIPS  Non-Identifying Connection Relationship DeptNameSSN BudgetCode OfficeNumber Name Phone JobCode DEPARTMENTEMPLOYEE DEPARTMENTEMPLOYEE 1:N A DEPARTMENT must have at least one, and can have many, EMPLOYEEs, but an EMPLOYEE need not belong to a DEPARTMENT. If Child entity is required, then add P; if Parent optional, add diamond p

IDEF1X RELATIONSHIPS  Non-Identifying Connection Relationship BadgeNumberSSN IssueDate IssuedBy Name Phone JobCode BADGEEMPLOYEE BADGEEMPLOYEE 1:1 An EMPLOYEE must have one, and only one, BADGE and a BADGE belongs to one, and only one, EMPLOYEE. 1:1 Relationship 1

IDEF1X RELATIONSHIPS  Non-Identifying Connection Relationship SerialNumberSSN Make Model DiskCapacity Name Phone JobCode COMPUTEREMPLOYEE COMPUTEREMPLOYEE 1:1 An EMPLOYEE may have zero or one COMPUTER, and a COMPUTER need not belong to any EMPLOYEE. 0:1 Relationship Z

IDEF1X RELATIONSHIPS  Identifying Connection Relationship Same as an ID-Dependent relationship in Extended E-R BuildingNumber ReceptionPhone NumFloors ParkingLot BUILDING OFFICE BUILDING 1:N A BUILDING may be connected to 0, 1, or many OFFICES; an OFFICE must be associated with a BUILDING. 1:N Relationship OFFICE OfficeNumber BuildingNumber NetPortNumber PhoneNumber MaxCapacity Note: Parent cannot be optional (“P”)

IDEF1X RELATIONSHIPS  Non-Specific Relationships Many-to-many (M:N) relationship CourseId CourseName Credits COURSESTUDENT COURSE M:N A COURSE may have many STUDENTs and a STUDENT may enroll in many COURSEs. M:N Relationship STUDENT Note: IDEF1X cannot represent min cardinalities for M:N StudentId StudentName Curriculum

IDEF1X RELATIONSHIPS  Categorization Relationships Generalization/subtype relationship in Extended E-R SSN Name Phone JobCode EMPLOYEE LevelCode LastBonus HourlyRate VacationDays Title Language OS YearsExperience Language TECH_WRITERPQA_ENGINEERPROGRAMMERSTAFFMANAGER Z Z ZZ Z ZZ JobCode