A

Project Report
on
BLOOD BANK & DONATION MANAGEMENT SYSTEM
submitted
in partial fulfillment
for the award of the degree of
MASTER OF COMPUTER APPLICATION

Supervisor: - Submitted by: -

Name : Name of Candidate: Prajapati Anand
Designation: Roll No: - 20CSFMC628

SHEKHAWATI INSTITUTE OF TECHNOLOGY, SIKAR

BIKANER TECHNICAL UNIVERSITY, BIKANER

2020- 2022
 CERTIFICATE

This is to certify that Project on BLOOD BANK & DONATION MANAGAMENT

SYSTEM, at TECHNOGLOBE (JAIPUR) in PHP Technology has been completed under
my supervision. The Report Consists of result empirical study conduct by Mr. Prajapati
Anand, student of final year MCA as a partial fulfillment for the award of Degree of Master
of Computer Application is a record of student’s work carried out under my guidance and
supervision.

This work has not been submitted elsewhere for the award of any other degree.

DATE:

PLACE: SIT, SIKAR

(…………………………..) (………………………..)

(Supervisor) (H.O.D)
 CANDIDATE DECLARATION

I hereby declare that the work, which is being presented in the Project, entitled “BLOOD
BANK & DONATION MANAGAMENT SYSTEM” in partial fulfillment for the award of
Degree of “Master of Computer Application” and submitted to Shekhawati Institute of
Technology, Bikaner Technical University is a record of my own investigations carried under
the Guidance of Shri/ Dr. ...............................,

I have not submitted the matter presented in this Seminar anywhere for the award of any
other Degree.

(Signature)

Name: Prajapati Anand

Roll No.: 20CSFMC628

Date:…………

SIT, Sikar
 ACKNOWLEDGEMENT

I am highly indebted to Mr. …………………………………., for their guidance and constant

supervision as well as for providing necessary information regarding the project & also for
their support in completing the project. Indeed, it was your support that saw us through the
many ups and down of life. I would like to express my gratitude towards my parents and
friends for their kind cooperation and encouragement which help me in completion of this
project. My thanks and appreciations also go to my colleague in developing the project and
people who have willingly helped me out with their abilities. Thanks to my friends and my
team members for being a constant source of encouragement in all my endeavours.

Thank You!
COMPANY PROFILE
 APPROVAL SHEET

This project report entitled Blood Bank & Donation Management System by
Prajapati Anand is approved for the degree of MCA.

Examiners

________________________

________________________

________________________

Supervisor (s)

________________________

________________________

_______________________
 CONTENTS

PAGE NO.

ABSTRACT …………………………....................... 1

Chapter 1 INTRODUCTION ………………………………….. 3

Chapter 2 STATEMENT OF PROBLEMS…………………… 5

Chapter 3 USER REQUIREMENTS………………………….. 7

Chapter 4 ANALYSIS………………………………………... 9

4.1 SYSTEM ANALYSIS ………………….. 9

4.2 FESEABILITY STUDY………………… 10

4.2.1 ECONOMICAL FESEABILITY…. 10

4.2.2 TECHNICAL FESEABILITY……. 11

4.2.3 OPERATIONAL FESEABILITY… 12

4.3 SYSTEM SPECIFICATIONS…………… 12

Chapter 5 ADVANTAGES AND DISADVANTAGES

OF THE EXISTING SYSTEM…………………………… 13

5.1 ADVANTAGES OF THE SYSTEM…………………. 13

5.2 DISADVANTAGES OF THE SYSTEM…………….. 13

Chapter 6 OBJECTIVES OF THE SYSTEM……………………… 14

Chapter 7 DESIGN APPROACH……………………………… 15

7.1 SYSTEM DESIGN……………………………. 15

7.2 DESIGN TOOLS………………………………. 15

7.2.1 USE CASE DIAGRAMS…………… 15

7.2.2 DATA FLOW DIAGRAMS………… 17

7.2.3 E-R DIGRAMS……………………… 20

Chapter 8 SYSTEM TESTING ……………………………….. 21

Chapter 9 FUTURE SCOPE OF THE SYSTEM……….……… 26

Chapter 10 PROJECT SNAPSHOTS ………………………….. 34

Chapter 11 CONCLUSION…………………………………… 57

Chapter 12 APPENDIX……………………………………….. 58

Chapter 13 REFERENCES…………………………………… 61
LIST OF TABLES…………………………………………………………….. [28-33]

LIST OF FIGURES…………………………………………………………… [16-20]

ABBREVIATION…………………………………………………………. 56
 ABSTRACT

“Blood Bank & Donation Management System” is a browser-based system that is

designed to store, process, retrieve and analyse information concerned with the administrative
and inventory management within a blood bank. This system is mainly based on collection,
storage, and usage of blood in needy situations. 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
must be requested and we supply the information of the donor. The donors can update their
status whether they are available or not.

The project analyses the system requirements and then comes up with the requirements
specifications. It studies other related systems and then come up with system specifications.
The system is then designed in accordance with specifications to satisfy the requirements.
The system design is then implemented with MYSQL, PHP and HTML. The system is
designed as an interactive and content management system. The content management system
deals with data entry, validation confirm and updating whiles the interactive system deals
with systems and product development projects or indeed for any activity where you must
manage a relationship.

The purpose of this BLOOD BANK & DONATION MANAGEMENT SYSTEM

