VISVESVARAYA TECHNOLOGICAL UNIVERSITY

BELAGAVI-590 018, KARNATAKA.

DBMS MINI PROJECT REPORT

ON
”

Submitted in the partial fulfillment of requirements for the

5th SEM DBMS MINI PROJECT (18CSL58)

PROJECT ASSOCIATES

MAYUR A KASAL 4BD20CS054

SAGAR K R 4BD20CS082

PROJECT GUIDES

Dr. Gururaj T Ph.D. Prof. Chandrashekar M V M.Tech.

Associate Professor Assistant Professor
Department of CS&E Department of CS&E

2022-2023
Bapuji Institute of Engineering & Technology
Department of Computer Science and Engineering
Davanagere - 577004
 Bapuji Institute of Engineering and Technology
Davangere -577004

Department of Computer Science and Engineering

CERTIFICATE

This is to certify that MAYUR A KASAL and SAGAR K R bearing USN 4BD20CS054 and
4BD20CS082 respectively of Computer Science and Engineering department have satisfactorily
submitted the mini project report entitled “BLOOD BANK MANAGEMENT SYSTEM” for DBMS
LABORATORY WITH MINI PROJECT (18CSL58). The report of the mini project has been
approved as it satisfies the academic requirements in respect of mini project work prescribed for the
year 2022-2023.

Dr. Gururaj T Ph.D. Prof. Chandrashekar M V M.Tech.

Associate Professor Assistant Professor
Department of CS&E Department of CS&E

Guide Co-Guide

Dr. Nirmala C R Ph.D.,

Prof.& Head of Deparment, CS&E.
B.I.E.T, Davanagere.

Date: Signature of Examiners:

Place: Davanagere (1)

(2)
 ACKNOWLEDGEMENT

Salutations to our beloved and highly esteemed institute, “BAPUJI INSTITUTE OF

ENGINEERING AND TECHNOLOGY” for having well qualified staff and lab furnished
with necessary equipment’s.

We express our sincere thanks to our resourceful guides Dr. Gururaj T and Prof.
Chandrashekar M V for giving us constant encouragement, support and valuable guidance
throughout the course of project without whose guidance this project would not have been
achieved.

We express whole hearted gratitude to Dr. Nirmala C R, H.O.D of Computer Science &
Engineering Department. We wish to thank her for making our task easy by providing her
valuable help and encouragement.

We also express our whole hearted gratitude to our principal, Dr. H B Aravind for his moral
support and encouragement.

We would like to extend our gratitude to all staff of Computer Science and Engineering
Department for their help and support. We have benefited a lot from the feedback, suggestions
given by them.

We would like to extend our gratitude to all my family members and friends especially for their
advice and moral support.

MAYUR A KASAL
4BD20CS054

SAGAR K R
4BD20CS082
 VISION AND MISSION OF THE INSTITUTE

Vision
To be centre of excellence recognized nationally and internationally, in distinctive areas of
engineering education and research, based on a culture of innovation and invention.

Mission
BIET contributes to the growth and development of its students by imparting a board-
based engineering education and empowering them to be successful in their chosen field
by inculcating in them positive approach, leadership qualities and ethical values.

VISION AND MISSION OF THE DEPARTMENT

Vision
To be a centre of excellence by imparting state-of-the-art technology in the field of
Computer Science and Engineering, thereby enabling students to excel professionally
and be ethical.”

Mission
• Adapting best class teaching and learning techniques that cultivates questioning and
reasoning culture among the students.

• Creating collaborative learning environment that ignites the critical thinking in

student and leading to the Innovation.

• Establishing industry institute relationship to bridge the skill gap and make then

industry ready and relevant.

• Mentoring students to be socially responsible by inculcating ethical and moral

values.
1.Program Educational Outcomes (PEOs):

PEO1 To apply skills acquired in the discipline of Computer Science and Engineering for
solving societal and industrial problems with apt technology intervention

PEO2 To continue their career in industry/academia or to pursue higher studies and

research.
PEO3 To became successful entrepreneurs, innovators to design and develop software
products and services that meets the societal, technical and business challenges.
PEO4 To work in the diversified environment by acquiring leadership qualities with
effective communication skills accompanied by professional and ethical values.

2. Program Specific Outcomes (PSOs):

Analyze and develop solutions for problems that are complex in nature by
PSO1 applying the knowledge acquired from the core subject of this program

