Software Requirements

Specification

for

Blood Bank

Version 1.0 approved

Prepared by Aditya Kumar Mishra (20304)

Amit Kumar (20307)

IIIT Una

16/08/2022
Software Requirements Specification for Blood Bank Page 2

Table of Contents

Table of Contents ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 2

2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 3
2.6 User Documentation 3
2.7 Assumptions and Dependencies 3

3. External Interface Requirements 3

3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 4

4. System Features 4
4.1 System Feature 1 4
4.2 System Feature 2 (and so on) 5

5. Other Nonfunctional Requirements 5

5.1 Performance Requirements 5
5.2 Safety Requirements 6
5.3 Security Requirements 6
5.4 Software Quality Attributes 6
Software Requirements Specification for Blood Bank Page 3

6. Other Requirements 7
Software Requirements Specification for Blood Bank Page 1

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the website Blood Bank. It will explain
the purpose and features of the website, the interfaces of the website, what the website will do and the
constraints under which it must operate. This document is intended for users of the website and also
potential developers.

1.2 Document Conventions

This Document was created based on the IEEE template for System Requirement Specification Documents.

1.3 Intended Audience and Reading Suggestions

Typical Users, such as patients, who want to use it to view the availability of blood.
Doctors can use it to find the required blood.

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:

● Donors Management
● Blood Group Management
● User Management
● General Setting
● Profile Setting
Software Requirements Specification for Blood Bank Page 2

1.5 References

Code with harry you tube channel

https://www.youtube.com/channel/UCeVMnSShP_Iviwkknt83cww

Code with harry website

https://www.codewithharry.com/

2. Overall Description

2.1 Product Perspective

● To provide an efficient donor and blood stock management system to the blood bank
by recording the donor and blood details.
● To improve the management of blood.

2.2 Product Functions

The Hospital Manger has to register the Hospital which acts as an acceptor here. The details of the blood
inventory i.e The availability of a particular type of blood is regularly updated and maintained by the
Inventory Manager. It is confidential data so the access is only with the administrators.

2.3 User Classes and Characteristics

There are mainly five users interacting with each other in this system: Donor, Receptionist, Hospital
Manager, Inventory Manager. Here the system admin & the donor are the system users. Users are very
generous to attend the donation with such a small announcement. (Email & SMS Messages).

2.4 Operating Environment

Operating system - Windows 2000 Prof/Linux

Processor - Pentium 4, 1.2GHz
Hard Disk - 40GB
RAM - 256 MB
Software Requirements Specification for Blood Bank Page 3

2.5 Design and Implementation Constraints

Blood bank is developed in PHP, it uses MySql for its database storage . It uses a modular design where
every feature is wrapped into a separate module and the modules depend on each other through well-written
APIs. There are several APIs available to make plugin development easy.

2.6 User Documentation

Users can register his details. Then user login. Then the user can see the availability of blood.

2.7 Assumptions and Dependencies

Blood Bank is developed in PHP and therefore requires Apache to be installed on the user’s system..

3. External Interface Requirements

3.1 User Interfaces

It has been required that every form’s interface should be user friendly and simple to use.

3.2 Hardware Interfaces

● 1GHz or High processor

● 512 MB RAM

● 500 MB Hard Disk

3.3 Software Interfaces

● Clint on internet : Web Browser, Operating system (any)

● Web Server : Operating system (any) , Apache 2
● Database : MySQL
● Scripting Language : Javascript, Jquery
Software Requirements Specification for Blood Bank Page 4

3.4 Communications Interfaces

There are :-

● Should run on 500GHz, 64MB Machine.

● Should have a proper internet connection.

● The response time for a change will be more than 4 seconds.

● The response time for accessing the database will be no more than 5 seconds.

4. System Features

● Donor management-donor registration, managing donor databases, recording their physical and
medical statistics.

4.1 System Feature 1

4.1.1 Description and Priority

● Information of all blood banks donor details, donate blood with their interest and others will
do in future.
● Interested in donating blood can register.
● General users want to contact blood donors by checking if they are interested to donate
blood, he can also take the help of this site.
● Inventory and stock management.
● Interactions with the blood establishment.

4.1.2 Stimulus/Response Sequences

<List the sequences of user actions and system responses that stimulate the behavior defined for this
feature. These will correspond to the dialog elements associated with use cases.>

4.1.3 Functional Requirements

● Login of admin.
Software Requirements Specification for Blood Bank Page 5

● Blood Donor.
● Change the login password of the admin.
● Register the donor by himself.
● Register the donor by system admin.
● Login of the donor.
● Change the login password of the donor.
● Change personal contact details by the donors himself.
● Change personal contact details by the system admin.
● Withdraw reg. details by the donor.
● Withdraw reg. details by the admin.

4.2 System Feature 2 (and so on)

There are some features of blood bank management system are :

● Generating reports on stock- blood group wise, area wise and expiry date wise.
● Donor database-blood group wise and area wise.
● Improved the Effectiveness and Efficiency of blood banks- faster response time and better control.
● Accurate database/Record management.
● Blood cross match and result storage facility.
● Comprehensive donor database with search facility.
● Improve blood bank processes by providing efficient and continuous software support

5. Other Nonfunctional Requirements

A characteristic of a quality SRS is that in addition to describing the functional requirements of a system, it
will also provide detailed coverage of the non-functional requirements. In practice, this would entail detailed
analysis of issues such as availability, security, usability and maintainability.

5.1 Performance Requirements

● The system is interactive and the delays involved are less.

● When connecting to the server the delays is based editing on the distance of the two
System configuration between them so there is high probability that there will be or not
Software Requirements Specification for Blood Bank Page 6

a successful connection in less than 20 seconds for the sake of good communications

5.2 Safety Requirements

● The blood request queue screen, from where all the daily transfusions can be handled.

● Fresh blood and stored blood request processing.

● Blood returns are made easy in the blood bank management system.

● Transfusion detailed and charging.

● Destruction Details.

● Blood bank management system is integrated with lab module for blood cross match
and grouping

5.3 Security Requirements

Blood Bank does not have security requirements for users and thus any type of user can use it without any
additional privileges.

5.4 Software Quality Attributes

The system will posses some quality attributes to the users :

● Reliability :

The system has the ability to work all the time without failures apart from network failure.
A donor can have faith in the system. The authorities will keep the privacy of all donors in a proper
manner.
● Robustness :
The entire system includes every function which is always help to the system to
work correctly and strongly in all conditions.

.
Software Requirements Specification for Blood Bank Page 7

6. Other Requirements

Security: The system doesn’t have a tight security system. Because People who log into the system are
volunteers who like to donate blood for innocent patients. But The system consists of some security features.
● Any donor can’t see any details of any other donor.
● If a donor doesn’t manage to provide hi user name and a password in three times
the user automatically will log out from the website.