1.

INTRODUCTION

1.1 PROJECT OVERVIEW

The system provide online information of blood bank and administrators can also all
information about blood bank donor, patient request and blood requirements.Location Based
Mobile Blood Bank is basically a solution for primary and emergency blood transfusion
services.

It consists of an application which is present on the donorssmart –phone and on blood bank
machine.The main aim is to provide fast and efficient way to gainattention of potential donors
in the need of hour.

1.2 MODULE DESCRIPTION

ADMIN

The admin can manage the following modules from the admin control panel. The
system admin should enter the username and password to authenticate the admin panel. The
admin can view the details of blood group. The system admin can also manage the donor list.

DONOR

The user of the application can login into the account. The account was activated by
system admin. The module is also contains user login form and user data form. The user
module is used to know the how to become a donor, blood details and the contact information.

BLOODBANK

Theadmin can able to view the information about the donor. The admin can also manage the
request for the blood. The admin can also update the information about blood.

SYSTEM REPORT

The system report module is used to generate the system report from the admin panel.
The system report is generated as PDF format.
 2. SYSTEM CONFIGURATION

2.1 SOFTWARE SPECIFICATION

COMPONENTS MINIMUM REQUIREMENTS

OPERATING SYSTEM : Microsoft windows 8 and above

SERVER : XAMPP Apache

FRONT- END : PHP 5.5,HTML 5, CSS 3 and Flat

UI

BACK-END : MYSQL

2.2 HARDWARE CONFIGURATION

COMPONENTS MINIMUM REQUIREMENTS

PROCESSOR : Intel® Pentium® CPU P6200 @ 2-

13GHz

RAM : 2.00GB (1.74GB usable)

HARD DISK DRIVE : 320GB

CACHE MEMORY : 2MB

2.3 SOFTWARE DESCRIPTION

OVERVIEW OF THE FRONT – END:

PHP HYPERTEXT PROCESSOR is a Widely-used general-purpose scripting

language that is especially for development and can be embedded into HTML.

The PHP Hypertext Processor (PHP – yes, the first “P” in the acronym does indeed
stands for PHP!) Allows web developers to create dynamic content that interacts with
database. PHP application is normally on Linux server and conjunction with MYSQL
database. It provides those servers with functionality similar to that provide to the window
platform by Active server pages technology.

 PHP Stands for: HypertextPre-processor.

 PHP is server-side scriptinglanguage.
 PHP scriptingis executed on server.
 PHPsupportmanyDatabases(MYSQL,Informix,Oracle,andSybase,Solid,
POSTGRESQL,GenericODBC, etc.).
 PHP is freeto downloadand use.PHP is open source.PHP is platform independent
language.

PHP FILES

 PHP files maytext, HTMLTagsand scripts.

 PHP files arereturned tothe browseras plain HTML
 PHP files haveafile extension of “.PHP”, “.PHP3”, and “.PHTML”

ADVANTAGESOF PHP

 PHP runs on different platforms (Window, UNIX,Linux, etc.).

 PHP is compatiblewith almostallservers used today(Apache,IIs, etc.).
 PHP is Freeto DOWNLODE from the official PHP resources: www.php.net
 PHP is easyto learn andruns efficientlyon the server side.
HYPERTEXT MARKUP LANGUAGE (HTML 5)

HTML 5 features which are useful right now include:

WEB WORKERS

Certain web applications use heavy scripts to perform functions. Web Workers use
separate background threads for processing and it does not affect the performance of a web
page.

VIDEO

You can embed video without third-party proprietary plug-ins or codec. Video
becomes as easy as embedding an image.

CANVAS
This feature allows a web developer to render graphics on the fly. As with video,
there is no need for a plug in.

APPLICATION CACHES

Web pages will start storing more and more information locally on the visitor's
computer. It works like cookies, but where cookies are small, the new feature allows for
much larger files. Google Gears is an excellent example of this in action.

RELOCATION
Best known for use on mobile devices, relocation is coming with HTML5.

CSS 3

Cascading Style Sheet is a style sheet language used for describing the presentation
semantics (the look and formatting) of a document written in a mark-up language. Its most
common application is to style web pages written in HTML and XHTML.CSS3 is
completely backwards compatible, so you will not have to change the existing designs.
Browsers will always support CSS2.Many of the new CSS3 properties have been
implemented in modern browsers. Eventually, CSS 3 along with HTML5 are going to be the
future of the web.
 OVERVIEW OF THE BACK – END:

