Chapter 1 Data model in DBMS
Chapter 1 Data model in DBMS
The conceptual data model describes the database at a very high level
and is useful to understand the needs or requirements of the database. It is this
model, that is used in the requirement-gathering process i.e. before the Database
Designers start making a particular database. One such popular model is the
entity/relationship model (ER model). The E/R model specializes in entities,
relationships, and even attributes that are used by database designers. In terms
of this concept, a discussion can be made even with non-computer science(non-
technical) users and stakeholders, and their requirements can be understood.
a. Components of ER Model:
• This type of Data Models are designed and developed for a business
audience.
This type of data model is used to represent only the logical part of the
database and does not represent the physical structure of the database. The
representational data model allows us to focus primarily, on the design part of the
database. A popular representational model is a Relational model. The relational
Model consists of Relational Algebra and Relational Calculs. In the Relational
Model, we basically use tables to represent our data and the relationships
between them. It is a theoretical concept whose practical implementation is
done in Physical Data Model.
The physical Data Model is used to practically implement Relational Data Model.
Ultimately, all data in a database is stored physically on a secondary storage
device such as discs and tapes. This is stored in the form of files, records, and
certain other data structures. It has all the information on the format in which the
files are present and the structure of the databases, the presence of external data
structures, and their relation to each other. Here, we basically save tables in
memory so they can be accessed efficiently. In order to come up with a good
physical model, we have to work on the relational model in a better way.
Structured Query Language (SQL) is used to practically implement Relational
Algebra.
This Data Model describes HOW the system will be implemented using a specific
DBMS system. This model is typically created by DBA and developers. The purpose
is actual implementation of the database.
• The physical data model describes data need for a single project or
application though it maybe integrated with other physical data models
based on project scope.
• Primary and Foreign keys, views, indexes, access profiles, and authorizations,
etc. are defined
1. Hierarchical Model
The hierarchical Model is one of the oldest models in the data model which was
developed by IBM, in the 1950s. In a hierarchical model, data are viewed as a
collection of tables, or we can say segments that form a hierarchical relation. In
this, the data is organized into a tree-like structure where each record consists of
one parent record and many children. Even if the segments are connected as a
chain-like structure by logical associations, then the instant structure can be a fan
structure with multiple branches. We call the illogical associations as directional
associations.
2. Network Model
The Network Model was formalized by the Database Task group in the 1960s. This
model is the generalization of the hierarchical model. This model can consist of
multiple parent segments and these segments are grouped as levels but there
exists a logical association between the segments belonging to any level. Mostly,
there exists a many-to-many logical association between any of the two
segments.
In the Object-Oriented Data Model, data and their relationships are contained in
a single structure which is referred to as an object in this data model. In this, real-
world problems are represented as objects with different attributes. All objects
have multiple relationships between them. Basically, it is a combination of Object
Oriented programming and a Relational Database Model.
The float data model basically consists of a two-dimensional array of data models
that do not contain any duplicate elements in the array. This data model has one
drawback it cannot store a large amount of data that is the tables can not be of
large size.
The Context data model is simply a data model which consists of more than one
data model. For example, the Context data model consists of ER Model, Object-
Oriented Data Model, etc. This model allows users to do more than one thing
which each individual data model can do.
Semi-Structured data models deal with the data in a flexible way. Some entities
may have extra attributes and some entities may have some missing attributes.
Basically, you can represent data here in a flexible way.
4. The data model should be detailed enough to be used for building the
physical database.
5. The information in the data model can be used for defining the relationship
between tables, primary and foreign keys, and stored procedures.
Conclusion
• Data modeling is the process of developing data model for the data to be
stored in a Database.
• Data Models ensure consistency in naming conventions, default values,
semantics, security while ensuring quality of the data.
• Data Model structure helps to define the relational tables, primary and
foreign keys and stored procedures.
• There are three types of conceptual, logical, and physical.
• The main aim of conceptual model is to establish the entities, their attributes,
and their relationships.
• Logical data model defines the structure of the data elements and set the
relationships between them.
• A Physical Data Model describes the database specific implementation of
the data model.
• The main goal of a designing data model is to make certain that data
objects offered by the functional team are represented accurately.
• The biggest drawback is that even smaller change made in structure require
modification in the entire application.