UNIVERSITY OF MUMBAI

A PROJECT REPORT ON

Blood Bank Management System

SUBMITTED BY

DEEPAK PATEL
DIVAKAR PRAJAPATI

Under the guidance of

(Prof. Chadani Patel)

 Vishnu Waman Thakur Charitable Trust’s

VIVA INSTITUTE OF TECHNOLOGY

Shirgaon, Virar (East)

2023-24

Vishnu Waman Thakur Charitable Trust’s

VIVA INSTITUTE OF TECHNOLOGY

Shirgaon, Virar (East)

CERTIFICATE

This is to certify that

DEEPAK PATEL (20)

DIVAKAR PRAJAPATI (24)

(BLOOD BANK MANAGEMENT SYSTEM)

Towards the project fulfilment of the
MASTER OF COMPUTER APPLICATION (MCA)
As laid by University of Mumbai

Principal External Examiner Internal Guide

 Declaration
I hereby declare that the work recorded in this project report entitled "Blood
Bank Management System in partial fulfilment for the requirements for the
award of Degree in Master of Computer Applications from Mumbai University
Sikkim, is a faithful and bonafide work carried out under the supervision and Guidance of
Prof. Chadani Patel from 2nd June 2024 to 6th May 2024.
The results of this investigation reported in this project have so far not
been reported for any other Degree or other technical forum. The assistance
and help received during the investigation have been duly acknowledged.
 ACKNOWLEDGEMENT

I am using this opportunity to express my gratitude to everyone who supported me

throughout the course of this project. I am thankful for their aspiring guidance and friendly
advice during the project work. I am sincerely grateful to them for sharing their truthful and
illuminating views on a number of issues related to the project. There are many who
helped me with this project and I want to thank them all from the core of my heart. I
express my warm thanks to my respected project guide Prof. Chadani Patel for allowing me
to use the facilities available and also help me to coordinate my project. Last but not least, I
would like to thank friends who help me to assemble the parts and gave a suggestion about
the project.

ABSTRACT
The Blood Bank Management System (BBMS) is a comprehensive software solution designed to
streamline the process of managing blood inventory, donor information, and blood requests within
a blood bank or similar healthcare facility. This project aims to address the challenges faced by
blood banks in maintaining accurate records, efficiently managing blood donations, and facilitating
timely responses to blood requests. The BBMS offers a user-friendly interface for blood bank staff
to record and track blood donations, manage donor profiles, and update inventory levels in real-
time. Through its integrated functionalities, the system enables efficient communication between
blood banks, hospitals, and other medical institutions, ensuring prompt fulfilment of blood requests
and reducing the risk of blood shortages.
 Index
Sr. No. Contents Page No.

1. Introduction
1.1 Introduction
1.1.1 Problem definition
1 1.1.2 Objectives of Project
1.1.3 Scope of Project
1.2 Technical Details
1.2.1 Overview of Front End
1.2.2Overview of Back End
2. System Study and Planning
2.1 System Study
2 2.1.1 Existing System
2.1.2 Disadvantages of Existing system
2.1.3 Proposed System
2.2 System Planning and Schedule
2.2.1 S/W development Model
3. System Design
3.1 Software Requirement Specification(SRS)
3.1.1 Introduction of SRS
3 3.1.2 Technology Requirements
3.1.2.1 Hardware to be used
3.1.2.2 Software/tools to be used
3.2Detailed life Cycle of the Project
3.1.3 Modules
3.1.4 Object Oriented Analysis & Design
Diagrams
3.2.2.1 Use Case Diagram
3.2.2.2 Activity Diagram
3.2.2.3 Class Diagram
3.2.2.4 Sequence Diagram
3.2.2.5 Flowchart/DFD/ER diagram
3.2.3 Database
3.2.3.1 Database Table
3.2.4 I/O Screen Layout
 4. Testing (Any Model explanation in terms of your
4 project)
4.1 Methodologies used for testing
4.2 Types of Testing (Whichever Used)
5 5. Conclusion

