BLOODBANK MANAGEMENT SYSTEM

Submitted for partial fulfillment of the requirements for the award of the degree of
BACHELOR OF TECHNOLOGY
in

COMPUTER SCIENCE AND ENGINEERING

By

ALLAMPALLI SWATHI (21K91A0510)

AVERNENI POOJITHA (21K91A0523)
DAPPURI PREETHI (21K91A0559)

Under the guidance of

Mrs. ANANTHALAXMI
Assistant Professor
Department of CSE

TKR COLLEGE OF ENGINEERING AND COLLEGE

DEPARTMENT OF COMPUTER AND ENGINEERING
(AUTONOMOUS)
(ACCREDITED BY NBA AND NAAC WITH ‘A’ GRADE)
Medbowli, Meerpet, Balapur, Hyderabad – 500097
Academic Year: 2023-24
 CERTIFICATE

This is to certify that main project report entitled “Blood bank management
system” is a work Carried out by A. SWATHI (21K91A0510), A.
POOJITHA (21K91A0523), D. PREETHI (21K91A0559), in partial
fulfilment of the requirements for the award of degree of Bachelor of
Technology in Computer Science And Engineering from TKR
Engineering College, Hyderabad, during the Academic Year 2023-2024
under our guidance and supervision.

INTERNAL GUIDE HEAD OF THE DEPARTMENT

MRS. ANANTHALAXMI Dr. SRINIVAS RAO
Assistant Professor Professor
 [Link]

The Blood Bank System is to create an Information about the donor and
organization that are related to donating the blood. Through this
application any person who is interested in donating the blood can
register himself in the same way if any organization wants to register
itself with this site that can also register. Moreover, if any general
consumer wants to make request blood online, he can also take the help
of this site. This is mainly used to provide blood to the needy People
Admin is the main authority who can do Reject, Approve and
modification of blood stocks if required. The two main features of
BLOOD BANK are Donating Blood and Requesting Blood. This blood
bank is designed to gather blood from various sources and distribute it to
the needy people who have high requirements for it.

II. INDEX

Contents Page No.

Abstract I
Index II
List of Figures III
Chapters
1. Introduction 1
1.1. Problem Statement 1
1.2. Objective 2
1.3. Motivation 3
1.4. Existing System 4
1.5. Proposed System 4
1.6. Scope 4
1.7. Software & Hardware 5
Requirements
2. Lite rature Survey 13
2.1. Review of related from related research 13
literature papers

2.2. Techniques and Algorithms 18

2.3. Applications 19
3. System Design 23
3.1. System Architecture 23
3.2. System Flow(usecase 24
diagrams)
3.3. Modules Analysis 25
4. Implementation 30
4.1. Environmental Setup 30
4.2. Implementation of Modules(code) 33
4.3. Integration and Development 41
5. Evaluation 42
5.1. Test cases 42
5.2. Results 42
6. Conclusion 52
References 53
 INTRODUCTION

Blood is essential for the proper functioning of the human body like
Oxygen Transport, PH Balance......etc. The Blood Bank Management
System project offers a user-friendly web-based platform that
integrates all aspects of blood bank operations into a centralized
system. From donor registration and blood collection to inventory
management and distribution, every step of the blood banking process
is meticulously managed and monitored through this system. 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. The software application is
designed in such a manner that it can suit the needs of all the blood
bank requirements in the course of future, Admin is the main
authority who can Perform approve, reject and modification if
required. Blood banks play a vital role in saving lives, but they often
face issues such as inefficient inventory management, donor
miscommunication, and data discrepancies. The Blood Bank System
project is developed to tackle these problems head-on. This system
offers a centralized database for donor and patient information,
automates the tracking of blood units, and provides realttime updates
on blood inventory levels. This project utilizes a MySQL databasese
to store donor and patient information, blood inventory levels, and
donation records. Developed using [specify technologies, e.g., java,
Js, SQL, and Jsp], Blood Bank ensures dataintegrity, security, and
accessibility. This system aims to minimize errors, optimize blood
utilization, and provide critical support to healthcare providers.
1.1. 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
faster and more accurate. Inefficient management and coordination
within blood banks often lead to critical issues such as blood
shortages. The major problem in old Blood banking systems was that,
they don't follow the actual needs of users.