PROJECT was to develop a blood management information system to assist in the
management of blood donor records and ease/or control the distribution of blood in various
parts of the country basing on the hospital demands. Without quick and timely access to
donor records, creating market strategies for blood donation, lobbying and sensitization of
blood donors becomes very difficult. The blood management information system

1
offers functionality to quick access to donor records collected from various parts of the
country.

It enables monitoring of the results and performance of the blood donation activity such that
relevant and measurable objectives of the organization can be checked.

It provides to management timely, confidential and secure medical reports that facilitates
planning and decision making and hence improved medical service delivery. The reports
generated by the system give answers to most of the challenges management faces as far as
blood donor records are concerned.

The Ethiopian Red Cross Society publication, Development in the 1990 states that
information from blood donors should be completely confidential and if this is not assured,
names of the blood donors should not be recorded at all and/or an alternative record
identification should be used.

CHAPTER 1

2
 INTRODUCTION

A blood donation is a process whereby a person voluntarily has blood drawn to be used for
future transfusions when in need at hospitals for treatment procedures that require them.
Donation may be of whole blood (blood drawn directly from the body) or of specific
components of the blood; such as red blood cells, white blood cells, plasma, and platelets.
Blood banks often participate in the process of collecting blood and other procedures such as
managing stocks, approving blood requests, and updating donation information. The
inspiration of this project is to improve blood banks in Thailand and to develop a blood bank
information system which focuses on making an online system that is accessible for both
donors and administrators. Donors can directly receive information regarding their previous
blood donations, including their blood results and donation history, in order to easily schedule
their next donations. They can also update the personal information through the system,
without having to contact the blood bank registry. The system is also developed for the
administrators, who are the main authority in the system. Administrators can add, modify,
delete, and query any donation 1 information if necessary. The administrator is also
responsible for responding to the hospital’s blood requests and checking the stocks in the
blood bank’s inventory.

Data is the code word of the computer industry. Data refers to a collection of facts usually
collected as a result of observation and experiment or processes within a computer system.
This may consist of numbers, words or images or observations of a set of variables. Data are
often viewed as a lowest level of abstraction from which information and knowledge are
derived.

In this project we have given an insight to the development of a computer-based database

titled "BLOOD BANK & DONATION MANAGEMENT SYSTEM" using PHP as a
front-end and SQL as back-end.

Blood Bank automation or computerization of the blood bank is the application of computers
to perform either in part or the activities that are carried out in the blood bank setting. Blood
bank automation requires the use of computers and associated programs that are suited for

3
the purpose. These associated or group of programs that are use on the computer system can
be describe as Pharmacy Management System.

Blood Bank management system is used to perform tasks such as registration of customers,
blood and staffs. It helps the customer to purchase the required blood bases on their needs.
Customer can make transaction through cash. Information related to blood, employees,
customers, etc can be easily retrieved.

This software is required to eliminate tedious manual searching, cataloguing, and loaning out
of medicines, Including registration and clearance of customers.

4
 CHAPTER 2

STATEMENT OF PROBLEMS

The following problem arises when using a typical blood bank’s existing system:

(i) Personal profile accessibility: -

The donor’s information can only be updated by the administrators of the blood
bank. A donor can update their information by calling, faxing, e-mailing, but not
by themselves. This is a waste of time just for updating a piece of information and
it may be troublesome for some donors.

(ii) Lost or damaged card: -

A typical membership card can easily get damaged if it is exposed to the sunlight
or weather and this causes to ruin the card’s barcode which is significantly
important for retrieving records. If the card gets lost or stolen, the donor has to
make a replacement card to keep their membership at the blood bank

(iii) Donation record accessibility: -

The donor ID card is the only tangible evidence that contains the donor’s
recent donation records, if the card gets lost, donors may find it difficult to
schedule their next appointment since they are not able to see the last time, they
had donated blood.

(iv) Blood result notifications

After the process of blood donation, the donor will receive a card that only
contains their name and blood type. They will not be notified of their blood result
unless they request that information from the blood bank.

(v) Blood stock management: -

5
 Blood banks are required to maintain account of blood bags in the inventory. This
increases with each blood donation recorded in our system, and decreases as they
are checked out upon hospital requests. Our system will need to keep the
information up-to-date to ensure correctness of the inventory.

(vi) Mailing by postal system: -

Blood banks will only mail donors when the donated blood is disqualified,
however, this mail is sent through the postal system to the donor’s given address.
If the donor’s address is recorded incorrectly, the mail will be sent to the wrong
address and the donor will never be notified that their blood is rejected and given
the reason for that.

6
 CHAPTER 3

USER REQUIREMENTS

There are two internal users involved in this system. The user requirements are considered as
follows:

(i) Donor: -

(a) To be able to view their donation records, including where and when they
made donations, and the blood results for each, to learn of their donated blood
quality and schedule their next donations.

(b) To be able to view and update their personal information, including name,
contact address, and phone number, to keep their donor’s information record
up to-date with the blood bank.

(c) To be notified of the blood results of their previous donation by e-mail, to

know the success of their donation.

(ii) Administrator –.

(a) To be able to create, update, delete, and query donor’s records in order to
manage donor information.

(b) To be able to create, update, delete, and retrieve donation records to manage
information about donations made.

(c) To be able to deposit donated blood into inventory when donations are made.

(d) To be able to withdraw blood from the inventory and keep a record of blood
stocks to always keep count of the blood bags.

(e) To be able to create, update, delete, and retrieve request records from hospitals
to manage hospital requests for blood.

(f) To be able to create, update, delete, and query hospital’s records in order to