6 6. Future Enchantments

7 7. References
 1. Introduction
1.1 Introduction
Blood Bank Management is a browser-based system that is designed to store, process, retrieve and analyse
blood related information. This project aims at maintaining all the information pertaining to blood donors,
different blood group available in this blood bank and help them to manage in a better way. This website
provides the user or the donors a secured environment by accepting the log in ID’s and password from the
user. This application allows the user to store the donor details as soon as the donor is registered. The
admin will check the donor registered details if only he/ she is capable for donating the blood then only the
donor can donate the blood at their registered centres. Before that the admin will send message or
notification to donor registered mobile number or email.

1.1.1 Problem definition

The existing system is manual system. Needs to be converted into automated system. As it
has a risk of mismanagement of data, less Security, no proper coordination between
different Applications and Users, fewer users - friendly, accuracy not guaranteed and not in
reach of distant users.

1.1.2 Objectives of Project

Furniture management system allows users to check various furniture products available at
the online store and purchase online. The project consists list of furniture products
displayed in various categories. The user may browse through these items as per
categories. If the user likes a product he/she may add it to his/her cart. Once user wishes to
checkout he/she must register on the site first. He/she can then login using same id
password next time. Now he/she may make payment on cash on delivery. Once the user
makes a successful transaction he/she gets a copy of the shopping receipt on his email id.
Here we use user friendly interface to make the entire front end. It is a easy to use
interface developed in PHP with MySQL as the back end to store the details. It is secure,
easy to use and reliable software system. It also provides a good level of security as there is
an admin who can only edit and update details .Believe in focus on core competence in
furniture solution. Provide one stop solutions including supply of different furniture brands

1
as per the customer requirement. Carry on with the value that drives us give out the best in
doing office, educational and home furniture business.

1.1.3 Scope of Project

This application avoids the manual work and the problems concern with it. It is an easy way
to obtain the information regarding the various products information that are present in
the Furniture Mart. Well in order to present an improved website better than the existing
one’s regarding the information about the various activities. Still, we found out that the
project can be done in a better way. Primarily, when we request information about a
particular product it just shows the company, product id, product name and no. of
quantities available. So, after getting the information we can get access to the product
company website just by a click on the product name. The next enhancement that we can
add the searching option. We can directly search to the particular product company from
this site .These are the two enhancements that we could think of at present.

1.2 Technical Details

1.2.1 Overview of Front End

HTML
HTML is the standard markup language for creating web pages. It describes the structure
of information on a web page. It can be assisted by technologies such as Cascading Style
Sheets (CSS) and scripting languages such as JavaScript. Together, HTML, CSS, and
JavaScript make up the essential building blocks of websites worldwide, with CSS
controlling a page’s appearance and JavaScript programming its functionality.

CSS
CSS stands for Cascading Style Sheets. CSS saves a lot of work. It can control the layout of
multiple web pages all at once. It provides an additional feature to HTML. It is generally
used with HTML to change the style of web pages and user interfaces. It is easier to make
the web pages presentable using CSS.

2
JAVASCRIPT
Javascript is a dynamic programming language. It is lightweight and most commonly used
as a part of web pages, whose implementations allow client-side script to interact with the
user and make dynamic pages. Javascript can update and change both HTML and CSS.
Javascript can calculate, manipulate and validate data.

1.2.2 Overview of Back End

PHP
PHP is an acronym for "PHP: Hypertext Pre-processor”. PHP is a widely-used, open-source
scripting language .PHP scripts are executed on the server. PHP is free to download and use
.PHP files can contain text, HTML, CSS, JavaScript, and PHP code. PHP code is executed on
the server, and the result is returned to the browser as plain HTML. PHP files have
extension ".php" PHP can generate dynamic page content. PHP can create, open, read,
write, delete, and close files on the server. PHP can collect form data. PHP can send and
receive cookies. PHP can add, delete, and modify data in your database. PHP can be used to
control user-access. PHP can encrypt data.
MYSQL
MySQL is a relational database management system based on the structured Query
Language, which is the popular language for accessing and managing the records in the
database