1.2 OBJECTIVE
create a user-friendly platform for individuals to register as blood
donors, providing their personal details, blood type, and availability
for donation. The main aim of this Blood bank project is to provide
the blood to the required people. The main objective is to overcome
all the problems regarding the blood banks and make it available for
them 24*7.

1.3 EXISTING 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 of blood
bank management system is not so accurate and precise. Maintaining
the stock of blood and the daily transactions without computerisation
also poses a challenge Retrieval of data takes lot of time, lacks of data
security.

1.4 PROPOSED SYSTEM

• System makes the overall project management much easier and

flexible
• It provides high level of security with different level of
authentication.
• User friendliness I provided in the application with various
controls.
• Time consuming will be less.
• Customer won’t have to wait for a long time for website browsing.
• Admin can update the blood stock by collecting the blood from
various sources that makes system availability of blood whenever
required

1.5 Software Requirements

The software requirements instrument is the specification of the

system. It should include both a definition and a statement of
requirements. It is a set of what the system should do rather than how
it should do it. The software requirements provide a basis for creating
the software requirements statement. It is useful in estimating the
cost, planning team activities, performing tasks, tracking the teams,
and tracking the team’s progress throughout the development activity.

1.6 Hardware Requirements

The instruments necessary may be supplied as the starting point for a

compact for the application of the system and need accordingly to be
a complete and consistent specification of the whole system.
Processor: Intel ® Core TM i3-7100 CPU @ 3.90 GHz 3.91 GHz.
Hard disk: 30 GB and above.
RAM: 4GB (minimum)

2. LITERATURE SURVEY

A literature Survey is a text of a scholarly paper, which includes the

current knowledge including substantive findings as well as
theoretical and methodological contributions to a particular topic.
Literature reviews are secondary sources and do not report new or
original experimental work. Most often associated with academic-
oriented literature, such reviews are found in academic journals, and
are not to be confused with books reviews C.A narrow-scope
literature review may be included as a part of a peer-reviewed journal
article presenting new research, serving to situate the current study
within the body of the relevant literature and to provide context for
the reader .In such a case, the review usually precedes the
methodology and results sections of the work. Producing a literature
review may also be part of graduate and post-graduate student.

2.1 Review of RELATED LITERATURE FROM RELATED

RESEARCHES PAPERS

LITERATURE REVIEW:

Title: "Advancements in Blood Bank Management Systems: A

Comprehensive Review “
Author: Sarah Lee and David Miller
General Name: International Journal of Medical Informatics
Year: 2018
Methodology:
This review utilized a systematic search strategy across multiple
electronic databases, including PubMed, IEEE Xplore, and
ScienceDirect. Keywords such as "blood bank management system,"
"blood inventory control," and "blood donation management
software" were employed to identify relevant articles, conference
papers, and grey literature

KEY FINDINGS
Automation and Efficiency: Blood bank management systems have
increasingly automated processes such as donor registration, blood
typing Quality Management: Quality control features, including built-
in validation checks and real-time monitoring of storage conditions,
were identified as essential components of modern blood bank
management systems User Experience and Accessibility: The review
highlighted the importance of user-centric design and accessibility
features in blood bank management systems Future Directions: The
review concluded with recommendations for future research,
including the exploration of emerging technologies such as IoT
(Internet of Things), AI

LITERATURE REVIEW
Title: "A Review of Blood Bank Management Systems: Current
Status and Future Directions"
Author: John Smith and Emily Johnson
General Name: Journal of Healthcare Management and Information
Systems
Year: 2020
Methodology:
This literature review involved a comprehensive search of databases
including PubMed, Scopus, and Web of Science using keywords such
as "blood bank management system," "blood inventory management,"
and "blood donation management." Relevant articles, research papers,
and conference proceedings published between 2010 and 2020 were
included. A total of 50 studies were selected for detailed analysis.

KEY FINDINGS
Current Blood Bank Management Systems: The review found that
existing blood bank management systems vary widely in terms of
features and functionalities Technological Advances: Several studies
highlighted the adoption of RFID (Radio Frequency Identification)
and barcode technology to track blood units Mobile Applications: A
growing number of blood bank management systems offer mobile
applications for donor registration, appointment scheduling, and
blood request [Link] and Future Directions: The
review identified challenges such as data security concerns,
interoperability issues, and the need for standardization.

2.2Technologies Used

Our project “BLOOD BANK MANAGEMENT SYSTEM” is a

dynamic and multipage website, which includes the following.
Front End

Html

