Entity Relationship Model  Presented By  Swati Patil
Introduction A model is an abstraction process that hides details not required Data model is a collection of conceptual tools for describing data and data relationships The abstraction levels : Physical Level, Logical level and View Level There are three various types of models Object Based Logical Model – Used for describing data at logical and view levels. Record Based Logical Model  Physical Model
Basic Concepts of E-R Model: It is high level conceptual model which  is based on perception of real world It consists of set of basic objects called as entities and of relationships among these objects. It helps in database design and also helps to represent the overall logical structure of a database It helps to represent the meaning of data .
Three notations of E-R Model –  Entity sets, relationship sets and attributes   Entities: It is the basic object of the ER model which is a “thing” in the real world and independent existence i.e it is distinguishable from other objects. An entity may be an object with a physical existence, for e.g. a particular person–car, house or employee or it may be an object with a conceptual existence e.g a company, job or a university course. An entity set is a set of entities of same type that share same properties or attributes.  For e.g  - Employee Entity set Customer entity set Each individual member of an entity set is called extension of entity set.
Attributes Each entity is described by a set of properties called as attributes. For e.g person entity described by person name, person age, person address. Attributes are descriptive properties of each member of an entity set. A particular entity will have a value of its attributes. It is this value of the attribute of each entity that is stored in the database. For each attributes, there is set of permissible values for that attributes called as domain of attributes. For e.g Domain for employee number attributes of employee entity is the set of all positive integers.
Types of the attributes Simple or atomic and composite attributes .   Those attributes that is not divisible into subparts. Composite attributes are opposite to simple which can be divided into smaller subparts. For e.g employee name is composite attributes as it can be divided into subparts as first name, middle name and last name. These sub parts are turned to simple attributes since they can not further sub divided.
Composite attributes forms a hierarchy for e.g address
Single valued and multi valued attributes Attributes that have single value for particular entitiy called as single valued attributes. For e.g Age is a single valued attribute of a person. The attributes that have a set of values for particular entity are called as multi valued attributes. For e.g College degrees
Multi valued attributes may have lower and upper bound on the number of values for an individual entity.  For e.g in case of bank offering accounts to customers, if customer is allowed to hold maximum three accounts in the bank, then account no. becomes multi valued attribute with upper bound 3
Stored and derived attributes: An attribute value can be derived from the value of another attributes, then it is said to be derived attributes.  For e.g From an attribute birth date. The age can be derived for an employee birth date so age is derived attributes and birth date is stored attribute,  E.g. no of employees of the department can be derived by counting the no. of employees related to that department.
Null attributes: A null value is used when an entity does not have value for an attribute.  For e.g Telephone no.
Relationship and relationship sets: It is association between several entities. For e.g we can define relationship between an employee E1 and the department in which he works say D1. So this becomes relationship between an entity set employee and entity set department.
Mapping Cardinalities: It represents the number of relationship instance that an entity can participate in. i.e the number of entities to which another entity can be associated via a relationship set.  It is useful for binary relationship.
Types of Mapping Cardinalities: one to one –   An entity in A is associated with at most one entity in B and entity B is associated with at most one entity in A .  For e.g employee, department two entities and manages is relationship among these entities
For e.g employee, department
One to Many : An entity in A is associated with many entities of B and an entity in B can be associated  with at most one entity in A. For e.g. Department and employees are two entity set and works in is relationship
One to Many
Many to one: An entity in A is associated at most in entity B and entity in B can be associated any number of entities A.  For e.g Student and class are two entity sets and studying in is the relationship
Many to One
Many to Many: An entity in A is associated with any no. of entities B and an entity in B is associated with any no. of entities in A.  For e.g Employees and project are two entity sets and works in is the relationship
 
Participation: The participation of an entity set E in a relationship set R, is said to be total if every entity in E participates in at least one relationship in R. If only some entities of E participates in R, then participation of entity set E in R is said to be partial.  For e.g Customer borrow Loan
Super key or Primary Key: It is a set of one or more attributes that taken collectively allows us to identify uniquely and entity in the entity set for e.g customer no in customer entity  Weak entity set: An entity may not have enough attribute that can uniquely identify each member of the set such entity set are called weak entity set. An entity set that has a primary key is called is strong entity set. The strong entity set corresponds to weak entity set is also called identifying owner. The relationship that a weak entity type to its owner or strong entity is called identifying relationship of weak entity.
Notations used for E-R diagram:
 
 
Mapping cardinality is indicated by direct line  Or undirected line  Foe e.g Consider Customer ( Cust –name, SSN, address) Account ( acc-no, balance)
 
 
 
 
 