To develop secure, scalable, resilient and disturbed applications for industry and
PSO2 societal requirements
To learn and apply the concepts and construct of emerging technologies like
PSO3 Artificial Intelligence, Machine learning, Deep learning, Big data analytics, IOT,
Cloud computing etc. for any real time problems.

3. Course Outcomes(COs):

CO1 Demonstrate the working of different concepts of DBMS

CO2 Implement ER-schema mapping rules

CO3 Create, Update and query on the database

CO4 Implement trigger and stored procedure on database

CO5 Develop and analyse the project for an application

 ABSTRACT

This project aims to develop a Blood Bank Management System. A Blood Bank Management System
can be used in any clinic, hospital, labs or any emergency situation which requires blood units for
survival. Our system can be used to find required type of blood in emergency situations from either
blood bank or even blood donors. Current system uses a grapevine communication for finding blood
in cases of emergency, may it be by a donor or blood bank. The intentions of proposing such a system
is to abolish the panic caused during an emergency due to unavailability of blood.
CONTENTS
CHAPTERS Page No

CHAPTER 1: INTRODUCTION

1.1 Introduction 1

1.2 DBMS 1-3

1.3 PHP 4

1.4 Problem Statement 4

1.5 Obiectives 4

1.6 Existing System 5

1.7 Proposed System 5

CHAPTER 2: - HARDWARE AND SOFTWARE REQUIREMENTS

2.1 Hardware Requirement 6

2.2 Software Requirement 6

CHAPTER 3- DESIGNS

3.1 ER Diagram 7

3.2 Description 8

3.3 Seven Steps Eor ER To Schema Conversion 9-11

3.4 Schema Diagram 12

3.5 Database Description 13-15

CHAPTER 4:- IMPLEMENTATION CODE 16-19

CHAPTER 5: SNAPSHOTS 20-26

CONCLUSION 27

REFERENCES 28
LIST OF FIGURES :

Sl.n Fig.no Description Page.

o no
1. 3.1 Entity relationship diagram 7

2. 3.4 Schema diagram 12

3. 5.1 User login page 20

4. 5.2 Home Page 20

5. 5.3 Add Person page 21

6. 5.4 Search Person Page 22

7. 5.5 Donation page 22

8. 5.6 Receive page 23

9. 5.7 Check Stock Page 23

10. 5.8 Donation History Page 24

11. 5.9 Receive History page 25

12. 5.10 Add user page 26

LIST OF ACRONYMS

Sl.n Acronyms Expansion

o
1. DBMS Database Management
System
2. SQL Structure Query Language

3. PHP Hypertext Preprocessor

4. HTML Hypertext Markup Language

5. CSS Cascading Style Sheet

6. ER Entity Relationship Diagram

Diagram
LIST OF TABLES

Sl.no Table.no Description Page.

no
1. 3.5.1 Description of project database 13

2. 3.5.2 Donation table 13

3. 3.5.3 Person table 14

4. 3.5.4 Receive table 14

5. 3.5.5 Stock table 15

6. 3.5.6 User table 15

 BLOOD_BANK MANAGEMENT SYSTEM

CHAPTER 1
INTRODUCTION

1.1 INTRODUCTION

Blood banks collect, store and provide collected blood to the patients who are in need of blood.
The people who donate blood are called ‘donors’. The banks then group the blood which they
receive according to the blood groups. They also make sure that the blood is not contaminated.
The main mission of the blood bank is to provide the blood to the hospitals and health care
systems which saves the patient’s life. No hospital can maintain the health care system without
pure and adequate blood.

The major concern each blood bank has is to monitor the quality of the blood and monitor the
people who donates the blood, that is ‘donors’. But this a tough job. The existing system will not
satisfy the need of maintaining quality blood and keep track of donors. To overcome all these
limitations we introduced a new system called ‘Blood Donation Management System’.

The ‘Blood Bank Management System’ allows us to keep track of quality of blood and also keeps
track of available blood when requested by the acceptor. The existing systems are Manual
systems which are time consuming and not so effective. ‘Blood Bank Management system’
automates the distribution of blood. This database consists of thousands of records of each blood
bank.

By using this system searching the available blood becomes easy and saves lot of time than the
manual system. It will hoard, operate, recover and analyse information concerned with the
administrative and inventory management within a blood bank. This system is developed in a
manner that it is manageable, time effective, cost effective, flexible and much man power is not
required

CS&E Dept ,B.I.E.T, Davanagere 1

 BLOOD_BANK MANAGEMENT SYSTEM