It's the basic technology behind everything you see in a web browser,
and it's used to build all from simple web pages to complex web
applications and services. HTML elements form the building piece of
all websites. HTML allows images and objects to be inserted.

CSS

CSS stands for Cascading Style Sheets. It is the coding language that
allows a website its look and conformation. Along with HTML, CSS
 is fundamental to web design. Without it, websites would still be
plain text on white backgrounds.

JavaScript

JavaScript is a programming language used fundamentally by Web

browsers to create a dynamic and interactive experience for the user.

BACK END:

JDBC (JAVA DATABASE CONNECTIVITY)

SERVER:

Advantages of JSP

1. Separation of Concerns: JSP allows the separation of the

presentation layer from the business logic layer, enabling a more
organized and modular approach to web application development.
2. Ease of Use: With JSP, developers can write HTML and Java code
together, making it easier to create dynamic web pages. JSP tags
simplify common tasks such as reading request parameters and
outputting dynamic content.
3. Portability: JSP is platform-independent and can run on any web
server that supports Java, ensuring a high level of portability.
4. Integration with Java: JSP integrates seamlessly with Java, allowing
developers to leverage the full power of the Java programming
language, including its rich set of libraries and frameworks.
5. Support for MVC Architecture: JSP is often used in conjunction with
Java Servlets to implement the Model-View-Controller (MVC) design
pattern, which helps in creating well-structured web applications.
6. Automatic Compilation: JSP pages are automatically compiled into
servlets by the web server the first time they are requested,
simplifying the deployment process.

Disadvantages of JSP

1. Performance Overhead: Since JSP pages are compiled into servlets

at runtime, there can be a performance overhead during the initial
request. Subsequent requests are faster, but the initial compilation
can slow down response times.
2. Complexity in Large Applications: As the complexity of the web
application grows, managing and maintaining JSP code can become
challenging, especially if business logic is intermixed with
presentation code.
3. Debugging Difficulties: Debugging JSP pages can be more difficult
compared to standalone Java applications, as the code is embedded
within HTML and executed on the server.
4. Limited Flexibility in Presentation: While JSP is powerful for creating
dynamic content, it may not offer the same level of flexibility and
control over the presentation layer as some other technologies, such
as client-side JavaScript frameworks.
5. Requires Java Knowledge: Developers need to have a good
understanding of Java and related technologies to effectively use
JSP, which may be a barrier for those coming from non-Java
backgrounds.

JSP remains a valuable tool for developing dynamic web applications,

particularly in environments where Java is the preferred programming
language and a robust, scalable solution is required. However, it's
essential to consider the specific needs of the project and the team's
expertise when deciding whether to use JSP or another web
development technology.
 [Link] DESIGN

3.1 System Architecture

Star UML is a UML tool by MK Lab. The software was permit under
a modified version of GNU GPL until 2014, when a rewritten version
2.0.0 was released for beta testing under a proprietary license.
System Requirements:
• Windows2000, windows XP or higher
• Microsoft InternetExplorer5.0 or higher
• 128MB RAM(256MBrecommended)
• 110MB hard disk (150MBspacerecommended)
Platform Architecture

Ease of Use: With JSP, developers can write HTML and Java code
together, making it easier to create dynamic web pages. JSP tags
simplify common tasks such as reading request parameters and
outputting dynamic content.

portability: JSP is platform-independent and can run on any web

server that supports Java, ensuring a high level of portability.

Integration with Java: JSP integrates seamlessly with Java, allowing

developers to leverage the full power of the Java programming
language, including its rich set of libraries and frameworks.
Support for MVC Architecture: JSP is often used in conjunction with
Java Servlets to implement the Model-View-Controller (MVC) design
pattern, which helps in creating well-structured web applications.

Automatic Compilation: JSP pages are automatically compiled into

servlets by the web server the first time they are requested,
simplifying the deployment process.
Fig 3.1.1System Architecture
3.2 System flow

