ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.
-
Upload
vanessa-paul -
Category
Documents
-
view
226 -
download
1
Transcript of ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.
![Page 1: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/1.jpg)
ENTITY-RELATIONSHIP MODEL
Database System : the complete bookChapter 2
![Page 2: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/2.jpg)
Systems Development Life Cycle
Project Identification and Selection
Project Initiation and Planning
Analysis
Physical Design
Implementation
Maintenance
Logical Design
![Page 3: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/3.jpg)
Purpose of E-R Model
The E/R model allows us to sketch database schema designs Includes some constraints, but not
operations. Designs are pictures called entity-
relationship diagrams Later: convert E/R designs to relational
DB designs
![Page 4: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/4.jpg)
Elements of ER Model
In the E-R Model the structure is represented graphically using three element types:
Entity set: collection of similar entities Attribute: property of (the entities of) an
entity set Relationships: Connection among two or
more entity set
![Page 5: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/5.jpg)
ER Diagrams
An ER diagram is a graph representing entity sets, attribute, and relationships
In an entity-relationship diagram: Entity set are represented by rectangle Attribute represented by oval, with a line to
the rectangle representing its entity set Relationships are represented by diamonds
![Page 6: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/6.jpg)
Example
Entity set student has two attributes, name and e-mail
Each entity has values for these two attributes, e.g. (Bilal, [email protected])
Student
name email
![Page 7: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/7.jpg)
Relationships
A relationship connects two or more entity sets
It is represented by a diamond, with lines to each of the entity sets involved
![Page 8: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/8.jpg)
Example: Relationships
Exam dateTime
courses
idname
Student
name
addr
take
Has writtenAppears
![Page 9: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/9.jpg)
Multi-way Relationships
Sometimes, we need a relationship that connects more than two entity sets
Suppose that drinkers will only drink certain beers at certain bars
![Page 10: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/10.jpg)
Example: 3-Way Relationship
Bars Beers
Drinkers
name nameaddr manf
name addr
license
Preferences
![Page 11: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/11.jpg)
The Entity Relationship Model Widely accepted and adapted graphical
tool for data modeling
Introduced by Chen in 1976
Graphical representation of entities and their relationships in a database structure
![Page 12: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/12.jpg)
The Entity Relationship Model—Basic Structure Entity relationship diagram (ERD)
Uses graphic representations to model database components
Entity is mapped to a relational table Entity instance (or occurrence) is row in
table Entity set is collection of like entities Connectivity labels types of relationships
Diamond connected to related entities through a relationship line
![Page 13: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/13.jpg)
The Entity Relationship Model
Advantages
Exceptional conceptual simplicity
Visual representation
Effective communication tool
Integrated with the relational data model
![Page 14: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/14.jpg)
The Entity Relationship Model (continued) Disadvantages
Limited constraint representation
Limited relationship representation
No data manipulation language
Loss of information content
![Page 15: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/15.jpg)
Many-One Relationships
Some binary relationships are many -one from one entity set to another
Each entity of the first set is connected to at most one entity of the second set
But an entity of the second set can be connected to zero, one, or many entities of the first set
![Page 16: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/16.jpg)
Example: Many-One Relationship Favorite, from Drinkers to Beers is many-
one A drinker has at most one favorite beer But a beer can be the favorite of any
number of drinkers, including zero
![Page 17: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/17.jpg)
One-One Relationships
In a one-one relationship, each entity of either entity set is related to at most one entity of the other set.
Example: Relationship Best-seller between entity sets Manfs (manufacturer) and Beers. A beer cannot be made by more than one
manufacturer, and no manufacturer can have more than one best-seller (assume no ties).
![Page 18: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/18.jpg)
Example: Many-One Relationship
Drinkers BeersLikes
FavoriteNotice: two relationshipsconnect the same entitysets, but are different.
![Page 19: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/19.jpg)
Example: One-One Relationship
Consider Best-seller between Manfs and Beers.
Some beers are not the best-seller of any manufacturer, so a rounded arrow to Manfs would be inappropriate.
But a beer manufacturer has to have a best-seller.
![Page 20: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/20.jpg)
In the ER Diagram
Manfs BeersBest-seller
A manufacturer hasexactly one bestseller.
A beer is the best-seller for 0 or 1manufacturer
![Page 21: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/21.jpg)
Many-Many Relationships
Focus: binary relationships, such as Sells between Bars and Beers
In a many-many relationship, an entity of either set can be connected to many entities of the other set E.g., a bar sells many beers; a beer is sold
by many bars
![Page 22: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/22.jpg)
Relationships: The Basic Chen ERD
![Page 23: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/23.jpg)
Relationships: The Basic Crow’s Foot ERD
![Page 24: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/24.jpg)
Attributes on Relationships
Sometimes it is useful to attach an attribute to a relationship
Think of this attribute as a property of tuples in the relationship set
![Page 25: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/25.jpg)
Example: Attribute on Relationship
Bars BeersSells
price
Price is a function of both the bar and the beer,not of one alone
![Page 26: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/26.jpg)
Equivalent Diagrams Without Attributes on Relationships
Create an entity set representing values of the attribute
Make that entity set participate in the relationship
![Page 27: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/27.jpg)
Example: Removing an Attribute from a Relationship
Bars BeersSells
price
Prices
![Page 28: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/28.jpg)
Roles
Sometimes an entity set appears more than once in a relationship
Label the edges between the relationship and the entity set with names called roles
![Page 29: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/29.jpg)
Example: Roles
Drinkers
Married
husband wife
![Page 30: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/30.jpg)
Subclasses in ER Diagrams
Assume subclasses form a tree I.e., no multiple inheritance
Isa triangles indicate the subclass relationship Point to the superclass
![Page 31: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/31.jpg)
Example: Subclasses
Car
Toyota
isa
name manf
color
![Page 32: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/32.jpg)
Keys
A key is a set of attributes for one entity set such that no two entities in this set agree on all the attributes of the key It is allowed for two entities to agree on
some, but not all, of the key attributes We must designate a key for every
entity set Underline the key attribute(s)
![Page 33: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/33.jpg)
Example: name is Key for Beers
Beers
Ales
isa
name manf
color
![Page 34: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/34.jpg)
Example: a Multi-attribute Key
Courses
dept number hours room
• Note that hours and room could also serve as a key, but we must select only one key.
![Page 35: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/35.jpg)
Weak Entity Sets
Occasionally, entities of an entity set need “help” to identify them uniquely
Entity set E is said to be weak if in order to identify entities of E uniquely, we need to follow one or more many-one relationships from E and include the key of the related entities from the connected entity sets
![Page 36: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/36.jpg)
Example: Weak Entity Set
name is almost a key for football players, but there might be two with the same name
number is certainly not a key, since players on two teams could have the same number
But number, together with the team name related to the player by Plays-on should be unique
![Page 37: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/37.jpg)
In E/R Diagrams
Players TeamsPlays-on
name namenumber
• Double diamond for supporting many-one relationship.• Double rectangle for the weak entity set.
Note: must be roundedbecause each player needsa team to help with the key.
![Page 38: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/38.jpg)
Weak Entity-Set Rules
A weak entity set has one or more many-one relationships to other (supporting) entity sets. Not every many-one relationship from a
weak entity set need be supporting. But supporting relationships must have a
rounded arrow (entity at the “one” end is guaranteed).
![Page 39: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/39.jpg)
Weak Entity-Set Rules – (2)
The key for a weak entity set is its own underlined attributes and the keys for the supporting entity sets. E.g., (player) number and (team) name is a
key for Players in the previous example.
![Page 40: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/40.jpg)
Design Techniques
1. Avoid redundancy.2. Limit the use of weak entity sets.3. Don’t use an entity set when an
attribute will do.
![Page 41: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/41.jpg)
Avoiding Redundancy
Redundancy = saying the same thing in two (or more) different ways.
Wastes space and (more importantly) encourages inconsistency. Two representations of the same fact
become inconsistent if we change one and forget to change the other.
Recall anomalies due to FD’s.
![Page 42: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/42.jpg)
Example: Good
Beers ManfsManfBy
name
This design gives the address of each manufacturer exactly once.
name addr
![Page 43: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/43.jpg)
Example: Bad
Beers ManfsManfBy
name
This design states the manufacturer of a beer twice: as an attribute and as a related entity.
name
manf
addr
![Page 44: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/44.jpg)
Example: Bad
Beers
name
This design repeats the manufacturer’s address once for each beer and loses the address if there are temporarily no beers for a manufacturer.
manf manfAddr
![Page 45: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/45.jpg)
Entity Sets Versus Attributes An entity set should satisfy at least one
of the following conditions: It is more than the name of something; it
has at least one nonkey attribute.or
It is the “many” in a many-one or many-many relationship.
![Page 46: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/46.jpg)
Example: Good
Beers ManfsManfBy
name
•Manfs deserves to be an entity set because of the nonkey attribute addr.•Beers deserves to be an entity set because it is the “many” of the many-one relationship ManfBy.
name addr
![Page 47: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/47.jpg)
Example: Good
Beers
name
There is no need to make the manufacturer an entity set, because we record nothing about manufacturers besides their name.
manf
![Page 48: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/48.jpg)
Example: Bad
Beers ManfsManfBy
name
Since the manufacturer is nothing but a name, and is not at the “many” end of any relationship, it should not be an entity set.
name
![Page 49: ENTITY-RELATIONSHIP MODEL Database System : the complete book Chapter 2.](https://reader036.fdocuments.net/reader036/viewer/2022062517/56649f265503460f94c3ccef/html5/thumbnails/49.jpg)
References
• Chapter 2 Database systems: the complete book
• VU handouts Lecture No. 7 in it