School of Computer Science and Engineering

Academic Year:
Course Code: DBMS Lab Mini Project Report
Semester & Batch:
Project Details:

Mini Project
Title:
Place of Project: REVA UNIVERSITY, BENGALURU

Student Details:

Name: Sign:

Mobile No:

Email-ID:

SRN:

Guide and Lab Faculty Members Details

Guide
Name: Sign:
(The Date:
Faculty
Member
Assigned)
Grade by Guide:
Name of Lab Sign:
Co- Faculty 1 Date:
Name of Lab Sign:
Co- Date:
Faculty 2
Grade by Lab
Faculty
Members
(combined)
SEE Examiners
Name of Sign:
Examiner 1: Date:
Name of Sign:
Examiner Date:
2:
 Abstract

TABLE OF CONTENTS

Chapter No. Chapter Name Page No.

1 INTRODUCTION 01
1.1 Overview 01
1.2 Problem Statement 02
1.3 Objectives 02
1.4 Limitations 02
1.5 Literature Review 03
2 ANALYSIS 05
2.1 Proposed System 05
2.2 Requirements Specification 05
2.2.1 Hardware Requirements 05
2.2.2 Software Requirements 05
2.3 Development Environment 06
2.3.1 HTML 06
2.3.2 Java 06
2.3.3 JSP 07
3 DESIGN 08
3.1 ER Diagram 08
3.2 Schema Diagram 11
4 IMPLEMENTATION 14
4.1 Tables 14
4.2 Triggers 18
5 SNAPSHOTS 19
6 CONCLUSION & FUTURE 31
ENHANCEMENTS
6.1 Conclusion 31

6.2 Future Enhancements 31

BIBLIOGRAPHY 32
 LIST OF FIGURES

Figure No. Figure Name Page No.

3.1 ER Diagram 9
3.2 Schema Diagram 12
5.1 Home Page 19
5.2 Blood Request Page 19
5.3 Blood Bank Page 20
5.4 Blood Camp Page 20
5.5 About Page 21
5.6 Home Page 21
5.7 Receptionist Login Page 22
5.8 Receptionist Signup Page 22
5.9 Admin Home Page 23
5.10 Donor Registration Page 23
5.11 Donor Edit Page 24
5.12 Admin Login Page 24
5.13 Admin Signup Page 25
5.14 Admin Home Page 25
5.15 Add Stock Page 26
5.16 Manage Stock Page 26
5.17 Blood Details Page 27
5.18 Edit Delete Page 27
5.19 Blood Bank Register Page 28
5.20 Requested Blood Page 28
5.21 Request Blood Complete Page 29
5.22 Add Camps Page 29
5.23 Search Event/Camp Page 30
 LIST OF TABLES

Table No. Table Name Page No.

4.1.1 Blood Bank Table 14

4.1.2 Blood Bank Manager Table 14

4.1.3 Receptionist Table 15

4.1.4 Blood Table 15

4.1.5 Donor Table 16

4.1.6 Blood Requested Table 17

4.1.7 Blood Camp Table 17

4.1.8 Stock Table 18

BLOOD BANK MANAGEMENT SYSTEM

CHAPTER 1

INTRODUCTION

1.1 Overview

Blood is a necessary element in the human body. Without blood, the human body is
incomplete. Blood is about 7% to 8% of human weight, according to scientists. Blood is denoted
in the conventional wat by blood donation services or blood bank. Blood bank is defined as an
area where blood is obtained as a result of donor blood donation operation that is processed and
preserved for subsequent transfusion (maximum twenty-eight days). Many Bangladesh blood
banks don’t help the online database of blood donors. A huge amount of blood units are denoted
on average every year in countries like Bangladesh. Approximately five lakh units of blood were
registered as donated in Bangladesh, the value of which increased to seven lakhs in the following
five years, according to statistical study in 2011. Because of this enormous amount of donor data
there must be an efficient and successful way of managing data that could make the online blood
donation site a pavestone.
It is a clear sign that blood donors raise with population growth. In addition to blood
handling, there is a that a data is obsolete and the process of data retrieval is also hindered by
conventional manual operator’s data entry techniques. The project is carried out on an automated
blood bank to solve any issue. Factors such as gender, age, last blood donation date and their
modern traditional methods, Blood donation frequency per year is not registered, which is avital
importance in this project and used as recruiting criteria for blood donation.
The main aim of this project will therefore be to find more effective ways of managing the
database pf blood banks and blood donors and establish a forum for people connected to potential
blood donors in the region.