7
 manage hospital information.

(g) To be able to send e-mails to donors for their user account and blood results
through the system.

(h) To be able to send e-mail responding to hospitals for their blood requests
through the system.

8
 CHAPTER 4

ANALYSIS

4.1 SYSTEM ANALYSIS: -

Systems Analysis and Design is an active field in which analysts repetitively learn new
approaches and different techniques for building the system more effectively and efficiently.
The primary objective of systems analysis and design is to improve organizational systems
There are two types of process in the existing system:

(i) The blood donation process by donors: -

When a new donor comes to donate blood, they are required to fill out their personal
information during the registration process before donating. After the donation, the donor is
given a donor identification card with their name, blood type and a barcode to be used as a
reference for future donations. The barcode is used to retrieve the donor’s record containing
their personal information, medical history, and donation information, including blood
results. Only blood bank administrators have the authority to access the donor’s records, since
the system is only available for their use within the organization. This makes it difficult for
donors to make changes to their personal information within the system. That is, for donors to
update their personal information, such as their phone number, mailing address, or e-mail,
they cannot update the information by themselves, but must contact the blood bank centre to
update their information. At the back the card is a table that contains number of donations,
date, location, and the blood collector’s signature. Existing donors can submit their donor ID
cards to retrieve their personal information and donation records and start the blood donation
process, and they will be given a new card after they have donated blood for a total of eight
times. Having a donor ID card may be a tangible reminder to people that they are helping
lives as a blood donor; however, possessing a physical card comes with drawbacks such as
loss or damage. To ensure donors can still identify themselves with the system, other
credentials, such as username and password, can be used as a safeguard if their donor ID card
is lost or damaged. If the donated blood is disqualified, the donor will be notified through
postal mail that their blood component is reactive to viruses [4], meaning that there is a
positive result of the blood being infected, and the organization will also inform the donor to

9
perform another blood test at the blood bank to confirm the result of blood. If the blood is
qualified, the administrator then will deposit the blood into the inventory for future requests.
Blood Request Process by Hospitals can request for blood by calling in or e-mailing the blood
bank the type of blood and the quantity that is in need. The administrator is responsible in
checking the availability of the blood type according to the request. If the requested blood
type is available, the administrator will withdraw the blood from the inventory and transfer it
to the hospital. However, if the requested blood is unavailable, the administrator will send an
e-mail to inform the hospital.

4.2 FEASIBILITY STUDY

Feasibility is conducted to identify the best system that meets all requirements. It is both
necessary and important to evaluate the feasibility of a project at the earliest possible time.
Feasibility study includes an identification description, an evaluation of proposed system
and feasibility study of the proposed system is to be carried out. This is to ensure that the
proposed system is not a burden to the shop. The feasibility study should be relatively
cheap and quick. The results should inform the decision of whether to go ahead with a
more detailed analysis for feasibility analysis, some understanding of the major
requirements for the system is essential. Four key considerations involved in the feasibility
analysis are:-

(i) ECONOMICAL FEASIBILITY

(ii) TECHNICAL FEASIBILITY

(iii) OPERATIONAL FEASIBILITY

4.2.1 ECONOMICAL FEASIBILITY:

Economical feasibility is the most frequently used method for evaluating the effectiveness
of the candidate system. It is very essential because the main goal of the proposed system
is to have economically better result along with increased efficiency. A cost evaluation is
weighed against the ultimate income or product. Economic justification is generally the
bottom-line consideration that includes cost benefit analysis, long term corporate income
strategies, and cost of resources needed for development and potential market growth.

10
When compared to the advantage obtained from implemented the system its cost is
affordable. This organization. The amount of fund that company can pour into the research
and development of the system is limited. The expenditures must be justified. Thus, the
developed system as well within the budget and this was achieved because most of the
technologies used are freely available

Installation of new system will reduce administrative and operational cost. The newly
developed software that does not require any existing manual paper works and files. So
cost also can reduced by removing these types of materials. Proposed system was
developed with available resources. Since cost input for the software is almost nil the
output of the software is always a profit. Hence software is economically feasible.

4.2.2 TECHNICAL FEASIBILITY:

The study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. The developed system must have a modest requirement, as only minimal or null
changes are required for implementing this system. This is related to the technicality of the
project. This evaluation determines whether the technology needed for the proposed
system is available or not. It deals with hardware as well as software requirements. That is,
type of hardware, software and the methods required for running the system are analysed.
A study of function, performance and constraints may improve the ability to create an
acceptable system, technical feasibility is frequently the most difficult area to achieve at
the stage of product engineering process. The scope was whether the work for the project
is done with the current equipment and the existing system technology has to be examined
in the feasibility study. The result was found to be true. This feasibility is carried out to
check the technical requirements of the system.

This system is implemented by using PHP. So, it can be used in any Windows OS
computer. This system requires very low system resources and it will work in almost all
configurations. In the existing system all functions are doing manually. So, if they get this
designed software, the problems can be avoided and thus the system will run smoothly. In
the proposed system, data can be easily stored and managed using database management

11
system software. The reports and results for various queries can be generated easily. Our
proposed system is technically feasible to use by any user.

4.2.3 OPERATIONAL FEASIBILITY: -