PHPMYADMIN
PhpMyAdmin is an open source tool written in PHP intended to handle the administration
of MySQL over the World Wide Web. PhpMyAdmin supports a wide range of operations
with MySQL. Currently it can create and drop databases, create/drop/alter tables, and
delete/edit/add fields, execute any SQL statement, manage users and permissions, and
manage keys on fields. While you still have the ability to directly execute any SQL
statement. PhpMyAdmin can manage a whole MySQL server (needs a super-user) as well
as a single database. To accomplish the latter you’ll need a properly set up MySQL user who
can read/write only the desired database.

2. System Study and Planning

2.1 System Study
2.1.1 Existing System
The existing system is manual system. Needs to be converted into automated system. As it
has a risk of mismanagement of data, less security, no proper coordination between die rent
application and Users, fewer users-friendly, accuracy not guaranteed not in reach of distant
users

3
  In existing system Furniture shopping can done in a manual way, the customer
has to go for shopping, and then he is having the possibility to choose the
products whatever he wants.
 It is a time consuming process.
 Thus, the system has to be automated.
 In existing system the customer is completely depending on the manual
process for buying the furniture products.
 Manual process is a time consuming factor. And when customer approaches
for a manual shopping directly, actually he/she does not idea about things like,
price range, time etc.
 Thus we need to change to a system like “Online Furniture Shopping”.

2.1.2 Disadvantages of existing system

The main disadvantage of ordering furniture online is the inability to touch and see
the products directly before making the purchase. When buying other types of
products this is probably more bearable and acceptable, but the furniture in
particular, like clothing, is the type of thing I prefer to do in person unless the online
store where you decide to make the purchase offers minute details about each item.

2.1.3 Proposed System

The main purpose behind this furniture management system, we have created a system
where a user who gives orders according to the choice of type of wood, usage area, cost,
small or large, colour. He can also give the order for the customized item and specify the
attributes and then next is ordering it and get the item. Admin assigns the wood, tools, and
staff to the customized item to make and then completes it on time as mentioned. So, it all
working fine.

2.2 System Planning and Schedule

Project planning defines the project activities and end products that will be performed and
describes how the activities will be accomplished. The purpose of the project planning is to
define each major task, estimate the time and resources required, and provide a framework
for management review and control.

The project planning activities and goals include defining:

a) The specific work to be performed and goals that define and blind the
project.
b) Estimate to be documented for planning, tracking and controlling the project.

4
 3. System Design
3.1 Software Requirement Specification (SRS)
3.1.1 Introduction of SRS
 A software requirements specification (SRS) is a document that captures complete
description about how the system is expected to perform.
 It is usually signed off at the end of requirements engineering phase.
Characteristics of good SRS Document:
Some of the identified desirable qualities of the SRS document are as follows: 
Concise:
• The SRS document should be concise and at the same time unambiguous, consistent, and
complete.
 Clarity:
• SRS is clear when it has single interpretation for the author, the user, the end user, the
stake-holder, the developer, the tester& the customer.
• This is possible if the language of the SRS is unambiguous.
• The clarity can be enhanced if SRS includes diagrams, models & charts.
 Completeness:
• SRS is complete when it is documented after
• The involvement of all types of concerned personnel.
• Focusing on all problems, goals & objectives, & not only on functions & features.
• Correct definition of scope & boundaries of the s/w & system  Correctness:
• The requirements are termed as correct if they have link to goals & objectives.
• The requirements should achieve the business goals & solve managerial & operational
problems
• The requirement & its functions & features are considered correct when it is most
efficient & effective, & when it is considered valid by all concerned.  Consistency :
• Consistency in SRS is essential to achieve correct results across the system. This is
achieved by:
• Use of standard terms & definitions
• Consistent application of business rules in all functionality
• Use of data dictionary
• Lack of consistency results in incorrect SRS & failure in deliverables to customer. 
Structured:
• It should be well-structured. A well-structured document is easy to understand and
modify

 Black box view:

• It should only specify what the system should do and from stating how to do these.
• This means that the SRS document should specify the external behaviour of the system
and not discuss the implementation issues.

5
• The SRS document should view the system to be developed as black box, and should
specify the externally visible behaviour of the system.
• For this reason, the SRS document is also called the black-box specification of a system.
 Conceptual integrity:
• It should show conceptual integrity so that the reader can easily understand it.
• Response to undesired events:
• It should characterize acceptable responses to undesired events
• These are called system response to exceptional conditions.
 Verifiable:
• All requirements of the system as documented in the SRS document should be verifiable.
• This means that it should be possible to determine whether or not requirements have
been met in an implementation.  Modifiability:
• The SRS document should be well structured. A well-structured document is easy to
understand & modify.  Traceability:
• This characteristic facilitates an understanding of the effects on various functions &
features
• If any error occurs in the testing then its cause analysis is possible through traceability. •
With traceability, navigating through test plan, test case, test results, design, and
architecture & source code is easily possible.  Feasibility:
• Technical feasibility must be checked to confirm whether the organization has a proper
technology that is capable enough to deliver what is expected in SRS.  Testability:
• SRS should be written in such a way that it is possible to create a test plan to confirm
whether specifications can be met & requirements can be delivered • Considering
functional & non-functional requirements
• Determining features & facilities required for each requirement
• Ensuring that ‘users’ & ‘stake-holders’ freeze the requirement.
 Parts of SRS Document:
• The important parts of SRS document are:
1. Functional requirements of the system
2. Non-functional requirements of the system

3. Goals of implementation

3.1.1Technology Requirements

3.1.2.1 Hardware to be used

This software requires following minimum hardware configuration:
• Processor: Pentium-iv and above
• RAM: 256 MB
• Hard Disk: 4.3GB
• Floppy Disk: 1.44 MB

6
• CD Drive
• Monitor-15” Colour Monitor

3.1.2.2 Software/tools to be used

