1. Southeast University (SEU)
Department of Computer Science & Engineering (CSE)
Project Name : Blood Bank Management System
Information System Design
&
Software Engineering Lab(CSE 346.2)
Submitted By :
Group Name: Team United
Name:Shanta Akter ID: 2019000000103
Name:Lamisa Sobnom Faria ID: 2019000000097
Name:Johurul Islam ID: 2019000000113
Submitted To:
Md.Shafiur Raihan Shafi[MSRS]
Lecturer,Department of CSE,
Southeast University

2. Table Of Contents:
Project Proposal Part #1:
Table Of Contents: 1
Introduction: 3
Goal of the Project: 3
Case Study: 4
Problem Statement: 4
Issues/Limitations: 4
Objectives: 5
Feasibility Analysis: 5
Technical Feasibility: 6
Economic Feasibility: 6
Operational Feasibility: 6
Cost-Benefit Analysis: 7
Tangible Costs: 7
Intangible Costs: 7
Tangible Benefits: 7
Intangible Benefits: 8
Types of Stakeholders: 8
Types of Users of the Proposed System: 8
Functionality Grouping According to the Types of Users: 8
Non-Functional Requirements (NFRs): 9
Availability: 9
Performance: 10
Security: 10
Safety Requirements: 10
Overall Constraints:
1

3. ER Diagram 12
Description Of ER Diagram; 12
Use Case Diagram(UCD) 13
Description of Use Case Diagram: 14
Activity Diagram : 15
Gantt Chart 17
Introduction:
Blood bank management system is an online software system that helps in
managing various blood banks in a better way.This project gives
information about various blood deposits available along with associated
details. These details include blood type, storage area and date of storage.
These details help in maintaining and monitoring the blood deposits.The
project is an online system that allows to check whether required blood
deposits of a particular group are available in the blood bank.Moreover, the
system also has added features such as patient name and contacts, blood
booking and even need for certain blood group is posted on the website to
find available donors for a blood emergency. This online system is
developed on the .NET platform and supported by the SQL database to
store blood and user specific details.
Goal of the Project:
The goal of this project is to computerize the blood bank management
system in order to manage the records of blood donors, blood donation
campaign announcements and broadcast messages about critical blood
demand to donors.Also,the goal of this project is to get a simple & easy
2

4. way of finding blood in an emergency & maintain the records of blood
donors.We have to ensure safe transfusion and maintain the transfusion
history.On the other hand,all the informations have to keep in the database
& it have to secured by authorized user.
Case Study:
Bangladesh Blood Bank and Transfusion Center is a well renowned
blood bank in bangladesh. The current system of this bank is manually
carrying out all the tasks.Such as:
❖ Telephonic communications regarding need of blood
❖ Retrieving the required blood group
❖ Searching the blood from storage
❖ Performing necessary documentations
❖ Delivering the blood
Problem Statement:
Nowadays, people who need blood are increasing day by day.Being
popular people are trying to communicate with this blood bank when they
need blood in difficulty.But their way of communication is telephonic that’s
why people can’t easily communicate with them.If the blood group isn’t
available at the blood bank then the manual transmission might prove in
vain.There is no information regarding the blood donation or managing
programs available on any of the portal.This manually system raises the
cost and time required to a considerable extent.Also, people don’t have any
idea about blood donation how it works.
3

5. Issues/Limitations:
★ With the manual system, there are problems in managing the donor
records. The records of the donor might not be kept safely and there
might be missing of donor's records due to human error or disasters.
★ It is not that people don’t want to donate blood but their limited
knowledge they don't have any idea of blood donation.
★ The way of communication is telephonic which is sometimes
unreachable & makes it unbearable.
★ Being careless the confidential data may be handed on to
unauthorized users.
★ No valid information regarding the blood donation or managing
programs available on any of the portals.
Objectives:
After defining the problems existing the current systems, the objectives of
blood bank management system are -
➢ Provide a report that can be generated of donors, seekers, total
consumption of the blood units so that costs, records and
counts are maintained precisely.
➢ To help raise awareness in the community about blood donation
and make some blood donation events or campaigns for the
public.
➢ To allow the public and organization to make online
reservations on the day and session that they want to make
blood donation.
➢ To provide authentic and authorized features to the current
system where private and confidential data can only be viewed
by authorized users.
➢ To make a valid informative portal about blood donation &
managing systems.
4

6. Feasibility Analysis:
It is the most important part of our system.Feasibility analysis helps us to
know-
● Whether or not we can complete implementing the proposed system.
● The proposed system is worth implementing or not.
● How beneficial or detrimental it might be.
Technical Feasibility:
➔ The existing technology is very much available in this
project.
➔ Resources are available to use.
➔ To complete the project we have a reliable platform.
➔ The platform which we are using is an open source
development platform that can develop web based
applications,mobile apps,desktop applications,etc.
➔ In the future the technology gets developed, our system
can be easily updated as per necessity.
Economic Feasibility:
➔ In the existing platform most of the resources are free of
cost,So we can develop the software at a very low cost .
➔ The necessary software is already within our reach.
➔ The system is feasible in all respects and hence it encourages
taking up the system design.
5