The purpose of the operational feasibility is to determine whether the new system will be
used if it is developed and implemented and whether there will be resistance from user that
will undermine the possible application benefits. The aspect of study is to check the level of
acceptance of the system by the user. This includes the process of training the user to use the
system efficiently. The user must not feel threatened by the system, instead must accept it as
a necessity. The level of acceptance by the user solely depends on the methods that are
employed to educate the user about the system and to make him familiar with it. His level of
confidence must be raised so that he is also able to make some constructive. The proposed
system is an upgrade version of the current system new fields have been implemented
according to the user need, hence it ensures a user-friendly environment in such a way that it
ensures all the aspects. The proposed system is very much user friendly and the system is
easily understood by simple training and it is operationally feasible

4.3 SYSTEM SPECIFICATIONS: -

HARDWARE REQUIREMENTS: -

 Pentium-IV(Processor).

 2 GB RAM

 Hard disk with at least free space of 2 GB

 Microsoft Compatible 101 or more Key Board

SOFTWARE REQUIREMENTS: -

 Operating System: Windows (Windows 10 Recommended for ease)

 Web-Technology: PHP

 Front-End: HTML, CSS, JAVASCRIPT

12
 Back-End: MySQL, PHP

 Web Server: Apache SERVER (XAMPP)

CHAPTER 5

ADVANTAGES & DISADVANTAGES OF THE EXISTING SYSTEM

5.1 ADVANTAGES OF THE SYSTEM: -

(i) User view all blood bank information is location wise.

(ii) Donor easily donates blood near blood bank location.

(iii) Patient easily request for blood near blood bank location.

(iv) In this system also supported inquiry for user.

5.2 DISADVANTAGES OF THE SYSTEM: -

The following drawbacks of existing system emphasize the need for computerization:

(i) A lot of users/ Blood Donator came at a time on BLOOD BANK & DONATIN
MANAGEMENT SYSTEM website, at this situation it is become too difficult
maintain it in proper way.

(ii) A lot of blood donators came in same time for queries, which makes the task of
admin tough.

(iii) It lacks of data security.

(iv) Retrieval of data takes lot of time.

(v) Percentage of accuracy is less.

(vi) Reports take time to produce.

13
 CHAPTER 6

OBJECTIVES OF THE SYSTEM

The goal of the project is to develop a web application for blood banks to manage
information about their donors and blood stock. The main objectives of this website
development can be defined as follows:

(i) To develop a system that provides functions to support donors to view and manage

their information conveniently.

(ii) To maintain records of blood donors, blood donation information and blood stocks in a

centralized database system.

(iii) To inform donors of their blood result after their donation.

(iv) To support searching, matching and requesting for blood convenient for administrators.

(v) To provide a function to send an e-mail directly to the donor for their user account and

the hospital, the availability of the blood bag.

14
 CHAPTER 7

DESIGN APPROACH

7.1 SYSTEM DESIGN: -

System design is the process of developing specification for candidate system that meet the
criteria established in the system analysis. Major step in system design is the preparation of
the input forms and the output reports in a form to the user. The main objectives of the system
design is to the packages easily by any computer operator system design is the creative act of
invention, developing new outputs, a database, offline files, methods, procedures and out for
processing business to meet an organization objectives. System builds information gathered
during the system analysis. System design has four phases

7.2 DESIGN TOOLS: -

7.2.1 USE CASE DIAGRAM: -

To model a system the most important aspect is to capture the dynamic behaviour. To clarify
a bit in details, dynamic behaviour means the behaviour of the system when it is running
/operating. So only static behaviour is not sufficient to model a system rather dynamic
behaviour is more important than static behaviour. In UML there are five diagrams available
to model dynamic nature and use case diagram is one of them. Now as we must discuss that
the use case diagram is dynamic in nature there should be some internal or external factors
for making the interaction. These internal and external agents are known as actors. So, use
case diagrams are consists of actors, use cases and their relationships. The diagram is used to
model the system/subsystem of an application. A single use case diagram captures a
particular functionality of a system.

The purpose of use case diagram is to capture the dynamic aspect of a system. But this
definition is too generic to describe the purpose. Because other four diagrams (activity,
sequence, collaboration, and State chart) are also having the same purpose. So we will look
into some specific purpose which will distinguish it from other four diagrams. Use case

15
diagrams are used to gather the requirements of a system including internal and external
influences. These requirements are mostly design requirements. So, when a system is
analysed to gather its functionalities use cases are prepared and actors are identified.

USE CASE FOR ADMIN:

REGISTRATION

LOGIN

MANAGE DONOR

MANAGE ACCEPTOR
REQUEST

VIEW BLOOD STOCK

FIGURE 7.1

16
 USE CASE FOR DONOR:

REGISTRATION

LOGIN

VIEW PROFILE

MAKE NEW BLOOD

DONATION

FIGURE 7.2

7.2.2 DATA FLOW DIAGRAM (DFD)

A DFD, also known as a “bubble chart” has the purpose of clarifying system- requirements
and identifying major transformations that will become programs in system design. A DFD
consists of a series of bubbles joined by lines. The bubbles represents data transformations
and the lines represents data flow in the system. A data flow diagram may be used to
represent a system or software at any level of abstraction. A DFD is a diagram that describes
the flow of data and the processes that change or transform data throughout a system. It is a
structured analysis and design tool that can be used or flowcharting in place of, or in
association with, information oriented and process-oriented system flowchart. When analyst
prepare the DFD, they specify the user needs at a level of detail that virtually determines the
information flow into and out of the system and the required data resources. This network is
constructed by using a set of symbols that do not imply a physical implementation. The DFD
implementation plan reviews the current physical system, prepare input and output
specification.

17
CONTEXT DIAGRAM: -