• OS: Windows XP/7/8/10/11
• PHP Triad (PHP, MySQL, Apache, and PHPMyAdmin
• Technology: Xampp/Wamp
• IDE: Visual Studio Code
• Web Browser: Mozilla, Chrome
• User Interface Design: HTML, CSS, JAVASCRIPT, JQUERY

3.2 Detailed life Cycle of the Project

3.2.1 Modules

Admin
• Admin is the super user of the website who can manage
everything on the website. Admin can log in through the login
page.
• Dashboard: In this section, admin can see all detail in brief
like the total new order, total confirmed order, total delivered
order, and total cancelled order, Total Order, Total Product
Products, Total Brand and Total Registered Users Brand: In
this section, admin can manage furniture.
• Brand (add/update). Category: In this section, admin can
manage furniture Category (add/update).
• Sub-Category: In this section, admin can manage furniture
Sub-Category (add/update). Products. In this section, admin can
manage furniture Products (add/update).
• Orders: In this section admin can view the order details and
they have also right to change order status according to current
status.
• Pages: In this section, admin can manage about us and contact
us pages.
• Reports: In this section admin can view order details, order
counts and sales report according to dates.
• Reg Users: In this section admin can view register users.
• Search: In this section admin can search particular order with
the help of order number.
• Admin can also update his profile, change the password and
recover the password.

7
 User (Registered Users)
• Home: In this section, user can view home page of website.
• Furniture: In this section, user can view furniture products
according to categories and add products to cart.
• My Accounts: In this section user view and update his/her
profile, view the products which is added in the cart, view order
details, can change his/her own password and logout from
accounts.

• User has also a facility to view his/her invoice and cancel order
if he/her wants to cancel.
• Brief Information about homepage : On this page guest user
can only view about us page, contact us page and which
product is available if anybody want to order the product they
must registered

3.2.2 Object Oriented Analysis & Design Diagram

3.2.2.1 Use Case Diagram

8
9
3.2.2.2 Activity Diagram

10
11
3.2.2.3 Class Diagram

12
3.2.2.4 Sequence Diagram

3.2.2.5 Flowchart/DFD/ER diagram Flowchart:

13
14
Data Flow Diagram:

15
E-R Diagram:

16
3.2.3 Database

3.2.3.1 Database Table

17
3.2.4 I/O Screen Layout

18
Home Page

Products

19
Login

Forgot Password

20
Change Password

My Cart

21
Dashboard

About Us

22
Contact us

4. Testing
4.1 Methodologies used for testing

 Waterfall Methodologies

• This model is built on a team’s step-by-step progress during the testing process.

• First, a whole project is documented and planned. Then, a team of testers makes
small steps, one after another.

• Each step can’t be taken until the previous one is completed.

• One of the main advantages of this methodology is that it’s relatively simple.

• The disadvantage is that the team is not able to make fast corrections to the
testing process, because it is regimented.

4.2 Types of Testing

23
Unit Testing

Unit testing is a software development process in which the smallest testable parts of an
application, called units, are individually and independently scrutinized for proper operation.
This testing methodology is done during the development process by the software developers
and sometimes QA staff. The main objective of unit testing is to isolate written code to test
and determine if it works as intended. Unit testing is an important step in the development
process, because if done correctly, it can help detect early flaws in code which may be more
difficult to find in later testing stages. Unit testing is a component of test-driven development
(TDD), a pragmatic methodology that takes a meticulous approach to building a product by
means of continual testing and revision. This testing method is also the first level of software
testing, which is performed before other testing methods such as integration testing. Unit tests
are typically isolated to ensure a unit does not rely on any external code or functions. Testing
can be done manually but is often automated
Integration Testing

Integration testing is the second level of the software testing process comes after unit testing.
In this testing, units or individual components of the software are tested in a group. The focus
of the integration testing level is to expose defects at the time of interaction between
integrated components or units. Unit testing uses modules for testing purpose, and these
modules are combined and tested in integration testing. The Software is developed with a
number of software modules that are coded by different coders or programmers. The goal of
integration testing is to check the correctness of communication among all the modules. Once
all the components or modules are working independently, then we need to check the data
flow between the dependent modules is known as integration testing.

System Testing
System Testing is a type of software testing that is performed on a complete integrated
system to evaluate the compliance of the system with the corresponding requirements. In
system testing, integration testing passed components are taken as input. The goal of
integration testing is to detect any irregularity between the units that are integrated
together. System testing detects defects within both the integrated units and the whole
system. The result of system testing is the observed behaviour of a component or a system
when it is tested.

Beta Testing
This was conducted at one or more customer sites by the end-user of the software. Unlike
alpha testing, the developer is generally not present. Therefore, the beta test is a “live”
application of the software in an environment that cannot be controlled by the developer. The
customer records all problems that are encountered during beta testing and reports these to
the developer at regular intervals. As a result of problems reported during beta tests, software
engineers make modifications and then prepare for release of the software product to the
entire customer base.

24
 5. Conclusion
Based on results, this study concluded that online blood bank management system is much better than the manual
system. The findings showed that users prefer to use online blood bank management system rather than the manual
system because it offers many advantages and benefits that lead to its effectiveness, and efficiency. Because of the
increased confidence on the users on the system, it can be concluded that the online blood bank management
system enhances blood transfusion safety since it provides better ways of handling the various processes in blood
bank.

6. Future Enchantments
In view of the findings, the researchers recommend that implementation of online blood bank
management system. Further, the researchers recommend that further studies on how online
blood bank management system enhances blood transfusion safety can be undertaken to
strengthen this project’s findings. Lastly, this project recommends that the system can be
expanded by allowing donors to register online and be a system user, and these donors will be
informed about the planned blood donation activities through the online system.

25
 7. References
• WWW.GOOGLE.COM
• WWW.YOUTUBE.COM
• WWW.W3SCHOOLS.COM
• WWW.MYSQLTUTORIAL.ORG

26