Developing an IT Application Using Advantage:Gen  Data Modeling: I-bars and subtypes.

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Author: Graeme C. Simsion and Graham C. Witt Chapter 8 Organizing the Data Modeling Task.
Basic notation for supertype/subtype relationships
1 © Prentice Hall, 2002 Chapter 4: The Enhanced E-R Model and Business Rules Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
CHAPTER 3: THE ENHANCED E-R MODEL © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition Jeffrey A. Hoffer,
System Analysis - Data Modeling
Chapter 4 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Use of supertype/subtype relationships Use of supertype/subtype.
Associative Entities A relationship cannot have attributes
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.
Data Modeling Advanced Concepts.
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.
Lecture a: Additional UML Models: Package, Activity, Deployment Lecture b: Generalization, Aggregation and Additional Domain Model Notation Copyright W.
FIS 431/631 Financial Information Systems: Analysis and Design ERD & Normalization Joe Callaghan Oakland University Department of Accounting & Finance.
The Enhanced E-R (EER) Model
IS 4420 Database Fundamentals Chapter 4: The Enhanced ER Model and Business Rules Leon Chen.
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.
PRJ566: PROJECT PLANNING AND MANAGEMENT Class Diagrams.
Modern Systems Analysis and Design Third Edition
Entity Relationship Model Chapter 6. Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier,
Extending ER Diagrams (13) CPSC 356 Database Ellen Walker Hiram College (Includes figures from Database Systems: A Practical Approach to Design, Information.
 Keys are special fields that serve two main purposes: ◦ Primary keys are unique identifiers of the relation in question. Examples include employee numbers,
Class Agenda – 04/04/2006 Discuss database modeling issues
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Advanced Entity Relationship Concepts. Advanced Concepts UIDs Intersection Entities Recursive Relationships Roles Subtypes Exclusivity Historical Fan.
Entity Relationship Diagrams
Chapter 4 The Relational Model.
IS 475/675 - Introduction to Database Design
CSEN 5314 Quiz Inheritance is which of the following? A. When a supertype entity inherits values of the subtype attribute B. When a subtype entity.
Entity-Relationship (ER) Modelling ER modelling - Identify entities - Identify relationships - Construct ER diagram - Collect attributes for entities &
Database Systems: Enhanced Entity-Relationship Modeling Dr. Taysir Hassan Abdel Hamid.
Overview of Database Development Data Modeling and Relational Database Design.
Question 11 Attribute inheritance is the gaining of attributes by a subtype entity from a supertype entity. This inheritance of common pieces of data from.
DeSiamorePowered by DeSiaMore1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
1 A Demo of Logical Database Design. 2 Aim of the demo To develop an understanding of the logical view of data and the importance of the relational model.
1 The Enhanced Entity Relationship Diagrams (E-ERDs)
Enhanced Entity-Relationship and Object Modeling Chapter 4
Database Systems Supertypes and Subtypes Lecture # 10.
Database Management System Prepared by Dr. Ahmed El-Ragal Reviewed & Presented By Mr. Mahmoud Rafeek Alfarra College Of Science & Technology- Khan younis.
Entity Relationship Modeling
Entity-Relation Model. E-R Model The Entity-Relationship (ER) model was originally proposed by Peter in 1976 ER model is a conceptual data model that.
Exam 1 Review Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
INTRODUCTION TO DATA MODELING CS 260 Database Systems.
Exam 1 Review Dr. Bernard Chen Ph.D. University of Central Arkansas.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 4: The Enhanced E-R Model Modern Database Management 9 th Edition Jeffrey A. Hoffer,
Chapter 14 Semantic Modeling. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.14-2 Topics in this Chapter The Overall Approach The E/R Model.
EntityRelationshipDiagrams. Entity Relationship Models The E-R (entity-relationship) data model views the real world as a set of basic objects (entities)
subtype 1.inherits all attributes of the supertype 2.inherits all relationships of the supertype 3. usually has its own attributes or.
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 © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 3: THE ENHANCED.
Lecture 4: Logical Database Design and the Relational Model 1.
BTM 382 Database Management Chapter 5: Advanced Data Modeling
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Modeling data in the Organization
The Enhanced E-R Model and Business Rules
Revised: 2 April 2004 Fred Swartz
Requirements Become the E-R Data Model
Entity Relationship Diagrams
Entity Relationship Diagrams
Database Management System 1 (ITED123A)
Overview of Entity‐Relationship Model
Chapter 5 Advanced Data Modeling
MBA 664 Database Management
Database Management System
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
Weak Entities (cont…) Entities that do not have key attributes of their own Related to specific entities from another entity type plus their own attributes.
Object Oriented System Design Class Diagrams
Presentation transcript:

Developing an IT Application Using Advantage:Gen  Data Modeling: I-bars and subtypes

Data Analysis u What information is required by the business u Logical view vs. physical view u Carried out in parallel with activity analysis

Composite Identifier Using an Attribute and Relationship Order Item Order I is included on includes Attributes ITEM NUMBER PRICE QUANTITY Identifier is a combination of: ITEM NUMBER and the fact that Each ORDER ITEM is included on one ORDER

Composite Identifier Using Relationships ProductWarehouse Stock Item IooI holds is held for is stored in stores Identifier is a combination of: Each STOCK ITEM is stored in one WAREHOUSE and each STOCK ITEM holds one PRODUCT

Entity Subtypes u An subtype is a subdivision of the entity supertype u Each subtype must have one or more special attributes of its own and/or participate in one or more special relationship of its own u The special attributes and relationships are not common to all instances of the entity

Partitioning u A basis for subdividing instances of an entity supertype into subtypes. A subtype can in turn have partitionings of its own. u A classifying attribute is the basis for partitioning, e.g. EMPLOYEE - Name, Number, Type where Type can be Full-Time or Part-Time u Each subtype must be associated with a permitted value of the classifying attribute u Each subtype inherits properties ( attributes, identifiers, relationships) of its parent entity

Partitioning can be u There can be multiple partitionings EmployeeManager Staff Full Time Part Time NAME ADDRESS NUMBER TYPE JOB STATUS

Rules for Partitioning and Subtypes u Each subtype belongs to exactly one partitioning u Each partitioning must be associated with a classifying attribute u The subtype to which a given entity occurrence belongs must be identifiable by a classifying attribute value u A fully enumerated partitioning must divide the entity type into two or more subtypes