A context diagram is a level-0 DFD and represents the entire system elements as a single
bubble with input and output data indicated by incoming and outgoing arrows respectively.
The user gives data or commands as input and the user will get the details as output.

FIG 7.3 CONTEXT DIAGRAM OF BLOOD BANK & DONATION MANAGEMENT

SYSTEM

18
FIG 7.4 LEVEL 1 DFD

FIG 7.5 ADMIN STRUCTURE DFD DIAGRAM

19
 7.2.3 ENTITY RELATIONSHIP DIAGRAMS (ERD)

E-R DIAGRAM
Gender
Donor Name Blood Group
Age
Collection Date
DID
BBID
Expiry Date
Blood Group

Status

Address Donor Donates Blood

Ph No Address
Ph No
Name

Hospital
Registers Stored

Orders
Works

Blood Group
Receptionist Blood Bank

No of Bags
Ph No
Emp ID
Address Issues

Name

Transaction No Blood Bag Amount

Registered Donor
Date

Hospital
Outsiders Blood Group No of Bags

FIG 7.6 ER DIAGRAM

20
 CHAPTER 8

SYSTEM TESTING

Testing is a process of executing a program with the indent of finding an error. Testing is a
crucial element of software quality assurance and presents ultimate review of specification,
design, and coding. System Testing is an important phase. Testing represents an interesting
anomaly for the software. Thus, a series of testing are performed for the proposed system
before the system is ready for user acceptance testing. A good test case is one that has a high
probability of finding an as undiscovered error. A successful test is one that uncovers an as
undiscovered error.

Testing Objectives: -

(i) Testing is a process of executing a program with the intent of finding an error.

(ii) A good test case is one that has a probability of finding a yet undiscovered error.

(iii) A successful test is one that uncovers an undiscovered error.

Testing Principles: -

(i) All tests should be traceable to end user requirements.

(ii) Tests should be planned long before testing begins.

(iii) Testing should begin on a small scale and progress towards testing in large.

(iv) Exhaustive testing is not possible.

(v) To be most effective testing should be conducted by a independent third party. The
primary objective for test case design is to derive a set of tests that has the highest livelihood
for uncovering defects in software. To accomplish this objective two different categories of
test case design techniques are used.

White-box testing:
White box testing focus on the program control structure. Test cases are derived to ensure

21
that all statements in the program have been executed at least once during testing and that all
logical conditions have been executed.

Block-box testing:

Black box testing is designed to validate functional requirements without regard to the
internal workings of a program. Black box testing mainly focuses on the information domain
of the software, deriving test cases by partitioning input and output in a manner that provides
through test coverage. Incorrect and missing functions, interface errors, errors in data
structures, error in functional logic are the errors falling in this category.

Testing strategies:

A strategy for software testing must accommodate low-level tests that are necessary to verify
that all small source code segment has been correctly implemented as well as high-level tests
that validate major system functions against customer requirements.

Testing fundamentals:

Testing is a process of executing program with the intent of finding error. A good test case is
one that has high probability of finding an undiscovered error. If testing is conducted
successfully, it uncovers the errors in the software. Testing cannot show the absence of
defects, it can only show that software defects present.

Testing Information flow:

Information flow for testing flows the pattern. Two class of input provided to test the process.
The software configuration includes a software requirements specification, a design
specification and source code. Test configuration includes test plan and test cases and test
tools. Tests are conducted and all the results are evaluated. That is test results are compared
with expected results. When erroneous data are uncovered, an error is implied and debugging
commences.

Unit testing:

Unit testing is essential for the verification of the code produced during the coding phase and
hence the goal is to test the internal logic of the modules. Using the detailed design

22
description as a guide, important paths are tested to uncover errors with in the boundary of
the modules. These tests were carried out during the programming stage itself. All units of
ViennaSQL were successfully tested.

Integration testing :

Integration testing focuses on unit tested modules and build the program structure that is
dictated by the design phase.

System testing:

System testing tests the integration of each module in the system. It also tests to find
discrepancies between the system and it’s original objective, current specification and system
documentation. The primary concern is the compatibility of individual modules. Entire
system is working properly or not will be tested here, and specified path ODBC connection
will correct or not, and giving output or not are tested here these verifications and validations
are done by giving input values to the system and by comparing with expected output. Top-
down testing implementing here.

Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation. Acceptance
testing begins when the system is complete. Its purpose is to provide the end user with the
confidence that the system is ready for use. It involves planning and execution of functional
tests, performance tests and stress tests in order to demonstrate that the implemented system
satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

Timing Analyzer – also called a profiler, reports the time spent in various regions of the code
are areas to concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect code for
deviations from standards and guidelines.

23
Test Cases:

Test cases are derived to ensure that all statements in the program have been executed at least
once during testing and that all logical conditions have been executed. Using White-Box
testing methods, the software engineer can drive test cases that: -

(i) Guarantee that logical decisions on their true and false sides.

(ii) Exercise all logical decisions on their true and false sides.

(iii) Execute all loops at their boundaries and within their operational bounds.

(iv) Exercise internal data structure to assure their validity.

The test case specification for system testing must be submitted for review before system
testing commences. elements consisting of "tags" surrounded by angle brackets within the
web page content. It can include or can load scripts in languages such as JavaScript which
affect the behaviour of HTML processors like Web browsers; and Cascading Style Sheets
(CSS) to define the appearance and layout of text and other material. The W3C, maintainer of
both HTML and CSS standards, encourages the use of CSS over explicit presentational
markup.