Page 1
BLOOD BANK MANAGEMENT SYSTEM

1.2 Problem Statement:

In present system all work is done on papers manually. The member’s details are stored in a
register. The validity has to be calculated manually. There is no means to effectively keep
track of subscription validity of the members.

Disadvantages of present working system:

-The data storage is relatively difficult in papers, files and registers. The retrieval of any data
like member’s plan is time consuming.

-Possibility of loss of data or any other circumstances.

-Updating of new data like attendance, subscription renewals of current month time to time is
not possible.

- More number of workers are needed only to maintain registers and files.

1.3 Objectives of the Project

 To ease the process of blood donation and reception.
 To improve the existing system.
 To develop a scalable system.
 To be highly available.

The project is to make an application for the users where they can view different persons in
different countries. In order to build such an application complete web support needs to be
provided. A complete and efficient web page which can provide the information is the basic
aim of the project.

1.4 Limitations

 It is time consuming.
 It leads to an error prone results.
 It consumes lot of man power to better results.

Page 2
BLOOD BANK MANAGEMENT SYSTEM

 It lacks of data security.

 Retrieval of data takes a lot of time.
 Percentage of accuracy is less.
 Reports take time to produce.

1.5 Literature Survey

Applying optimization methods to healthcare management and logistics is a developing

research area with numerous study. Specifically, facility location, staff rostering, patient
allocation, and medical supply transportation are main themes analysed. Optimization approaches
have been developed for several healthcare related problems, ranging from the resource
management in hospitals to delivery of care services in the territory. However, optimization
approaches can also improve other services in the health system that have been only marginally
addressed, yet. One of them is the blood donation system (BD), aiming at providing an adequate
supply of blood to Transfusion Centres (TCs) and hospitals.

Blood is necessary for several treatments and surgeries, and still a limited resource. The need
for blood is about ten million units per year in the USA, 2.1 in Italy and 2 in Turkey; moreover,
people still die in some countries because of inadequate supply of blood products (World Health
Organization’s 2014). Hence, BD plays a fundamental role in healthcare systems, aiming at
guaranteeing an adequate blood availability to meet the demand and save lives. In western
countries blood is usually collected from donors, i.e., unpaid individuals who give blood
voluntarily. Blood is classified into groups and based on the Rhesus factor (Rh+ or Rh-), and each
donor should be correctly matched within the patient who receives his/her blood. Moreover, as it
may transmit diseases, blood must be screened before utilization.

Generally, there are two types of donation: whole-blood donation, in which the whole blood is
directly collected in a plastic bag, and apheresis, i.e., the donation of the specific components in
which a mechanical gathering unit decays required blood parts.

Page 3
BLOOD BANK MANAGEMENT SYSTEM

Blood requires the particular precautions for collection and storage, and its shelf life from
donation and utilization is limited, thus requiring a continuous feeding of the system. Hence, the
successful Blood Donation supply chain should meet the daily demand of blood and follow its
temporal pattern. According to Sundaram and Santhanam (2011), BD supply chain and related
management problems can be classified based on the main phases of a blood bag life: donor
registration, blood collection, blood screening/evaluation, inventory storage and delivery. A
slightly different classification is proposed in Pierskalla (2004), according to which management
of BD supply chain concerns both strategic decisions and tactical operation decision.

Page 4
BLOOD BANK MANAGEMENT SYSTEM

CHAPTER 2

ANALYSIS
2.1 Proposed System

The proposed system (Blood Bank Management System) is designed to help the Blood
Bank administrator to meet the demand of Blood by sending and/or serving the request for
blood as and when required, the proposed system gives the procedural approach of how to
bridge the gap between recipient, donor, and blood banks. This application will provide a
common ground for all the three parties (i.e., Recipient, Donor, and Blood Banks) and will
ensure the fulfilment of demand for blood requested by Recipient and/or blood bank.

2.2 Requirement Specification

The System Requirement Specification (SRS), the requirements specification for

software system, is complete description of the functionality of the system to be implemented
and may include a collection of cases describing the experiences that users will have with the
software.

2.2.1 Hardware Requirements

Processor : Intel Core

Processor Speed : 2.0 GHz