1.2 DBMS (DATABASE MANAGEMENT SYSTEM)

A database management system (DBMS) refers to the technology for creating and managing
databases. DBMS is a software tool to organize, create, retrieve, update and manage data in a
database. Databases and database technology have a major impact on the growing use of
computers. It is fair to say that databases play a critical role in almost all areas where computers
are used including business, electronic, commerce, engineering, medicine, genetics, law,
education, and library science.

1.2.1 Causes to use DBMS

To develop software applications in less time.

Data independence and efficient use of data.

For uniform data administration.

For data integrity and security.

For concurrent access to data, and data recovery from crashes.

To use user-friendly declarative query language.

1.2.2 Uses of DBMS

Airlines: reservations, schedules, etc.

Telecom: calls made customer details, network usage, etc.

Universities: registration, results, grades, etc.

Sales: products, purchases, customers, etc.

Banking: all transactions etc.

CS&E Dept ,B.I.E.T, Davanagere

2
 BLOOD_BANK MANAGEMENT SYSTEM

1.2.3 Advantage of DBMS

A DBMS manage data and has many advantages. These are:

Data independence: Application programs should be as free or independent as possible from

details of data representation and storage. DBMS can supply an abstract view of the data for
insulating application code from such facts.

Efficient data access: DBMS utilizes a mixture of sophisticated concepts and techniques for

storing and retrieving data competently, and this feature becomes important in cases where the
data is stored on external storage devices.

Data integrity and security: If data is accessed through the DBMS, the DBMS can enforce

integrity constraints on the data.

Data administration: When several users share the data, integrating the administration of data

can offer major improvements. Experienced professionals understand the nature of the data being
managed and can be responsible for organizing the data representation to reduce redundancy and
make the data to retrieve efficiently.

1.2.4 Components of DBMS

Users: Users may be of any kind such as DB administrator, System developer or database users.

Database application: Database application may be Departmental, Personal, organization's and

/ or Internal.

DBMS: Software that allows users to create and manipulate database access.

Database: Collection of logical data as a single unit.

PHP (Hypertext Pre-processor) is an open-source HTML-embedded server-side scripting

language which is used to develop dynamic and interactive web applications and also used as a
general-purpose programming language.

CS&E Dept ,B.I.E.T, Davanagere

3
 BLOOD_BANK MANAGEMENT SYSTEM

1.3 PHP (HYPERTEXT PREPROCESSOR)

PHP is the most popular and widely used server side scripting language for web development.
It is used to make the Dynamic pages in websites. Rasmus Lerdorf was the creator of PHP in
1995. PHP codes are embedding in HTML source codes for making the page dynamic. PHP
can deal with most of the requirements in web development like Database, File handling, String
operations, Arrays, Graphics, File Uploads, Data processing etc. PHP can be used in any
operating system with a web server Supports PHP. Apache web server is one of the popular
web server dealing with PHP + MySQL. Moreover PHP is absolutely free to use.

1.4 PROBLEM STATEMENT

The problem definition of the system is to launch an online interaction medium for the blood
donation management. The main aim of this project is to help the people who needs blood in
emergency and to associate some donors who are willing to donate their blood to needy people
and save their lives.

1.5 OBJECTIVES

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

• A blood bank collects, separates, tests and stores blood until a patient needs it. If you've
donated blood before, you've been part of the blood banking process

CS&E Dept ,B.I.E.T, Davanagere 4

 BLOOD_BANK MANAGEMENT SYSTEM

1.6 EXISTING SYSTEMS

Despite the immense technological advancement, blood bank systems use manual date for
storing valuable data. Even it is time consuming to retrieve any data if required. Consequently,
one of the major issues in blood bank systems, as talked in many articles and research papers
it has lack of data security. People doubt whether their personal information and medical
records are safely secured or not. Therefore our project aims to develop blood bank
management system along with database security and encryption.

1.7 PROPOSED SYSTEM

Admin/User has to login first. All the personal details of the person is recorded and stored in the
database. Admin can search for any personal details. He can retrieve any donation/receive
history. They can even have the complete information about the stock present in the blood bank.
Apart from this, we will be using concepts of database encryption to make sure that the person’s
information is kept secure and confidential. This will help us keep their donation and receive
records protected from any threats from individuals with potentially malicious intentions or
unforeseen hazards to the security of the data.

CS&E Dept ,B.I.E.T, Davanagere 5

 BLOOD_BANK MANAGEMENT SYSTEM