Thank You

More Related Content

PPT
Database Management System
PPTX
E r diagram
PPT
Bsc cs ii-dbms- u-iii-data modeling using e.r. model (entity relationship model)
PPTX
Schema relationship to E-R diagram
PPT
2. Entity Relationship Model in DBMS
PPT
PPT
Er Model Nandha&Mani
PPT
Chapter2
Database Management System
E r diagram
Bsc cs ii-dbms- u-iii-data modeling using e.r. model (entity relationship model)
Schema relationship to E-R diagram
2. Entity Relationship Model in DBMS
Er Model Nandha&Mani
Chapter2

What's hot (19)

PPTX
Design issues with constraints of E-R model
PPT
Data modeling using the entity relationship model
DOCX
Chapter-3 Data Modeling Using the Entity-Relationship Model
PPT
Entity relationship diagram
PPTX
Data model and entity relationship
PPTX
Fundamentals of database system - Data Modeling Using the Entity-Relationshi...
PPT
ER model
PPT
Test presentation
PDF
Database Systems - Entity Relationship Modeling (Chapter 4/2)
PPT
03 Ch3 Notes Revised
PDF
L7 er2
PPT
Unit02 dbms
PPTX
Database Modeling Using Entity.. Weak And Strong Entity Types
PDF
ER Diagrams Simplified
PPT
DBMS PPT
PPT
27 fcs157al3
PPTX
How to Draw an Effective ER diagram
PPT
Entity Relationship Model
PPT
Special lecture er diagram
Design issues with constraints of E-R model
Data modeling using the entity relationship model
Chapter-3 Data Modeling Using the Entity-Relationship Model
Entity relationship diagram
Data model and entity relationship
Fundamentals of database system - Data Modeling Using the Entity-Relationshi...
ER model
Test presentation
Database Systems - Entity Relationship Modeling (Chapter 4/2)
03 Ch3 Notes Revised
L7 er2
Unit02 dbms
Database Modeling Using Entity.. Weak And Strong Entity Types
ER Diagrams Simplified
DBMS PPT
27 fcs157al3
How to Draw an Effective ER diagram
Entity Relationship Model
Special lecture er diagram
Ad

Viewers also liked (13)

PDF
Database management system
PPT
The Power of Social Capital: How To Move Your Business Forward
PPTX
A 2 aumen fund measuring social impact-molly alexander
PPTX
Social capital: Value, Impact and Reporting
PDF
Understanding and Building Social Capital
PPTX
The Future of Social Influence in a Social Capital World
PPTX
Social Network Theory
PPT
Social capital
PDF
3 data modeling using the entity-relationship (er) model
PPT
What is social capital
PPT
PDF
Social Networks and Social Capital
PPTX
Database : Relational Data Model
Database management system
The Power of Social Capital: How To Move Your Business Forward
A 2 aumen fund measuring social impact-molly alexander
Social capital: Value, Impact and Reporting
Understanding and Building Social Capital
The Future of Social Influence in a Social Capital World
Social Network Theory
Social capital
3 data modeling using the entity-relationship (er) model
What is social capital
Social Networks and Social Capital
Database : Relational Data Model
Ad

Similar to E r model (20)

