# Chapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant

Save this PDF as:

Size: px
Start display at page:

Download "Chapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant"

## Transcription

1 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 Tables 2.1 Entity Sets! A database can be modeled as: " a collection of entities, " relationship among entities.! An entity is an object that exists and is distinguishable from other objects. " Example: specific person, company, event, plant! Entities have attributes " Example: people have names and addresses! An entity set is a set of entities of the same type that share the same properties. " Example: set of all persons, companies, trees, holidays 2.2 1

2 Entity Sets customer and loan customer-id customer- customer- customer- loan- amount name street city number 2.3 Attributes! An entity is represented by a set of attributes, that is descriptive properties possessed by all members of an entity set. Example: customer = (customer-id, customer-name, customer-street, customer-city) loan = (loan-number, amount)! Domain the set of permitted values for each attribute! Attribute types: " Simple and composite attributes. " Single-valued and multi-valued attributes # E.g. multivalued attribute: phone-numbers " Derived attributes # Can be computed from other attributes # E.g. age, given date of birth 2.4 2

3 Composite Attributes 2.5 Relationship Sets! A relationship is an association among several entities Example: Hayes depositor A-102 customer entity relationship set account entity! A relationship set is a mathematical relation among n 2 entities, each taken from entity sets {(e 1, e 2, e n ) e 1 E 1, e 2 E 2,, e n E n } where (e 1, e 2,, e n ) is a relationship " Example: (Hayes, A-102) depositor 2.6 3

4 Relationship Set borrower 2.7 Relationship Sets (Cont.)! An attribute can also be property of a relationship set.! For instance, the depositor relationship set between entity sets customer and account may have the attribute access-date 2.8 4

5 Degree of a Relationship Set! Refers to number of entity sets that participate in a relationship set.! Relationship sets that involve two entity sets are binary (or degree two). Generally, most relationship sets in a database system are binary.! Relationship sets may involve more than two entity sets. "E.g. Suppose employees of a bank may have jobs (responsibilities) at multiple branches, with different jobs at different branches. Then there is a ternary relationship set between entity sets employee, job and branch! Relationships between more than two entity sets are rare. Most relationships are binary. (More on this later.) 2.9 Mapping Cardinalities! Express the number of entities to which another entity can be associated via a relationship set.! Most useful in describing binary relationship sets.! For a binary relationship set the mapping cardinality must be one of the following types: " One to one " One to many " Many to one " Many to many

6 Mapping Cardinalities One to one One to many Note: Some elements in A and B may not be mapped to any elements in the other set 2.11 Mapping Cardinalities Many to one Many to many Note: Some elements in A and B may not be mapped to any elements in the other set

7 Mapping Cardinalities affect ER Design! Can make access-date an attribute of account, instead of a relationship attribute, if each account can have only one customer! I.e., the relationship from account to customer is many to one, or equivalently, customer to account is one to many 2.13 E-R R Diagrams! Rectangles represent entity sets.! Diamonds represent relationship sets.! Lines link attributes to entity sets and entity sets to relationship sets.! Ellipses represent attributes! Double ellipses represent multivalued attributes.! Dashed ellipses denote derived attributes.! Underline indicates primary key attributes (will study later)

8 E-R R Diagram With Composite, Multivalued, and Derived Attributes 2.15 Relationship Sets with Attributes

9 Roles! Entity sets of a relationship need not be distinct! The labels manager and worker are called roles; they specify how employee entities interact via the works-for relationship set.! Roles are indicated in E-R diagrams by labeling the lines that connect diamonds to rectangles.! Role labels are optional, and are used to clarify semantics of the relationship 2.17 Cardinality Constraints! We express cardinality constraints by drawing either a directed line ( ), signifying one, or an undirected line ( ), signifying many, between the relationship set and the entity set.! E.g.: One-to-one relationship: " A customer is associated with at most one loan via the relationship borrower " A loan is associated with at most one customer via borrower