CHAPTER 2

REQIUREMENT SPECIFICATION

2.1 Hardware requirements:

The hardware required for the development of this project is :

• Processor : Intel dual core or above

• Processor speed : 1.0 GHz or above

• RAM : 1 GB RAM or above

• Hard Disk : 2GB hard disk or above

2.2 Software requirements:

The software required for the development of this project is:

• Language : PHP

• Database : My SQL

• User Interface Design : BootStrap, JavaScript

• Web Browser : Mozilla, Google Chrome,

Opera

• Server : XAMPP Server

• Software : APACHE

CS&E Dept ,B.I.E.T, Davanagere 6

 BLOOD_BANK MANAGEMENT SYSTEM

CHAPTER 3
DESIGNS

3.1 ENTITY - RELATIONSHIP DIAGRAM:

Fig3.1: Entity Relationship Diagram of Blood Bank Management System

CS&E Dept ,B.I.E.T, Davanagere

7
 BLOOD_BANK MANAGEMENT SYSTEM

3.2 DESCRIPTION :
The ER Model figure shows the proposed system. It defines the conceptual view of the
database. It works around real-world entities and the associations among them .At view level,
the ER model is considered a good option for designing databases .So , let’s see each entity
* User:

The entity stores the information about admin to register with the user ID and password.
The attributes are username,usr_password

* Person:
This entity is used to store all the personal details of the donor or receiver.
The attributes are p_id , p_name ,p_address ,p_phone,p_bloodgroup, p_gender, p_dob,
p_medissue.

* Donation:
This entity is used to record the date and time along with quantity of blood donted by a
person. Personal details is accessed using person ID.
The attributes are p_id, d_date, d_time, quantity.

* Receive:
In this entity date and time, quantity of blood received along with hospital details are
recorded.
The attributes are r_date, p_id, quantity, r_hospital,

* Stock:
Here we can check availability of each blood group blood.
The attributes are s_blood_group, quantity.

8
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

3.3 SEVEN STEPS FOR ER TO SCHEMA CONVERSION

Step 1: Mapping of Regular Entity Types.

For each regular (strong) entity type E in the ER schema, create a relation R that includes all
the simple attributes of E. Include only the simple component attributes of a composite
attribute. Choose one of the key attributes of E as the primary key for R. If the chosen key of
E is a composite, then the set of simple attributes that form it will together form the primary
key of R. If multiple keys were identified for E during the conceptual design, the information
describing the attributes that form each additional key is kept in order to specify secondary
(unique) keys of relation R. Knowledge about keys is also kept for indexing purposes and other
types of analyses.

Step 2: Mapping of Weak Entity Types.

For each weak entity type W in the ER schema with owner entity type E, create a relation
R and include all simple attributes (or simple components of composite attributes) of was
attributes of R. In addition, include as foreign key attributes of R, the primary key attribute(s)
of the relation(s) that correspond to the owner entity type(s); this takes care of mapping the
identifying relationship type of W. The primary key of R is the combination of the primary
key(s) of the owner(s) and the partial key of the weak entity type W, if any. If there is a weak
entity type E2 whose owner is also a weak entity type E1, then E1 should be mapped before E2
to determine its primary key first.

Step 3: Mapping of Binary 1:1 Relationship Types.

For each binary 1:1 relationship type R in the ER schema, identify the relations S and T
that correspond to the entity types participating in R. There are three possible approaches:
1. The foreign key approach.
2. The merged relationship approach, and
The first approach is the most useful and should be followed unless special conditions exist, as
we discuss below.

9
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

1. Foreign key approach:

Choose one of the relations—S, say—and include as a foreign key in S the primary key of T.
It is better to choose an entity type with total participation in R in the role of S. Include all the
simple attributes (or simple components of composite attributes) of the 1:1 relationship type R
as attributes of S.

2. Merged relation approach:

An alternative mapping of a 1:1 relationship type is to merge the two entity types and the
relationship into a single relation. This is possible when both participations are total, as this
would indicate that the two tables will have the exact same number of tuples at all times.

3. Cross-reference or relationship relation approach:

The third option is to set up a third relation R for the purpose of cross-referencing the primary
keys of the two relations S and T representing the entity types. As we will see, this approach is
required for binary M:N relationships. The relation R is called a relationship relation (or
sometimes a lookup table), because each tuple in R represents a relationship instance that
relates one tuple from S with one tuple from T. The relation R will include the primary key
attributes of S and T as foreign keys to S and T. The primary key of R will be one of the two
foreign keys, and the other foreign key will be a unique key of R. The drawback is having an
extra relation, and requiring an extra join operation when combining related tuples from the
tables.

