MAHARASHTRA STATE BOARD

OF TECHNICAL EDUCATION

MICRO PROJECT

ON
“E-R Diagram of Blood Bank”
Submitted by
Derren Tuscano (22)
Aaryan Tuscano (31)
Laveen Dcunha (34)
Ron Correia (36)

Under the Guidance of

Prof. Hemant Bansal
In partial fulfilment of Third Semester of
Diploma in Computer Engineering

Department of Computer Engineering.

St. John Polytechnic, Palghar
A.Y. 2023-2024

1
Subject and code: DMS (22319) Academic Year: 2023-24
Course Name and Code: CO-3I Semester: Third

MICRO PROJECT REPORT ON

E-R Diagram of Blood Bank

Submitted in November 2023 By The Group Of Students

Sr Roll No Full Name of Student Enrollment Seat No

No. Sem-II No (Sem-III)
1. 22 DERREN PIUS TUSCANO 2216020049 148708
2. 31 AARYAN RICHARD TUSCANO 2216020045 148704
3. 34 LAVEEN VIJAY DCUNHA 2216020042 148701
4. 36 RON WILLAM CORREIA 2216020059 148713

Under the guidance of

Prof: Hemant Bansal

MAHARASHTRA STATE BOARD OF

TECHNICAL EDUCATION, MUMBAI

Department of Computer Engineering.

St. John Polytechnic, Palghar

2
 Certificate

This is to certify that Mr./Ms. DERREN PIUS TUSCANO Roll No: 22 of Third Semester
of Computer Engineering Diploma Programme at St. John college of Engineering and
Management has completed the Micro Project satisfactorily in subject Database Mangment
System (22319) in the academic year 2023-2024 as Prescribed in the MSBTE prescribed
curriculum of I Scheme.

Place: Palghar Enrollment No: 2216020049

Date: / / 2023 Exam. Seat No:

Project Guide Head of the Department Principal

3
 Certificate
This is to certify that Mr./Ms. AARYAN RICHARD TUSCANO Roll No: 31 of Third
Semester of Computer Engineering Diploma Programme at St. John college of Engineering
and Management has completed the Micro Project satisfactorily in subject Database
Management System (22319) in the academic year 2023-2024 as Prescribed in the MSBTE
prescribed curriculum of I Scheme.

Place: Palghar Enrollment No: 2216020045

Date: / / 2023 Exam. Seat No:

Project Guide Head of the Department Principal

4
 Certificate
This is to certify that Mr./Ms. LAVEEN VIJAY DCUNHA Roll No: 34 of Third Semester
of Computer Engineering Diploma Programme at St. John college of Engineering and
Management has completed the Micro Project satisfactorily in subject Database
Management System (22319) in the academic year 2023-2024 as Prescribed in the MSBTE
prescribed curriculum of I Scheme.

Place: Palghar Enrollment No: 2216020042

Date: / / 2023 Exam. Seat No:

Project Guide Head of the Department Principal

5
 Certificate
This is to certify that Mr./Ms. RON WILLIAM CORREIA Roll No: 36 of Second Semester
of Computer Engineering Diploma Programme at St. John college of Engineering and
Management has completed the Micro Project satisfactorily in subject Database Management
System (22319) in the academic year 2023-2024 as Prescribed in the MSBTE prescribed
curriculum of I Scheme.

Place: Palghar Enrollment No: 2216020059

Date: / / 2023 Exam. Seat No:

Project Guide Head of the Department Principal

6
 INDEX
Sr Topic Page
No. No.

1 Abstract 8

2 Introduction 9

3 Survey On Two 10
Software
4 E-R Diagram 11

5 Table With 15
Commands
6 Triggers 19

7 Conclusion 20

8 Reference 21

9 Weekly Report 22

7
 Abstract:
The Entity-Relationship (ER) diagram for the Blood Bank
Management System offers a concise visualization of the
essential components within the system. It encapsulates key
entities such as donors, recipients, blood units, hospitals/clinics,
and blood types, each associated with their respective attributes,
providing a comprehensive overview of the system's data
structure. The diagram also highlights vital relationships,
including those between donors and donated blood units,
recipients and transfused units, and the healthcare facilities
where blood units are stored. This ER diagram lays the
groundwork for an efficient and organized blood bank system,
facilitating data integrity, ease of data retrieval, and a deep
understanding of the data model's architecture. It is a valuable
resource for healthcare database architects and software
developers, aiding in the creation of a robust management
system that enhances blood inventory management and
ultimately improves patient care.

In summary, the ER diagram for the Blood Bank Management

System serves as a foundational tool, simplifying the intricacies
of data management within a blood bank. It streamlines the
interaction between donors, recipients, blood units, hospitals,
and blood types while ensuring data accuracy and consistency,
all of which are vital in the healthcare domain.

8
Introduction:
The Blood Bank Management System is a critical component of
modern healthcare infrastructure, playing a pivotal role in the
collection, storage, and distribution of life-saving blood and
blood products. The management of blood resources is a
complex and vital task, and an effective system is imperative to
ensure the availability of safe and compatible blood for medical
procedures, emergencies, and patient care. The Entity-
Relationship (ER) diagram presented here serves as a
foundational blueprint for the design and development of such a
system. It encapsulates the fundamental entities, attributes, and
relationships necessary to orchestrate the seamless flow of blood
from donors to recipients while maintaining data accuracy and
integrity. This ER diagram provides a visual representation of
the system's architecture, laying the groundwork for the creation
of a robust Blood Bank Management System that enhances
patient care, ensures efficient inventory management, and
contributes to the success of healthcare institutions.

9
 DATABASE MANAGEMENT SYSTEM
1 Survey of two different software MySQL and Oracle:-
• Use and Comparison of Database Software:
Choosing a database management system (DBMS) for any application is
an important decision for developers because their applications need to
run efficiently. This decision should be based on the information that
compares different database management systems based on various
performance factors. Different applications have unique characteristics in
their functionalities.
The survey's main objective is to compare the functions of two widely
used database management systems. One of them is SQL and the other
is Oracle. Both software has been implemented some unique features
under various conditions for choosing and performing the software for
the project to the database administrator.

• Using MySQL for Microproject of University:

The main difference between MySQL and Oracle is:
In MySql, we can perform basic components of SQL which are:-
1. DDL ( Data Definition Language )
2. DML ( Data Manipulation Language )
3. DCL ( Data Control Language )
4. DQL ( Data Query Language )
5. TCL ( Transaction Control Language )
All these 5 components of SQL can be used in MySql Software for
the basic queries to make the tables in the project University
Management System.

10
E-R Diagram:

11
Explanation Of E-R Diagram :
In an ER (Entity-Relationship) diagram for a blood bank, typically
represent entities, attributes, and relationships to visualize how data is
structured and connected. While I can't view your specific diagram, I
can provide a general explanation of the common components in such a
diagram:

Entities:
1. User:
- This entity represents individuals who have access to the blood bank
management system. Attributes like UserID, Username, Password, and
Email store information about each user.

2. Login:
- The Login entity is used to track the login sessions of users. It
includes attributes such as LoginID, UserID (foreign key referencing
User), LoginTime, LogoutTime, and IPAddress. This helps in auditing
and monitoring user activities.

3. Roles:
- Roles define the set of permissions a user can have. Attributes like
RoleID, RoleName, and Description characterize each role. This entity
facilitates managing and assigning different levels of access within the
system.

4. Permission:
- Permissions define specific actions or operations that users can
perform. Attributes like PermissionID, PermissionName, and
Description describe each permission. These are linked to roles to
control access at a granular level.

12
5. Patient:
- The Patient entity represents individuals who require blood.
Attributes like PatientID, FirstName, LastName, Gender, DateOfBirth,
and ContactNumber store details about each patient. This information is
crucial for tracking and managing blood requirements.

6. Blood:
- This entity represents different types of blood. Attributes like
BloodID, BloodType, RhFactor, and ExpiryDate provide information
about each blood type. Tracking the expiration date is essential for
maintaining the quality of the blood supply.