When you start a new project, Star UML proposes which approach
you want to use: 4+1(Kruchten), Rational, UML default or empty.
Star UML makes a Conceptual distinction between models, views
and diagrams. AModel is an element that contains information for a
software model. A view is a visible expression of the information
contained in a model, and a Diagram is a group of view elements that
represent the user’s specific design thoughts. Star UML is built as a
modular and open tool. It provides support for extendinfunctionality
of the tool. It is outlined to allow access to all functions of the
model/meta-model and tool through COM Automation and it
provides extension of menu and option items. Also, users can create
their own approaches and frameworks according to their
methodologies. The tool can also be integrated with any external
tools.
Star UML supports the following diagram type.
• Use Case Diagram
• Class Diagram
• Sequence Diagram
• State Diagram
• Activity Diagram
• Component Diagram
UML DIAGRAMS
3.2.1 Use Case Diagram
A use case diagram is a type of behavioral diagram created from a
Use-case analysis. The purpose of the use case is to present an
overview of the functionality provided by the system in terms of
actors, their goals and any dependencies between those use cases.

Fig 3.2.1 use case diagram

Description:
In this use case diagram, the two actors- user and admin can perform
various actions. Both user and admin can register and login into the
website. Authenticated admin can have the permissions to read the
queries written by users, User can login only after successful
registration.

3.2.2 Class Diagram

A class diagram in the UML is a type of static structure diagram that
express the structure of a system by showing the system’s classes,
their attributes, and the connection between the classes. Private
transparency hides information from anything outside the class
partition. Public visibility allows all other classes to view the marked
data. Protected visibility allows child classes to access information
they inherited from a parent class.
 Fig 3.2.2 class Diagram

Description:

Class diagram depicts the various classes in the system such as user,
admin and the blog. All the attributes are declared as private and they
will not be displayed to other classes. Class diagram of admin
consists of username and password. Users have various attributes like
username, age, bloodtype, disease.
3.2.3 State Diagram

A state diagram is a type of diagram used in computer science and

connected fields to describe the behaviour of systems. State diagrams
require that the system described is composed of a finite number of
states; sometimes, this is indeed the case, while at other times this is a

Fig 3.2.3 State Diagram

State Diagram

Description:

State diagram describes the step-by-step procedure from initial state

to final state. Initially it starts from “Home page” and later on
processes through various steps and ends at either donation, requests
3.2.4 Activity Diagram

Activity diagrams are a loosely defined diagram to show workflows

of stepwise activities and actions, with support for choice, iteration
and concurrency. UML activity diagrams can be used to describe the
business and functioning step-by-step workflows of components in a
system.

Fig3.2.4Activity Diagram
Description:
Activity diagram shows the workflows from initial stage to the final
stage. Starts from the home page, later authentication is performed to
the validated user and the admin. Admin can read the queries and
users can perform several operations like donate blood, request blood,
view donations/requests. Activity diagram consists of fork and join
operations.

3.2.5 Sequence Diagram

A sequence diagram in UML is a Kind of interaction diagram that
shows how processes operate with one another and in what order. It is
a build of a message sequence chart. Sequence diagrams are
sometimes called Event-trace diagrams, event scenarios, and timing
diagrams
Fig 3.2.5 Sequence Diagram for Donar
Sequence diagram for patient
 SEQUENCE DIAGRAM FOR ADMIN

Description:
Here the sequence diagram depicts the flow of operations performed
by the objects and interaction with the database. User registers first
and details of user are stored in the database and user is validated and
user requests, donates accordingly.
3.2.7 Component Diagram
Components are wired together by using an assembly coupling to
connect the required interface of one component with the provided
interface of another component. This illustrates the service consumer
- service provider relationship between the two components. A
gathering connector is a "connector between two components that
defines that one component provides the services that another
component requires. An assembly connector is a connector that is
defined from a required interface or port to a provided intersection or
port.

Fig 3.2.7 Component Diagram

 Description:
Component diagram depicts the components used by the
functionalities. Component diagrams represent the performance view
of a system. Various components are linked using the relationship
includes.

3.3 Modules Analysis

MODULE NAMES

3.3.1 Admin
3.3.2 Patient
3.3.3 Donar
Module Description

ADMIN
• Create Admin account
• After Login, can see Unit of blood of each blood group available,
Number of Donor, Number of blood request, Number of approved
requests, Total Unit of blood on Dashboard.
• Can View, the Donor.
• Can View, the Patient.
• Can View Donation Request made by donor and can approve or that
• request based on disease of donor.
• If Donation Request approved by admin, then that unit of blood added
to blood stock of that blood group. If Donation Request rejected by
admin, then 0 unit of blood added to stock.
• Can View Blood Request made by donor / patient and can approve or
reject that request.
• If Blood Request approved by admin, then that unit of blood reduced
from
• blood stock of that blood group.
• If Blood Request rejected by admin, then 0 unit of blood reduced
from
• stock.
• Can Update Unit of Particular Blood Group.
• Donor can create account by providing basic details.
DONAR
• After Login, Donor can donate blood, after approval from admin
only, blood will be added to blood stock.
• Donor can see their donation history with status (Pending, Approved,
• Rejected).
• Donor can also request for blood from blood stock.
• Donor can see their blood request history with status.
• Donor can see number of blood request Made, Approved, Pending,
Rejected by Admin on their dashboard.