Step 4: Mapping of Binary 1:N Relationship Types.

For each regular binary 1:N relationship type R, identify the relation S that represents the
participating entity type at the N-side of the relationship type. Include as foreign key in S the
primary key of the relation T that represents the other entity type participating in R; we do this
because each entity instance on the N-side is related to at most one entity instance on the 1-side
of the relationship type. Include any simple attributes (or simple components of composite
attributes) of the 1:N relationship type as attributes of S.

10
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Step 5: Mapping of Binary M:N Relationship Types.

For each binary M:N relationship type R, create a new relation S to represent R. Include as
foreign key attributes in S the primary keys of the relations that represent the participating
entity types; their combination will form the primary key of S. Also include any simple
attributes of the M:N relationship type (or simple components of composite attributes) as
attributes of S.
Notice that we cannot represent an M:N relationship type by a single foreign key attribute in
one of the participating relations (as we did for 1:1 or 1:N relationship types) because of the
M:N cardinality ratio; we must create a separate relationship relation S.

Step 6: Mapping of Multivalued Attributes.

For each multivalued attribute A, create a new relation R. This relation R will include an
attribute corresponding to A, plus the primary key attribute K—as a foreign key in R—of the
relation that represents the entity type or relationship type that has A as a multivalued attribute.
The primary key of R is the combination of A and K. If the multivalued attribute is composite,
we include its simple components.

Step 7: Mapping of N-array Relationship Types.

For each n-array relationship type R, where n > 2, create a new relation S to represent R. Include
as foreign key attributes in S the primary keys of the relations that represent the participating
entity types. Also include any simple attributes of the n-array relationship type (or simple
components of composite attributes) as attributes of S. The primary key of S is usually a
combination of all the foreign keys that reference the relations representing the participating
entity types. However, if the cardinality constraints on any of the entity types E participating
in R is 1, then the primary key of S should not include the foreign key attribute that references
the relation E ‘corresponding to E.

11
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

3.4 SCHEMA DIAGRAM

Fig 3.4 : Schema Diagram For Blood Bank Management System.

12
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

3.5 DATABASE DESCRIPTION :

Table 3.5.1: Description of Database Blood_Bank

Table 3.5.2 : Table description for Donation

13
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Table 3.5.3 : Table description for Person

Table 3.5.4 : Table description of receive.

14
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Table 3.5.5:Table description of Stock.

Table 3.5.6 : Table description of User.

15
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

CHAPTER 4
IMPLEMENTATION CODE

4.1 CONNECTION CODE FOR FRONT END TO BACK END

<?php
$host = "localhost";
$user = "root";
$password = '';
$db_name = "blood_bank";

$con = mysqli_connect($host, $user, $password, $db_name);

if(mysqli_connect_errno()) {
die("Failed to connect with MySQL: ". mysqli_connect_error());
}
?>

4.2 DDL STATEMENTS

Create commands:

CREATE DATABASE IF NOT EXISTS `blood_bank` DEFAULT CHARACTER SET

utf8mb4 COLLATE utf8mb4_general_ci;
USE `blood_bank`;

