Use a high-level conceptual data model (ER Model). Identify objects of interest (entities) and relationships between these objects



Similar documents
Entity-Relationship Model

Chapter 3. Data Modeling Using the Entity-Relationship (ER) Model

THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)

The example is taken from Sect. 1.2 of Vol. 1 of the CPN book.

Entity-Relationship Model

Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model

Architecture of the proposed standard

June Enprise Rent. Enprise Author: Document Version: Product: Product Version: SAP Version:

Adverse Selection and Moral Hazard in a Model With 2 States of the World

QUANTITATIVE METHODS CLASSES WEEK SEVEN

WORKERS' COMPENSATION ANALYST, 1774 SENIOR WORKERS' COMPENSATION ANALYST, 1769

Free ACA SOLUTION (IRS 1094&1095 Reporting)

Lecture 20: Emitter Follower and Differential Amplifiers

Category 7: Employee Commuting

FACULTY SALARIES FALL NKU CUPA Data Compared To Published National Data

Basis risk. When speaking about forward or futures contracts, basis risk is the market

CSC 742 Database Management Systems

Remember you can apply online. It s quick and easy. Go to Title. Forename(s) Surname. Sex. Male Date of birth D

Data warehouse on Manpower Employment for Decision Support System

Traffic Flow Analysis (2)

Attached Benefit Enrollment Forms must be returned to the Business Office within 30 days after your first day of work

REPORT' Meeting Date: April 19,201 2 Audit Committee

Category 1: Purchased Goods and Services

C H A P T E R 1 Writing Reports with SAS

Cookie Policy- May 5, 2014

Mathematics. Mathematics 3. hsn.uk.net. Higher HSN23000

by John Donald, Lecturer, School of Accounting, Economics and Finance, Deakin University, Australia

User-Perceived Quality of Service in Hybrid Broadcast and Telecommunication Networks

ER & EER to Relational Mapping. Chapter 9 1

Business rules FATCA V. 02/11/2015

Sci.Int.(Lahore),26(1), ,2014 ISSN ; CODEN: SINTE 8 131

On the moments of the aggregate discounted claims with dependence introduced by a FGM copula

2. Conceptual Modeling using the Entity-Relationship Model

The international Internet site of the geoviticulture MCC system Le site Internet international du système CCM géoviticole

CPS 220 Theory of Computation REGULAR LANGUAGES. Regular expressions

Planning and Managing Copper Cable Maintenance through Cost- Benefit Modeling

Foundations of Information Management

SCHOOLS' PPP : PROJECT MANAGEMENT

Fleet vehicles opportunities for carbon management

union scholars program APPLICATION DEADLINE: FEBRUARY 28 YOU CAN CHANGE THE WORLD... AND EARN MONEY FOR COLLEGE AT THE SAME TIME!

CARE QUALITY COMMISSION ESSENTIAL STANDARDS OF QUALITY AND SAFETY. Outcome 10 Regulation 11 Safety and Suitability of Premises

(Analytic Formula for the European Normal Black Scholes Formula)

This page is left blank intentionally.

Projections - 3D Viewing. Overview Lecture 4. Projection - 3D viewing. Projections. Projections Parallel Perspective

Whole Systems Approach to CO 2 Capture, Transport and Storage

COMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model

Econ 371: Answer Key for Problem Set 1 (Chapter 12-13)

Keynote Speech Collaborative Web Services and Peer-to-Peer Grids

New Basis Functions. Section 8. Complex Fourier Series

AP Calculus AB 2008 Scoring Guidelines

Key Management System Framework for Cloud Storage Singa Suparman, Eng Pin Kwang Temasek Polytechnic

B April 21, The Honorable Charles B. Rangel Ranking Minority Member Committee on Ways and Means House of Representatives

Asset set Liability Management for

5.3.2 APPROACH TO PERFORMANCE MANAGEMENT

CPU. Rasterization. Per Vertex Operations & Primitive Assembly. Polynomial Evaluator. Frame Buffer. Per Fragment. Display List.

An IAC Approach for Detecting Profile Cloning in Online Social Networks

not necessarily strictly sequential feedback loops exist, i.e. may need to revisit earlier stages during a later stage

DATABASE DESIGN. - Developing database and information systems is performed using a development lifecycle, which consists of a series of steps.

Keywords Cloud Computing, Service level agreement, cloud provider, business level policies, performance objectives.

Logo Design/Development 1-on-1

Do Not Cut, Fold, or Staple Forms on This Page Do Not Cut, Fold, or Staple Forms on This Page

MAXIMAL CHAINS IN THE TURING DEGREES

Essays on Adverse Selection and Moral Hazard in Insurance Market

SPREAD OPTION VALUATION AND THE FAST FOURIER TRANSFORM

