Software Requirement specification

(SRS)

FOR

Blood Bank Management System

Presented by:
Vishakha Agrawal: 1851110902
Yukti Agrawal: 1751110121

B.tech CSE 2ND Year.

 1. INTRODUCTION

 The project blood bank management system is known to

be a pilot project that is designed for the blood bank to
gather blood from various sources and distribute it to the
needy people who have high Requirements for it.
 The Software is designed to handle the daily transaction
of the blood bank and Search the details when required.
 It also helps to register the details of donors, blood
collection details as well as blood issued reports.
 The software Application is designed in such a manner
that it can suit the needs of all the blood bank
requirements in the course of future.
 It will help us to find the Blood group with its most efficient
time to take care of the blood and it is more easy to hand
over the blood to the hospital to help people to get blood
on time.
 This all thing is been stored and been seen in this blood
bank management system. To help more people trying
best to do so.

1.1 PURPOSE
Blood Bank Management Software is designed and suitable for
several Blood Bank either operating as individuals
organizations or part of organizations covers all blood banking
process from donors recruitment, donor management, mobile
session component preparation, screening covering all test,
blood stock inventory maintenance, patient registration, cross
matching, patient issues etc.
1.2 DOCUMENT CONVENTIONS
 ER: Entity relationship
 This document will use IEEE format. For clarity, acronyms
and technical jargon, deemed uncommon by the author,
will be annotated and included in the glossary. The format
for headings is as followed: Major headings are in bold
18pt font, and concurrent headings in bold 14 pt font.
Sections are in the format of x.y, where x and y are real,
positive integers.

1.3 INTENDED AUDIENCE AND READING

SUGGESTIONS
Anybody can use this blood bank management system to donor
as well as who need blood e.g., Public, Hospitals, Blood Banks,
etc.

1.4 PRODUCT SCOPE

This application is built such a way that it suits for all type of
blood bank in future.so every effort is taken to implement this
project in this blood bank, on successful implementation in this
blood bank, we can target other blood banks in the city.
Main modules of the project:
This project have the following modules, to manage all the
requirements of the blood bank.
1. Blood donor details
2. Donor details
3. Recipient details
4. Blood collection details
5. Blood issued details
6. Stock details
7. Camp details
8. Reports
To manage employees in the blood bank it had the following
modules:
1. Employee details
2. Employee attendance details
3. Employee salary generation
4. Employee salary payment
5. Report

1.5 REFRENCES
1. http://www.bharatbloodbank.com
2. http://www.lionbloodbank.net/

1. GENERAL DESCRIPTION

2.1 PROJECT PRESPECTIVE

 To provide an efficient donor and blood stock
management system to the blood bank by recording the
donor and blood details.
 To improve the efficiency of blood stock management by
altering the blood bank staff when the blood quantity is low
it par level or when the blood stock has expired.
  To provide pure blood with no wastage blood is been
collected in different types of packs. They are double,
triple, and triple (AS), Quadruple pack.
 They provide synchronized and centralized donor and
blood stock database.
 To provide immediate storage and retrieval of data and
information.

2.2 Product Function

Class of use cases Use cases Descriptions

Use cases related to 1.Login of admin. 1.Log admin into the
system authorization of 2.Change password of system.
system administrator admin. 2.Change login
password of the
admin of the system.

Use cases related to 1.Register the donor by 1.store personal,

registration of donor. himself. contact, medical
2.Register the donor by details of donors.
system admin. 2. store personal,
contact, medical
details of donors.
Use cases related to 1.Login of donor. 1.Log donor into the
system authorization of 2.Change password of system.
the donor. the donor. 2.Change login
password of the
donors of the system.
Use cases related to 1.Change personal, 1. Change personal
change the registration contact details by the and contact details of
details of donor. donor himself. donors.
2.Change personal, 2. Change personal
contact details by and contact details of
system admin. donors.
 Use cases related to 1.withdraw reg. details 1.Delete all details of