MYSQL

“MYSQL” the most popular „open source‟ SQL database management system is
developed, distributed and supported by „MYSQL „AB‟.‟MYSQL AB‟ is a commercial
company, founded by the MYSQL developers that build its business by providing services
around the „MYSQL‟ database management system.

To add, access, and process data store in a computer database, you need a database
management system such as „MYSQL „server. Since computer are very good at handling
large amount of data, database, management systems play a central role in computing, as
stand-alone utilities or as part of other application.

 MYSQL is Database server.

 MYSQL is ideal for both small and large application.

 MYSQL support standard SQL.

 MYSQL complies on a number of platforms.

 MYSQL is free to download and use.

ADVANTAGES OF MYSQL DATABASE SERVER

The “MYSQL”database server is very fast, reliable and easy to use. If that is what you are
looking for, you should give it a try. „MYSQL‟ server also has a practical set features developed in close
cooperation with users.

You can find a performance comparison of „MYSQL‟ server with other database managers on
their benchmark page. ‟MYSQL‟ was originally developed to handle large database much faster than
existing solution and has been successfully use in highly demanding production environments for several
year
 3. SYSTEM ANALYSIS

In any web development, bugs are inevitable. Let it be in any kind of product bugs
arise at any phase of development. One has to take a great care in the proper maintenance and
resolution of the bugs. In the Existing system, the bugs are not properly maintained and they
are simply relied on shared lists and email to monitor the bugs. In this type of system it
becomes difficult to track, a bug if a bug is over looked then it may because tremendous
errors in the next phase and can improve the cost of project whatever necessary effort spent
on the bug maintenance may not be worthy. Therefore, bug history has to be maintained
properly. In addition, there is no efficient search technique.

One has to search the whole database for the details of particular bug, which might have
occurred sometime earlier. It is both time consuming and error prone. In addition, it is very
difficult to share the bug among several users, as there is no proper maintenance of the bugs.
In order to have an efficient product bugs must be maintained properly and should be
resolved in time both to reduce time and money spent on the development.

3.1 EXISTING SYSTEM

 Manual procedure for organizing a Blood drive.

 Existing system is window Application.

 So much time consuming this application also one machine and one by one record 9-
stored.

 Single Blood bank information also no inquiry for directly Bloodbank.

3.2 PROPOSED SYSTEM

In proposed system, the application is improved as more dynamic. The application

security feature is improved and system user friendly is improved.

 User view all Blood bank information is locationwise.

 Donor easily donate the blood near Blood bankLocation.

 Patient easily request for blood near Blood banklocation.

 In proposed system, the admin can maintain the internal and external database

 In this system also supported inquiry form foruser.

6
 4. SYSTEM DESIGN

4.1 USE CASE DIAGRAM

7
4.2 ENTITY RELATIONSHIP DIAGRAM

An entity-relationship (ER) diagram is a specialized graphic that illustrates the

relationships between entities in a database. ER diagrams often use symbols to represent three
different types of information.

Boxes are commonly used to represent entities. Diamonds are normally used to represent
relationships and ovals are used to represent attributes.

An entity-relationship diagram (ERD) is a data modeling technique that graphically

illustrates an information system’s entities and the relationships between those entities.

An ERD is a conceptual and representational model of data used to represent the entity
framework infrastructure.

ER DIAGRAM SYMBOLS

ATTRIBUTE

ENTITY

RELATIONSHIP

Steps involved in creating an ERD include:

 Identifying and defining the entities

 Determining all interactions between the entities

 Analyzing the nature of interactions/determining the cardinality of the

relationships

 Creating the ERD.

8
 ER DIAGRAM

Username ID
 0 1
Admin

Password BloodGr
Blood group oup
Posting
Date

1 1
ID
Has
Donor
FullName

MobileNumber

EmailId

Gender
1

Age ID
Contact
Information Address
BloodGroup

EmailId
Address

ContactNo
Message

PostingDate

9
4.3 DATAFLOW DIAGRAM

A data-flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system. DFDs can also be used for the visualization of data
processing (structured design).On a DFD, data items flow from an external data source or an
internal data store to an internal data store or an external data sink, via an internal process.
The purpose of a DFD is:

 To show the scope and boundaries of a system.

 To show that the whole system has been considered.

 May be used as a communications tool between a systems analyst and any person who
plays a part in the system.

 To act as the starting point for redesigning a system.

The circlerepresents theprocess.It shows thepair ofthe