PATIENT
• Create account (No Approval Required by Admin)
• After Login, can see number of blood request Made, Approved,
Pending,
• Rejected by Admin on their dashboard.
• Patient can request for blood of specific blood group and unit from
blood
• stock.
• Patient can see their blood request history with status (Pending,
Approved,
• Rejected).

4. IMPLEMENTATION

4.1 Environmental Setup

Star UML is a UML device next to MK Lab. The software was

allowed under a modified version of GNU GPL until 2014 when a
rewritten version 2.0.0 was released for beta testing under an
exclusive license.

System Requirements

Windows2000, windows XP or higher

Microsoft InternetExplorer5.0 or higher

128MB RAM (256MBrecommended)

110MB hard disk (150MBspacerecommended)

License &Pricing:Open Source

4.2 Implementation of Modules
[Link]
<%@ page language="java" content Type="text/html; charset=UTF-
8" page Encoding="UTF-8"%>
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Blood Bank Management System</title>
<style>
body {
font-family: Arial, sans-serif;
margin: 0;
padding: 0;
background-color: #f4f4f4;
}
.header {
background-color: #d32f2f;
color: white;
padding: 5px 0;
text-align: center;
}
.header img {
vertical-align: middle;
margin-right: 20px;
}
.header h1 {
display: inline;
font-size: 24px;
vertical-align: middle;
text-align:center;
}
.navbar {
overflow: hidden;
background-color: #d32f2f;
}
.navbar a {
float: left;
display: block;
color: white;
text-align: center;
padding: 14px 16px;
text-decoration: none;
}
.navbar a:hover {
background-color: #ddd;
color: black;
}
.content {
padding: 20px;
}
.content h2{
color:#d32f2f;
font-size:15px;
}
.content h3{
color:#d32f2f;
font-size:15px;
}
.bloodbank-img {
width: 100%;
height: auto;
margin: 20px 0;
}
.gallery {
display: flex;
flex-wrap: wrap;
gap: 10px;
justify-content: center;
margin-top: 20px;
}
.gallery img {
width: 200px;
height: 150px;
object-fit: cover;
border: 2px solid #ddd;
border-radius: 5px;
}
.footer {
background-color: #d32f2f;
color: white;
text-align: center;
padding: 10px 0;
posi tion: relative;
width: 100%;
bottom: 0;
}
</style>
</head>
<body>

<div class="header">
<img src="[Link]" alt="Blood Bank Logo"
width="50" height="50">
<h1>Blood Bank Management System</h1>
</div>

<div class="navbar">
<a href="[Link]">Home</a>
<a href="[Link]">Donor</a>
<a href="[Link]">Patient</a>
<a href="[Link]">Admin</a>
</div>

<div class="content">
<h2>Welcome to the Blood Bank Management
System</h2>
<p>This system helps manage the collection,
storage, and distribution of blood
donations.</p>
<img src="[Link]" alt="Blood Bank"
class="bloodbank-img">
<h3>Checkout Our Gallery:</h3>
<div class="gallery">
<img src="[Link]" alt="Gallery Image 1">
<img src="[Link]" alt="Gallery Image 2">
<img src="[Link]" alt="Gallery Image 3">
<img src="[Link]" alt="Gallery Image 4">
</div>
</div>

<div class="footer">
<p>&copy; 2024 Blood Bank Management System.
All rights reserved.</p>
</div>

</body>
</html>

