Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

COMPLETE

Download as pdf or txt
Download as pdf or txt
You are on page 1of 20

ACKNOWLEDGEMENT

We give our high, respectful gratitude to our guide MR. HARSHA HONNU,
Assistant professor, dept of CSE and Mr. FAYAZ SHAIKH, Assistant professor,
dept of CSE, who have been our source of inspiration. They have been especially
enthusiastic in giving their opinions and critical reviews.

We have learnt a lot throughout this semester with many challenges yet
valuable experience in order to complete this task. We will remember their
contribution forever.

We sincerely thank Dr. SOMESHA M, HOD, dept of CSE, who has been the
constant driving force behind the completion of the project.

We also thank our respected Principal Dr. SHANTALA B for her constant help
and support throughout.

Our special thanks to faculty members who have supported us in making this
project a successful one.

We also take this opportunity to thank the technician staffs who have helped
us a lot in providing the software support and any other support whenever needed.
My thanks and appreciations also goes to my friends who have willingly help us with
their ability.

HARISH KUMBHAR 2GP19CS009

DARSHAN PEDNEKAR 2GP19CS028

PRAVEEN M R 2GP19CS018
ABSTRACT

The main objective of the project is to create an bloodbank that allows users to
receive and donate blood by their blood group. The blood group are displayed in a
tabular format and the user can receive or donate their blood. Using this web
application, the user can get the blood online. The entire project has been developed
keeping in view of the distributed client server computing technology, in mind.

The Blood bank management system provides an alternative to the traditional


blood bank management system that involves handling huge amount of user data
and manually evaluating acceptor request with stock or donor availability. This
system allows direct contact with donor and acceptor to the hospital. Every donor
and acceptor will have a registered account. Through there account, they can
request or donate the blood through the blood bank.

The registered user, can view all the donors of a specific location in their
locality. The recipient may request for a donation to any of the donors or to the
administrator if the specific blood group is available in stock.

The website will consists of two modules: Hospital module and User module.
The hospital has the privilege to view stock details, add a donor, request blood from
a donor. The user can donate a blood or become acceptors. They can request blood
from the hospitals. The hospitals sends the blood request to user so they can donate.
TABLE OF CONTENTS

CHAPTER CHAPTER NAME PAGE NO.


NO.

1. INTRODUCTION 1

2. SYSTEM ANALYSIS 2

2.1 Module information

3. REQUIREMENT SPECIFICATION 3

3.1 Hardware requirements

3.2 Software requirements

4. SYSTEM DESIGN 4-7

4.1 Architectural design

4.2 Use case diagram

4.3 Schema diagram

4.4 ER diagram

5. SNAPSHOTS OF OUTPUT 8-15

CONCLUSION

REFERENCE
BLOOD BANK MANAGEMENT

CHAPTER-1

INTRODUCTION

The population of the world is multiplying with each coming year and so are
the diseases and health issues. With an increase in the population there is an increase in the
need of blood. The growing population of the world results in a lot of potential blood donors.
But in spite of this not more than 10% of the total world population participates in blood
donation. With the growing population and the advancement in medical science the demand
for blood has also increased.

Due to the lack of communication between the blood donors and the blood
recipients, most of the patients in need of blood do not get blood on time and hence lose their
lives. There is a dire need of synchronization between the blood donors and hospitals. This
improper management of blood leads to wastage of the available blood inventory. Improper
communication and synchronization between the donors and hospitals leads to wastage of the
blood available. These problems can be dealt with by automating the existing manual blood
bank management system. A high-end, efficient, highly available and scalable system has to
be developed to bridge the gap between the donors and the recipients and to reduce the
efforts required to search for blood donors.

NEED:
 Efficiently maintains the details about blood stock.
 Simultaneously updates change made to any data, item in entire database.
 That is faster than manual system.

Dept of CSE GEC, KARWAR Page | 1


BLOOD BANK MANAGEMENT

CHAPTER-2

SYSTEM ANALYSIS

2.1 MODULES INFORMATION:

This project involves two actors:

a) Hospital / Blood bank


b) Donor / Patient

HOSPITAL:

The modules involved in the Hospital are:

i. Account
ii. Blood stock
iii. Request blood
iv. Request status
v. Request from patient
vi. Logout

DONOR / PATIENT:

The modules involved in the Donor / Patient are:

i. Account
ii. Request blood
iii. Request status
iv. Request from hospital
v. Logout

Dept of CSE GEC, KARWAR Page | 2


BLOOD BANK MANAGEMENT

CHAPTER-3

REQUIREMENT SPECIFICATION