Processthat transforms input to output.

The arrow represents the graphical flow into or out of a

process.

Thestoreis used tomodel a collection ofdataat rest.

The terminator represents external entities with system

Communication.

10
 DATA FLOW DIAGRAM

LEVEL 0

LOGIN
ADMIN
Manage Blood Admin Login

LEVEL 1

Admin
Panel
ADMIN
Donor Details Donor Table

Blood Group Blood Group Table

Contact
Information

Contact
information Table

Manage
Contact us
query

11
LEVEL 2

LOGIN
USER
Login User Table

Become a
donor Donor Table

Blood group Table

Search Blood

Contact
Contact
information Table
Information

12
4.4 INPUT DESIGN

The Input design is the process of entering data to the system. The input design goal is to
enter to the computer as accurate as possible. Here inputs are designed effectively so that
error made by the operations are minimized. The inputs to the system have been designed in
such a way that manual forms and the inputs are co -ordinate where the data elements are
common to the source documents and to the input. The input is acceptable and
understandable by the users who are using it.

The quality of the system input determiners the quality for system output. Input
specification describes the manner in which data entered the system processing.

Input design is the process of converting user - oriented inputs to a computer – based
format input data are collected and organized into group of similar data. Once identified
appropriate input media are selected for processing.

The input design also determinate the user to interact sufficiently with the system.
Input design is a part of overall system design that requires special attention because it is the
common source for data processing error. The goal of designing input data is to make entry
easy and from errors.

13
Registration page:

Description:This page for user registration page

Registration validation page:

Description:This page for registration validation

14
Registration filling:

Description: This page for filling registration form

15
4.5 OUTPUT DESIGN

The output design was done so that result of processing could be communicate to the
users. The various output have designed in such a way that they represent the same format
that the office and management.

Computer output is the most important and direct source of information to the user
efficient intelligible output design should improve the system relationship with the user and
help in decision making. A major form of output is hardcopy form the printer.

Output requirements are designed during system analysis. A good starting point for
the output design is the data flow diagram (DFD). Human factors issues for design involves
addressing internal controls to ensure readability.

Search donor:

Description: This page for search donor

16
Donor list:

Description: This page for the donor list information

17
Manage blood group:

Description: This page for blood group list

18
4.6 DATABASE DESIGN

A database is an organized mechanism that has the capability of storing information

through which a user can retrieve stored information in an effective and efficient manner.

The database design is a two level process. In the first step, user requirements are
gathered together and a database is designed which will meet these requirements as clearly as
possible. This step is called Information Level Design and it is taken independent of any
individual DBMS.

In the second step, this Information level design is transferred into a design for the
specific DBMS that will be used to implement the system in question. A database design runs
parallel with the system design. The organization of the data in the database is aimed to
achieve the following two major objectives.

 Data Integrity

 Data independence

DATABASE NORMALIZATION

Normalization is the process of decomposing the attributes in an application, which

results in a set of tables with very simple structure. The purpose of normalization is to make
tables as simple as possible. Normalization is carried out in this system for the following
reasons.

 To structure the data so that there is no repetition of data.

 To permit simple retrieval of data in response to query and report request.

19
TABLE DESIGN

Table design is the process of the producing a detailed data model of a database. This
logical data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a data definition language, which can then
be used to create a database fully attributed data model contains detailed attributes for each.

The term database design can be used to describe many different parts of the design of
an overall database system. Principally, and most correctly, it can be thought of as the logical
design of the vase data structure used to store the data. In the relation model these are the
table and views. In an object database the entities and relationship map directly to object
classes and named relationships.

Table Name : Admin Table

Primary Key : Aid

Description : Admin login Details.

S.N NAME DATA SIZE CONSTRAINT DESCRIPTION

TYPE

1 Aid Int 5 Primary key Admin ID

2 Username Varchar 10 Not Null Username

3 Password Password 10 Not Null Password

20
Table Name : tbbloodgroup

Primary Key : id

Description : Blood Group details.

S.N NAME DATA SIZE CONSTRAINT DESCRIPTION

TYPE

1 Id Int 5 Primary Key ID

2 BloodGroup Varchar 20 Not Null Blood Group

3 PostingDate Timestamp 6 Not Null Time Stramp

21
Table Name : tbblooddonars
Description : Donor Details.

S.N NAME DATA SIZE CONSTRAINT DESCRIPTION

TYPE

1 Id Int 5 Not Null Donor ID

2 FullName Varchar 20 Not Null Name