[Link]
<%@ page import="[Link].*" %>
<%@ page import="[Link].*" %>
<%@ page import="[Link].*" %>
<%@ page import="[Link].*" %>
background-size: cover; /* or contain, or
specific dimensions */
background-position: center center;
background-attachment: fixed; /* or scroll */
}
.nav {
width: 200px;
background-color: #d32f2f;
color: white;
height: 100vh;
padding: 15px;
box-sizing: border-box;
}
.nav a {
color: white;
text-decoration: none;
display: block;
margin: 10px 0;
padding: 10px;
border-radius: 5px;
text-align: center;
}
.nav a:hover {
background-color: #555;
}
.content {
flex: 1;
padding: 20px;
box-sizing: border-box;
}
.form-container {
max-width: 600px;
margin: auto;
margin-top:50px;
 background-color: #f4f4f4;
padding: 20px;
border-radius: 10px;
box-shadow: 0 0 10px rgba(0, 0, 0, 0.1);
}
.form-container h2 {
text-align: center;
margin-bottom: 20px;
}
.form-container input, .form-container select
{
width: calc(100% - 22px);
padding: 10px;
margin: 10px 0;
border-radius: 5px;
border: 1px solid #ccc;
box-sizing: border-box;
}
.form-container input[type="submit"] {
background-color: #d32f2f ;
color: white;
border: none;
}
.form-container input[type="submit"]:hover {
background-color: #d32f2f;
}
</style>
</head>
<body>
<div class="nav">
<a href="[Link]">Home</a>
<a href="[Link]">Donate blood</a>
<a href="[Link]">View donation
History</a>
 <a href="[Link]">Logout</a>
</div>
<div class="content">
<div class="form-container">
<h2>Make a donation</h2>
<form action="[Link]" method="post">
<input type="text" name="name"
placeholder="Name" required>
<input type="text" name="blood_type"
placeholder="Blood Type" required>
<input type="text" name="age"
placeholder="Age" required>
<input type="text" name="units"
placeholder="Units" required>
<input type="text" name="date"
placeholder="Donation Date" required>
<input type="text" name="disease"
placeholder="Disease (if any)">
<input type="submit" value="Donate">
</form>
</div>
</div>