PPTX
Revision ch 3
PPT
ER-Model-ER Diagram
PPT
ermodelN in database management system.ppt
PPT
3144-unit-1entityrmodel-171122051336.ppt
PPTX
ER MODEL
PPTX
Entityrelationshipmodel
PPT
ER Diagram introduction .ppt
PPTX
The Entity-Relationship Model(ER Diagram).pptx
PPTX
entityrelationshipmodel.pptx
PPT
39f1b9a797dbms chapter2 b.sc2
PPT
39f1b9a797dbms chapter2 b.sc2 (1)
PPTX
DBMS Conceptual Design using ER Model.pptx
PPTX
Er model
PPTX
ER-Diagram.pptx , ER diagram , entity reltaionship diagram , data base
PPTX
Database week 5 lecture includes spexiafix
PDF
ERD with complete knowledge
PDF
ER Modelling
PDF
Entity Relationship Model
ODP
ER Model in DBMS
Revision ch 3
ER-Model-ER Diagram
ermodelN in database management system.ppt
3144-unit-1entityrmodel-171122051336.ppt
ER MODEL
Entityrelationshipmodel
ER Diagram introduction .ppt
The Entity-Relationship Model(ER Diagram).pptx
entityrelationshipmodel.pptx
39f1b9a797dbms chapter2 b.sc2
39f1b9a797dbms chapter2 b.sc2 (1)
DBMS Conceptual Design using ER Model.pptx
Er model
ER-Diagram.pptx , ER diagram , entity reltaionship diagram , data base
Database week 5 lecture includes spexiafix
ERD with complete knowledge
ER Modelling
Entity Relationship Model
ER Model in DBMS

Recently uploaded (20)

PPTX
2025 High Blood Pressure Guideline Slide Set.pptx
PPT
Acidosis in Dairy Herds: Causes, Signs, Management, Prevention and Treatment
PPTX
4. Diagnosis and treatment planning in RPD.pptx
PPTX
pharmaceutics-1unit-1-221214121936-550b56aa.pptx
PDF
Chevening Scholarship Application and Interview Preparation Guide
PDF
Hospital Case Study .architecture design
PPTX
Designing Adaptive Learning Paths in Virtual Learning Environments
PDF
anganwadi services for the b.sc nursing and GNM
PPTX
Why I Am A Baptist, History of the Baptist, The Baptist Distinctives, 1st Bap...
PDF
The TKT Course. Modules 1, 2, 3.for self study
PPTX
Reproductive system-Human anatomy and physiology
PPTX
Diploma pharmaceutics notes..helps diploma students
PDF
Farming Based Livelihood Systems English Notes
PDF
Everyday Spelling and Grammar by Kathi Wyldeck
PPTX
IT infrastructure and emerging technologies
PPT
hemostasis and its significance, physiology
PDF
Disorder of Endocrine system (1).pdfyyhyyyy
PPTX
ACFE CERTIFICATION TRAINING ON LAW.pptx
PDF
Horaris_Grups_25-26_Definitiu_15_07_25.pdf
PDF
faiz-khans about Radiotherapy Physics-02.pdf
2025 High Blood Pressure Guideline Slide Set.pptx
Acidosis in Dairy Herds: Causes, Signs, Management, Prevention and Treatment
4. Diagnosis and treatment planning in RPD.pptx
pharmaceutics-1unit-1-221214121936-550b56aa.pptx
Chevening Scholarship Application and Interview Preparation Guide
Hospital Case Study .architecture design
Designing Adaptive Learning Paths in Virtual Learning Environments
anganwadi services for the b.sc nursing and GNM
Why I Am A Baptist, History of the Baptist, The Baptist Distinctives, 1st Bap...
The TKT Course. Modules 1, 2, 3.for self study
Reproductive system-Human anatomy and physiology
Diploma pharmaceutics notes..helps diploma students
Farming Based Livelihood Systems English Notes
Everyday Spelling and Grammar by Kathi Wyldeck
IT infrastructure and emerging technologies
hemostasis and its significance, physiology
Disorder of Endocrine system (1).pdfyyhyyyy
ACFE CERTIFICATION TRAINING ON LAW.pptx
Horaris_Grups_25-26_Definitiu_15_07_25.pdf
faiz-khans about Radiotherapy Physics-02.pdf