Hyper Text Markup Language (HTML) is the encoding scheme used to create and format a
web document. A user need not be an expert programmer to make use of HTML for creating
hypertext documents that can be put on the internet. Most graphical e-mail clients allow the
use of a subset of HTML (often ill-defined) to provide formatting and semantic markup not
available with plain text. This may include typographic information like coloured headings,
emphasized and quoted text, inline images, and diagrams. Many such clients include both a
GUI editor for composing HTML e-mail messages and a rendering engine for displaying
them. Use of HTML in e-mail is controversial because of compatibility issues It is possible to
simulate many class-based features with prototypes in JavaScript. Functions double as object
constructors along with their typical role. Prefixing a function call with new creates a new
object and calls that function with its local this keyword bound to that object for that
invocation. The constructor's prototype property determines the object used for the new
object's internal prototype. JavaScript's built-in constructors, such as Array, also have
prototypes that can be modified. Unlike many object-oriented languages, there is no

24
distinction between a function definition and a method definition. Rather, the distinction
occurs during function calling.

USAGE: -

The primary use of JavaScript is to write functions that are embedded in or included from
HTML pages and interact with the Document Object Model (DOM) of the page. Because
JavaScript code can run locally in a user's browser (rather than on a remote server) it can
respond to user actions quickly, making an application feel more responsive. Furthermore,
JavaScript code can detect user actions which HTML alone cannot, such as individual
keystrokes. Applications such as Gmail take advantage of this: much of the user-interface
logic is written in JavaScript, and JavaScript dispatches requests for information (such as the
content of an e-mail message) to the server. The wider trend of Ajax programming similarly
exploits this strength.

MySQL Introduction: -

There are a large number of database management systems currently available, some
commercial and some free. Some of them : Oracle, Microsoft Access, MySQL and
PostgreSQL. These database systems are powerful, feature-rich software, capable of
organizing and searching millions of records at very high speeds.

Understanding Databases, Records, and Primary Keys: -

Every Database is composed of one or more tables. These Tables, which structure data into
rows and columns, impose organization on the data. The records in a table(below) are not
arranged in any particular order. To make it easy to identify a specific record, therefore, it
becomes necessary.

Relational Database Management System (RDBMS): -

You already know that a single database can hold multiple tables. In a Relational database
management system (RDBMS), these tables can be linked to each other by one or more
common fields, called foreign keys.

Database administrator (DBA): -

25
Database administrator is the super user of database; he has unrestricted rights and privileges
to access database, grant permission to other database users.

CHAPTER 9

FUTURE SCOPE OF THE PROJECT

The system functions and features of our system will include the following:

(i) Registration: -

This function allows the donor and administrator to register as a user to interact with the
system. The system requires the user to login before viewing and editing any
information.

(ii) View and edit information online: -

Donors are allowed to view their blood donation records online by their given account.
They can also edit their personal information through the system.

(iii) Data is entered by the Administrators: -

The donor’s information and donation records can be sent from the hospital to the
administrator by calling or e-mail. The administrator is responsible for keying the
received data into the system.

(iv) Recording donation records: -

The system can record data of whole blood which is sent from the hospital.

(v) Manage blood inventory: -

The system uses a First-In-First-Out stock management, where the blood stock that is
checked-in to the system first will be the first one given to the hospital when requested.

26
When the blood stock is expired, the administrator is responsible for removing the stock
from the inventory and updating the system.

(vi) Blood requests: -

The hospital can request blood via e-mail and by calling to the blood bank.

(vii) Notify by E-mail: -

The donor’s account and generated password will be sent via e-mail, following by their
blood result of the previous donation sent in a separated e-mail. Hospitals can also
receive e-mail responding to their requested blood whether it is available in our stock or
not.

(viii) Summary Report: -

The system can generate a report to summarize all records including blood donation,
blood requests and blood stock for the administrator.

27
 LIST OF TABLES

Table name: sign up

Primary key: regno

Description: This table store the sign up information.

Field Name Data Type Size Constraints Description

regno Int 10 Primary key To Store register

number

fname Varchar 50 Not null To store first name

lname Varchar 50 Not null To store last name

email Varchar 50 Not null To store email

contact Bigint 12 Not null To store contact

Number

username Varchar 50 Not null To store Username

28
 Table name: login
Primary key: loginid

Description: This table store the login information.

Field Name Data Type Size Constraints Description

loginid Int 10 Primary key To store Loginid

Username Varchar 50 Not null To store Username

password Varchar 50 Not null To store Password

usertype Varchar 50 Not null To store Usertype

29
 Table name: Donor
Primary key: donorid

Description: This table store the donor information.

Field Name Data Type Siz Constraints Description

e

Donorid Int 10 Primary key To store the donor id

donorname Varchar 50 Not null To store the donor name

bloodgroup Varchar 12 Not null To store the blood group

gender Varchar 12 Not null To store the Gender

city Varchar 50 Not null To store the city

Hosdeatils Varchar 100 Not null To store the hospital

name & address

doctorname Varchar 50 Not null To store the doctor name

cname Varchar 50 Not null To store the

contact name

cemail Varchar 50 Not null To store the

contact email

cnumber Bigint 12 Not null To store the

contact number

message Varchar 100 Not null To store the

Messages

30
Table name: Acceptor Primary
key: acceptorid
Description: This table store the acceptor information.

Field Name Data Type Size Constraints Description

acceptorid Int 10 Primary Key To store the acceptor id