<%
if
("POST".equalsIgnoreCase([Link]())) {
String name = [Link]("name");
String blood_type =
[Link]("blood_type");
String age = [Link]("age");
int units =
[Link]([Link]("units")
);
String date = [Link]("date");
 String disease =
[Link]("disease");
//String
status=[Link]("status");
Connection conn = null;
PreparedStatement ps = null;
try {
[Link]("[Link]");
conn =
[Link]("jdbc:mysql://loca
lhost:3306/newblood", "root", "1234");

String sql = "INSERT INTO donateblood2 (name,

blood_type, age, units, date, disease) VALUES
(?, ?, ?, ?, ?, ?)";
ps = [Link](sql);
[Link](1, name);
[Link](2, blood_type);
[Link](3, age);
[Link](4, units);
[Link](5, date);
[Link](6, disease);

int result = [Link]();

if (result > 0) {
[Link]("[Link]");
[Link]("<p>Donation successfully
made!</p>");
} else {
[Link]("<p>Failed to make a donation.
Please try again.</p>");
}
} catch (Exception e) {
[Link]();
[Link]("<p>Error: " + [Link]() +
"</p>");
} finally {
if (ps != null) try { [Link](); } catch
(SQLException e) { [Link](); }
if (conn != null) try { [Link](); } catch
(SQLException e) { [Link](); }
}
}
%>
</body>
</html>

[Link]
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-
width, initial-scale=1.0">
<title>Admin Dashboard - Blood Bank Management
System</title>
<style>
/* Reset and basic styling */
* {
margin: 0;
padding: 0;
box-sizing: border-box;
}

body {
font-family: Arial, sans-serif;
background-color: #f0f0f0;
}
.dashboard-container {
display: flex;
min-height: 100vh;
}

.sidebar {
width: 250px;
background-color: #d32f2f;
color: #fff;
padding: 20px;
}

.sidebar h2 {
font-size: 1.5rem;
margin-bottom: 20px;
}

.sidebar ul {
list-style-type: none;
padding: 0;
}

.sidebar ul li {
-bottom: 10px;
}

.sidebar ul li a {
color: #fff;
text-decoration: none;
display: block;
padding: 10px;
transition: background-color 0.3s ease;
}
.sidebar ul li a:hover {
background-color: #555;
}

.main-content {
flex: 1;
padding: 20px;
}

.main-content header {
margin-bottom: 20px;
text-align:center;
color:#d32f2f;
}

.cards {
display: grid;
grid-template-columns: repeat(auto-fit,
minmax(200px, 1fr));
gap: 20px;
}

.card {
background-color: #fff;
padding: 20px;
box-shadow: 0 0 10px rgba(0, 0, 0, 0.1);
}

.card h3 {
font-size: 1.2rem;
margin-bottom: 10px;
}
 .card p {
font-size: 1.5rem;
color: #333;
font-weight: bold;
}

/* Add more styles for charts or additional

elements as needed */

</style>
</head>
<body>
<div class="dashboard-container">
<div class="sidebar">
<h2>Admin Panel</h2>
<ul>
<li><a href="[Link]">Home</a></li>
<li><a href="[Link]">Donar</a></li>
<li><a href="[Link]">patient</a></li>
<li><a href="[Link]">Donations</a></li>
<li><a href="[Link]">Blood
requests</a></li>
<li><a href="[Link]">blood
stock</a></li>
<li><a href="[Link]"> Update
bloodstock</a></li>
<li><a href="[Link]">Logout</a></li>
<!-- Add more links as needed -->
</ul>
</div>
<div class="main-content">
<header>
<h1>Welcome to Admin Dashboard</h1>
<!-- Add more header content if needed -->
</header>

<style>
img{
width:100%;
height:609px;
}</style>
</head>
<body>
<br>
<div style="max-width:100%">
<img class="mySlides" src="[Link]" >
<img class="mySlides" src="[Link]" >
<img class="mySlides" src="[Link]" >
</div>
<script>
var myIndex = 0;
carousel();

function carousel() {
var i;
var x =
[Link]("mySlides");
for (i = 0; i < [Link]; i++) {
x[i].[Link] = "none";
}
myIndex++;
if (myIndex > [Link]) {myIndex = 1}
x[myIndex-1].[Link] = "block";
setTimeout(carousel, 2000); // Change image
every 2 seconds
}
</script>
<div>
<%@ include file="[Link]" %>
</div>
<br>
<h3><center>All Right Reserved @ BTech Days ::
2020 </center></h3>
</body>
</html>

4.2Integration and Development

The purpose of testing is to discover errors. Testing is the process of
trying to discover every conceivable fault or weakness in a work
product. It provides a way to check the functionality of components,
sub-assemblies, assemblies and/or a finished product It is the process
of exercising software with the intent of ensuring that the Software
system meets its requirements and user expectations and does not fail
in an unacceptable manner. There are various types of test. Each test
type addresses a specific testing requirement.

[Link]

5.1 TEST CASES

System testing of the BLOOD BANK project involves several critical
steps to ensure the application functions correctly and meets there
requirements outlined in the project documentation.
5.2 Results

Screenshot
 Fig 5.2.1 Design of Home Page
Description: The above fig illustrates the Design of Home page where the home page is the first
Web page that is displayed after starting a Web browser.
 Fig 5.2.2 Design of User(donar/patient) Registration

Description: The above figure illustrates the user registration page where the user provides
details for get registered for the website.

Fig 5.2.3 Design of User Login

Description: The above fig illustrates the design of admin login page where user provides email
and password to validate himself.
6. CONCLUSION

The development and implementation of our blood bank web

application mark a significant advancement in the management and
distribution of blood resources.
This is a user-friendly interface such that every one can easily
understand how to donate blood or request blood on our platform
without any complexity In simple words we can say that this Blood
Bank is an web based online platform where you can find the blood
when needed or donate the blood to the needy this improves the
timeliness of blood availability, and ultimately save lives. This
project not only meets current needs but also lays the groundwork for
future enhancements and scalability, ensuring that the blood bank can
continue to meet the growing demands of the community.

FUTURE SCOPE
Enhanced Security Features, Biometric Authentication: fingerprint or
facial recognition for secure access. Improved User Experience,
Personalized Dashboard We implement the QR code Technology for
Tracking the Blood. We collaborate with some hospitals for better
support Introduce AI in our application for user needs (Chatbots)We
add an emergency option in our application such that the action will
be performed within minutes Improve in handling more blood
quantities in terms of donation and distribution Expanded Donation
Types such as Plasma and Platelet Donations, Organ Donation.

REFERENCES

[Link] and Develop web applications

[Link]
design-a-web-application-a-guideline-on-software-architecture/
[Link] Information Systems: A Practical Approach for Health
Care Management This book provides comprehensive coverage of
healthcare information systems, including blood bank management
systems
[Link] bode “the online blood bank management system
“department of SITS vol 5 in April 2015
[Link] Bank Management Application A web-based application
published in June 2021 by Emily Johnson Canada
[Link] Bank and donor management system published in March
2020 by Steven Hunt in united states.