Expert-Mediated Search

Upper Bounding the Price of Anarchy in Atomic Splittable Selfish Routing

! Home%Rental%Information%and%Application%%!! NeighborWorks!Provo!is!a!non1profit!organization.!We!have!been!creating!

Sample Green Belt Certification Examination Questions with Answers

YouthWorks Youth Works (yüth- w rkz), n.

Database Systems. Session 3 Main Theme. Enterprise Data Modeling Using The Entity/Relationship (ER) Model. Dr. Jean-Claude Franchitti

Chapter 2: Entity-Relationship Model. E-R R Diagrams

ESTIMATING VEHICLE ROADSIDE ENCROACHMENT FREQUENCY USING ACCIDENT PREDICTION MODELS

TIME MANAGEMENT. 1 The Process for Effective Time Management 2 Barriers to Time Management 3 SMART Goals 4 The POWER Model e. Section 1.

Rural and Remote Broadband Access: Issues and Solutions in Australia

Caution laser! Avoid direct eye contact with the laser beam!

Lecture 3: Diffusion: Fick s first law

An Adaptive Clustering MAP Algorithm to Filter Speckle in Multilook SAR Images

Teaching Computer Networking with the Help of Personal Computer Networks

Data Analysis 1. SET08104 Database Systems. Napier University

5 2 index. e e. Prime numbers. Prime factors and factor trees. Powers. worked example 10. base. power

Enforcing Fine-grained Authorization Policies for Java Mobile Agents

Parallel and Distributed Programming. Performance Metrics

Developing Software Bug Prediction Models Using Various Software Metrics as the Bug Indicators

Personal Identity Verification (PIV) Enablement Solutions

The price of liquidity in constant leverage strategies. Marcos Escobar, Andreas Kiechle, Luis Seco and Rudi Zagst

Unit 2.1. Data Analysis 1 - V Data Analysis 1. Dr Gordon Russell, Napier University

ANDREAS MAHENDRO KUNCORO S.T., University of Gadjah Mada, 2004 M.S., University of Cincinnati, 2009 M.S., University of Central Florida, 2010

IHE IT Infrastructure (ITI) Technical Framework Supplement. Cross-Enterprise Document Workflow (XDW) Trial Implementation

Usability Test of UCRS e-learning DVD

Vector Network Analyzer

Database Design Process

Long run: Law of one price Purchasing Power Parity. Short run: Market for foreign exchange Factors affecting the market for foreign exchange

Continuity Cloud Virtual Firewall Guide

Category 11: Use of Sold Products

Business Systems Analysis with Ontologies

SPECIAL VOWEL SOUNDS

UNIVERSITY OF NAIROBI SCHOOL OF COMPUTING & INFORMATICS IMPROVING APPLICATION OF KNOWLEDGE MANAGEMENT SYSTEMS IN ORGANIZATIONS:

Constraint-Based Analysis of Gene Deletion in a Metabolic Network

Transcription:

Chaptr 3: Entity Rlationship Modl Databas Dsign Procss Us a high-lvl concptual data modl (ER Modl). Idntify objcts of intrst (ntitis) and rlationships btwn ths objcts Idntify constraints (conditions) End rsult is an E-R Diagram that capturs all ntity, rlationship typs and constraints Figur 3. Phass of Databas Dsign

Miniworld DBMS-indpndnt DBMS-spcific Functional Rquirmnts FUNCTIONAL ANALYSIS High-lvl Transaction Spcification APPLICATION PROGRAM DESIGN REQUIREMENTS COLLECTION AND ANALYSIS Databas Rquirmnts CONCEPTUAL DESIGN Concptual Schma (In a high-lvl data modl) LOGICAL DESIGN (DATA MODEL MAPPING) Logical (Concptual) Schma (In th data modl of a spcific DBMS) PHYSICAL DESIGN Figur 3. A simplifid diagram to illustrat th main phass of databas dsign. TRANSACTION IMPLEMENTATION Intrnal Schma Application Programs

Exampl Databas Application (Company Databas) Company organizd into DEPARTMENTs. Each dpartmnt has uniqu nam and a particular mploy who manags th dpartmnt. Start dat for th managr is rcordd. Dpartmnt may hav svral locations. A dpartmnt controls a numbr of PROJECTs. Projcts hav a uniqu nam, numbr and a singl location. Company s EMPLOYEEs nam, ssno, addrss, salary, sx and birth dat ar rcordd. An mploy is assignd to on dpartmnt, but may work for svral projcts (not ncssarily controlld by hr dpt). Numbr of hours/wk an mploy works on ach projct is rcordd; Th immdiat suprvisor for th mploy. Employ s DEPENDENTs ar trackd for halth insuranc purposs (dpndnt nam, birthdat, rlationship to mploy). Figur 3.2: ER Diagram