10 One-To To-Many Relationship! In the one-to-many relationship a loan is associated with at most one customer via borrower, a customer is associated with several (including 0) loans via borrower 2.19 Many-To To-One Relationships! In a many-to-one relationship a loan is associated with several (including 0) customers via borrower, a customer is associated with at most one loan via borrower

11 Many-To To-Many Relationship! A customer is associated with several (possibly 0) loans via borrower! A loan is associated with several (possibly 0) customers via borrower 2.21 Participation of an Entity Set in a Relationship Set! Total participation (indicated by double line): every entity in the entity set participates in at least one relationship in the relationship set! E.g. participation of loan in borrower is total! every loan must have a customer associated to it via borrower! Partial participation: some entities may not participate in any relationship in the relationship set! E.g. participation of customer in borrower is partial

12 Alternative Notation for Cardinality Limits! Cardinality limits can also express participation constraints 2.23 Keys! A super key of an entity set is a set of one or more attributes whose values uniquely determine each entity.! A candidate key of an entity set is a minimal super key " Customer-id is candidate key of customer " account-number is candidate key of account! Although several candidate keys may exist, one of the candidate keys is selected to be the primary key

13 Keys for Relationship Sets! The combination of primary keys of the participating entity sets forms a super key of a relationship set. " (customer-id, account-number) is the super key of depositor " NOTE: this means a pair of entity sets can have at most one relationship in a particular relationship set. # E.g. if we wish to track all access-dates to each account by each customer, we cannot assume a relationship for each access. We can use a multivalued attribute though! Must consider the mapping cardinality of the relationship set when deciding the what are the candidate keys! Need to consider semantics of relationship set in selecting the primary key in case of more than one candidate key 2.25 E-R Diagram with a Ternary Relationship

14 Cardinality Constraints on Ternary Relationship! We allow at most one arrow out of a ternary (or greater degree) relationship to indicate a cardinality constraint! E.g. an arrow from works-on to job indicates each employee works on at most one job at any branch.! If there is more than one arrow, there are two ways of defining the meaning. " E.g a ternary relationship R between A, B and C with arrows to B and C could mean " 1. each A entity is associated with a unique entity from B and C or " 2. each pair of entities from (A, B) is associated with a unique C entity, and each pair (A, C) is associated with a unique B " Each alternative has been used in different formalisms " To avoid confusion we outlaw more than one arrow 2.27 Binary Vs. Non-Binary Relationships! Some relationships that appear to be non-binary may be better represented using binary relationships " E.g. A ternary relationship parents, relating a child to his/her father and mother, is best replaced by two binary relationships, father and mother # Using two binary relationships allows partial information (e.g. only mother being know) " But there are some relationships that are naturally non-binary # E.g. works-on

15 Converting Non-Binary Relationships to Binary Form! In general, any non-binary relationship can be represented using binary relationships by creating an artificial entity set. " Replace R between entity sets A, B and C by an entity set E, and three relationship sets: 1. R A, relating E and A 2.R B, relating E and B 3. R C, relating E and C " Create a special identifying attribute for E " Add any attributes of R to E " For each relationship (a i, b i,c i ) in R, create 1. a new entity e i in the entity set E 2. add (e i,a i ) to R A 3. add (e i, b i ) to R B 4. add (e i,c i ) to R C 2.29 Converting Non-Binary Relationships (Cont.)! Also need to translate constraints " Translating all constraints may not be possible " There may be instances in the translated schema that cannot correspond to any instance of R # Exercise: add constraints to the relationships R A, R B and R C to ensure that a newly created entity corresponds to exactly one entity in each of entity sets A, B and C " We can avoid creating an identifying attribute by making E a weak entity set (described shortly) identified by the three relationship sets

16 Design Issues! Use of entity sets vs. attributes Choice mainly depends on the structure of the enterprise being modeled, and on the semantics associated with the attribute in question.! Use of entity sets vs. relationship sets Possible guideline is to designate a relationship set to describe an action that occurs between entities! Binary versus n-ary relationship sets Although it is possible to replace any nonbinary (n-ary, for n > 2) relationship set by a number of distinct binary relationship sets, a n- ary relationship set shows more clearly that several entities participate in a single relationship.! Placement of relationship attributes 2.31 How about doing an ER design interactively on the board? Suggest an application to be modeled. 16

