Database Management System

(DBMS) Overview
Understanding the Basics and Key
Features
Name: Prof.M.A.Vhatkar
 Introduction to DBMS
• Definition: A Database Management System (DBMS) is a
software system designed to manage and organize data in a
structured manner.

• Create, modify, and query databases . Manage security

and access controls.

• Efficient storage and retrieval of data.

• Provides a user-friendly environment to store and retrieve

data.
 Key Features of DBMS
Data Modeling : Tools for creating and modifying data models . Data models defines
structure and relationships of data.

Data Storage and Retrieval: Responsible for storing and retrieving data,
Provides various methods for searching and querying data.

Concurrency Control:
Mechanisms for controlling concurrent access.
Ensures multiple users can access data without conflicts.

Data Integrity and Security : Tools for enforcing data integrity and security constraints.
(Data integrity refers to the accuracy, consistency, and reliability of data stored in a
database)
Includes constraints on data values and access controls.

Backup and Recovery:

Mechanisms for backing up data.
Provides recovery options in case of system failure.
 Data Abstraction in DBMS
• Data abstraction in a database system means
hiding the complex details of how data is
stored and organized and exposing only
required details to the user , so that users can
easily access the data they need without
dealing with the complexity. Data integrity
refers to the accuracy, consistency, and
reliability of data stored in a database
 Benefits of Data Abstraction in DBMS
• Simplifies data access: User can get required data
only ,unnecessary data is hidden from the user.

• Focus on Relevant Data: Users see only the relevant data they
need, not the details of how data is managed behind the
scenes.

• Efficient System: This makes the database system more user-

friendly and efficient.

• Abstract View: Users get a simplified view of the data without

the complications.
Levels of Data Abstractions in DBMS
Data abstraction is divided into three levels.

The physical level (internal level)is the lowest

level of abstraction and focuses on how data is
actually stored in the database. It involves
complex data structures and access methods,
making it difficult to understand, and is
managed by Data Administrators (DBAs).

The logical or conceptual level is the

intermediate level of abstraction. It defines
what data is stored and the relationships
between them, representing the data as tables

The highest level of abstraction is the view or

external level, which provides different views
of the data for end-users. This level allows
users to access data based on their specific
queries, making it easier for them to interact
with the database.
 Data Models
A data model in DBMS is a framework that defines how data is structured,
stored, and accessed in a database. It provides a clear blueprint—a detailed
plan or guide—for organizing data, including the relationships and constraints
among different data elements. It offers tools for designing a database at
different levels of abstraction.
 Types of data models
Therefore, there are following four data models used for understanding the
structure of the database:
 Relational Data Model:
• This type of model designs the data in the form
of rows and columns within a table.
• Thus, a relational model uses tables for
representing data and in-between
relationships.
• Tables are also called relations.
• The relational data model is the widely used
model which is primarily used by commercial
data processing applications.
 Entity-Relationship Data Model
• An ER model is the logical representation of data as
objects and relationships among them.

• These objects are known as entities, and relationship is

an association among these entities.
• A set of attributes describe the entities. For example,
student_name, student_id describes the 'student' entity.
• A set of the same type of entities is known as an 'Entity
set', and the set of the same type of relationships is
known as 'relationship set'.
 Object-based Data Model
• In object based data models, the focus is on how data is represented.
• The data is divided into multiple entities each of which have some defining
characteristics.
• These data entities are connected with each other through some relationships.

• So, in object based data models the entities are based on real world models, and
how the data is in real life.
• There is not as much concern over what the data is as compared to how it is
visualized and connected.

• Some examples of object based data models are

• Entity Relationship Data Model

• Object Oriented Data Model

 4) Semi structured Data Model:
• The semi structured data model is different
from other data models. It allows data items
of the same type to have different sets of
attributes. XML (Extensible Markup Language)
is commonly used for semi structured data.
Although XML was first designed to add
markup to text documents, it became
important for data exchange.
 Example of semi structured database
In a traditional database, all entries of the same type must have the same structure.
For instance, in a table of "Books," every entry might need to have fields for "Title,"
"Author," and "ISBN."In a semistructured data model using XML, each "Book" entry
can have different attributes. For example:
<Books>
<Book>
<Title>The Great Gatsby</Title>
<Author>F. Scott Fitzgerald</Author>
<ISBN>9780743273565</ISBN>
</Book>
<Book>
<Title>Introduction to Algorithms</Title>
<Author>Thomas H. Cormen</Author>
<Edition>3rd</Edition>
<Publisher>MIT Press</Publisher>
</Book>
</Books>
 Database design