7. Stock:
- The Stock entity keeps track of the available stock of blood.
Attributes like StockID, BloodID (foreign key referencing Blood),
Quantity, and LastStockUpdate help monitor the quantity of each blood
type in stock. This is vital for ensuring an adequate blood supply.

8. Donor:
- Donors are individuals who contribute blood. Attributes like
DonorID, FirstName, LastName, Gender, DateOfBirth, ContactNumber,
BloodType, RhFactor, and LastDonationDate store details about each
donor. Tracking the last donation date helps manage donation intervals
and ensures donor health.

13
Attributes
1. User:
- Attributes:UserID (Primary Key), Username, Password, Email, etc.
2. Login:
- Attributes:LoginID (Primary Key), UserID (Foreign Key referencing
User), LoginTime, LogoutTime, IPAddress, etc.
3. Roles:
- Attributes: RoleID (Primary Key), RoleName, Description, etc.
4. Permission:
- Attributes: PermissionID (Primary Key), PermissionName,
Description, etc.
5. Patient:
- Attributes: PatientID (Primary Key), FirstName, LastName, Gender,
DateOfBirth, ContactNumber, etc.
6. Blood:
- Attributes:BloodID (Primary Key), BloodType, RhFactor,
ExpiryDate, etc.
7. Stock:
- Attributes:StockID (Primary Key), BloodID (Foreign Key
referencing Blood), Quantity, LastStockUpdate, etc.
8. Donor:
- Attributes: DonorID (Primary Key), FirstName, LastName, Gender,
DateOfBirth, ContactNumber, BloodType, RhFactor,
LastDonationDate, etc.

14
Table With Commands
Table No 1.User :
CREATE TABLE User (
UserID INT PRIMARY KEY,
Username VARCHAR(255),
Password VARCHAR(255),
Email VARCHAR(255)
);

-- Inserting values into User table

INSERT INTO User (UserID, Username, Password, Email)
VALUES (1, 'user1', 'pass1', 'user1@email.com');

INSERT INTO User (UserID, Username, Password, Email)

VALUES (2, 'user2', 'pass2', 'user2@email.com');

UserID (PK) Username Password Email

1 user1 pass1 user1@email.com

2 user2 pass2 user2@email.com

15
Table No 2 Login :
CREATE TABLE Login (
LoginID INT PRIMARY KEY,
UserID INT,
LoginTime DATETIME,
LogoutTime DATETIME,
IPAddress VARCHAR(15),
FOREIGN KEY (UserID) REFERENCES User(UserID)
);
- Inserting values into Login table
INSERT INTO Login (LoginID, UserID, LoginTime,
LogoutTime, IPAddress)
VALUES (1, 1, '2023-01-01 08:00:00', '2023-01-01 16:00:00',
'192.168.1.1');

INSERT INTO Login (LoginID, UserID, LoginTime,

LogoutTime, IPAddress)
VALUES (2, 2, '2023-01-02 09:30:00', '2023-01-02 17:30:00',
'192.168.1.2');

LoginID UserID LoginTime LogoutTime IPAddres

(PK) (FK)
1 1 2023-01- 2023-01-01 192.168.1.1
01 16:00:00
08:00:00
2 2 2023-01- 2023-01-02 192.168.1.2
02 17:30:00
09:30:00

16
Table No 3 Roles:

Field Description Type Length

RoleID Role ID INT 20

RoleName Role Name VARCHAR 255

Description Description VARCHAR 255

Table No 4 Permission:
Field Description Type Length
PermissionID Permission ID INT 20
PermissionName Permission VARCHAR 255
Name
Description Description VARCHAR 255

Table No 5 Patient:
Field Description Type Length
PatientID Patient ID INT 20
FirstName FirstName VARCHAR 255
LastName LastName VARCHAR 255
Gender Gender VARCHAR 10
DateOfBirth Date Of Birth DATE 6
ContactNumber Contact Number VARCHAR 15

17
Table No 6 Blood:
Field Description Type Length
BloodID Blood ID INT 20
BloodType Blood Type VARCHAR 5
RhFactor Rh Factor VARCHAR 10
ExpiryDate Expiry Date DATE 6