RAM : 4GB

Storage Space : 21GB

2.1.2 Software Requirements

 Windows 10 Operating system

Page 5
 BLOOD BANK MANAGEMENT SYSTEM

 Front End : HTML, CSS , JAVA SERVER PAGES(JSP)

 Back End : MySQL

2.3 Development Environment

LANGUAGES: HTML, JAVA, JSP

2.3.1 HTML

Hyper Text Markup Language (HTML) is the main markup language for creating web pages
and other information that can be displayed in a web browser.
HTML is written in the form of HTML elements consisting of tags enclosed on angle brackets (like
<html>), within in the web page content. HTML tags most commonly come in pairs like <h1> and
</h1>, although some tags, known as empty elements, are unpaired, for example <imp. the first tag
in the pair is the start tag, the second tag is the end tag (they are also called opening tag and closing
tag). In between these tags’ web designers can add text, tags, comments and other types of text-
based content.
The purpose of the web browser is to read HTML documents and compose them into visible or
audible web pages. The browser does not display the HTML tags, but uses the tags to interpret the
content of the page.
HTML elements from the building blocks of all websites. HTML allows images and objects to be
embedded and can be used to create the interactive forms. It provides the means to create structured
documents by denoting the structural semantics for text such as headings, paragraphs, lists, links,
quotes and other items. It can embed scripts written in languages such as JavaScript’s which affect
the behavior of the HTML web pages

2.3.2 Java

Java is a class based, object-oriented programming language that is designed to have as few
implementation dependencies as possible. It is a general-purpose programming language intended
to let application developers write once run anywhere (WORA), meaning that complied Java code
can run on all platforms that support Java without the need for recompilation. Java applications
are
Page 6
 BLOOD BANK MANAGEMENT SYSTEM

typically compiled to bytecode that can run on any Java Virtual Machine (JVM) regardless of the
underlying computer architecture. The syntax of Java is similar to C and C++, but has fewer low-
level facilities than either of them. The Java runtime provides dynamic capabilities (such as
reflection and runtime code modification) that are typically not available in traditional compiled
languages.Java has become invaluable to developers by enabling them to Write software on one
platform and run it on virtually any other platform. Create programs that can run within a web
browser and access available web services. Develop server-side applications for online forums,
stores, polls, HTML forms processing, and more. Combine applications or services using the Java
language to create highly customized applications or services. Write powerful and efficient
applications for mobile phones, remote processors, microcontrollers, wireless modules, sensors,
gateways, consumer products, and practically any other electronic device

2.3.3 JSP
Java Server Page (JSP) is a text-based document that executes as a servlet. It is also referred
to as a HTML or Extensible Mark-up Language (XML) page with embedded Java code. JSPs can
add dynamically generated content from other resources to a static Web page. JSP generates other
text- based mark-up such as Scalable Vector Graphics (SVG) and Wireless Markup Language
(WML). A JSP is compiled by the Web Container, either at first request or when the
application starts depending on how you have configured your Web Container Service.

JSP technology allows Web developers to rapidly develop and easily maintain, information-rich,
dynamic Web pages that leverage existing business systems. It also enables rapid development
of web-based application that are platform independent. JSP technology separates the user interface
from content generation enabling designers to change the overall page layout without altering the
underlying dynamic content.It is a technology for developing Webpages that supports dynamic
content. This helps developers insert java code in HTML pages by making use of special JSP tags,
most of which start with <% and end with %>.

A Java Server Pages component is a type of Java servlet that is designed to fulfill the role of a user
interface for a Java web application. Web developers write JSPs as text files that combine HTML
or XHTML code, XML elements, and embedded JSP actions and commands.

Using JSP, you can collect input from users through Webpage forms, present records from a

Page 7
BLOOD BANK MANAGEMENT SYSTEM

database or another source, and create Webpages dynamically tags can be used for a variety of
purposes, such as retrieving information from a database or registering user preferences, accessing
JavaBeans components, passing control between pages, and sharing information.

Page 8
BLOOD BANK MANAGEMENT SYSTEM

Chapter 3

SYSTEM DESIGN

3.1 ER Diagram

Page 9
BLOOD BANK MANAGEMENT SYSTEM

Entity-Relationship Diagram is a graphical representation and relationship between