3 MobileNumber Varchar 16 Not Null Mobile Number

4 Addreess Varchar 20 Not Null Address

5 Email Varchar 15 Unique Email ID

6 Gender Varchar 12 Not Null Gender

7 Age Varchar 10 Not Null Age

8 BloodGroup Varchar 5 Not Null Blood Group

9 Message Mediumtext 10 Not Null Message

10 PostingDate Date Not Null Posting Date

11 Status Varchar 3 Not Null Status

22
Table Name : tbcontactusinfo
Primary Key : id

Description : Contact Details.

S.N NAME DATA SIZE CONSTRAINT DESCRIPTION

TYPE

1 Id Int 5 Primary Key ID

2 Address Tinytext 20 Not Null Address

3 EmailId Varchar 225 Not Null Email Id

4 ContactNo Char 11 Not Null Contact Number

Table Name : tbcontactusquery

Primary Key : id

Description : Contact query Details.

S.N NAME DATA SIZE CONSTRAINT DESCRIPTION

TYPE

1 Id Int 5 Primary Key ID

2 Email Varchar 15 Not Null Email ID

3 Name Varchar 25 Not Null Name

4 ContactNumber Varchar 11 Not Null Contact Number

5 Message Mediumtext 10 Not Null Message

6 PostingDate Date Not Null Posting Date

7 Status Varchar 3 Not Null Status

23
 5. SYSTEM TESTING AND IMPLEMENTATION

5.1 SYSTEM TESTING

It is the stage of implementation, which ensures that system works accurately and
effectively before the live operation commences. It is a confirmation that all are correct and
opportunity to show the users that the system must be tested with the text data and show that
the system will operate successfully and produce expected results under expected conditions.

Web Application testing is a crucial element of applications quality assurance and

represents the unlimited review of specification, design and coding. Testing represents an
interesting anomaly for the software.

The testing phase is responsible for ensuring that the system performs the way that the
detailed design documentation specifies. Testing involves testing of developed system using
various test data. Preparation of test data plays a vital role in system testing. After preparing
the test data, the system under study was tested using those test data. During this stage, the
errors are detected and corrected.

Before implementation, the proposed system must be tested with raw data to ensure
that the modules of the system work correctly and satisfactorily. The system must be tested
with valid data to achieve its objective.

Testing is vital to the parts of the system are correct; the goal will be successfully
achieved. Inadequate testing or non-testing leads to errors that may not appear until this
months later.

This creates two problems:

 This time lag between the cause and appearance of the problem.
 The effort of system errors on files and records within the system. A small system
error can conceivably exploded into much larger problem. Effectively early in the
process translates directly into long term cost savings from a reduced number of
errors.

24
BLACK BOX TESTING

Functional or Black box testing is from where the tests are derived from the program
specification. Interface testing where the tests are derived from the specifications plus
knowledge of its internal interfaces. This type of testing is particularly important for object
oriented system.

Project Aspect:

In this project the system is a black box whose behavior can only be determined by
studying its inputs and the related outputs. The testing process is derived from the program
specification.

 By the use of these techniques the missing functions are identified and placed in their
positions.
 The errors in the interfaces were identified and corrected.
 This technique was also used to identify the initialization and determination errors and
correct them.

BLACK BOX TEST CASE

Table Name : Admin table

TEST EVENT RESULT INPUT OUTPUT

ID

T1 Admin Pass Details Entry Saved

Entry

T2 Login Pass Login=”admin” Ok

Password=”$$$$”

25
Table Name : Donor Details

TEST EVENT RESULT INPUT OUTPUT

ID

T1 Add Pass Name=”Deepak” Successfully

added
DOB=”20/03/1997”

Address=”112/10 East Street

Coimbatore”

MobileNo=”8344436231”

Email=”[email protected]”

Gender=”Male”

Age=”23”

Blood Group=”o+”

Message=”Available”

T2 Save Pass Name=”Deepak” Successfully

saved
DOB=”20/03/1997”

Address=”112/10 East Street

Coimbatore”

MobileNo=”8344436231”

Email=”[email protected]”

Gender=”Male”

Age=”23”

Blood Group=”o+”

Message=”Available”

26
Table Name : Contact query Details

TEST EVENT RESULT INPUT OUTPUT

ID

T1 Add Pass Email=”[email protected]” Successfully added

Name=”Naveen”

Contact No=”8344436231”

Message=” Not Available Till

Jan”

T2 Save Pass Email=”[email protected]” Successfully saved