acceptor Varchar 50 Not null To store the acceptor name

name

bloodgroup Varchar 12 Not null To store the blood group

gender Varchar 12 Not null To store the Gender

City Varchar 50 Not null To store the city

Hosdeatils Varchar 100 Not null To store the hospital name

& address

doctorname Varchar 50 Not null To store the doctor name

cname Varchar 50 Not null To store the contact name

cemail Varchar 50 Not null To store the contact email

cnumber Bigint 12 Not null To store the contact

number

31
message Varchar 100 Not null To store the Messages

38
 Table name: blood bank
Primary key: bankid

Description: This table store the blood bank information.

Field Name Data Type Size Constraints Description

bankid Int 10 Primary key To store the bank id

Bloodbankname Varchar 50 Not null To store the bank name

username Varchar 12 Not null To store the Username

password Varchar 12 Not null To store the Password

City Varchar 50 Not null To store the city

Hosdeatils Varchar 100 Not null To store the hospital name &
address

cname Varchar 50 Not null To store the contact name

cemail Varchar 50 Not null To store the contact email

cnumber Bigint 12 Not null To store the contact Number

message Varchar 100 Not null To store the Messages

33
Table name: stock details
Primary Key:- stockid
Description: This table store the stock information.

Field Name Data Type Size Constraints Description

stockid Int 12 Primary key To store stock id

bloodgroup Varchar 12 Not null To store blood group

quantity Int 20 Not null To store Quantity

Expairydate Date 12 Not null To store Expairydate

Table Name:- contact

Primary Key:- contactid
Description: This table store the contact information.

Field Name Data Type Size Constraints Description

cid Int 10 Primary key To store contact id

Name Varchar 50 Not null To store name

Email Varchar 50 Not null To store email

Phone Bigint 12 Not null To store phone number

Message Varchar 50 Not null To store message

33
 CHAPTER 10

PROJECT SNAPSHOTS

(i) home.php (Home page of the this project): -

34
(ii) about_us.php (About us page) :-

35
(iii) Why_donate_blood.php

36
(iv) donate_blood.php

37
(v) need_blood.php

38
(vi) contact_us.php

39
(vii) admin/login.php (Administrator’s Login Page): -

40
(viii) admin/dashboard.php

41
(ix )admin/add_donor.php

42
(x) admin/donor_list.php

43
44
(xi) admin/query.php

45
(xii) admin/pages.php: -

46
(xiii) admin/update_contact.php

47
(xiv) admin/change_password.php

48
Database Tables’ Snapshots:-

(xv) blood_donation Database Snapshot:-

49
(xvi) Admin Info Table

50
(xvii) “blood” Table (Contains Blood Groups Info.)

51
(xviii) “contact_info” Table:-

52
(xix) “contact_query” Table:-

53
(xx) “donor_details” Table:-

54
(xxi) “pages” Table:-

55
(xxii) “query_stat” Table:-

56
 ABBREVIATIONS

Abbreviation Definition / Full Form

PHP Hypertext Pre-processor / Personal Home Page

USD Use Case Diagram

DFD Data Flow Diagram

ERD Entity Relationship Diagram

CRM Customer Relationship Management

CMS Content Management System

SQL Structured Query Language

HTML Hyper Text Markup Language

ID Identity Document

ADMIN Administrator

SAD Systems Analysis and Design

OS Operating System

DBMS Database Management System

RDBMS Relational Database Management System

DBA Database administrator

RBC Red Blood Cells

57
WBC White Blood Cells

BDMS Blood Donation Management System

CHAPTER 11

CONCLUSION

In this project, “BLOOD BANK MANAGEMENT SYSTEM” we have tried to

computerize various processes of Blood Bank.

Blood Bank Management System is very flexible project and can be used in any branch of
BLOOD BANK for keeping record. In this php project we have tried to provide all the Blood
bank management system related record keeping facilities which helps to keep record and
employees who belongs to it.

The main focus of this project is to less in human efforts. The maintenance of the record is
made efficient, as all the records are stored in the SQL database.

It is user interactive and effective than the existing system. The flexibility of visual basic
helps to maintain the “BLOOD BANK MANAGEMENT SYSTEM” more efficiently.

Finally, I am thankful to all the people including my project partner who have supported me
in the development of this project.

58
 CHAPTER 12

APPENDIX

(i) home.php (HOME PAGE OF THE PROJECT):-

<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><meta

name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> <meta
name="description" content=""><meta name="author" content=""> <link rel="stylesheet"
href="https://maxcdn.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css"><script
src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.0/umd/popper.min.js">

</script> <script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.5.2/js/bootstrap.min.js">

</script><style></style></head><body><div class="header"><?php $active="home";

include('head.php'); ?></div> <?php include'ticker.php'; ?>

<div id="page-container" style="margin-top:50px; position: relative;min-height: 84vh;

"><text style="background-color:lightpin;width:0px;height:90px;color:red"><b><i>PLEASE
FOLLOW COVID-GUIDELINES & WEAR A MASK WHILE GOING
OUTSIDE.</i></b></text><div class="container"><div id="content-wrap"style="padding-
bottom:75px;"> <div id="demo" class="carousel slide" data-ride="carousel"> <!--
Indicators --> <ul class="carousel-indicators"> <li data-target="#demo" data-slide-to="0"
class="active"></li> <li data-target="#demo" data-slide-to="1"></li></ul> <!-- The
slideshow--> <div class="carousel-inner"><div class="carousel-item active"> <img
src="image\_107317099_blooddonor976.jpg" alt="image\_107317099_blooddonor976.jpg"
width="100%" height="500"></div> <div class="carousel-item">