3.1 HARDWARE REQUIREMENTS:

 Processor Intel Dual core CPU


@ 2.90GHz
 Ram 1.00GB

 System type Windows 10 / Linux.

 Hard disk 40GB

3.2 SOFTWARE REQUIREMENTS:

 User on Internet Web Browser, Operating System (any)


 Application Web Server browser [Chrome, Firefox and Internet Explorer]
 Data Base Mysql
 Applications server XAMPP
 Front End Tool HTML and CSS

Dept of CSE GEC, KARWAR Page | 3


BLOOD BANK MANAGEMENT

CHAPTER-4

SYSTEM DESIGN

4.1 ARCHITECTURAL DESIGN:

Architecture focuses on looking at a system as a combination of many different


components, and how they interact with each other to produce the desired result. The
focus is on identifying components or subsystems and how they connect. In other
words, the focus is on what major components are needed.

4.2 USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of


behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use
cases. The main purpose of a use case diagram is to show what system functions are
performed for which actor. Roles of the actors in the system can be depicted.

Terms used in Use case diagram:

Use cases:A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse.

Actors: An actor is a person, organization, or external system that plays a role in one
or more interactions with the system.

System boundary boxes:A rectangle is drawn around the use cases, called the
system boundary box, to indicate the scope of system. Anything within the box
represents functionality that is in scope and anything outside the box is no

Dept of CSE GEC, KARWAR Page | 4


BLOOD BANK MANAGEMENT

Fig 4.2.1 Use case diagram of Hospital

Fig 4.2.2 Use case diagram of Donor/Patient

Dept of CSE GEC, KARWAR Page | 5


BLOOD BANK MANAGEMENT

4.3 SCHEMA DIAGRAM:

Fig 4.2.2 Schema diagram

Dept of CSE GEC, KARWAR Page | 6


BLOOD BANK MANAGEMENT

4.4 ER DIAGRAM:

Fig 4. 4: ER- Diagram of bloodbank

Dept of CSE GEC, KARWAR Page | 7


BLOOD BANK MANAGEMENT

CHAPTER-5
SNAPSHOTS OF OUTPUT
Home Page:

About us :

Dept of CSE GEC, KARWAR Page | 8


BLOOD BANK MANAGEMENT

Hospital Login Page:

Hospital Register Page :

Dept of CSE GEC, KARWAR Page | 9


BLOOD BANK MANAGEMENT

Hospital Home Page :

Account (Update Hospital Details) :

Dept of CSE GEC, KARWAR Page | 10


BLOOD BANK MANAGEMENT

Blood Stock (Add Blood) :

Request Donor:

Dept of CSE GEC, KARWAR Page11


BLOOD BANK MANAGEMENT

Request Status:

Request From Patient:

Dept of CSE GEC, KARWAR Page12


BLOOD BANK MANAGEMENT

Donor/Patient Home Page :

Account (Update Donor/Patient Details) :

Dept of CSE GEC, KARWAR Page13


BLOOD BANK MANAGEMENT

Request Blood :

Request Status :

Dept of CSE GEC, KARWAR Page14


BLOOD BANK MANAGEMENT

Request From Hospital :

Dept of CSE GEC, KARWAR Page15


CONCLUSION

The Blood bank management system has been computed successfully and
was also tested successfully by taking “test case”. It is user friendly and has required
options, which can be utilized by the user to perform the desired operations.

Today the world is becoming a global village where everything is online. There
are so many web-based solutions provided in the society for the comfort of the
people. Just by providing the web solution of blood bank management system is just
one step in order to serve the mankind.

Technology is introducing new innovations day by day, thus reducing the time
required to do things. The proposed system can be used to reduce the time required
to deliver required blood to the needy in cases of emergency. The web application
can be used by the people interested in donating their blood by locating their nearest
blood bank. The web application provides a way of communication and
synchronization between the hospitals and the donars. It also provides them with the
facility of communicating with the nearby donors in emergency. The database is a
vital aspect of the system. The database of the hospitals and the donors must be
checked for consistency on regular basis for smooth working of the system. The
proposed system uses ‘Google Maps’ which provides the user with an efficient way
of locating the nearby donors/blood banks. The Web application is developed using
‘Visual Studio Code’ which is an open source software, while the web application for
the hospitals and the donors is also developed using open source tools, hence the
system developed is quite feasible.
REFERENCE

[1] https://www.php.net

[2] http://dev.mysql.com/doc/refman/8.0/en

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

[4] https://en.m.wikipedia.org/wiki/PHP

[5] https://github.com/kingster/Way2SMS-API

[6] https://www.youtube.com/c/CodeWithHarry

You might also like