Figur 3.2 ER schma diagram for th company databas. Fnam Minit Lnam Numbr Nam Addrss N WORKS_FOR Nam Locations Sx Salary Ssn Bdat EMPLOYEE NumbrOfEmploys StartDat MANAGES DEPARTMENT CONTROLS N Hours suprvisor suprvis WORKS_ON N PROJECT SUPERVISION N Nam Location DEPENDENTS_OF Numbr N DEPENDENT Nam Sx BirthDat Rlationship

Entitis and Attributs Entity: an objct in th ral world with an indpndnt xistnc. Attribut: Proprty that dscribs an aspct of th ntity. Figur 3.3 Attribut typs: Simpl vs Composit (Figur 3.4) Singl-valud vs Multi-valud (.g. Locations for DEPARTMENT) Stord vs Drivd (.g. NumbrOfEmploys for DEPARTMENT) Figur 3.5: xampl of a complx attribut with multi-valud and composit componnts Null valus for attributs: Not applicabl, Unknown (Missing; not known if applicabl)

Figur 3.3 Two ntitis, an mploy and a company c, and thir attribut valus. Nam = John Smith Nam = Sunco Oil Addrss = 23 Kirby, Houston, Txas 7700 c Hadquartrs = Houston Ag = 55 HomPhon = 73-749-2630 Prsidnt = John Smith

Figur 3.4 A hirarchy of composit attributs; th StrtAddrss componnt of an Addrss is furthr composd of Numbr, Strt, and ApartmntNumbr. Addrss StrtAddrss City Stat Zip Numbr Strt ApartmntNumbr

Figur 3.5 A complx attribut AddrssPhon with multivalud and composit componnts. {AddrssPhon( {Phon(AraCod,PhonNumbr)}, Addrss(StrtAddrss(Numbr,Strt,ApartmntNumbr), City,Stat,Zip) ) }

Entity Typs, Valu Sts, Ky Attributs An ntity typ dfins a st of ntitis that hav th sam attributs. S Figur 3.6 Rctangular box in ER Diagram dnots Entity Typs Ovals dnot Attributs doubl-ovals: multi-valud attribut tr structurd ovals: composit attribut Entity St = St of all ntitis of th sam typ. Ky Attributs: uniquly idntify ach ntity within an ntity st (ths ar undrlind in th ER Diagram) Valu Sts: or Domains for attributs. A: E -> P(V) A:attribut, E:Entity st, V: Valu st V = P(V) x... x P(Vn) for composit attributs A() dnots th valu of attribut A for ntity Figur 3.7 Car Entity Typ

Figur 3.6 Two ntity typs namd EMPLOYEE and COMPANY, and som of th mmbr ntitis in th collction of ntitis (or ntity st) of ach typ. ENTITY TYPE NAME: EMPLOYEE Nam, Ag, Salary COMPANY Nam, Hadquartrs, Prsidnt c (John Smith, 55, 80k) (Sunco Oil, Houston, John Smith) ENTITY SET: (EXTENSION) 2 (Frd Brown, 40, 30K) 3 (Judy Clark, 25, 20K) c 2 (Fast Computr, Dallas, Bob King)

Figur 3.7 Th CAR ntity typ, with two ky attributs Rgistration and VhiclID. Multivalud attributs ar shown btwn st bracs {}. Componnts of a composit attribut ar shown btwn parnthss (). CAR Rgistration(RgistrationNumbr, Stat), VhiclID, Mak, Modl, Yar, {Color} car ((ABC 23, TEXAS), TK629, Ford Mustang, convrtibl, 998, {rd, black}) car 2 ((ABC 23, NEW YORK), WP9872, Nissan Maxima, 4-door, 999, {blu}) car 3 ((VSY 720, TEXAS), TD729, Chryslr LBaron, 4-door, 995, {whit, blu})

Initial dsign of th COMPANY DATABASE Figur 3.8 4 ntity typs: DEPARTMENT EMPLOYEE PROJECT DEPENDENT Not a prfct dsign! bcaus it capturs rlationships btwn ntitis as attributs (in gnral not a good ida)

Figur 3.8 Prliminary dsign of ntity typs for th COMPANY databas whos rquirmnts ar dscribd in Sction 3.2. DEPARTMENT Nam, Numbr, {Locations}, Managr, ManagrStartDat PROJECT Nam, Numbr, Location, ControllingDpartmnt EMPLOYEE Nam (FNam, MInit, LNam), SSN, Sx, Addrss, Salary, BirthDat, Dpartmnt, Suprvisor, {WorksOn (Projct, Hours)} DEPENDENT Employ, DpndntNam, Sx, BirthDat, Rlationship