17 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 existence of a identifying entity set " it must relate to the identifying entity set via a total, one-to-many relationship set from the identifying to the weak entity set " Identifying relationship depicted using a double diamond! The discriminator (or partial key) of a weak entity set is the set of attributes that distinguishes among all the entities of a weak entity set.! The primary key of a weak entity set is formed by the primary key of the strong entity set on which the weak entity set is existence dependent, plus the weak entity set s discriminator Weak Entity Sets (Cont.)! We depict a weak entity set by double rectangles.! We underline the discriminator of a weak entity set with a dashed line.! payment-number discriminator of the payment entity set! Primary key for payment (loan-number, payment-number)

18 Weak Entity Sets (Cont.)! Note: the primary key of the strong entity set is not explicitly stored with the weak entity set, since it is implicit in the identifying relationship.! If loan-number were explicitly stored, payment could be made a strong entity, but then the relationship between payment and loan would be duplicated by an implicit relationship defined by the attribute loan-number common to payment and loan 2.35 More Weak Entity Set Examples! In a university, a course is a strong entity and a course-offering can be modeled as a weak entity! The discriminator of course-offering would be semester (including year) and section-number (if there is more than one section)! If we model course-offering as a strong entity we would model course-number as an attribute. Then the relationship with course would be implicit in the coursenumber attribute

19 Specialization! Top-down design process; we designate subgroupings within an entity set that are distinctive from other entities in the set.! These subgroupings become lower-level entity sets that have attributes or participate in relationships that do not apply to the higher-level entity set.! Depicted by a triangle component labeled ISA (E.g. customer is a person).! Attribute inheritance a lower-level entity set inherits all the attributes and relationship participation of the higher-level entity set to which it is linked Specialization Example

20 Generalization! A bottom-up design process combine a number of entity sets that share the same features into a higher-level entity set.! Specialization and generalization are simple inversions of each other; they are represented in an E-R diagram in the same way.! The terms specialization and generalization are used interchangeably Specialization and Generalization (Contd.)! Can have multiple specializations of an entity set based on different features.! E.g. permanent-employee vs. temporary-employee, in addition to officer vs. secretary vs. teller! Each particular employee would be " a member of one of permanent-employee or temporary-employee, " and also a member of one of officer, secretary, or teller! The ISA relationship also referred to as superclass - subclass relationship

21 Design Constraints on a Specialization/Generalization! Constraint on which entities can be members of a given lower-level entity set. " condition-defined # E.g. all customers over 65 years are members of seniorcitizen entity set; senior-citizen ISA person. " user-defined! Constraint on whether or not entities may belong to more than one lower-level entity set within a single generalization. " Disjoint # an entity can belong to only one lower-level entity set # Noted in E-R diagram by writing disjoint next to the ISA triangle " Overlapping # an entity can belong to more than one lower-level entity set 2.41 Design Constraints on a Specialization/Generalization (Contd.)! Completeness constraint -- specifies whether or not an entity in the higher-level entity set must belong to at least one of the lower-level entity sets within a generalization. " total : an entity must belong to one of the lower-level entity sets " partial: an entity need not belong to one of the lower-level entity sets

22 Aggregation! Consider the ternary relationship works-on, which we saw earlier! Suppose we want to record managers for tasks performed by an employee at a branch 2.43 Aggregation (Cont.)! Relationship sets works-on and manages represent overlapping information " Every manages relationship corresponds to a works-on relationship " However, some works-on relationships may not correspond to any manages relationships # So we can t discard the works-on relationship! Eliminate this redundancy via aggregation " Treat relationship as an abstract entity " Allows relationships between relationships " Abstraction of relationship into new entity! Without introducing redundancy, the following diagram represents: " An employee works on a particular job at a particular branch " An employee, branch, job combination may have an associated manager