E r model

  • 1. Entity Relationship Model Presented By Swati Patil
  • 2. Introduction A model is an abstraction process that hides details not required Data model is a collection of conceptual tools for describing data and data relationships The abstraction levels : Physical Level, Logical level and View Level There are three various types of models Object Based Logical Model – Used for describing data at logical and view levels. Record Based Logical Model Physical Model
  • 3. Basic Concepts of E-R Model: It is high level conceptual model which is based on perception of real world It consists of set of basic objects called as entities and of relationships among these objects. It helps in database design and also helps to represent the overall logical structure of a database It helps to represent the meaning of data .
  • 4. Three notations of E-R Model – Entity sets, relationship sets and attributes Entities: It is the basic object of the ER model which is a “thing” in the real world and independent existence i.e it is distinguishable from other objects. An entity may be an object with a physical existence, for e.g. a particular person–car, house or employee or it may be an object with a conceptual existence e.g a company, job or a university course. An entity set is a set of entities of same type that share same properties or attributes. For e.g - Employee Entity set Customer entity set Each individual member of an entity set is called extension of entity set.
  • 5. Attributes Each entity is described by a set of properties called as attributes. For e.g person entity described by person name, person age, person address. Attributes are descriptive properties of each member of an entity set. A particular entity will have a value of its attributes. It is this value of the attribute of each entity that is stored in the database. For each attributes, there is set of permissible values for that attributes called as domain of attributes. For e.g Domain for employee number attributes of employee entity is the set of all positive integers.
  • 6. Types of the attributes Simple or atomic and composite attributes . Those attributes that is not divisible into subparts. Composite attributes are opposite to simple which can be divided into smaller subparts. For e.g employee name is composite attributes as it can be divided into subparts as first name, middle name and last name. These sub parts are turned to simple attributes since they can not further sub divided.
  • 7. Composite attributes forms a hierarchy for e.g address
  • 8. Single valued and multi valued attributes Attributes that have single value for particular entitiy called as single valued attributes. For e.g Age is a single valued attribute of a person. The attributes that have a set of values for particular entity are called as multi valued attributes. For e.g College degrees
  • 9. Multi valued attributes may have lower and upper bound on the number of values for an individual entity. For e.g in case of bank offering accounts to customers, if customer is allowed to hold maximum three accounts in the bank, then account no. becomes multi valued attribute with upper bound 3
  • 10. Stored and derived attributes: An attribute value can be derived from the value of another attributes, then it is said to be derived attributes. For e.g From an attribute birth date. The age can be derived for an employee birth date so age is derived attributes and birth date is stored attribute, E.g. no of employees of the department can be derived by counting the no. of employees related to that department.
  • 11. Null attributes: A null value is used when an entity does not have value for an attribute. For e.g Telephone no.
  • 12. Relationship and relationship sets: It is association between several entities. For e.g we can define relationship between an employee E1 and the department in which he works say D1. So this becomes relationship between an entity set employee and entity set department.
  • 13. Mapping Cardinalities: It represents the number of relationship instance that an entity can participate in. i.e the number of entities to which another entity can be associated via a relationship set. It is useful for binary relationship.
  • 14. Types of Mapping Cardinalities: one to one – An entity in A is associated with at most one entity in B and entity B is associated with at most one entity in A . For e.g employee, department two entities and manages is relationship among these entities
  • 15. For e.g employee, department
  • 16. One to Many : An entity in A is associated with many entities of B and an entity in B can be associated with at most one entity in A. For e.g. Department and employees are two entity set and works in is relationship
  • 18. Many to one: An entity in A is associated at most in entity B and entity in B can be associated any number of entities A. For e.g Student and class are two entity sets and studying in is the relationship
  • 20. Many to Many: An entity in A is associated with any no. of entities B and an entity in B is associated with any no. of entities in A. For e.g Employees and project are two entity sets and works in is the relationship
  • 21.  
  • 22. Participation: The participation of an entity set E in a relationship set R, is said to be total if every entity in E participates in at least one relationship in R. If only some entities of E participates in R, then participation of entity set E in R is said to be partial. For e.g Customer borrow Loan
  • 23. Super key or Primary Key: It is a set of one or more attributes that taken collectively allows us to identify uniquely and entity in the entity set for e.g customer no in customer entity Weak entity set: An entity may not have enough attribute that can uniquely identify each member of the set such entity set are called weak entity set. An entity set that has a primary key is called is strong entity set. The strong entity set corresponds to weak entity set is also called identifying owner. The relationship that a weak entity type to its owner or strong entity is called identifying relationship of weak entity.
  • 24. Notations used for E-R diagram:
  • 25.  
  • 26.  
  • 27. Mapping cardinality is indicated by direct line Or undirected line Foe e.g Consider Customer ( Cust –name, SSN, address) Account ( acc-no, balance)
  • 28.  
  • 29.  
  • 30.  
  • 31.  
  • 32.