entities. It describes the relationship between data. An entity is a piece of data – an object or a
definition that stores data about. Whether data is exchanged between organizations is a
partnership. There are three main components in the E-R diagram:

Entity Type:
It symbolizes anything in the real world that has multiple existence.
 Weak Entity Type:

An entity set that does not have a primary key is referred to as a weak entity set. Here a
primary key refers to the unique attribute about an entity.
 Relationship Type:

A diamond box is used to represent the relationship between two entities. Relationships can be
one-to-one, one-to-many or many-to-many.
 Identifying Relationship Type:

The relationship type that is used to relate weak entity type to its owner is shown by double lined
diamond shaped box.
Attribute:
Characteristics of interest that describe the various properties of an entity.
 Key Attribute:

A key attribute is one for which each entity has a unique value. It is represented by an oval shape
with the attribute name underlined.
 Multi Valued Attribute:

An entity that has multiple values for that attribute is called multi valued attribute.
 Derived Attribute:

As discussed earlier, an attribute whose value depends upon the value of the stored attribute. It
is represented using a dashed oval shape.

In a database system, we deal with various types of keys as follows:

 Candidate Key:
Page 10
BLOOD BANK MANAGEMENT SYSTEM

Minimal set of attributes that uniquely identifies each occurrence of an entity type.

 Primary Key:

Candidate key selected to uniquely identify each occurrence of an entity type.

 Unique Key:

Can accept unique or null values.

 Composite Key:

A key that consists of two or more attributes and removal of even one of them would result in
loss of intended information

Page 11
BLOOD BANK MANAGEMENT SYSTEM

3.2 SCHEMA DIAGRAM

Page 12
 BLOOD BANK MANAGEMENT SYSTEM

Relational Schema
A relational database schema is the tables, columns and relationships that make up a relational
database. A relational database schema helps you to organize and understand the structure of a
database. This is particularly useful when designing a new database, modifying support more
functionality, or building integration between databases. There are two steps to creating a relational
database schema: creating the logical schema and creating the physical schema. The logical schema
depicts the structure of the database, showing the tables, columns and relationships with other tables in
the database and can be created with modelling tools or spread sheet and drawing software. The
physical schema is created by actually generating the tables, columns and relationships in the relational
database management software (RDBMS).

Page 13
BLOOD BANK MANAGEMENT SYSTEM

Chapter 4

SYSTEM IMPLEMENTATION
4.1 Tables

CREATE TABLE blood bank (

B_ID varchar(12) PRIMARY KEY, Name varchar(50), Phone number int(10), Location
varchar(100), BBM_ID varchar(12), FOREIGN KEY(BBM_ID) REFERENCES
bloodbankmanager(BBM_ID), Password varchar(20), Email varchar(100));
4.1.1 Blood Bank Table
NAME TYPE SIZE DESCRIPTION
B_ID Varchar 12 ID of the blood bank
Name Varchar 50 Name of the blood bank
Phone number Bigint 10 Phone number of the blood bank
Location Varchar 100 Location of the of the blood bank
Password Varchar 20 Password of the blood bank
BBM_ID Varchar 12 ID of the blood bank manager
Email Varchar 100 Email ID of the blood bank

CREATE TABLE Blood Bank Manager (BBM_ID varchar(12) PRIMARY KEY, Name
varchar(50),Phone number int(10), Email varchar(100), Address varchar(100), Username
varchar(50), Password varchar(20), Gender varchar(15));
4.1.2 Blood Bank Manager Table
NAME TYPE SIZE DESCRIPTION
BBM_ID Varchar 12 ID of the blood bank manager

Name Varchar 50 Name of the blood bank manager

Gender Varchar 15 Gender of the blood bank manager
Phone number Bigint 10 Phone number of the blood bank manager
Email Varchar 100 Email of the blood bank manager
Address Varchar 100 Address of the blood bank manager

Page 14
BLOOD BANK MANAGEMENT SYSTEM

Username Varchar 50 Username of the blood bank manager

Password Varchar 20 Password of the blood bank manager