23 E-R R Diagram With Aggregation 2.45 E-R R Design Decisions! The use of an attribute or entity set to represent an object.! Whether a real-world concept is best expressed by an entity set or a relationship set.! The use of a ternary relationship versus a pair of binary relationships.! The use of a strong or weak entity set.! The use of specialization/generalization contributes to modularity in the design.! The use of aggregation can treat the aggregate entity set as a single unit without concern for the details of its internal structure

24 E-R R Diagram for a Banking Enterprise 2.47 How about doing another ER design interactively on the board? 24

25 Summary of Symbols Used in E-R E Notation 2.49 Summary of Symbols (Cont.)

26 Alternative E-R E R Notations 2.51 UML! UML: Unified Modeling Language! UML has many components to graphically model different aspects of an entire software system! UML Class Diagrams correspond to E-R Diagram, but several differences

27 Summary of UML Class Diagram Notation 2.53 UML Class Diagrams (Contd.)! Entity sets are shown as boxes, and attributes are shown within the box, rather than as separate ellipses in E-R diagrams.! Binary relationship sets are represented in UML by just drawing a line connecting the entity sets. The relationship set name is written adjacent to the line.! The role played by an entity set in a relationship set may also be specified by writing the role name on the line, adjacent to the entity set.! The relationship set name may alternatively be written in a box, along with attributes of the relationship set, and the box is connected, using a dotted line, to the line depicting the relationship set.! Non-binary relationships drawn using diamonds, just as in ER diagrams

28 UML Class Diagram Notation (Cont.) overlapping disjoint *Note reversal of position in cardinality constraint depiction *Generalization can use merged or separate arrows independent of disjoint/overlapping 2.55 UML Class Diagrams (Contd.)! Cardinality constraints are specified in the form l..h, where l denotes the minimum and h the maximum number of relationships an entity can participate in.! Beware: the positioning of the constraints is exactly the reverse of the positioning of constraints in E-R diagrams.! The constraint 0..* on the E2 side and 0..1 on the E1 side means that each E2 entity can participate in at most one relationship, whereas each E1 entity can participate in many relationships; in other words, the relationship is many to one from E2 to E1.! Single values, such as 1 or * may be written on edges; The single value 1 on an edge is treated as equivalent to 1..1, while * is equivalent to 0..*

29 Reduction of an E-R E R Schema to Tables! Primary keys allow entity sets and relationship sets to be expressed uniformly as tables which represent the contents of the database.! A database which conforms to an E-R diagram can be represented by a collection of tables.! For each entity set and relationship set there is a unique table which is assigned the name of the corresponding entity set or relationship set.! Each table has a number of columns (generally corresponding to attributes), which have unique names.! Converting an E-R diagram to a table format is the basis for deriving a relational database design from an E-R diagram Representing Entity Sets as Tables! A strong entity set reduces to a table with the same attributes

30 Composite and Multivalued Attributes! Composite attributes are flattened out by creating a separate attribute for each component attribute " E.g. given entity set customer with composite attribute name with component attributes first-name and last-name the table corresponding to the entity set has two attributes name.first-name and name.last-name! A multivalued attribute M of an entity E is represented by a separate table EM " Table EM has attributes corresponding to the primary key of E and an attribute corresponding to multivalued attribute M " E.g. Multivalued attribute dependent-names of employee is represented by a table employee-dependent-names( employee-id, dname) " Each value of the multivalued attribute maps to a separate row of the table EM # E.g., an employee entity with primary key John and dependents Johnson and Johndotir maps to two rows: (John, Johnson) and (John, Johndotir) 2.59 Representing Weak Entity Sets! A weak entity set becomes a table that includes a column for the primary key of the identifying strong entity set