Rlationships, Rols, Structural Constraints Rlationship typ: R among n Entity typs E,..., En dfins a st of associations among ntitis from ths typs. ach association will b dnotd as: (,..., n) whr i blongs to Ei, <= i <= n. x. WORKS_FOR rlationship in Figur 3.9 Dgr of rlationship = n (usually n = 2, binary rlationship) Trnary rlationship: Figur 3.0 Rlationships as attributs (.g. Dpt -- Empl rlationship can b viwd as two attributs on in Dpt. and th othr in Empl)

Figur 3.9 Som instancs of th WORKS_FOR rlationship btwn EMPLOYEE and DEPARTMENT. EMPLOYEE WORKS_FOR DEPARTMENT r 2 r 2 d 3 r 3 d 2 4 r 4 d 3 5 6 r 5 7 r 6 r 7

Figur 3.0 Som rlationship instancs of a trnary rlationship SUPPLY. SUPPLIER SUPPLY PROJECT s r s 2 r 2 j r 3 j 2 PART r 4 j 3 r 5 p p 2 r 6 p 3 r 7

Rol nams Each ntity participating in a rlationship has a ROLE..g. Employ plays th rol of workr and Dpartmnt plays th rol of mployr in th WORKS_FOR rlationship typ Rol nams ar mor important in rcursiv rlationships x. Figur 3.

Figur 3. Th rcursiv rlationship SUPERVISION, whr th EMPLOYEE ntity typ plays th two rols of suprvisor () and suprvis (2). EMPLOYEE SUPERVISION r 2 2 2 r 2 3 4 2 r 3 5 2 r 4 6 7 2 r 5 2 r 6

Structural Constraints on Rlationships 2 typs: Cardinality Ratio Constraint (-, -N, M-N) Participation Constraint * total participation (xistnc dpndncy) * partial participation Figurs 3.2 and 3.3 In ER Diagrams: total participation is dnotd by doubl lin and partial participation by singl lin cardinality ratios ar mntiond as labls of dgs

Figur 3.2 Th : rlationship MANAGES, with partial participation of mploy and total participation of DEPARTMENT. EMPLOYEE MANAGES DEPARTMENT 2 r d 3 r 2 d 2 4 5 r 3 d 3 6 7

Figur 3.3 Th M:N rlationship WORKS_ON btwn EMPLOYEE and PROJECT. EMPLOYEE WORKS_ON r PROJECT r 2 2 p 3 r 3 p 2 4 r 4 p 3 r 5 p 4 r 6 r 7

Attributs of rlationships:.x. Hours attribut for WORKS_ON rlationship If rlationship is -N or -, ths attributs can b b migratd to th ntity sts involvd in th rlationship. -N: migrat to N sid -: migrat to ithr sid

Wak Entity Typs: Entity Typs that do not hav ky attributs. Such ntitis ar idntifid by bing rlatd to othr ntity sts calld idntifying ownr. This rlationship is calld idntifying rlationship. Partial ky: attributs that uniquly idntify ntitis within th idntifying rlationship. A wak ntity typ always has TOTAL participation. Ex. DEPENDENT is a wak ntity typ.

Notation for ER Diagrams: Fig 3.4, 3.5 (Min,Max) notation ncapsulats both typs of structural constraints. This is mor gnral than prvious notation. Min >= implis TOTAL participation Min = 0 implis PARTIAL participation

Symbol Maning ENTITY TYPE WEAK ENTITY TYPE E R... E 2 RELATIONSHIP TYPE IDENTIFYING RELATIONSHIP TYPE ATTRIBUTE KEY ATTRIBUTE MULTIVALUED ATTRIBUTE COMPOSITE ATTRIBUTE DERIVED ATTRIBUTE TOTAL PARTICIPATION OF E 2 IN R Figur 3.4 Summary of ER diagram notation. E N R E 2 CARDINALITY RATIO : N FOR E :E 2 IN R R (MIN, MAX) E STRUCTURAL CONSTRAINT (min, max) ON PARTICIPATION OF E IN R

Figur 3.5 ER diagram for th COMPANY schma, with all rol nams includd and with structural constraints on rlationships spcifid using th altrnat notation (min, max). Fnam Minit Lnam Addrss Numbr Ssn Bdat Nam (0,N) Sx EMPLOYEE Salary (0,) (,) mploy (0,) managr (,N) workr StartDat WORKS_FOR MANAGES (4,N) dpartmnt NumbrOfEmploys Nam controllingdpartmnt (,) dpartmntmanagd DEPARTMENT Locations (0,N) suprvisor suprvis Hours CONTROLS SUPERVISION (0,N) mploy WORKS_ON projct (,N) controlldprojct (,) DEPENDENTS_OF Nam Numbr PROJECT Location dpndnt (,) DEPENDENT Nam Sx BirthDat Rlationship