CREATE TABLE Receptionist(Emp_ID int(10) PRIMARY KEY, Ename varchar(60), Ephone

number int(10), Email varchar(100), Eaddress varchar(200), Gender varchar(15), Username
varchar(50), Password varchar(20),B_id varchar(20),FOREIGN KEY(B_ID) REFERENCES
Blood Bank(B_ID));
4.1.3 Receptionist Table
NAME TYPE SIZE DESCRIPTIONS
Emp_ID Varchar 12 ID of the Employee
Ename Varchar 50 Name of the receptionist
Gender Varchar 15 Gender of the receptionist
Ephone number Bigint 10 Phone number of the receptionist
Email Varchar 100 Email ID of the receptionist
Address Varchar 100 Address of the receptionist
Username Varchar 50 Username of the receptionist
Password Varchar 20 Password of the receptionist
B_ID Varchar 12 ID of the blood bank

CREATE TABLE Blood(Bloodbagnumber_ID varchar(20) PRIMARY KEY, Blood group

varchar(10), Cost varchar(20),D_id int(10),FOREIGN KEY(D_id) REFERENCES
donor(D_id), B_ID varchar(20),FOREIGN KEY(B_id) REFERENCES bloodbank(B_id),
Validity varchar(12));
4.1.4 Blood Table
NAME TYPE SIZE DESCRIPTION
Bloodbagnumber_ID Varchar 20 ID of the blood bag number
Blood group Varchar 10 Indicates the Blood group
Cost Varchar 20 Cost of the blood
Validity Varchar 12 Validity of the blood

Page 15
BLOOD BANK MANAGEMENT SYSTEM

B_ID Varchar 20 ID of the blood bank

CREATE TABLE Donor(D_ID int(10) PRIMARY KEY, D name varchar(100), D dob date,
Age varchar(20), Gender varchar(10), Weight varchar(12), Blood group varchar(10), Date of
donation date(8), D phone number int(10), Email varchar(100), D address varchar(200), Health
issues varchar(20), Emp_ID int(10),FOREIGN KEY(Emp_ID) REFERENCES
receptionist(Emp_ID));
4.1.5 Donor Table
NAME TYPE SIZE DESCRIPTION
D_ID Int 10 ID of the donor
D name Varchar 100 Name of the donor
D dob Date 8 Date of birth of the donor
Age Int 11 Age of the donor
Gender Varchar 10 Gender of the donor
Weight Int 11 Weight of the donor
Blood group Varchar 10 Blood group of the donor
Date of donation Date 8 Date of blood donation by the donor
D phone number Bigint 10 Phone number of the donor
Email Varchar 100 Email of the donor
D address Varchar 200 Address of the donor
Health issues Varchar 20 Health issues of the donor
Emp_ID Varchar 12 ID of the Employee

CREATE TABLE Blood Request(Request_ID varchar(20) PRIMARY KEY, Name

varchar(100), Phone number int(10), Blood group varchar(10), Requested date date(8),
Otherdetails varchar(200), Status varchar(100), B_ID varchar(20),FOREIGN KEY(B_id)
REFERENCES bloodbank(B_id), Quantity varchar(50));

Page 16
 BLOOD BANK MANAGEMENT SYSTEM

4.1.6 Blood Request Table

NAME TYPE SIZE DESCRIPTION
Request ID Varchar 20 ID of the request
Name Varchar 100 Name of the blood requester
Phone number Bigint 10 Phone number of the blood requester
Blood group Varchar 10 Blood group of the blood requester
Email Varchar 100 Email ID of the blood requester
Requested date Date 8 Date of the blood request
Otherdetails Varchar 200 Other details of the blood requester
Status Varchar 100 Status of the blood request
B_ID Varchar 20 ID of the blood bank
Quantity Varchar 50 Quantity of the blood requested

CREATE TABLE Blood Camp(Event_ID int(12) PRIMARY KEY, Event_date date,

Event_time time, Event_place varchar(100), BBM_ID varchar(12), B_ID
varchar(12),FOREIGN KEY(BBM_ID) REFERENCES Blood Bank
Manager(BBM_ID),FOREIGN KEY(B_ID) REFERENCES Blood Bank(B_ID));
4.1.7 Blood Camp Table
NAME TYPE SIZE DESCRIPTION
Event ID Int 12 ID of the blood camp event
Event_Date Date 8 Date of the blood camp event
Event_time Varchar 30 Time of the blood camp event
Event_place Varchar 100 Place of the blood camp event
BBM_ID Varchar 12 ID of the blood bank manager
B_ID Varchar 12 ID of the blood bank

