DATA MODELS
Outline
Data Models
1. Relational Model
2. Entity Relationship Model
3. Object-Oriented Data Model
4. Object Relational Data Model
5. Hierarchical Data Model
6. Network Model
DATA MODELS
• Data Model gives us an idea that how the final system will
look like after its complete implementation.
• It defines the data elements and the relationships between the
data elements. Data Models are used to show how data is
stored, connected, accessed and updated in the database
management system.
• we use a set of symbols and text to represent the information
so that members of the organization can communicate and
understand it.
TYPES DATA MODELS
1. RELATIONAL MODEL
2. ENTITY-RELATIONSHIP MODEL
3. OBJECT-ORIENTED DATA MODEL
4. OBJECT-RELATIONAL DATA MODEL
5. HIERARCHICAL MODEL
6. NETWORK MODEL
RELATIONAL MODEL
• The most popular data model in DBMS is the Relational
Model.
• It is more scientific a model than others.
RELATIONAL MODEL
The main highlights of this model are −
Data is stored in tables called relations.
Each row in a relation contains a unique value.
Each column in a relation contains values from a same
domain.
ENTITY-RELATIONSHIP MODEL
• Entity-Relationship (ER) Model is based on the notion of
real-world entities and relationships among them. While
formulating real-world scenario into the database model, the
ER Model creates entity set, relationship set, general
attributes and constraints.
• ER Model is best used for the conceptual design of a
database.
• ER Model is based on −
Entities and their attributes.
Relationships among entities.
ENTITY-RELATIONSHIP MODEL
Entity − An entity in an ER Model is a real-world entity having
properties called attributes. Every attribute is defined by its set of
values called domain. For example, in a school database, a student is
considered as an entity. Student has various attributes like name, age,
class, etc.
Relationship − The logical association among entities is
called relationship. Relationships are mapped with entities in various
ways. Mapping cardinalities define the number of association between
two entities.
Mapping cardinalities −
o one to one
o one to many
o many to one
o many to many
OBJECT-ORIENTED DATA MODEL
• The real-world problems are more closely represented through
the object-oriented data model.
• In this model, both the data and relationship are present in a
single structure known as an object.
• We can store audio, video, images, etc. in the database which
was not possible in the relational model (although you can store
audio and video in relational database, it is advised not to store
in the relational database).
• In this model, two are more objects are connected through links.
We use this link to relate one object to other objects.
OBJECT-ORIENTED DATA MODEL
• In the above example, we have two objects employee and
department. All the data and relationships of each object
are contained as a single unit.
• The attributes like name, job_title of the employee and the
methods which will be performed by that object are stored
as a single object.
• The two objects are connected through a common
attribute i.e. the department_id and the communication
between these two will be done with the help of this
OBJECT-RELATIONAL MODEL
• As the name suggests it is a combination of both the
relational model and the object-oriented model.
• This model was built to fill the gap between object-oriented
model and the relational model.
• The problem with this model is that this can get complex and
difficult to handle. So, proper understanding of this model is
required.
HIERARCHICAL MODEL
• Hierarchical Model was the first DBMS model.
• This model organizes the data in the hierarchical tree
structure.
• The hierarchy starts from the root which has root data and
then it expands in the form of a tree adding child node to the
parent node. Example: We can represent the
relationship between the shoes present on a
shopping website in the following way:
NETWORK MODEL
• This model is an extension of the hierarchical model.
• It was the most popular model before the relational model.
This model is the same as the hierarchical model, the only
difference is that a record can have more than one parent. It
replaces the hierarchical tree with a graph.
• Example: In the example below we can see that node student
has two parents i.e. CSE Department and Library. This was
earlier not possible in the hierarchical model.
Thank you
