Transforming ER & EER diagrams into Relations (Chapter 9) Overview
|
|
- Joel Gibbs
- 7 years ago
- Views:
Transcription
1 Transforming ER & EER diagrams into Relations (Chapter 9) "!$# %&%#('()* Overview A relatively straightforward process with a welldefined set of rules. Many CASE Tools can automatically perform many of the conversion steps. CASE tools often cannot model complex data relationships. There are sometimes legitimate alternatives where you will need to choose a particular solution. You must be prepared to perform a quality check on the results obtained with a CASE Tool. +, -,.,/01,2, ":$; <&5<;(=(>? 1
2 Map Simple Regular Entities Each regular entity type in an ER diagram is transformed into a relation. The name given to the relation is generally the same as the entity type. Each simple attribute of the entity type become an attribute of the relation. Choose one of the key(s) as primary key of the relation. How about composite attributes? How about multi-valued A B A C ADEFAGA HEIEGB JKLM M"O$P Q&JQP(R(ST Map Composite Attributes When a regular entity type has a composite attribute, only the simple component attributes of the composite attribute are included in the new relation. Street City ID COSTOMER Address State Zip CUSTOMER(ID,, Street, City, State, Zip) U V W V Ẍ VYZ[V\V ]Z^Z\W _`ab cb"d$ë f&_fe(g(hi 2
3 Map Multi-valued Attributes When a regular entity type contains a multivalued attribute, two new relations (rather than one) are created. The first relation contains all of the attributes of the entity type except the multi-valued attribute. The second relation contains two sets of attributes. The primary key from the first relation, which becomes a foreign key of the second relation. Multi-valued attribute itself. The primary key of the second of relation is the combination of all attributes. The name of the second relation should capture the meaning of the multi-valued attribute. j k l k m knopkqk rosoql tuvw xw"y$z {&t{z( (}~ Example SS Skills Address Street City State Zip (SS,, State, City, State, Zip) _SKILL(SS, Skill) ƒ ˆ Š Œ Œ"Ž$ & ( ( 3
4 Map Binary One-Many Relationship Create a relation for each of the two entity types participating in the relationship. Include the primary key attribute (or attributes) of the entity on the one-side of the relationship as a foreign key in the relation that is on the many-side of the relationship ( a mnemonic you can use to remember this rule is this: The primary key migrates to many side). Dept SS 1 STUDET Major_in DEPT STUDET(SS,, Dept) DPET(Dept) š œ žÿ " $ &ž ( ( Map Binary Many-Many Relationships Suppose that there is a binary relationship (M:) between two entity types A and B. For such a relationship, create a new relation C: Include as foreign key attributes in C the primary key for each of the two participating entity type. These attributes become the primary key of C. Any attributes that are associated with the relationship are included with the relation C. Grade CID SID STUDET M taking COURSE Text STUDET(SID, AME) COURSE(CID, Text) Taking(SID, CID, Grade) ª «ª ª ª ª ± ² «³ µ " $¹ º&³º¹(»(¼½ 4
5 Map Binary One-One Relationship Binary 1:1 relationship can be viewed as a special case of 1:m relationship. The process of mapping such a relationship to relations requires to steps: first, two relations are created, one for each of the participating entity type. Second, the primary key of one of the relations is included as foreign key in the other relation. Dept SS 1 1 Manages DEPT (SS,, Dept) (SS, ) DEPT(Dept) DEPT(Dept, ManagerSS) ¾ À Á ÂÃÄ Å ÆÃÇÃÅÀ ÈÉÊË ÌË"Í$Î Ï&ÈÏÎ(Ð(ÑÒ Map Unary One-Many Relationship The entity type in the unary relationship is mapped to a relation using the procedure described before. Then a foreign key attribute is added within the same relation that references the primary key values. ote that the foreign key attribute name should reflect the role name on the one-side. A recursive foreign key is a foreign key in a relation that references the primary key values of that same relation. Supervisee SS Manages Supervisor 1 (SS,, SupervisorSS) Ó Ô Õ Ô Ö Ô ØÙÔÚÔ ÛØÜØÚÕ ÝÞßà áà"â$ã ä&ýäã(å(æç 5
6 Map Unary Many-Many relationship With this type of relationship: Two relations are created: one to represent the entity type in the relationship and the other an associative relation to represent the M: relationship itself. The primary key of the associative relation consists of two parts: both take their values from the primary key of the other relation. Any attribute of the relationship is included in the associative relation. ID Item M PART Contains Quantity Unit_cost Components COMPOET(ItemID, ComponentID, Quantity) PART(ID,, Unit_Cost) è é ê é ë éìíîéïé ðíñíïê òóôõ öõ" $ø ù&òùø(ú(ûü Map Weak Entities For each weak entity type, create a new relation and include all of the simple attributes (or simple components of composite attributes) as attributes of this relation. Then, include the primary key of the owner relation as a foreign key attribute in this relation. The primary key of the new relation is the combination of this primary key of the owner and the partial key of the weak entity type. salary sex SS name addr. Employees birthdate 1 DEPEDAT_ OF name birthdate Dependants sex ý þ ÿ þ þ þ þ ÿ!!" # relationship 6
7 Example Results Employee( SS, name, addr, salary sex, birthdate) Dependants(name, birthdate, sex, relationship, empss) The relation for the weak entity not only has the attributes of itself, but also has the key attributes of the other entity sets. Do not construct a relation for a double-diamond relationship. $&%'(% )% * +,-%. %/+0+.1' !:!; < Map Ternary (n-ary) Relationship It is recommended that you convert the ternary (n-ary) relationship to a number of binary relationships, and then transform the diagram into relationships. S Quantity Proj SUPPLIER SUPPLY PROJECT S Quantity Proj PART Parto SUPPLIER 1 1 SS SUPPLY SPJ PROJECT SP 1 PART Parto A B C-> D >EBFBD1? GHIJK JLMGM!O!P Q 7
8 Example Result SUPPLIER(S) PROJECT(Proj) SUPPLY(S, Proj, PartID, Quantity) PART(PartID) R&ST(S US V W X-S Y SZW[WY1T \]^_` _abc\cb!d!e f Map Supertype/Subtype Relationships The relational data model does not yet directly support/subtype relationships. There are various strategies that database designer can use to represent these relationships. In this lecture, we introduce the most commonly employed strategy. g&hi(h jh k l m-h n holpln1i qrstu tvwxqxw!y!z { 8
9 Mapping Strategy Create a separate relation for the supertype and for each of its subtypes. Assign to the relation created for the supertype the attributes that are common to all memebers of the supertype, including the primary key. Assign to the relation for each subtype the primary key of the supertype, and this primary key is also a foreign key that references the primary key in relation representing the supertype. Assign to the relation for each subtype the attributes that are unique to that subtype. &}~(} } -} ƒ } ƒ1~ ˆ Š Œ Œ!Ž! Example Address SS Date_hired d HOURLY SALARED COSULTAT Hourly_rate Annual_salary Stock_option Contract_o. Billing_rate ( SS,, Address, Date_hired) HOURLY_(SS, Hourly_Rate) SALARIED_(SS, Annual_salary, Stock_Option) COSULTAT(SS, Contract_o, Billing_rate) & ( - š 1 œ žÿ ž!! 9
10 Problem Map Categories Multiple supertypes may have different primary keys. Solution The concept of surrogate key, a specified new key attribute for the subtype. & ( ª «- ««1 ±²³ ³µ!!¹ º Example C Address SS COMPAY PERSO U Total_Balance B ACCOUT HOLDER M Has_Acct BAK»&¼½(¼ ¾¼ À Á-¼  ¼ÃÀÄÀÂ1½ ÅÆÇÈÉ ÈÊËÌÅÌË!Í!Î Ï 10
11 Example Results COMPAY(C, Address, OwnerID) PERSO(SS,, OwnerID) ACCOUTHOLDER(OwnerID) HASACCOUT(OwnerID, B, Total_Balance) BAK(B) Ð&ÑÒ(Ñ ÓÑ Ô Õ Ö-Ñ ÑØÕÙÕ 1Ò ÚÛÜÝÞ ÝßàáÚáà!â!ã ä 11
Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model
Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Outline Using High-Level Conceptual Data Models for
More informationTHE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)
THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E) 2 LECTURE OUTLINE Using High-Level, Conceptual Data Models for Database Design Entity-Relationship (ER) model Popular high-level conceptual
More informationnot necessarily strictly sequential feedback loops exist, i.e. may need to revisit earlier stages during a later stage
Database Design Process there are six stages in the design of a database: 1. requirement analysis 2. conceptual database design 3. choice of the DBMS 4. data model mapping 5. physical design 6. implementation
More informationDATABASE DESIGN. - Developing database and information systems is performed using a development lifecycle, which consists of a series of steps.
DATABASE DESIGN - The ability to design databases and associated applications is critical to the success of the modern enterprise. - Database design requires understanding both the operational and business
More informationModern Systems Analysis and Design
Modern Systems Analysis and Design Prof. David Gadish Structuring System Data Requirements Learning Objectives Concisely define each of the following key data modeling terms: entity type, attribute, multivalued
More informationConceptual Design: Entity Relationship Models. Objectives. Overview
Conceptual Design: Entity Relationship Models Craig Van Slyke, University of Central Florida cvanslyke@bus.ucf.edu John Day, Ohio University Objectives Define terms related to entity relationship modeling,
More informationthree Entity-Relationship Modeling chapter OVERVIEW CHAPTER
three Entity-Relationship Modeling CHAPTER chapter OVERVIEW 3.1 Introduction 3.2 The Entity-Relationship Model 3.3 Entity 3.4 Attributes 3.5 Relationships 3.6 Degree of a Relationship 3.7 Cardinality of
More informationER modelling, Weak Entities, Class Hierarchies, Aggregation
CS344 Database Management Systems ER modelling, Weak Entities, Class Hierarchies, Aggregation Aug 2 nd - Lecture Notes (Summary) Submitted by - N. Vishnu Teja Saurabh Saxena 09010125 09010145 (Most the
More informationER & EER to Relational Mapping. Chapter 9 1
ER & EER to Relational Mapping Chapter 9 1 Figure 3.2 ER schema diagram for the company database. Fname Minit Lname Number Name Address N 1 WORKS_FOR Name Locations Sex Salary Ssn Bdate EMPLOYEE NumberOfEmployees
More informationChapter 3. Data Modeling Using the Entity-Relationship (ER) Model
Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model Chapter Outline Overview of Database Design Process Example Database Application (COMPANY) ER Model Concepts Entities and Attributes Entity
More informationObject-Oriented Data Modeling
C h a p t e r 1 3 Object-Oriented Data Modeling Learning Objectives After studying this chapter, you should be able to: Concisely define each of the following key terms: class, object, state, behavior,
More informationEntity-Relationship Model
UNIT -2 Entity-Relationship Model Introduction to ER Model ER model is represents real world situations using concepts, which are commonly used by people. It allows defining a representation of the real
More informationProfessional Liability Errors and Omissions Insurance Application
If coverage is issued, it will be on a claims-made basis. Notice: this insurance coverage provides that the limit of liability available to pay judgements or settlements shall be reduced by amounts incurred
More informationDatabase Design. Database Design I: The Entity-Relationship Model. Entity Type (con t) Chapter 4. Entity: an object that is involved in the enterprise
Database Design Database Design I: The Entity-Relationship Model Chapter 4 Goal: specification of database schema Methodology: Use E-R R model to get a high-level graphical view of essential components
More informationEntity - Relationship Modelling
Topic 5 Entity - Relationship Modelling LEARNING OUTCOMES When you have completed this Topic you should be able to: 1. Acquire the basic concepts of the Entity-Relationship (ER) model. 2. Discuss how to
More informationXV. The Entity-Relationship Model
XV. The Entity-Relationship Model The Entity-Relationship Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of E-R Diagrams and Business Rules The
More informationEntity Relationship Diagram
Yufei Tao Department of Computer Science and Engineering Chinese University of Hong Kong A primary goal of database design is to decide what tables to create. Usually, there are two principles: 1 Capture
More informationDatabases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.
The Entity- Relationship Model R &G - Chapter 2 A relationship, I think, is like a shark, you know? It has to constantly move forward or it dies. And I think what we got on our hands is a dead shark. Woody
More information2. Conceptual Modeling using the Entity-Relationship Model
ECS-165A WQ 11 15 Contents 2. Conceptual Modeling using the Entity-Relationship Model Basic concepts: entities and entity types, attributes and keys, relationships and relationship types Entity-Relationship
More informationLecture 12: Entity Relationship Modelling
Lecture 12: Entity Relationship Modelling The Entity-Relationship Model Entities Relationships Attributes Constraining the instances Cardinalities Identifiers Generalization 2004-5 Steve Easterbrook. This
More informationUnit 2.1. Data Analysis 1 - V2.0 1. Data Analysis 1. Dr Gordon Russell, Copyright @ Napier University
Data Analysis 1 Unit 2.1 Data Analysis 1 - V2.0 1 Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship? Entities, attributes,
More informationDatabase Design Overview. Conceptual Design ER Model. Entities and Entity Sets. Entity Set Representation. Keys
Database Design Overview Conceptual Design. The Entity-Relationship (ER) Model CS430/630 Lecture 12 Conceptual design The Entity-Relationship (ER) Model, UML High-level, close to human thinking Semantic
More informationCSC 742 Database Management Systems
CSC 742 Database Management Systems Topic #4: Data Modeling Spring 2002 CSC 742: DBMS by Dr. Peng Ning 1 Phases of Database Design Requirement Collection/Analysis Functional Requirements Functional Analysis
More informationDatabases and BigData
Eduardo Cunha de Almeida eduardo.almeida@uni.lu Outline of the course Introduction Database Systems (E. Almeida) Distributed Hash Tables and P2P (C. Cassagnes) NewSQL (D. Kim and J. Meira) NoSQL (D. Kim)
More informationEntity-Relationship Model. Purpose of E/R Model. Entity Sets
Entity-Relationship Model Diagrams Class hierarchies Weak entity sets 1 Purpose of E/R Model The E/R model allows us to sketch the design of a database informally. Designs are pictures called entityrelationship
More informationRELATIONSHIP STRENGTH
Connectivity and Cardinality The term connectivity is used to describe the relationship classification. Cardinality expresses the minimum and maximum number of entity occurrences associated with one occurrence
More informationChapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More informationDesigning a Database Schema
Week 10: Database Design Database Design From an ER Schema to a Relational One Restructuring an ER schema Performance Analysis Analysis of Redundancies, Removing Generalizations Translation into a Relational
More informationData Modeling: Part 1. Entity Relationship (ER) Model
Data Modeling: Part 1 Entity Relationship (ER) Model MBA 8473 1 Cognitive Objectives (Module 2) 32. Explain the three-step process of data-driven information system (IS) development 33. Examine the purpose
More informationCOMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model
COMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model The entity-relationship (E-R) model is a a data model in which information stored
More informationSQL DDL. DBS Database Systems Designing Relational Databases. Inclusion Constraints. Key Constraints
DBS Database Systems Designing Relational Databases Peter Buneman 12 October 2010 SQL DDL In its simplest use, SQL s Data Definition Language (DDL) provides a name and a type for each column of a table.
More informationCS 4604: Introduc0on to Database Management Systems. B. Aditya Prakash Lecture #5: En-ty/Rela-onal Models- - - Part 1
CS 4604: Introduc0on to Database Management Systems B. Aditya Prakash Lecture #5: En-ty/Rela-onal Models- - - Part 1 Announcements- - - Project Goal: design a database system applica-on with a web front-
More informationBridge from Entity Relationship modeling to creating SQL databases, tables, & relations
1 Topics for this week: 1. Good Design 2. Functional Dependencies 3. Normalization Readings for this week: 1. E&N, Ch. 10.1-10.6; 12.2 2. Quickstart, Ch. 3 3. Complete the tutorial at http://sqlcourse2.com/
More informationBİL 354 Veritabanı Sistemleri. Entity-Relationship Model
BİL 354 Veritabanı Sistemleri Entity-Relationship Model Steps in building a DB application Pick application domain Conceptual design How can I describe that data? What data do I need for my application
More informationPart 7: Object Oriented Databases
Part 7: Object Oriented Databases Junping Sun Database Systems 7-1 Database Model: Object Oriented Database Systems Data Model = Schema + Constraints + Relationships (Operations) A logical organization
More informationThe Relational Model. Why Study the Relational Model? Relational Database: Definitions
The Relational Model Database Management Systems, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Microsoft, Oracle, Sybase, etc. Legacy systems in
More informationWhy & How: Business Data Modelling. It should be a requirement of the job that business analysts document process AND data requirements
Introduction It should be a requirement of the job that business analysts document process AND data requirements Process create, read, update and delete data they manipulate data. Process that aren t manipulating
More informationDatabase Design Process
Database Design Process Entity-Relationship Model From Chapter 5, Kroenke book Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning Problem:
More informationConverting E-R Diagrams to Relational Model. Winter 2006-2007 Lecture 17
Converting E-R Diagrams to Relational Model Winter 2006-2007 Lecture 17 E-R Diagrams Need to convert E-R model diagrams to an implementation schema Easy to map E-R diagrams to relational model, and then
More informationDatabase Design Process
Entity-Relationship Model Chapter 3, Part 1 Database Design Process Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning 1 Problem: University
More informationRelational Schema Design
Relational Schema Design Using ER Methodology to Design Relational Database Schemas The Development Process Collect requirements. Analyze the requirements. Conceptually design the data (e.g., draw an ER
More informationReview: Participation Constraints
Review: Participation Constraints Does every department have a manager? If so, this is a participation constraint: the participation of Departments in Manages is said to be total (vs. partial). Every did
More informationIntroduction to normalization. Introduction to normalization
Introduction to normalization Lecture 4 Instructor Anna Sidorova Agenda Presentation Review of relational models, in class exersise Introduction to normalization In-class exercises Discussion of HW2 1
More informationData Analysis 1. SET08104 Database Systems. Copyright @ Napier University
Data Analysis 1 SET08104 Database Systems Copyright @ Napier University Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship?
More informationAn international comparison of energy and climate change policies impacting energy intensive industries in selected countries. Table of Contents.
Table of Contents Page i Figures ii iii Tables iv 1 2 3 4 5 6 7 8 9 Converted 8 !! >?@AB CD EC CC FGF HIJA "#$%& '%($& )&*&% +,--$&.,/012 345 61%7&/08/&%91:1/7&%2 ';&
More informationDatabase Management Systems
Database Management Systems Database Design (1) 1 Topics Information Systems Life Cycle Data Base Design Logical Design Physical Design Entity Relationship (ER) Model Entity Relationship Attributes Cardinality
More informationExercise 1: Relational Model
Exercise 1: Relational Model 1. Consider the relational database of next relational schema with 3 relations. What are the best possible primary keys in each relation? employ(person_name, street, city)
More informationWe know how to query a database using SQL. A set of tables and their schemas are given Data are properly loaded
E-R Diagram Database Development We know how to query a database using SQL A set of tables and their schemas are given Data are properly loaded But, how can we develop appropriate tables and their schema
More informationxzy){v } ~ 5 Vƒ y) ~! # " $ &%' #!! () ˆ ˆ &Šk Œ Ž Ž Œ Ž *,+.- / 012 3! 45 33 6!7 198 # :! & ŠkŠk Š $š2 š6œ1 ž ˆŸˆ & Š)œ1 ž 2 _ 6 & œ3 ˆœLŸˆ &Šž 6 ˆŸ œ1 &Š ' 6 ª & & 6 ž ˆŸ«k 1±²\³ kµ² µ0 0 9 ² ķ¹>² µ»º
More informationA Comparative Analysis of Entity-Relationship Diagrams 1
A Comparative Analysis of Entity-Relationship Diagrams 1 Il-Yeol Song Drexel University Mary Evans USConnect E.K. Park U.S. Naval Academy The purpose of this article is to collect widely used entity-relationship
More informationThe Entity-Relationship Model
The Entity-Relationship Model Chapter 2 Slides modified by Rasmus Pagh for Database Systems, Fall 2006 IT University of Copenhagen Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Today
More informationLecture 6. SQL, Logical DB Design
Lecture 6 SQL, Logical DB Design Relational Query Languages A major strength of the relational model: supports simple, powerful querying of data. Queries can be written intuitively, and the DBMS is responsible
More informationLesson 8: Introduction to Databases E-R Data Modeling
Lesson 8: Introduction to Databases E-R Data Modeling Contents Introduction to Databases Abstraction, Schemas, and Views Data Models Database Management System (DBMS) Components Entity Relationship Data
More informationA Tool for Generating Relational Database Schema from EER Diagram
A Tool for Generating Relational Schema from EER Diagram Lisa Simasatitkul and Taratip Suwannasart Abstract design is an important activity in software development. EER diagram is one of diagrams, which
More informationThe Entity-Relationship Model
The Entity-Relationship Model Overview of Database Design Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning Conceptual Design Entities Conceptual
More informationIntroduction to Database Systems CS4320/CS5320. CS4320/4321: Introduction to Database Systems. CS4320/4321: Introduction to Database Systems
Introduction to Database Systems CS4320/CS5320 Instructor: Johannes Gehrke http://www.cs.cornell.edu/johannes johannes@cs.cornell.edu CS4320/CS5320, Fall 2012 1 CS4320/4321: Introduction to Database Systems
More informationDatabase Management Systems,
Database Management Systems Database Design Example 1 Topics Hospital Database E-R Design Entities Relationships Converting E-R Model to Relational Model Tables Queries Company Database Summary 2 Hospital
More information7.1 The Information system
Chapter 7. Database Planning, Design and Administration Last few decades have seen proliferation of software applications, many requiring constant maintenance involving: correcting faults, implementing
More informationSAMPLE FINAL EXAMINATION SPRING SESSION 2015
SAMPLE FINAL EXAMINATION SPRING SESSION 2015 School of Computing, Engineering and Mathematics Student family name: Student given name/s: Student ID number: Course: Unit Name (In Full): Database Design
More informationThe Relational Model. Why Study the Relational Model? Relational Database: Definitions. Chapter 3
The Relational Model Chapter 3 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase,
More informationIV. The (Extended) Entity-Relationship Model
IV. The (Extended) Entity-Relationship Model The Extended Entity-Relationship (EER) Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of EER Diagrams
More informationOutline. Data Modeling. Conceptual Design. ER Model Basics: Entities. ER Model Basics: Relationships. Ternary Relationships. Yanlei Diao UMass Amherst
Outline Data Modeling Yanlei Diao UMass Amherst v Conceptual Design: ER Model v Relational Model v Logical Design: from ER to Relational Slides Courtesy of R. Ramakrishnan and J. Gehrke 1 2 Conceptual
More informationRequirement Analysis & Conceptual Database Design. Problem analysis Entity Relationship notation Integrity constraints Generalization
Requirement Analysis & Conceptual Database Design Problem analysis Entity Relationship notation Integrity constraints Generalization Introduction: Lifecycle Requirement analysis -> Text Conceptual Design
More informationA brief overview of developing a conceptual data model as the first step in creating a relational database.
Data Modeling Windows Enterprise Support Database Services provides the following documentation about relational database design, the relational database model, and relational database software. Introduction
More informationDATABASE MANAGEMENT SYSTEMS. Question Bank:
DATABASE MANAGEMENT SYSTEMS Question Bank: UNIT 1 1. Define Database? 2. What is a DBMS? 3. What is the need for database systems? 4. Define tupule? 5. What are the responsibilities of DBA? 6. Define schema?
More informationConceptual Design Using the Entity-Relationship (ER) Model
Conceptual Design Using the Entity-Relationship (ER) Model Module 5, Lectures 1 and 2 Database Management Systems, R. Ramakrishnan 1 Overview of Database Design Conceptual design: (ER Model is used at
More informationData Modeling. Database Systems: The Complete Book Ch. 4.1-4.5, 7.1-7.4
Data Modeling Database Systems: The Complete Book Ch. 4.1-4.5, 7.1-7.4 Data Modeling Schema: The structure of the data Structured Data: Relational, XML-DTD, etc Unstructured Data: CSV, JSON But where does
More informationFDI inflows in Indian Insurance Sector An Analysis
FDI inflows in Indian Insurance Sector An Analysis A.Maruthi Devi Chowdary, Lecturer in Commerce, Govt Degree College-Mandapeta ß¾ ½ æ ²¼ ² ² «²½»»½ ± ± ¼±³ ²»¼ ¾» Ô º» ² «²½» ݱ ± ±²ô Ù»²» ² «²½» ݱ ±
More informationDatabasesystemer, forår 2005 IT Universitetet i København. Forelæsning 3: Business rules, constraints & triggers. 3. marts 2005
Databasesystemer, forår 2005 IT Universitetet i København Forelæsning 3: Business rules, constraints & triggers. 3. marts 2005 Forelæser: Rasmus Pagh Today s lecture Constraints and triggers Uniqueness
More informationBasic Concepts of Set Theory, Functions and Relations
March 1, 2006 p. 1 Basic Concepts of Set Theory, Functions and Relations 1. Basic Concepts of Set Theory...1 1.1. Sets and elements...1 1.2. Specification of sets...2 1.3. Identity and cardinality...3
More informationFundamentals of Database System
Fundamentals of Database System Chapter 4 Normalization Fundamentals of Database Systems (Chapter 4) Page 1 Introduction To Normalization In general, the goal of a relational database design is to generate
More informationLecture Notes INFORMATION RESOURCES
Vilnius Gediminas Technical University Jelena Mamčenko Lecture Notes on INFORMATION RESOURCES Part I Introduction to Dta Modeling and MSAccess Code FMITB02004 Course title Information Resourses Course
More informationFebruary 3, 2015. Scott Cline City College of San Francisco 50 Phelan Avenue San Francisco, CA
February 3, 2015 Scott Cline City College of San Francisco 50 Phelan Avenue San Francisco, CA RE: Fungal Investigation City College of San Francisco Administration Building 31 Gough Street San Francisco,
More informationCPS352 Database Systems: Design Project
CPS352 Database Systems: Design Project Purpose: Due: To give you experience with designing and implementing a database to model a real domain Various milestones due as shown in the syllabus Requirements
More informationDatabase Design and the E-R Model
C H A P T E R 7 Database Design and the E-R Model Practice Exercises 7.1 Answer: The E-R diagram is shown in Figure 7.1. Payments are modeled as weak entities since they are related to a specific policy.
More informationAn Example: Video Rental System
An Example: Video Rental System Video Rental Database Customers Rentals Videos E-R Analysis ERD Example CUSTOMER PRODUCER E-R Analysis Attributes Attribute - property or characteristic of an entity type
More informationUsing Entity-Relationship Diagrams To Count Data Functions Ian Brown, CFPS Booz Allen Hamilton 8283 Greensboro Dr. McLean, VA 22102 USA
Using Entity-Relationship Diagrams To Count Data Functions Ian Brown, CFPS Booz Allen Hamilton 8283 Greensboro Dr. McLean, VA 22102 USA Contents What Is an Entity-Relationship (E-R) Diagram? E-R Vocabulary
More informationIT2305 Database Systems I (Compulsory)
Database Systems I (Compulsory) INTRODUCTION This is one of the 4 modules designed for Semester 2 of Bachelor of Information Technology Degree program. CREDITS: 04 LEARNING OUTCOMES On completion of this
More informationChapter 2: Entity-Relationship Model. E-R R Diagrams
Chapter 2: Entity-Relationship Model What s the use of the E-R model? Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an E-R Database Schema
More informationFoundations of Information Management
Foundations of Information Management - WS 2012/13 - Juniorprofessor Alexander Markowetz Bonn Aachen International Center for Information Technology (B-IT) Data & Databases Data: Simple information Database:
More informationDatabase Design Methodology
Database Design Methodology Three phases Database Design Methodology Logical database Physical database Constructing a model of the information used in an enterprise on a specific data model but independent
More informationNotes. Information Systems. Higher Still. Higher. www.hsn.uk.net. HSN31010 Database Systems First Normal Form. Contents
Higher Information Systems First Normal Form Contents Normalising to First Normal Form 1 What is Normalising? 1 Normal Forms 1 The Process 1 Worked Example 2 Why do we Normalise? 4 These notes were created
More informationmodel license person owns car report-number participated damage-amount E-R diagram for a Car-insurance company.
Exercises 9 address model driver-id license person owns car report-number location date driver participated accident damage-amount Figure 2.1 E-R diagram for a Car-insurance company. Exercises 2.1 Explain
More informationReview Entity-Relationship Diagrams and the Relational Model. Data Models. Review. Why Study the Relational Model? Steps in Database Design
Review Entity-Relationship Diagrams and the Relational Model CS 186, Fall 2007, Lecture 2 R & G, Chaps. 2&3 Why use a DBMS? OS provides RAM and disk A relationship, I think, is like a shark, you know?
More information2. Supports eæcient access to very large amounts
What is a Database Management System? 1. Manages very large amounts of data. 2. Supports ecient access to very large amounts of data. 3. Supports concurrent access to v.l.a.d. 4. Supports secure, atomic
More informationHow To Write A Diagram
Data Model ing Essentials Third Edition Graeme C. Simsion and Graham C. Witt MORGAN KAUFMANN PUBLISHERS AN IMPRINT OF ELSEVIER AMSTERDAM BOSTON LONDON NEW YORK OXFORD PARIS SAN DIEGO SAN FRANCISCO SINGAPORE
More informationChapter 5: Logical Database Design and the Relational Model Part 2: Normalization. Introduction to Normalization. Normal Forms.
Chapter 5: Logical Database Design and the Relational Model Part 2: Normalization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS
More informationDatabase Systems. Session 3 Main Theme. Enterprise Data Modeling Using The Entity/Relationship (ER) Model. Dr. Jean-Claude Franchitti
Database Systems Session 3 Main Theme Enterprise Data Modeling Using The Entity/Relationship (ER) Model Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical
More informationIT2304: Database Systems 1 (DBS 1)
: Database Systems 1 (DBS 1) (Compulsory) 1. OUTLINE OF SYLLABUS Topic Minimum number of hours Introduction to DBMS 07 Relational Data Model 03 Data manipulation using Relational Algebra 06 Data manipulation
More informationChapter 9: Normalization
Chapter 9: Normalization Part 1: A Simple Example Part 2: Another Example & The Formal Stuff A Problem: Keeping Track of Invoices (cont d) Suppose we have some invoices that we may or may not want to refer
More informationDatabase Design Methodologies
Critical Success Factors in Database Design Database Design Methodologies o Work interactively with the users as much as possible. o Follow a structured methodology throughout the data modeling process.
More informationCHAPTER 3: DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL
Chapter 3: Data Modeling Using the Entity-Relationship Model 1 CHAPTER 3: DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL Answers to Selected Exercises 3.16 Consider the following set of requirements
More informationAyersGTS (Internet) User Manual. Ayers Solutions Limited
A 12.0 AyersGTS (Internet) User Manual By Ayers Solutions Limited AyersGTS User Manual (Internet) v1.12.0 V!"#$% D&' D '&#(" V)*+ )-Jun-04 I%#'#&(,$-. V)*) 3-Aug-04 U-/&' / I0&1 " V)*4 4+-Dec-04 5// /
More informationDatabase Design. Goal: specification of database schema Methodology: E-R Model is viewed as a set of
Database Design Goal: specification of database schema Methodology: Use E-R model to get a high-level graphical view of essential components of the model and how they are related Convert E-R diagram to
More informationComponentNo. C_Description UnitOfMeasure. C_Quantity
MIS 322: ERD Exercises Student Name: 1. Assume that at Pine Valley Furniture each product (described by Product No., Description, and Cost) is comprised of at least three components (described by Component
More informationLecture #11 Relational Database Systems KTH ROYAL INSTITUTE OF TECHNOLOGY
Lecture #11 Relational Database Systems KTH ROYAL INSTITUTE OF TECHNOLOGY Contents Storing data Relational Database Systems Entity Relationship diagrams Normalisation of ER diagrams Tuple Relational Calculus
More informationChapter 2: Entity-Relationship Model
Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E R Diagram Extended E-R Features Design of an E-R Database Schema Reduction of an E-R Schema to
More informationThere are five fields or columns, with names and types as shown above.
3 THE RELATIONAL MODEL Exercise 3.1 Define the following terms: relation schema, relational database schema, domain, attribute, attribute domain, relation instance, relation cardinality, andrelation degree.
More information