31 Representing Relationship Sets as Tables! A many-to-many relationship set is represented as a table with columns for the primary keys of the two participating entity sets, and any descriptive attributes of the relationship set.! E.g.: table for relationship set borrower 2.61 Redundancy of Tables! Many-to-one and one-to-many relationship sets that are total on the many-side can be represented by adding an extra attribute to the many side, containing the primary key of the one side! E.g.: Instead of creating a table for relationship accountbranch, add an attribute branch to the entity set account

32 Redundancy of Tables (Cont.)! For one-to-one relationship sets, either side can be chosen to act as the many side " That is, extra attribute can be added to either of the tables corresponding to the two entity sets! If participation is partial on the many side, replacing a table by an extra attribute in the relation corresponding to the many side could result in null values! The table corresponding to a relationship set linking a weak entity set to its identifying strong entity set is redundant. " E.g. The payment table already contains the information that would appear in the loan-payment table (i.e., the columns loan-number and payment-number) Representing Specialization as Tables! Method 1: " Form a table for the higher level entity " Form a table for each lower level entity set, include primary key of higher level entity set and local attributes table table attributes person name, street, city customer name, credit-rating employee name, salary " Drawback: getting information about, e.g., employee requires accessing two tables

33 Representing Specialization as Tables (Cont.)! Method 2: " Form a table for each entity set with all local and inherited attributes table table attributes person name, street, city customer name, street, city, credit-rating employee name, street, city, salary " If specialization is total, table for generalized entity (person) not required to store information # Can be defined as a view relation containing union of specialization tables # But explicit table may still be needed for foreign key constraints " Drawback: street and city may be stored redundantly for persons who are both customers and employees 2.65 Relations Corresponding to Aggregation! To represent aggregation, create a table containing! primary key of the aggregated relationship,! the primary key of the associated entity set! Any descriptive attributes

34 Relations Corresponding to Aggregation (Cont.)! E.g. to represent aggregation manages between relationship works-on and entity set manager, create a table manages(employee-id, branch-name, title, manager-name)! Table works-on is redundant provided we are willing to store null values for attribute manager-name in table manages 2.67 End of Chapter 2 34

35 E-R R Diagram for Exercise E-R R Diagram for Exercise

36 E-R R Diagram for Exercise E-R R Diagram for Exercise

37 Existence Dependencies! If the existence of entity x depends on the existence of entity y, then x is said to be existence dependent on y. " y is a dominant entity (in example below, loan) " x is a subordinate entity (in example below, payment) loan loan-payment payment If a loan entity is deleted, then all its associated payment entities must be deleted also

### Chapter 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

### Chapter 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

### Lesson 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

### Foundations 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:

### We 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

### ER 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

### Foundations of Information Management

Foundations of Information Management - WS 2009/10 Juniorprofessor Alexander Markowetz Bonn Aachen International Center for Information Technology (B-IT) Alexander Markowetz Born 1976 in Brussels, Belgium

### Bİ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

### COMP 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

### OVERVIEW 1.1 DATABASE MANAGEMENT SYSTEM (DBMS) DEFINITION:-

1 1 OVERVIEW Topics Covered: 1.1 Database management system 1.2 Data Independence 1.3 Data Abstraction 1.4 Data Models 1.5 DBMS Architecture 1.6 Users of DBMS 1.7 Overview of Conventional Data Models 1.1

### 2. 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

### The E-R èentity-relationshipè data model views the real world as a set of basic objects èentitiesè and

CMPT-354-Han-95.3 Lecture Notes September 20, 1995 Chapter 2 The Entity-Relationship Model The E-R èentity-relationshipè data model views the real world as a set of basic objects èentitiesè and relationships

### Chapter 8 The Enhanced Entity- Relationship (EER) Model

