GOVERNMENT POLYTECHNIC MALVAN

MICROPROJECT
ACADEMIC YEAR:- 2022-2023

TITLE OF THE PROJECT:-DESIGN E-R

DIAGRAM OF BLOOD BANK SYSTEM
PROGRAM CODE:-CO3I
COURSE:-DATABASE MANAGEMENT
SYSTEM
COURSE CODE:-22319
 CERTIFICATE

MAHARASHTRA STATE BOARD OF

TECHNICAL EDUACTION
This is to certify that the following students of
semester Third of diploma in Computer Engineering
of institute, Government Polytechnic Malvan
(Inst.Code-0117) have completed the microproject
satisfactorily in course, Database Management
System (22319) for the academic year 2022-2023 as
prescribed in the curriculum

Place:-Malvan
Date:-

SUBJECT TEACHER HOD PRINCIPAL

 GROUP DETAILS

Sr.No Roll Enrollment Name Of Sign

No No Group
Members
1 2226 2101170159 Ayush Anant
Kanekar
2 2232 2101170166 Prathamesh
Bhushan
Gawas
3 2234 2101170168 Varad
Makarand
Paradkar

Name Of Guide
Roshani Varak Madam
(Lecturer In Database Management System)
(Department Of Computer Engineering)
 INTRODUCTION
An entity relationship diagram (ERD) shows the relationships
of entity sets stored in a database. An entity in this context is
an object, a component of data. An entity set is a collection of
similar entities.
These entities can have attributes that define its properties,
by defining the entities, their attributes, and showing the
relationships between them, an ER diagram illustrates the
logical structure of databases. ER diagrams are used to sketch
out the design of a database.
Peter Chen developed ERDs in 1976. Since then Charles
Bachman and James Martin have added some slight
refinements to the basic ERD principles.
 Entity:-
Entities are represented by means of rectangles. Rectangles
are named with the entity set they represent.

It is set (or collection) of entities of the same type which

share the similar properties, or attributes.

An entity can be characterised into two types:

1. Strong entity
2. Weak entity

 Attributes:-
Attributes are the properties of entities. Attributes are
represented by means of ellipses. Every ellipse represents one
attribute and is directly connected to its entity (rectangle).
An attribute in an Entity Relationship Model describes the
properties or characteristic of an entity.
An attributes can be characterized into the following types :
1. Simple Attribute
2. Key Attribute
3. Composite Attribute
4. Derived Attribute
5. Multi – valued Attribute

 Relationships:-
Relationships are represented by diamond-shaped box. Name
of the relationship is written inside the diamond-box. All the
entities (rectangles) participating in a relationship, are
connected to it by a line. It is used to describe the relation
between two or more entities.
Degree of relationship :
A relationship where a number of different entity set
participate is called as degree of relationship.
Degree of relationship can be categorized into the following
types : -
1. Unary Relationship
2. Binary Relationship
3. Ternary Relationship
4. n - ary Relationship
ER DIAGRAM OF BLOOD BANK
SYSTEM
 RATIONALE ABOUT E-R DAIGRAM OF BLOOD
BANKING SYSTEM
Hospitals are a very integral part of the infrastructure of
society. So, they need to have good management and
management system.
To ensure the established of a good system, you must plan and
decide everything beforehand. Even after a system has been
established, there is a need for a proper database that keeps
track of everything that goes on in the hospital. So, to develop
a proper hospital management database, we can use Entity –
Relationship diagram.
This ER (Entity Relationship) Diagram represents the model
of Hospital Management System Entity. The entity –
relationship diagram of Hospital Management System shows
all the visual instrument of database tables and the relations
between User, Login, Medicine, Doctor, Patient, User. etc.
It used structure data and to define the relationships between
structured data group of Blood Banking System
functionalities. The main entities of the Hospital Management
System are User, Login, Medicine, Doctor, Patient, User.
 APPLICATIONS OF E-R DIAGRAM
 Database design: ER diagrams are used to model and
design relational databases, in terms of logic and business
rules (in a logical data model) and in terms of the specific
technology to be implemented (in a physical data model.) It’s
also later used to model a particular database or databases. A
relational database has an equivalent relational table and can
potentially be expressed that way as needed.
 Database troubleshooting: ER diagrams are used to
analyze existing databases to find and resolve problems in
logic or deployment. Drawing the diagram should reveal
where it’s going wrong.
 Business information systems: Thess diagrams are used to
design or analyze relational databases used in business
processes. Any business process that uses fielded data
involving entities, actions and interplay can potentially benefit
from a relational database. It can streamline processes,
uncover information more easily and improve results.
 Business process re-engineering (BPR): ER diagrams help
in analyzing databases used in business process re-
engineering and in modeling a new database setup.
 Education: Databases are today’s method of storing
relational information for educational purposes and later
retrieval, so ER Diagrams can be valuable in planning those
data structures.
 Research: Since so much research focuses on structured
data, ER diagrams can play a key role in setting up useful
databases to analyze the data.
 CONCLUSION
With the help of Entity-Relationship diagram we can create
the required database and perform queries. ER modelling
helps you to analyze data requirements systematically to
produce a well - designed database. It’s considered best
practice to complete ER modelling before implementing your
database.
We can represent a database that conforms to an E-R
database schema by a collection of tables. For each entity set
and for each relationship set in database, there is a unique
table to which we can assign the name of the corresponding
entity set and relationship set.
Each table has multiple columns, each of which has a unique
name. Both the E-R model and the relationaldatabase model
are abstract, logical representations of realworld enterprises.
Because the two models employ similar design principles, we
can convert an E-R design into a relational design.
Converting a database representation from an E-R diagram to
a table format is the way we arrive at a relationaldatabase
design from an E-R diagram. Informally, a relation can be
considered to be a table of values.
 REFERENCE
 https://www.javatpoint.com/E-R Diagram-tutorial
 https://www.geeksforgeeks.org/introduction-to-database-
management-system/
 https://www.tutorialspoint.com/dbms/attributes.html
 https://www.edx.org/course/Oracle2