7. Operational Feasibility:
➔ The system is robust, so there is very little possibility of any
kind of crashing and damage.
➔ The platform which we are using has a lot of security scope for
the software that is being developed.
➔ Designed to be used by all kinds of people .
➔ The customer is benefited more by this system as most of his
time is saved.
Cost-Benefit Analysis:
To identify the costs and benefits the proposed information is part of
ensuring the economic feasibility of the new information system.
Tangible Costs:
Cost of system analysts time and the cost of resources are the tangible
costs.
Intangible Costs:
If the system is not satisfied by the people who are using it to donate or
manage blood then it will be an intangible cost. The cost of the internet is
also an intangible cost.
6

8. Tangible Benefits:
Tangible benefits are those which can be measured by something.In this
project, making an online reservation system saves the time for both
donors or receivers.
Intangible Benefits:
It can’t be measured by anything. People will be satisfied by this system if
we complete the project properly. After completing this project, work will be
more accurate than before.
Types of Stakeholders:
A stakeholder can be any person, group or organization that has a concern
or interest in a business or project.
Stakeholders may include users, providers, governance, suppliers, internal
staff, members, customers and it also may include purchasers, clients,
owners, and non-governmental organizations.
Types of Users of the Proposed System:
● Admin
● Blood Bank
● Donor
● Patient
7

9. Functionality Grouping According to the Types
of Users:
Admin: The authority of the web page will be controlled by the admin.
They can see the user information.
➔ Monitoring the users registration
➔ Configure access for users
➔ Manage the information of users
➔ Manage patient request for needy users
➔ Manage modification like Update information, Deletion.
Blood Bank: Blood Bank is the process where blood will be stored for
the needy people and in blood banks the blood will be kept safe for the
users. And the users easily view the donor information and manage the
patient's blood request.
Donor: Donor is a person who will donate the blood to the acceptors.
Every donor has an individual account. Every registered donor has some
option which will be showing in their account.
➔ Login
➔ Update your information
➔ Delete account
➔ Logout
Patient: Patient can be anyone who can search in the system for the
required blood and in emergency issues they can call the admin panel for
more information about donors.
➔ Giving request for patient for the blood
➔ Patients can manage their personal information.
8

10. Non-Functional Requirements (NFRs):
Availability:
NFR-01-01 The system, which is called a web based blood
bank management system.
NFR-01-02 The system should be available at all times if the
internet connection is reliable, the user can
access it using an application.
Performance:
NFR-02-01 The system is interactive and the delays
involved are less.
NFR-02-02 The system performs its task efficiently and
effectively because the team project will use
advanced programming language, less number of
iterations for a given task and optimized query to
develop the system.
Security:
NFR-03-01 The system usesSSL in all transactions that
include any confidential customer information.
NFR-03-02 The system must automatically log out all
customers after a period of inactivity.
9

11. Safety Requirements:
Blood bank module maintains details about the donors and recipients. This
blood bank module is linked to other modules in the software for wards and
OT in the hospitals. Important information and parameters such as
availability of blood, cross-matching between donor’s and recipient’s blood
groups and blood transfusions reactions are recorded.
NFR-04-01 The blood request queue screen, from where all
the daily transfusions can be handled.
NFR-04-02 Fresh blood and stored blood request processing.
NFR-04-03 Blood return is made easy in the blood bank
management system.
Overall Constraints: Users will face some trouble from our
proposed system.
● Lacking of donor information
● Takes long time
● Less accuracy
● Shortage of donor availability
● Less Security
10

12. ER Diagram
Description Of ER Diagram;
There are six entities in our ER diagram.These are:Donor,Blood,
Receptionist ,Blood Bank,Blood Bank Manager and hospital.
11

13. Now, we will have to identify the relationship. So,we will discuss the first
entity in our ERD which is the donor. A donor may donate blood any
number of times.So, the cardinality is many to one.Second relationship
donor to receptionist.Donors may register with a single receptionist.So,the
cardinality is one to one.The next entity is blood.It’s different type in large
numbers in stored in a single blood bank.So, the cardinality is many to
one.blood bank is managed by an blood bank manager.So, cardinality is
one to one.A receptionist works in blood bank .So, cardinality is one to
one.Hospitals order blood from different blood from different blood
banks.So, the cardinality is zero to many.
Use Case Diagram(UCD)
12

14. Description of Use Case Diagram:
We can see that there are three actors in this diagram. They are:
User,Donor & Admin. User connected with six different use cases. Which
are: search location, login & logout,search blood,update profile,manage
donor,send request. Manage donor have an extended relationship with get
help on manage donor use case.Donor also have four use cases. Some of
them also connected with other actors. Like search location, login & logout ,
update profile .Another use case is accept request which is also connected
with Admin. Admin has also five use cases.Which is also connected with
other actors. Only login Id & password , manage stock has separate
bonding with this actor.Manage stock has two include relationship with
manage user & application , Manage blood.
13

15. Activity Diagram :
For User
This is the user login activity diagram of the blood bank management
system.
14

16. Which shows in the activity flows of editing , adding and updating of
blood.After that we need to give check user level & permissions user able
to search and generate report of blood cells, patient,donor.All activity such
as stock, blood, donor are interlinked in these diagram.If the process is
successfully completed then logout the system.in this way user login page
works.
For Admin
15

17. Another activity diagram made the perspective of the actor.Here the
actor is Admin. It is the admin login activity diagram of blood bank
management system.Where admin will be able to login using their
username and password.If we give correct username and password then
we will be able to login the system successfully.Otherwise, it will be showed
invalid login and password.
Finally we can say that these diagrams help how the login page works in a
blood bank management system.
Gantt Chart
For this project we made this gantt chart to overview our whole project.
___________The End____________
16