withdraw names from the by the donor. an exact donors by
donor list. 2.withdraw reg. details themselves.
by the admin. 2. Delete all details of
an exact donors by
the system admin.
Use cases related to Send blood donation Inform the
inform blood donation details to the relevant requirement of the
details. donors. blood group to donors
who has same blood
group.
Use cases related to Replace donors’ HC Override the help
replace the older HC Certificates. condition report
Certificates. details.
Use cases related to Send blood testing Inform disease details
inform blood testing to the details. to relevant donors.
donor. Inform donor details
who has diseases, to
relevant doctors.
Use cases related to Search relevant Search and display
access the database. details from the relevant details
database. from the database.
Use cases related to Print the list of newly Print the list of
print statements. registered donors, newly registered
donation details and donors, donation
list of removed name details, list of
as statements. removed names of
statements.

2.3 User Classes and Characterstics

In here the system admin & the donor are the system users.
According to my assumptions the donor who will register to the
system from the website easy questions which are in English
language & he/she has the ability to realize small instructions &
fill the application without any errors & a small knowledge of
computers to upload the health condition certificate to the
systems. User is very generous to attend the donation with
such a small announcement. (Email & SMS Messages).

2.4 operating environment

Particulars Client system server
system
Operating Windows2000prof/Linux Linux
system
Processor Pentium 4, 1.2GHz Pentium4,
2GHz
Hard Disk 40GB 100GB
RAM 256MB 512GB

2.5 Design and implementation constraints

Who uses internet connection will be guided through
small and clear descriptions. Every donor may get user
name and a password in order to log into the will
authenticate the accuracy of the donor’s mobile
numbers through counting the numbers of characters in
the entered mobile number system uses the donor
registration number and the identity card number to
identify each donor separately. Inside the system the
administrator has more advance function than the donor.
The hospital doctor is not a user of the system. But the
doctor connects to the system in a different manner. The
doctor mainly has the connection with the system admin.
2.6 User Documentation
For user documentation and information please consult section
4 external interface requirement and attached user manual.

2.7 Assumptions and dependency

 Every donor has a mobile phone.

 The system doesn’t keep the details of the gathering stock

of blood.

 The system database will be accessible in real time.

 The donor doesn’t submit any fake reports to his system.

 The donors who want to contribute to a donation will

definitely reply to the request of system.

 The installation of the system to the website server hasn’t

considered as a process inside the system that process will
do by the authorities who controlling the website Therefore,
in here the installation the process is considered as a
process which is in o3utside of the scope.

 A doctor or a patient can request for an exact blood group.

But the request comes through blood bank authorities to the
system admin. Therefore, doctor, patient are not directs
users of the system.
3.External Interface Requirement
The system is basically running on the official website of the
govt, blood bank. Mainly there are 2 actors in the system.
The system provides some advance features to the system
admin than the donor. If the system admin logs in,the
system interface provides some main command buttons to
the admin.
 Change login password.
 Edit donor profile details.
 Search donors for a exact blood group and send
messages.
 Print statements.
 Update the database.
 Send blood testing details.
 Search details from the database.
If the donors logs in, the system will provide another different
interface with different commands.

 Change login passwords.

 Edit personal .contact details
 Details related to contributions to donations.
 Future blood donation details.
 Withdraw name from the system.

2.3 User Interfaces

It has been required that every form’s interface should e user
friendly and simple to use.
3.2 Hardware Interfaces
 1GHz or High processor
 512 MB RAM
 500 MB Hard Disk

3.3 Software Interface

Dept of CEA, GLAU, Mathura

Smart blood bank

 Windows
 Internet Explorer, Chrome, Firefox

3.4 Communication Interface

 Should run on 500GHz, 64MB Machine.
 Should have a proper internet connection.
 The response time for occurs a change will be more
than 4 seconds.
 The response time for access the database will be no
more 5 seconds.