A Project/Dissertation Report

on
BLOOD BANK MAANGEMENT SYSTEM

Submitted in partial fulfillment of the

requirement for the award of the degree
of

SCHOOLOF COMPUTING SCIENCE AND

ENGINEERING

Under The Supervision of

Dr. Sudeept Singh
Yadav
Professor

Submitted By

Bhavya Gupta (19021011373)

Vijay Laxmi Vashisht (19021011290)

SCHOOL OF COMPUTING SCIENCE AND ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
GALGOTIAS UNIVERSITY, GREATER NOIDA
INDIA
MARCH,
2023
 SCHOOL OF COMPUTING SCIENCE AND
ENGINEERING
GALGOTIAS UNIVERSITY, GREATER NOIDA

CANDIDATE’S DECLARATION

We hereby certify that the work which is being presented in the

thesis/project/dissertation, entitled “BLOOD BANK MANAGEMENT SYSTEM”

in partial fulfillment of the requirements for the award of the Bachelor of

Technology submitted in the School of Computing Science and Engineering of

Galgotias University, Greater Noida, is an original work carried out during the period

of October, 2022, under the supervision of Dr. Sudeept Singh Yadav, Assitant

Professor, Department of Computer Science and Engineering/Computer Application

and Information and Science, of School of Computing Science and Engineering,

Galgotias University, Greater Noida.

This is to certify that the above statement made by the candidates is correct to the

best of my knowledge.

Dr. Sudeept Singh Yadav

Professor
 CERTIFICATE

The Final Thesis/Project/ Dissertation Viva-Voce examination of Bhavya Gupta 19SCSE1010180

and Vijay Laxmi Vashisht 19SCSE1010086 has been held on 12/04/2022 and their work is

recommended for the award of Bachelor of Technology.

Signature of Examiner(s) Signature of Supervisor(s)

Signature of Project Coordinator Signature of Dean

Date: April, 2023

Place: Greater Noida

 Abstract

Blood Bank Management System (BBMS) is a browser based system that is designed to store,
process, retrieve and analyze information concerned with the administrative and inventory
management within a blood bank. This project aims at maintaining all the information pertaining
to blood donors, different blood groups available in each blood bank and help them manage in a
better way. Aim is to provide transparency in this field, make the process of obtaining blood from
a blood bank hassle free and corruption free and make the system of blood bank management
effective. Our client is not interested in blood stocking instead we are stocking blood donors
information. The donors who are interested in donating blood has to register in the database.
There is no storage of blood so no complications in the project. The software is fully integrated
with CRM (customer relationship management) as well as CMS (content management system)
solution. It is developed in a manner that is easily manageable, time saving and relieving one from
manual works. The requirement of the blood has to be requested and we supply the information of
the donor. The donors can update their status whether they are available or not..
 List of Tables
Page
Table Table Name
No. Number

2.1 Literature Survey 16

 List of Figures
Figure Page
Table Name
No. Number

5.1 Aiml Script 25

5.2 Creating Interference 26

6.1 Execution of Final 27

6.2 Final Screenshot 27

 Acronyms
B.Tech. Bachelor of Technology
M.Tech. Master of Technology
BCA Bachelor of Computer Applications
MCA Master of Computer Applications
B.Sc. (CS) Bachelor of Science in Computer Science
M.Sc. (CS) Master of Science in Computer Science
SCSE School of Computing Science and Engineering
 TABLE OF CONTENTS

CONTENTS PAGE NO:-

ABSTRACT 2

LIST OF TABLES 3

LIST OF FIGURES 4

LIST OF SYMBOLS, ABBREVIATIONS 7

CHAPTERS 8–37

REFERENCES 39
LIST OF SYMBOLS, ABBREVIATIONS AND NOMENCLATURE

ACH AUTOMATED CLEARING HOUSE

ISP INTERNET SERVICE PROVIDER

OCC OPEN CASH CREDIT

ATM AUTOMATIC TELLER MACHINE

JDBC JAVA DATABASE CONNECTIVITY

JSP JAVA SERVER PAGE

IDE INTEGRATED DEVELOPMENT ENVIRONMENT

DFD DATA FLOW DIAGRAM

UML UNIFIED MODELING LANGUAGE

SQL STRUCTURE QUERY LANGUAGE

DML DATA MANIPULATION LANGUAGE

GUI GRAPHIC USER INTERFACE

DBS DATABASE SYSTEMS

J2EE JAVA 2 PLATFORM ENTERPRISE EDITION

J2SDKD JAVA 2 SDKD

JVM JAVA VIRTUAL MACHINE

CGI COMMON GATEWAY INTERFACE
 CHAPTER-1