59
<img src="image\Blood-facts_10-illustration-graphics__canteen.png" alt="image\Blood-
facts_10-illustration-graphics__canteen.png" width="100%" height="500"></div></div> <!--
Left and right controls --><a class="carousel-control-prev" href="#demo" data-
slide="prev"><span class="carousel-control-prev-icon"></span></a><a class="carousel-
control-next" href="#demo" data-slide="next"><span
class="carousel-control-next-icon"></span></a>

</div><br><h1 style="text-align:center;font-size:45px;">Welcome to BloodBank & Donor

Management System</h1><br><div class="row"><div class="col-lg-4 mb-4"><div
class="card"><h4 class="card-header card bg-info text-white" >The need for blood</h4>

<p class="card-body overflow-auto" style="padding-left:2%;height:120px;text-align:left;">

<?php include 'conn.php'; $sql=$sql= "select * from pages where page_type='needforblood'";

$result=mysqli_query($conn,$sql);

if(mysqli_num_rows($result)>0) { while($row = mysqli_fetch_assoc($result)) { echo

$row['page_data']; }}?> </p> </div></div><div class="col-lg-4 mb-4"><div
class="card"><h4 class="card-header card bg-info text-white">Blood Tips</h4>

<p class="card-body overflow-auto" style="padding-left:2%;height:120px;text-

align:left;"><?php include 'conn.php';

$sql=$sql= "select * from pages where page_type='bloodtips'"; $result=mysqli_query($conn,

$sql); if(mysqli_num_rows($result)>0) {

while($row = mysqli_fetch_assoc($result)) {echo $row['page_data'];} } ? </p></div></div>

<div class="col-lg-4 mb-4"><div class="card"><h4 class="card-header card bg-info text-

white" >Who you could Help</h4><p class="card-body overflow-auto" style="padding-
left:2%;height:120px;text-align:left;"><?php include 'conn.php';

$sql=$sql= "select * from pages where page_type='whoyouhelp'";

$result=mysqli_query($conn,$sql);

if(mysqli_num_rows($result)>0) {

60
while($row = mysqli_fetch_assoc($result)) { echo $row['page_data'];} }?></p>
</div></div></div><h2>Blood Donor Names</h2> <div class="row"> <?php
include 'conn.php'; $sql= "select * from donor_details join blood where
donor_details.donor_blood=blood.blood_id order by rand() limit 6";

$result=mysqli_query($conn,$sql); if(mysqli_num_rows($result)>0) { while($row =

mysqli_fetch_assoc($result)) { ?> <div class="col-lg-4 col-sm-6 portfolio-item" ><br>

<div class="card" style="width:300px"> <img class="card-img-top" src="image\

blood_drop_logo.jpg" alt="Card image" style="width:100%;height:300px">

<div class="card-body"> <h3 class="card-title"><?php echo $row['donor_name']; ?></h3>

<p class="card-text"> <b>Blood Group : </b> <b><?php echo $row['blood_group'];

?></b><br> <b>Mobile No. : </b> <?php echo $row['donor_number']; ?><br>

<b>Gender : </b><?php echo $row['donor_gender']; ?><br> <b>Age : </b> <?php echo

$row['donor_age']; ?><br> <b>Address : </b> <?php echo $row['donor_address']; ?><br>
</p> </div> </div> </div><?php }} ?></div><br><!-- /.row --><!-- Features Section -->

<div class="row"><div class="col-lg-6"><h2>BLOOD GROUPS</h2><p><?php include

'conn.php'; $sql=$sql= "select * from pages where page_type='bloodgroups'";

$result=mysqli_query($conn,$sql);

if(mysqli_num_rows($result)>0) {

while($row = mysqli_fetch_assoc($result)) {

echo $row['page_data']; } }

?></p> </div><div class="col-lg-6"><img class="img-fluid rounded" src="image\

blood_donationcover.jpeg" alt="" ></div> </div><!-- /.row --><hr> <!-- Call to
Action Section --><div class="row mb-4"><div class="col-md-8"><h4>UNIVERSAL
DONORS AND RECIPIENTS</h4><p> <?php include 'conn.php'; $sql=$sql= "select * from
pages where page_type='universal'"; $result=mysqli_query($conn,$sql);

if(mysqli_num_rows($result)>0) { while($row = mysqli_fetch_assoc($result)) {

61
echo $row['page_data']; } } ?></p> </div> <div class="col-md-4"> <a class="btn btn-lg btn-
secondary btn-block" href="donate_blood.php" style="align:center; background-
color:#7FB3D5;color:#273746 ">Become a Donor </a> </div> </div> </div>
</div><?php include('footer.php');?> </div> </body></html>

CHAPTER 13

REFERENCES

[1] Kevin Tatroe, Peter MacIntyre, Rasmus Lerdorf, Programming PHP: Creating Dynamic
Web Pages, O'Reilly Media, Inc., 2013. ISBN: 9781449365837

[2] Dave W. Mercer, Beginning Php 5, John Wiley & Sons, 2009. ISBN: 9788126505395

[3] Peter Moulding, PHP Black Book, Coriolis Group Books, 2001 ISBN : 9781588800534

[4] https://www.w3schools.com/php

[5] Atkinson Leon, PHP Core Programming, Beijing:Tsinghua university press, 2000

62