CREATE TABLE Stock(Stock_ID int(10) PRIMARY KEY, Blood group varchar(10), Units
varchar(50),B_ID varchar(12),FOREIGN KEY(B_ID) REFERENCES Blood Bank(B_ID),
BBM_ID varchar(12),FOREIGN KEY(BBM_ID) REFERENCES Blood Bank
Manager(BBM_ID));

Page 17
BLOOD BANK MANAGEMENT SYSTEM

4.1.8 Stock Table

NAME TYPE SIZE DESCRIPTION
Stock_ID Int 10 ID of the blood stock
Blood group Varchar 10 Blood group of the blood stock
Units Varchar 50 Number of units of blood stock
B_ID Varchar 12 ID of the blood bank
BBM_ID Varchar 12 ID of the blood bank manager

4.2 Triggers
TRIGGER specifies an event, a condition and an action. It specifies type of the action to be
taken when certain events occur and when certain condition are satisfied.

1. Start blood bank database system.

2. Create trigger trigger_name for table donor with action to be taken before update.

3. IncrementS the donor count.

4. Stop

Page 18
 BLOOD BANK MANAGEMENT SYSTEM

Chapter 5
SNAPSHOTS

Fig 5.1 Front Page

Fig 5.2 Blood Request Page

Page 19
BLOOD BANK MANAGEMENT SYSTEM

5.3 Blood Bank Page

5.4 Blood Camp Page

Page 20
BLOOD BANK MANAGEMENT SYSTEM

5.5 About Page

5.6 Home Page

Page 21
BLOOD BANK MANAGEMENT SYSTEM

5.7 Receptionist Login Page

5.8 Receptionist Signup Page

Page 22
BLOOD BANK MANAGEMENT SYSTEM

5.9 Admin Home Page

5.10 Donor Registration Page

Page 23
BLOOD BANK MANAGEMENT SYSTEM

5.11 Donor Edit Page

5.12 Admin Login Page

Page 24
BLOOD BANK MANAGEMENT SYSTEM

5.13 Admin Signup Page

5.14 Admin Home Page

Page 25
BLOOD BANK MANAGEMENT SYSTEM

5.15 Add Stock Page

5.16 Manage Stock Page

Page 26
BLOOD BANK MANAGEMENT SYSTEM

5.17 Blood Details Page

5.18 Edit Delete Page

Page 27
BLOOD BANK MANAGEMENT SYSTEM

5.19 Blood Bank Register Page

5.20 Request Blood Page

Page 28
BLOOD BANK MANAGEMENT SYSTEM

5.21 Requested Completed Page

5.22 Add Camp Camps

Page 29
BLOOD BANK MANAGEMENT SYSTEM

5.23 Search Event/Camp Page

Page 30
BLOOD BANK MANAGEMENT SYSTEM

Chapter 6

CONLUSION AND FUTURE ENCHANCEMENTS

6.1 Conclusion
The project entitled “BLOOD BANK MANAGEMENT SYSTEM” was completed on
time with total satisfaction after testing with possible sample data. The performance was found
to be efficient and error free. This is a user-friendly packaged application which is very easy to
access and understand. Anyone with Knowledge of Computers will find it very easy to use this
software and perform various operations on it. In this project, first an attempt has been made to
find the need of the system. To fulfil the needs, a detailed study had been conducted to find the
various requirements of the system. This particular system has been designed in an attractive
manner, so that even a user with minimum knowledge can be able to operate the system easily.

This software combines the best of both the world i.e.; programming language
(JAVA), and database (MYSQL) providing easy accessibility and security. It was developed to
benefit the organizations and the customers. Finally the system was tested with real data and
everything worked successfully. Thus the system has fulfilled all the objectives identified and is
able to replace the existing system.

6.2 Future Enhancements

Since there were a small amount of contact information, it may be difficult for some
people to get blood quickly. I would like to gather more information about contacts in other
cities and villages and will provide people with more support to connect all of us with morality.

Page 31
BLOOD BANK MANAGEMENT SYSTEM

BIBLIOGRAPHY
• FOR .NET INSTALATION
https://support.microsoft.com/
• FOR SQL SERVER https://docs.microsoft.com/en-us/
• FOR ASP.NET www.asp.net www.fmexpense.com/quickstart/aspplus//default.com
www.aspfree.com www.youtube.com

Page 32
BLOOD BANK MANAGEMENT SYSTEM

Page 33