Introduction

• The project blood bank management system is known to be a pilot project that is designed for
the blood bank to gather blood from various sources and distribute it to the needy people who
have high requirements for it.
• The software is designed to handle the daily transactions of the blood bank and search the
details when required.
• It also helps to register the details of donors, blood collection details as well as blood issued
reports.
• The software application is designed in such a manner that it can suit the needs of all theblood
bank requirements in the course of future.

I. WHAT IS BLOOD BANK ?

Blood banking is the process that takes place in the lab to make sure that donated blood, or blood
products, are safe before they are used in blood transfusions and other medical procedures. Blood
banking includes typing the blood for transfusion and testing for infectious diseases.

A blood bank is a center where blood gathered as a result of blood donation is stored and preserved
for later use in blood transfusion. The term "blood bank" typically refers to a department of a hospital
usually within a Clinical Pathology laboratory where the storage of blood product occurs and where
pre-transfusion and Blood compatibility testing is performed. However, it sometimes refers to a
collection center, and some hospitals also perform collection. Blood banking includes tasks related to
blood collection, processing, testing, separation, and storage.
II. EXISTING SYSTEM

• The operation of the blood bank still now is maintained in the manual system.
• The operation is tedious, time consuming and space consuming
• It creates room for errors as the data is entered manually by the persons.
• It includes the risk of the documents being lost over years and maintenance of the records is
difficult.
• The data recorded during testing or while acquiring the details of different aspects ofblood bank
management system is not so accurate and precise.
• Maintaining the stock of blood and the daily transactions without computerisation also poses a
challenge.

• The project blood bank management system is known to be a pilot project that is designed for
the blood bank to gather blood from various sources and distribute it to the needy people who
have high requirements for it.
• The software is designed to handle the daily transactions of the blood bank and search the
details when required.
• It also helps to register the details of donors, blood collection details as well as blood issued
reports.
III. PROBLEM STATEMENT

• Scarcity of rare blood group.

• Unavailability of blood during emergency.
• Less awareness among people about blood donation and blood transfusion.
• Deaths due to lack of blood during operations.
• The Blood Bank Management System project aims to make all the procedures automated and
therefore with computer system it can be more fast and accurate.
• This project is a high quality software to manage all these cumbersome jobs.

IV. CONCEPT USED

Cloud Computing: Cloud computing is a model for enabling portable and convenient on-demand
network access to a shared pool of configurable computing resources, such as network, server,
storage, application, and services [17]. Cloud computing has various type of model. It can be
Software as a Service (SaaS), Platform as a Service (PaaS) or Infrastructure as Service (IaaS).
Model used on this research is IaaS. Developer of BBIS rent a computer as database storage and
BBIS can make custom requirements such as upgrading or adding storage capacity, Random Access
Memory (RAM) or even processor to increase response speed of the cloud computing. The benefit
of using IaaS is the security of data on cloud computing, and then saving cost because no need to
buy server or perform maintenance system. Cloud computing also accommodating data storage with
large capacity, the system allocating resource can be managed easily and data or information can be
provided easily to access on real time. IaaS also can be hosted for data storage. A virtual data stored
can be found in the BBIS that can be accessed through a virtual machine and various integrated
applications that can be accessed by both providers and users. Overall, it can be illustrated at figure
7. Each hospital, UTD PMI, and personal user connected through internet service to the cloud
server.
 V. PROPOSED METHOD

The conventional time-consuming process of blood services can be eliminated by maintaining the
minimum units of each blood group in the blood bank, consistently. To achieve this, our web page
maintains a database to store the details of donors who are active and quickly respond to the blood
requests and this database is updated consistently. Our website makes use of this database to locate and
find the nearest donors in case of emergency blood requests. The details of the donors are kept private
and their security is ensured. The details are available to the requestor only after it is verified that the
request is valid and legitimate. The entire process can be explained in detail by dividing our web page
into 3 modules, namely, Registration, Request and Administration.

In this chapter we have Define the components that are needed, and Specified how components
“communicate” with other components. We have modularized the project into discrete work packages,
identified critical interfaces that must be well defined. We have designed the block diagram ,they are
typically used for higher level, less detailed descriptions. After that we have designed system
architecture, a system architecture is the conceptual model that defines the structure, behaviour, and
more views of a system. A data flow diagram is a graphical representation that depicts information flow
and the transforms that are applied as data move from input to output. A table is a data structure used to
organize information. A state transition diagram indicates how the system moves from state to state. E-
R diagrams fully specify data objects, properties of the objects and the relationship.
A blood bank management system is a software solution designed to manage blood bank operations
efficiently. Here is a proposed method of developing a blood bank management system:

1. Requirements Gathering: The first step is to gather requirements from the blood bank staff and
management. The requirements should include information about the blood bank's daily operations,
such as donor registration, blood collection, inventory management, and blood transfusion.

2. System Design: After gathering requirements, the next step is to design the blood bank management
system. The system should have different modules to manage various aspects of the blood bank's
operations, including donor registration, blood collection, blood testing, inventory management,
blood transfusion, and reporting.

3. System Development: The third step is to develop the blood bank management system based on the
design. The system should be user-friendly and should include all the necessary features required to
manage the blood bank's operations efficiently.

4. Testing and Quality Assurance: Once the system is developed, it should be thoroughly tested to
ensure that it is functioning correctly. Testing should include functional testing, performance testing,
and security testing.

5. Deployment and Training: After testing, the system should be deployed to the blood bank's servers.
The blood bank staff should also be trained on how to use the system.

6. Maintenance and Support: Finally, the system should be maintained and supported to ensure that it
continues to function correctly. Maintenance should include regular updates and bug fixes, and
support should be provided to help the blood bank staff if they encounter any issues while using the
system.

Overall, a blood bank management system can help streamline the blood bank's operations, improve
inventory management, and ensure the safety of blood transfusion procedures.
VI . METHODOLOGY

The methodology for developing a blood bank management system should include the following steps:
Needs assessment:

1. Identify the requirements of the blood bank system by conducting a thorough needs assessment. This
should include analyzing the current blood donation and storage processes, as well as identifying any
gaps or areas for improvement.

2. System design: Develop a detailed design plan for the blood bank management system. This should
include defining the system architecture, data models, user interface, and other technical
specifications.

3. Software development: Use the design plan to develop the software system. This will involve
coding, testing, and debugging the software to ensure it is functional and reliable.

4. System implementation: Install the software system in the blood bank and configure it according to
the needs assessment and design plan.

5. User training: Provide training to blood bank staff on how to use the new system, including any new
processes or procedures.

6. System maintenance: Monitor the system performance and provide ongoing maintenance and
support as needed.

7. Evaluation: Conduct periodic evaluations of the system to identify any issues or areas for
improvement, and make necessary changes to improve the system.
The methodology used in the development of a blood bank management system typically involves a
combination of traditional software development methodologies and domain-specific requirements. The
following are the common methodologies used:

a. Waterfall Model: The Waterfall model is a sequential software development methodology that
follows a structured approach. The process is divided into a set of phases, and each phase is
completed before the next phase begins. The phases include requirements gathering, system design,
implementation, testing, deployment, and maintenance. This methodology is useful when the project
requirements are well defined and fixed.

b. Agile Methodology: The Agile methodology is an iterative and flexible software development
approach. It involves a collaborative effort between the development team and the stakeholders. The
requirements are not fixed, and the development process is divided into sprints or iterations. Each
sprint involves designing, coding, testing, and reviewing the software. This methodology is useful
when the project requirements are changing frequently.

c. Rapid Application Development (RAD): The Rapid Application Development methodology is a

faster version of the Waterfall model. It involves prototyping, rapid design, development, and
testing. The RAD methodology is useful when there is a need for rapid software development.

d. Object-Oriented Methodology: The Object-Oriented Methodology is a software development

approach that focuses on the objects that make up a software system.

e. Overall, the methodology should follow a structured and systematic approach to ensure that the
blood bank management system meets the needs of the blood bank and its stakeholders. It should
also involve collaboration between the blood bank staff, software developers, and other stakeholders
to ensure that the system is effective and user-friendly.

The methodology used in the development of the blood bank management system is the Waterfall model.
The Waterfall model is a linear approach to software development that follows a sequential, step-by-step
process. The following are the steps involved in the Waterfall model:

1. Requirements gathering: This involves gathering the requirements of the system from the
stakeholders, including the blood bank staff, donors, and hospitals.

2. System design: This involves designing the system architecture, database schema, and user interface.

3. Implementation: This involves coding the system according to the design.

 4. Testing: This involves testing the system for bugs and errors.

5. Deployment: This involves deploying the system to the blood bank server.

6. Maintenance: This involves maintaining the system and providing support to users.

Functional Requirements:

a. Blood donor registration: The system should allow blood donors to register by filling a registration
form that includes personal details and medical history.

b. Blood inventory management: The system should keep track of blood inventory, including blood
type, expiry date, and quantity.

c. Blood request management: The system should allow hospitals to request for blood based on their
requirements.

d. Donor eligibility checking: The system should check the eligibility of donors based on their medical
history and other factors such as age and weight.