Table No 7 Stock:
Field Description Type Length
StockID Stock ID INT 20
BloodID (FK) Blood ID(FK) INT 20
Quantity Quantity INT 20
LastStockUpdate Last Stock Update DATETIME 6

Table No 8 Donor:
Field Description Type Length
DonorID Donor ID INT 20
FirstName First Name VARCHAR 225
LastName Last Name VARCHAR 225
Gender Gender VARCHAR 10
DateOfBirth Date Of Birth DATE
ContactNumber Contact Number VARCHAR 15
BloodType Blood Type VARCHAR 5
RhFactor Rh Factor VARCHAR 10
LastDonationDate Last Donation Date DATE 6

18
Triggers:

Applying Triggers:
Creating triggers:
CREATE OR REPLACE TRIGGER UpdateLastStockUpdateTrigger
BEFORE INSERT ON Stock
FOR EACH ROW
BEGIN
:NEW.LastStockUpdate := SYSDATE;
END;
/
OUTPUT: -
Trigger Created

Disabling Trigger: -
ALTER TRIGGER UpdateLastStockUpdateTrigger DISABLE;
OUTPUT:-
Trigger Disable

Deleting a Trigger:-
DROP TRIGGER UpdateLastStockUpdateTrigger;
OUTPUT:-
Trigger Drop

19
Conclusion:
In the context of developing a Blood Bank Management System, we
initiated the project by designing a comprehensive Entity-Relationship
(ER) diagram. The identified entities encompassed User, Login, Roles,
Permission, Patient, Blood, Stock, and Donor, each with its associated
attributes defining the essential components of the system.

This conceptual design was then translated into a practical

implementation through normalized SQL tables. We outlined the fields,
descriptions, data types, and lengths for each table, ensuring a structured
and efficient database schema.

The initial data population was demonstrated with sample insert

statements for the User and Login tables, laying the foundation for user
authentication and tracking login activities.

A crucial aspect of the system, the Stock table, was integrated with a
trigger. This trigger, named UpdateLastStockUpdateTrigger,
automatically updates the LastStockUpdate timestamp before each new
stock entry is inserted. This implementation enhances the system's
functionality by maintaining real-time records of stock updates.

To provide a holistic view of the project, we covered the process of

disabling, enabling, and deleting triggers, offering flexibility in
managing the system's behavior.

The overall goal of this project format was to illustrate a systematic

approach to designing a database, implementing tables, populating
initial data, and incorporating triggers for enhanced functionality. The
project structure aims to facilitate a scalable and efficient Blood Bank
Management System.

20
Reference
Introduction To Database Management System – ISRD Group
https://www.freeprojectz.com/entity-relationship/blood-bank-
management-system-er-diagram
https://www.studocu.com/in/document/lovely-professional-
university/dbms/blood-bank-management-system/39380010
https://www.slideshare.net/SohamNanekar/er-diagrams-for-blood-bank-
management-system
https://itsourcecode.com/uml/er-diagram-for-blood-bank-management-
system/

21
Weekly Report
Sr. Date Timing Work or activity Sign
No. Performed of the
From To Duration Guide
in hours
1 10/10/2023 3:30 4:30 One Discussion and
Hour Finalization of the
Project Title
2 14/10/2023 3:30 4 :30 One Preparation and
Hour Submission of
Abstracts
3 15/10/2023 4:30 5:30 One Literature Review
Hour
4 28/10/2023 3:30 4:30 One Collection of Data
Hours
5 29/10/2023 4:30 5:30 One Collection of Data
Hours
6 30/10/2023 4:30 5:30 One Discussion and Outline
hours of Content
7 31/10/2023 3:30 4:30 One Rough Writing of the
Hours Projects Contents
8 01/11/2023 4:30 11:30 One Editing and Proof
Hours Reading of the
Contents
9 2/11/2023 11:00 1:00 Two Final Completion of the
Hours Project
10 3/12/2022 Two Seminar Presentation,
Hours viva-vice Assessment
and Submission Report

Guided By Prof.Hemant Bansal

22