CREATE TABLE `donation` (

`p_id` int(10) NOT NULL,
`d_date` date NOT NULL,
`d_time` time NOT NULL,
`d_quantity` int(1) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

CREATE TABLE `person` (

`p_id` int(10) NOT NULL,
`p_name` varchar(25) NOT NULL,
`p_phone` char(10) NOT NULL,
`p_dob` date NOT NULL,
`p_address` varchar(100) DEFAULT NULL,
`p_gender` char(1) NOT NULL,
`p_blood_group` varchar(3) NOT NULL,
`p_med_issues` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

16
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

CREATE TABLE `receive` (

`p_id` int(10) NOT NULL,
`r_date` date NOT NULL,
`r_time` time NOT NULL,
`r_quantity` int(1) NOT NULL,
`r_hospital` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

CREATE TABLE `stock` (

`s_blood_group` varchar(3) NOT NULL,
`s_quantity` int(5) NOT NULL DEFAULT 0
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

CREATE TABLE `user` (

`username` varchar(10) NOT NULL,
`password` varchar(16) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Insert Commands:
INSERT INTO `stock` (`s_blood_group`, `s_quantity`) VALUES

('A+', 0),

('A-', 0),

('AB+', 0),

('AB-', 0),

('B+', 0),

('B-', 0),

('O+', 0),

('O-', 0);

INSERT INTO `user` (`username`, `password`) VALUES

('SuperAdmin', '12345678'),

('test_user', 'qwertyuiop');

CS&E Dept ,B.I.E.T, Davanagere

17
 BLOOD_BANK MANAGEMENT SYSTEM

Alter Table commands:

ALTER TABLE `donation`
ADD PRIMARY KEY (`p_id`,`d_date`,`d_time`);

ALTER TABLE `person`

ADD PRIMARY KEY (`p_id`);

ALTER TABLE `receive`

ADD PRIMARY KEY (`p_id`,`r_date`,`r_time`);

ALTER TABLE `stock`

ADD PRIMARY KEY (`s_blood_group`);

ALTER TABLE `user`

ADD PRIMARY KEY (`username`);

ALTER TABLE `person`

MODIFY `p_id` int(10) NOT NULL AUTO_INCREMENT;

ALTER TABLE `donation`

ADD CONSTRAINT `Donation_ibfk_1` FOREIGN KEY (`p_id`) REFERENCES `person` (`p_id`);

ALTER TABLE `receive`

ADD CONSTRAINT `Receive_ibfk_1` FOREIGN KEY (`p_id`) REFERENCES `person` (`p_id`);
COMMIT;

4.1 EMBEDDED SQL STATEMENTS

function signup()
{ extract($_POST);
$data = " name = '$name' ";
$data .= ", email = '$email' ";
$data .= ", address = '$address' ";
$data .= ", contact = '$contact' ";
$data .= ", password = '".md5($password)."' ";
$chk = $this->db->query("SELECT * from complainants where email ='$email'
".(!empty($id) ? " and id != '$id' " : ''))->num_rows;
if($chk > 0){
return 3;
exit;
}
if(empty($id))
$save = $this->db->query("INSERT INTO complainants set $data");

18
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

else $save = $this->db->query("UPDATE complainants set $data where id=$id ");

if($save){
if(empty($id))
$id = $this->db->insert_id;
$qry = $this->db->query("SELECT * FROM complainants where id = $id ");
if($qry->num_rows > 0){
foreach ($qry->fetch_array() as $key => $value) {
if($key != 'password' && !is_numeric($key))
$_SESSION['login_'.$key] = $value;
}

return 1;
}else{
return 3;
}
}

19
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

CHAPTER 5
SNAPSHOTS

Fig. 5.1: User login page

Fig. 5.2: Home page

20
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Fig. 5.3: Add person page

Fig. 5.3.1: Add person page

21
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Fig. 5.4: Search person page

Fig. 5.5: Donation page

22
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Fig. 5.6: Receive page

Fig. 5.7: Check Stock page

23
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Fig. 5.8: Donation History page

24
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Fig. 5.9: Receive History page

25
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

Fig 5.10: Add user page

26
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

CONCLUSION:

The main purpose of our blood management system is to provide blood bank with easier way to
store and retrieve data and keep record of the availability of blood in blood bank.
After inserting the data to database, staff need not register of the same person again. They can
simply search for recorded data and retrieve them for future blood donation or receiving purpose
of that person.
In the nutshell, it can be summarized that the future scope of the project circles around maintaining
information regarding:
❖ The person can fix their donation schedule using online reservation for donation of blood.
❖ The person can search for availability of required blood in the local blood bank in the case
of emergency.
❖ The blood bank to store the details of the blood donated by person, like RBC, WBC,
platelet count etc.
The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project.

27
CS&E Dept ,B.I.E.T, Davanagere
 BLOOD_BANK MANAGEMENT SYSTEM

REFERENCES

BOOKS:
1. Fundamentals of database systems,Ramez Elmasri and Shamkant B Navathe, 7th Edition,
2017 , Pearson.

2. Database management systems, Ramakrishnan, and Gehrke, 3rd Edition, 2014, McGraw Hill.

3. Coronel, Morris, and Rob,Database Principles Fundamentals of Design, Implementation and

Management, Cengage Learning 2012.

4. Silberschatz Korth and Sudharshan, Database System Concepts, 6th Edition, McGraw Hill,
2013.

LIST OF WEBSITES:
https://www.w3schools.com/

28
CS&E Dept ,B.I.E.T, Davanagere