e. Blood donation scheduling: The system should allow donors to schedule blood donation
appointments.

f. Blood transfusion management: The system should keep track of blood transfusion activities,
including donor details, recipient details, and blood type.
Non-functional Requirements:

Usability: The system should be user-friendly and easy to navigate.

Performance: The system should be able to handle a large number of users and transactions.

Security: The system should be secure and protect user data.

Reliability: The system should be reliable and available 24/7.

 VI. ER DIAGRAM

The entity/relationship diagram enables a software engineer to fully specify the data objects that are
input and output from a system, the attributes that define the properties of these objects, and their
relationships. Like most elements of the analysis model, the ERD is constructed in an iterative manner.
Relationship Diagram Notations
1) Entity An entity is an object or concept about which you want to store information.
2) Weak Entity A weak entity is an entity that must defined by a foreign key relationship withanother
entity as it cannot be uniquely identified by its own attributes alone
3) Key attribute A key attribute is the unique, distinguishing characteristic of the entity. For example, an
employee's social security number might be the employee's key attribute.
3) Multi valued attribute A multi valued attribute can have more than one value. For example, an
employee entity can have multiple skill values
6) Relationships Relationships illustrate how two entities share information in the database structure.
 VII. SCOPE AND FUTURE APPLICATION

BLOOD BANK MANAGEMENT is a software application to build such a way that it should suits for
all type of blood banks in future. One important future scope is availability of location-based blood
bank details and extraction of location-based donor’s detail, which is very helpful to the acceptant
people. All the time the network facilities cannot be use. This time donor request does not reach in
proper time, this can be avoided through adding some message sending procedure this will help to find
proper blood donor in time. This will provide availability of blood in time. The system is designed to
be used by blood banks of all sizes, ranging from small-scale community blood banks to large-scale
regional blood banks. The system can be used by blood bank staff, donors, and hospitals. The system
should be able to handle a large number of donors and recipients, keep track of blood inventory, and
generate reports.

VIII. CONCLUSION

Advancement in technology is the prime reason that most of the facilities are available easily and quickly in generally
all the sectors of life. Similarly, our proposed system is a major advancement in the management of blood which is
intended to increase efficiency in the collecting and procuring blood. Automating the process of blood management
provides a better and quick response in emergency cases. A proper management system that solves the existing issues
is the concerned sector will help restoring the value of life that is currently deteriorating because of blood non-
availability. The website provides a very organized medium of communication between the blood blanks and
hospitals. In conclusion online blood management system is a simplified solution to the problems in the current blood
flow process that tries to remove the hurdles in the path of having top notch as well as smooth transfer of blood. The
blood bank management system is an important software system that can help in the efficient management
of blood bank activities. The system should be user-friendly, secure, and reliable. The system should also be
able to handle a large number of donors, recipients, and transactions. The use of the Waterfall model ensures
that the system is developed in a systematic and structured manner.
 IX .REFERENCES

[1] G. Muddu Krishna; S. Nagaraju(2016),“Design and implementation of short message service (SMS) based
blood bank”, 2016 International Conference on Inventive Computation Technologies (ICICT)

[2] Muhammad Arif; S. Sreevas; K. Nafseer; R. Rahul (2012) “Automated online Blood bank database”, 2012
Annual IEEE India Conference (INDICON)

[3] “Benefits of Management Information System in Blood Bank” by 1, Vikas Kulshreshtha, 2, Dr. Sharad
Maheshwari 1, Research Scholar, 2, Associate Professor 2 1, Singhania University, Jhunjhunu, Rajasthan, India 2,
Government Engineering College Jhalawar, Rajasthan, India

[4] The Optimization of Blood Donor Information and Management System by Technopedia P. Priya1, V.
Saranya2, S. Shabana3, Kavitha Subramani4 Department of Computer Science and Engineering, Panimalar
Engineering College, Chennai, India 1, 2, 3, 4

[5] Anish Hamlin M R, Albert Mayan J (2016), “Blood Donation And Life Saver-Blood Donation App”, 2016
International Conference on Control, Instrumentation, Communication and Computational Technologies
(ICCICCT)

[6] “Android Blood Bank” by Prof. Snigdha1, Varsha Anabhavane2, Pratiksha lokhande3, Siddhi Kasar4, Pranita
More5 Lecturer, Information Technology, Atharva College of Engineering, Mumbai, India 1 Student, Information
Technology, Atharva College of Engineering, Mumbai, India 2,3,4,5

[7] “A Study on Blood Bank Management System” by A. Clemen Teena, K. Sankar and S. Kannan, Department of
MCA, Bharath University, Selaiyur, Chennai-73, Tamil Nadu, India