Chapter 8 The Enhanced Entity- Relationship (EER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 Outline Subclasses, Superclasses, and Inheritance Specialization

### Converting 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

### 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

### Chapter 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

### Database 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

### CSC 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

### Entity-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

### Boyce-Codd Normal Form

4NF Boyce-Codd Normal Form A relation schema R is in BCNF if for all functional dependencies in F + of the form α β at least one of the following holds α β is trivial (i.e., β α) α is a superkey for R

### THE 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

### Lecture 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

### three 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

### Database 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

### Concepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method

Concepts of Database Management Seventh Edition Chapter 6 Database Design 2: Design Method Objectives Discuss the general process and goals of database design Define user views and explain their function

### Databases 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

### Comp 3311 Database Management Systems. 2. Relational Model Exercises

Comp 3311 Database Management Systems 2. Relational Model Exercises 1 E-R Diagram for a Banking Enterprise 2 Tables for ER diagram Entities Branch (branch-name, branch-city, assets) Customer (customer-id,

### Chapter 7: Relational Database Design

Chapter 7: Relational Database Design Database System Concepts, 5th Ed. See www.db book.com for conditions on re use Chapter 7: Relational Database Design Features of Good Relational Design Atomic Domains

### IV. 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

### XV. 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

### not 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

### The Entity-Relationship Model

The Entity-Relationship Model 221 After completing this chapter, you should be able to explain the three phases of database design, Why are multiple phases useful? evaluate the significance of the Entity-Relationship

### Data 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

### Conceptual 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,

### Database 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

### Data 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?

### Conceptual 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

### 7.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

### Data 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

### Data Modeling Basics

Information Technology Standard Commonwealth of Pennsylvania Governor's Office of Administration/Office for Information Technology STD Number: STD-INF003B STD Title: Data Modeling Basics Issued by: Deputy

### Unit 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,

### Basic Concepts. Chapter A: Network Model. Cont.) Data-Structure Diagrams (Cont( Data-Structure Diagrams. General Relationships. The DBTG CODASYL Model

Chapter A: Network Model Basic Concepts Basic Concepts Data-Structure Diagrams The DBTG CODASYL Model DBTG Data-Retrieval Facility DBTG Update Facility DBTG Set-Processing Facility Mapping of Networks

### The 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

### Database 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

### Modern 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

### Exercise 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)

### Review: 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

### The 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,

### Relational 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

### The 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

### The Relational Data Model: Structure

The Relational Data Model: Structure 1 Overview By far the most likely data model in which you ll implement a database application today. Of historical interest: the relational model is not the first implementation

### Using UML Part One Structural Modeling Diagrams

UML Tutorials Using UML Part One Structural Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,

### ER & 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

### Database 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

### Outline. 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

### Introduction to SQL (3.1-3.4)

CSL 451 Introduction to Database Systems Introduction to SQL (3.1-3.4) Department of Computer Science and Engineering Indian Institute of Technology Ropar Narayanan (CK) Chatapuram Krishnan! Summary Parts

### Lecture 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

### Entity-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

### The Relational Model. Ramakrishnan&Gehrke, Chapter 3 CS4320 1

The Relational Model Ramakrishnan&Gehrke, Chapter 3 CS4320 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. Legacy systems in older models

### A 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

### Bridge 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/

### www.gr8ambitionz.com

Data Base Management Systems (DBMS) Study Material (Objective Type questions with Answers) Shared by Akhil Arora Powered by www. your A to Z competitive exam guide Database Objective type questions Q.1

### Chapter 1: Introduction. Database Management System (DBMS)

Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition Language Data Manipulation Language Transaction Management Storage Management Database Administrator Database

### Entity - 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

### Database 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

### Requirement 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

### Designing 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

### Entity 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

### DATABASE INTRODUCTION

Introduction The history of database system research is one of exceptional productivity and startling economic impact. We have learnt that from the days of file-based systems there are better ways to handle

### Database 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:

### 1 Class Diagrams and Entity Relationship Diagrams (ERD)

1 Class Diagrams and Entity Relationship Diagrams (ERD) Class diagrams and ERDs both model the structure of a system. Class diagrams represent the dynamic aspects of a system: both the structural and behavioural

### Relational model. Relational model - practice. Relational Database Definitions 9/27/11. Relational model. Relational Database: Terminology

COS 597A: Principles of Database and Information Systems elational model elational model A formal (mathematical) model to represent objects (data/information), relationships between objects Constraints

### SAMPLE 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

### Database IST400/600. Jian Qin. A collection of data? A computer system? Everything you collected for your group project?

Relational Databases IST400/600 Jian Qin Database A collection of data? Everything you collected for your group project? A computer system? File? Spreadsheet? Information system? Date s criteria: Integration

### Fundamentals 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

### Database Fundamentals: 1

Database Fundamentals Robert J. Robbins Johns Hopkins University rrobbins@gdb.org Database Fundamentals: 1 What is a Database? General: A database is any collection of related data. Restrictive: A database

### Review 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?

### CS 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-

### 11 November 2015. www.isbe.tue.nl. www.isbe.tue.nl

UML Class Diagrams 11 November 2015 UML Class Diagrams The class diagram provides a static structure of all the classes that exist within the system. Classes are arranged in hierarchies sharing common

### Introduction to database management systems

Introduction to database management systems Database management systems module Myself: researcher in INRIA Futurs, Ioana.Manolescu@inria.fr The course: follows (part of) the book "", Fourth Edition Abraham

### Data Model ing Essentials

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

### Advance DBMS. Structured Query Language (SQL)

Structured Query Language (SQL) Introduction Commercial database systems use more user friendly language to specify the queries. SQL is the most influential commercially marketed product language. Other

### Data Modeling with Entity-Relationship Diagrams

Riccardi04 6/28/02 0:20 P Page 6 CHAPTER4 Data odeling with Entity-Relationship Diagrams In this chapter, you will learn: What entity-relationship data modeling is How to read and draw entity-relationship

### Chapter 6: Integrity Constraints

Chapter 6: Integrity Constraints Domain Constraints Referential Integrity Assertions Triggers Functional Dependencies Database Systems Concepts 6.1 Silberschatz, Korth and Sudarshan c 1997 Domain Constraints

### DATABASE 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

### An 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

### DATABASE 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?

About the Tutorial Database Management System or DBMS in short refers to the technology of storing and retrieving users data with utmost efficiency along with appropriate security measures. DBMS allows

### B2.2-R3: INTRODUCTION TO DATABASE MANAGEMENT SYSTEMS

B2.2-R3: INTRODUCTION TO DATABASE MANAGEMENT SYSTEMS NOTE: 1. There are TWO PARTS in this Module/Paper. PART ONE contains FOUR questions and PART TWO contains FIVE questions. 2. PART ONE is to be answered

### Once the schema has been designed, it can be implemented in the RDBMS.

2. Creating a database Designing the database schema... 1 Representing Classes, Attributes and Objects... 2 Data types... 5 Additional constraints... 6 Choosing the right fields... 7 Implementing a table

### Database 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.

### Case studies: Outline. Requirement Engineering. Case Study: Automated Banking System. UML and Case Studies ITNP090 - Object Oriented Software Design

I. Automated Banking System Case studies: Outline Requirements Engineering: OO and incremental software development 1. case study: withdraw money a. use cases b. identifying class/object (class diagram)

### Object-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,

### Chapter 13: Query Processing. Basic Steps in Query Processing

Chapter 13: Query Processing! Overview! Measures of Query Cost! Selection Operation! Sorting! Join Operation! Other Operations! Evaluation of Expressions 13.1 Basic Steps in Query Processing 1. Parsing

### Relational Database Concepts

Relational Database Concepts IBM Information Management Cloud Computing Center of Competence IBM Canada Labs 1 2011 IBM Corporation Agenda Overview Information and Data Models The relational model Entity-Relationship

### Tutorial - Building a Use Case Diagram

Tutorial - Building a Use Case Diagram 1. Introduction A Use Case diagram is a graphical representation of the high-level system scope. It includes use cases, which are pieces of functionality the system

### Uses Crows feet notation for ER Diagrams in ERwin

ER odel Overview Entity types Attributes, keys Relationship types Weak entity types EER odel Outline Subclasses Specialization/Generalization Schea Design Single DB View integration in IS Uses Crows feet