• Database design is the process of planning and organizing which data

has to store and how data will be stored and accessed in a database. It
involves defining tables, columns, and relationships to ensure efficient
data management.

• Database design is the process of creating a detailed data model of a

database. It involves defining the structure, format, and organization of
the data stored in the database system. The goal is to optimize data
management, ensuring data is stored efficiently, and can be retrieved
and updated quickly and accurately. It involves defining data
structures, relationships, and rules for storing, accessing,
and manipulating data. Effective database design reduces redundancy,
ensures data integrity, and optimizes performance.
 Database Design using ER model
• Database design using the Entity-Relationship
(ER) model involves identifying what data you
need to store (entities), how they are related
(relationships), and what attributes they have.
• This is shown in a diagram called an ER
diagram, which helps organize and connect
the data logically in tables, ensuring
everything is structured and easy to manage.
 Introduction of ER Model
• ER diagrams are used to represent the E-R model in a database, which
makes them easy to convert into relations (tables).

• ER diagrams are really helpful because they show how real things are
connected in a simple way.

• ER diagrams require no technical knowledge and no hardware support.

• These diagrams are very easy to understand and easy to create even
for a naive user.

• It gives a standard solution for visualizing the data logically.

 Symbols Used in ER Model
• ER Model is used to model the logical view of the
system from a data perspective which consists of
these symbols:
 Components of ER Diagram
• ER Model consists of Entities, Attributes, and
Relationships among Entities in a Database
System
Entity and Entity set
• An entity is a specific thing we want to
store information about, like a person or a
product. Each entity has its own set of
details, called attributes, such as a person's
name or a product's price.

• An entity set is a group of similar entities ,

like all the students in a school or all the
products in a store. Each thing in the group
(an entity) has its own details (attributes),
such as a student's name or a product's
price.
 Strong entity and weak entity
• 1. Strong Entity
• A strong entity is a type of entity that has a key Attribute. Strong Entity does not
depend on any other entity. It has a primary key, that helps in identifying it
uniquely, strong entity is represented by a rectangle.

• 2. Weak Entity
• An Entity type has a key attribute that uniquely identifies each entity in the entity
set. But some entity type exists for which key attributes can’t be defined. These
are called weak entity and they rely on a related entity (called a "strong entity") to
provide part of their identifying information.

• For Example, A company may store the information of dependents (Parents,

Children, Spouse) of an Employee. But the dependents can’t exist without the
employee. So Dependent will be a Weak Entity Type and Employee will be
Identifying Entity type for Dependent, which means it is Strong Entity Type.
Example of strong and weak entity
 Attributes
• Attributes are the properties that define the
entity type. For example, Roll_No, Name, DOB,
Age, Address, and Mobile_No are the
attributes that define entity type Student. In
ER diagram, the attribute is represented by an
oval.
 Key Attribute
• The attribute which uniquely identifies each
entity in the entity set is called the key
attribute. For example, Roll_No will be unique
for each student. In ER diagram, the key
attribute is represented by an oval with
underlying lines.
 Composite Attribute
• An attribute composed
of many other attributes
is called a composite
attribute. For example,
the Address attribute of
the student Entity type
consists of Street, City,
State, and Country. In
ER diagram, the
composite attribute is
represented by an oval
comprising of ovals.
 Multivalued Attribute
• An attribute consisting of more than one value
for a given entity. For example, Phone_No (can
be more than one for a given student). In ER
diagram, a multivalued attribute is
represented by a double oval.
 Derived Attribute
• An attribute that can be derived from other
attributes of the entity type is known as a
derived attribute. e.g.; Age (can be derived
from DOB). In ER diagram, the derived
attribute is represented by a dashed oval.
The Complete Entity Type Student with its
Attributes can be represented as:
Relationship Type and Relationship Set
• A Relationship Type represents the association
between entity types. For example, ‘Enrolled
in’ is a relationship type that exists between
entity type Student and Course. In ER diagram,
the relationship type is represented by a
diamond and connecting the entities with
lines.