Name=”Naveen”

Contact No=”8344436231”

Message=” Not Available Till

Jan”

Email=” ” Successfully refersh

T3 Refresh Pass Name=” ”

Contact No=” ”

Message=” ”

27
WHITE BOX TESTING

Also known as glass box, structural, clear box and open box testing. Software testing
techniques whereby explicit knowledge of the internal working of the item being tested are
used to select the test data. Unlike black box testing, white box testing uses specific
knowledge of programming code to examine outputs.

Project Aspect:

The test is accurate only if the tester knows what the program is supposed to do. He or she
can then see if the program diverges from its intended goal. White box testing does not
account for errors caused by omission, and all visible code must also be readable. For a
complete software examination, both white box and black box tests are required.

 By using this technique it was tested that all the individual logical paths were
executed at least once.
 All logical decision were tested on both their true and false sides.
 All the loops were tested with the data in between the ranges and especially at the
boundary values.

WHITE BOX TEST CASE

TEST ID EVENT LOGIC RESULT

Test1 Login Database Pass

compare

Admin Database Pass

compare

Test2 Donor Details Entry Pass

Test3 Contact Query Details Entry Pass

28
UNIT TESTING

Unit tests perform basic test at component level and test a specific business process,
application, and /or system configuration. Unit tests ensure that each path of a business
process performs accurately to the documented specifications, functionality and contains
clearly defined inputs and expected results.

VALIDATION TESTING

Validation succeeds when the developed system functions as per the requirement of
the customer. Application validation is achieved through a series of black box that
demonstrate the conformity with the requirements. Deviations or errors in this steps are
corrected.

OUTPUT TESTING

Various outputs has been generated by the system. The system generated output and
the desk-calculated values have been compared. All the output is perfect as the company
desires. It begins with the low volumes of transactions based on live tone. The volume is
increased until the maximum level for each transaction type is reached. The total system is
also tested for recovery and fall back, after various major failures to ensure that no data are
lost during the emergency time.

INTEGRATION TESTING

Integration tests are done to test integrated application components were individually
satisfactory, as shown by successful unit testing; the combination of components is correct
and consistent.

5.2 SYSTEM IMPLEMENTATION

System implementation is the stage of the project when the theoretical design is
turned into a working system. If the implementation stage is not correctly planned and
controlled, it can be choice. The following are the main stages in the implementation:

 Planning
 Training
 Maintenance

29
PLANNING

Planning plays an important role in the implementation. The planning should face any
practical problems of controlling various activities of people out their own data processing
department.

TRAINING

Successful implementation needs trained computer staff. So some staff can teach them
about the computer implementation, which only then becomes a well-designed system.

MAINTENANCE

Maintenance involves recovery on crash such as the backups and the end user should
be given only executable format of the system.

30
 6. SCOPE FOR FUTURE ENHANCEMENT

 We can give more advance software for blood bank management system
including more facilities.

 We will host the platform on online servers to make it accessible worldwide.

 Integrate multiple load balancers to distribute the load of the system.

 Create the master and slave database structure to reduce the overload of the
database queries.

 Implement the backup mechanism for taking backup of codebase and database
on regular basis on different servers.

31
 7. CONCLUSION

Our project is only a humble venture to satisfy the need to manage their project work.
Several users friendly coding have also adopted. This package is true to be a powerful
package in satisfying all the requirement of the school. The objective of the software
planning is to provide a frame work that enables the manager to make responsible estimates
made within a limited frame at the beginning of the software project and should be updated
frequently as the project progresses.

32
 8. BIBLIOGRAPHY

Vikas Kulshreshtha, Sharad Maheshwari. (2 011).”Blood Bank Management Information

System in India”, International Journal of Engineering, 1,2, 260-263.
Rational Unified Process, Best Practices for Software Development Teams. (2012). Core
Workflows Retrieved from www.ibm.com/developerworks/rational/.../1251_bestpractices
Noushin Ashrafi, & Hessam Ashrafi. (2008). Object Oriented Systems Analysis and Design,
Pearson Higher Ed USA. Lions Blood Bank & Research Foundation. (2012). Retrieved
from http://www.lionsbloodbank.net/
Blood Bank India. (2012). Retrieved from http://www.bloodbankindia.net

33
 9. APPENDICES

a) Screen shots

Home page

Admin login page

34
Donor registration

Search donor list

35
Donor list

Manage blood group

36
b)Sample coding

Index.php:

<?php

error_reporting(0);

include('includes/config.php');

?>

<!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="">

<title>BloodBank& Donor Management System</title>

<link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">

<link href="vendor/font-awesome/css/font-awesome.min.css" rel="stylesheet"

type="text/css">

<link href="css/modern-business.css" rel="stylesheet">

37
<style>

.navbar-toggler {

z-index: 1;

@media (max-width: 576px) {

nav> .container {

width: 100%;

.carousel-item.active,

.carousel-item-next,

.carousel-item-prev {

display: block;

</style>

</head>

<body>

<!-- Navigation -->

<?php include('includes/header.php');?>

38
<?php include('includes/slider.php');?>

<!-- Page Content -->

<div class="container">

<h1 class="my-4">Welcome to BloodBank& Donor Management System</h1>

<!-- Marketing Icons Section -->

<div class="row">

<div class="col-lg-4 mb-4">

<div class="card">

<h4 class="card-header">The need for blood</h4>

<p class="card-text" style="padding-left:2%">Loremipsum dolor sit amet,

consecteturadipiscingelit, sed do eiusmodtemporincididuntutlabore et dolore magna aliqua.
</p>

</div>

</div>

<div class="col-lg-4 mb-4">

<div class="card">

<h4 class="card-header">Blood Tips</h4>

39
<p class="card-text" style="padding-left:2%">Loremipsum dolor sit amet,
consecteturadipiscingelit, sed do eiusmodtemporincididuntutlabore et dolore magna aliqua.
</p>

</div>

</div>

<div class="col-lg-4 mb-4">

<div class="card">

<h4 class="card-header">Who you could Help</h4>

<p class="card-text" style="padding-left:2%">Loremipsum dolor sit amet,

consecteturadipiscingelit, sed do eiusmodtemporincididuntutlabore et dolore magna aliqua.
</p>

</div>

</div>

</div>

<!-- /.row -->

<!-- Portfolio Section -->

<h2>Some of the Donar</h2>

<div class="row">

<?php

$status=1;

$sql = "SELECT * from tblblooddonars where status=:status order by rand() limit 6";

$query = $dbh ->prepare($sql);

$query->bindParam(':status',$status,PDO::PARAM_STR);

40
$query->execute();

$results=$query->fetchAll(PDO::FETCH_OBJ);

$cnt=1;

if($query->rowCount() > 0)

foreach($results as $result)

{ ?>

<div class="col-lg-4 col-sm-6 portfolio-item">

<div class="card h-100">

<a href="#"><img class="card-img-top img-fluid" src="images/blood-donor.jpg" alt=""

></a>

<div class="card-block">

<h4 class="card-title"><a href="#"><?php echo htmlentities($result-

>FullName);?></a></h4>

<p class="card-text"><b> Gender :</b><?php echo htmlentities($result->Gender);?></p>

<p class="card-text"><b>Blood Group :</b><?php echo htmlentities($result-

>BloodGroup);?></p>

</div>

</div>

</div>

<?php }} ?>

41
</div>

<!-- /.row -->

<!-- Features Section -->

<div class="row">

<div class="col-lg-6">

<h2>BLOOD GROUPS</h2>

<p> blood group of any human being will mainly fall in any one of the following
groups.</p>

<ul>

<li>A positive or A negative</li>

<li>B positive or B negative</li>

<li>O positive or O negative</li>

<li>AB positive or AB negative.</li>

</ul>

<p>A healthy diet helps ensure a successful blood donation, and also makes you feel better!
Check out the following recommended foods to eat prior to your donation.</p>

</div>

42
<div class="col-lg-6">

<img class="img-fluid rounded" src="images/blood-donor (1).jpg" 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>

The most common blood type is O, followed by type A.

Type O individuals are often called "universal donors" since their blood can be transfused
into persons with any blood type. Those with type AB blood are called "universal recipients"
because they can receive blood of any type.</p>

</div>

<div class="col-md-4">

<a class="btnbtn-lgbtn-secondary btn-block" href="become-donar.php">Become a

Donar</a>

</div>

</div>

</div>

<!-- /.container -->

<!-- Footer -->

43
<?php include('includes/footer.php');?>

<!-- Bootstrap core JavaScript -->

<scriptsrc="vendor/jquery/jquery.min.js"></script>

<scriptsrc="vendor/tether/tether.min.js"></script>

<scriptsrc="vendor/bootstrap/js/bootstrap.min.js"></script>

</body>

</html>

44