Software Requirements Specification

Software Requirements
Specification
For
BLOOD BANK MANAGEMENT SYSTEM
Version 1.0 approved
Prepared by
11702 Faizan Kamal

11116 Adeel Khan
Karachi Institute of Economics and Technology
12 January, 2023
Software Requirements Specification for Blood Bank Management System Page 1
Table of Contents
Table of Contents ...........................................................................................................................1
Revision History .............................................................................................................................1
1. Introduction ................................................................................ Error! Bookmark not defined.
1.1 Purpose............................................................................................Error! Bookmark not defined.
1.2 Document Conventions ...................................................................Error! Bookmark not defined.
1.3 Intended Audience and Reading Suggestions .................................Error! Bookmark not defined.
1.4 Product Scope .................................................................................Error! Bookmark not defined.
1.5 References .......................................................................................Error! Bookmark not defined.
2. Overall Description .................................................................... Error! Bookmark not defined.
2.1 Product Perspective.........................................................................Error! Bookmark not defined.
2.2 Product Functions ...........................................................................Error! Bookmark not defined.
2.3 User Classes and Characteristics ....................................................Error! Bookmark not defined.
2.4 Operating Environment ...................................................................Error! Bookmark not defined.
2.5 Design and Implementation Constraints .........................................Error! Bookmark not defined.
2.6 User Documentation .......................................................................Error! Bookmark not defined.
2.7 Assumptions and Dependencies .....................................................Error! Bookmark not defined.
3. External Interface Requirements ............................................. Error! Bookmark not defined.
3.1 User Interfaces ................................................................................Error! Bookmark not defined.
3.2 Hardware Interfaces ........................................................................Error! Bookmark not defined.
3.3 Software Interfaces .......................................................................................................................... 5
3.4 Communications Interfaces ............................................................................................................. 5
4. System Features ......................................................................... Error! Bookmark not defined.
4.1 System Feature 1 .............................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on) ..........................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements ......................................... Error! Bookmark not defined.
5.1 Performance Requirements .............................................................Error! Bookmark not defined.
5.2 Safety Requirements .......................................................................Error! Bookmark not defined.
5.3 Security Requirements ....................................................................Error! Bookmark not defined.
5.4 Software Quality Attributes ............................................................Error! Bookmark not defined.
5.5 Business Rules ................................................................................Error! Bookmark not defined.
6. Other Requirements .................................................................. Error! Bookmark not defined.
Appendix A: Glossary...................................................................... Error! Bookmark not defined.
Appendix B: Analysis Models ......................................................... Error! Bookmark not defined.
Appendix C: To Be Determined List .............................................. Error! Bookmark not defined.
Revision History
Name Date Reason For Changes Version
1. Introduction
1.1 Purpose
Blood Bank Management System (BBMS) is a web-based system that can assists the information
of blood bag during its handling in the blood bank. With this system, the user of this system can
key in the result of blood test that has been conducted to each of the blood bag received by the
blood bank.
1.2 Document Conventions
Font Style Size
Heading Times New Roman Bold 18
Sub-Heading Times New Roman Bold 14
Other’s Arial Regular 11
1.3 Intended Audience and Reading Suggestions

This Document has been made for Developers, Project Manager, users, testers, Professor,
Documentation Writer and Client.
1.4 Product Scope

The system calculates the estimated locations of the donors, hospitals and blood banks and
also provides online chat service between donors and consumers
● Simple and easy to operate
● Increase Blood Bank Work efficiencies
● Mobile access, anytime, anywhere
● Search, add, update, and view Blood Stock online
● Helps to manage Blood Bank functions constructively
● Saves time and reduces overheads
● Reduce Blood Bank operating cost

● Customized reports for better management
● Remove manual processes to issue blood and maintain records
1.5 References
https://www.studocu.com/in/document/national-institute-of-technology-rourkela/software-
engineering/online-blood-bank-manamgement-system-srs-report/6935838
https://www.scribd.com/document/408508426/Blood-Bank-Management-System-BBMS
2. Overall Description
2.1 Product Perspective

WBBDS is mainly towards persons who are willing to donate blood to the patients. Through this
system it will be easier to find a donor for exact blood type and easy to build the connection
between donor & the blood bank authorities. The main intend of building this software is too
formal the procedure of blood donation & motivate donors in order to donation blood. The
system also consists of some local system hardware devices as well. A printer & SMS indicator
are the main devices among the other devices. The entire software product includes the all-
relevant features to create a better connection between the blood donor & blood bank
authorities.
2.2 Product Functions
Admin: This module focuses on the both donors & acceptors. Each member in a donor &
acceptor is given a user id and password, which identifies him uniquely. The member is given a
login form. he enters the login details user id and password. . The options given to • Maintain
donor details • Maintain referral once • Update donor details • View Experiences • Logout
Change Password Whenever a user wants to change his / her password he can select the
change password option. The system displays the form, which asks him for his old password
and new password. The system then compares the old password with the existing password in
the database
2.3 User Classes and Characteristics

 User module
In the user module, user will check the availability of the blood.
o Blood donates
o Blood reserve
o Details
 Blood Bank module:

o Add new Blood Bottle
o Remove Blood Bottle
o Update details Blood
 Administration module:
The following are the sub module in the administration module :
o Register user
o Enter Blood Details
o Blood gives
2.4 Operating Environment
Operating System
 Windows Operating System(7/8/8.1/10/11)
Language
 C#
 HTML
 CSS
Hardware
 Intel Core i5
 1.2 GHz processor
 4GB ram
Software
 Microsoft Visual Studio 2022
2.5 Design and Implementation Constraints

The system is developed in C# language and is supposed to work only on Windows OS that has
Microsoft Visual Studio 2013 or higher installed on it.
2.6 User Documentation

It will provide specific guidelines to a user for using the blood bank management system.
2.7 Assumptions and Dependencies

The user must login to their accounts from the system installed in the Blood Bank bounds as the
software is installed on only those systems.
3. External Interface Requirements
3.1 User Interfaces

The system is basically running on the official website of the govt. blood bank. Mainlythere are 2
actors in the
system. The system provides some advance features to the system adminthan the donor. If the
system admin logs
in, the system interface provides some main commandbuttons to the admin. Software Require
ments Specification.
3.2 Hardware Interfaces

Various interfaces for the product could be:
 Monitor
 Keypad
 Mouse
 A connection to the Blood Bank database
3.3 Software Interfaces

 Windows OS(7 or higher).
 Microsoft Visual Studio (2013 or higher) must be installed on the system to run the
application. In addition to that, Xampp should also be installed for easier execution of the
application.
3.4 Communications Interfaces

The communications standards that will be used is GUI (Graphical user interface). This interface
must be highly intuitive or interactive because there will not be an assistance for the user who is
opera ting the system. The interface is designed to be very user-friendly so anyone with a very
little knowledge of the computers can also operate the system. Also, the password should be
private, this can be by using asterisks at the password panel.
4. System Features
4.1 User Registration and Login

4.1.1 Description and Priority
Users are required to register to use the system. This is a high priority feature.
4.1.2 Stimulus/Response Sequences
Click on the register link in the home page of Blood bank ms. A registration form
will be displayed. Enter Details and click on the Submit button in the registration
form. All the entered details will be validated and error messages will be
displayed. If there are no validation errors, the user will be registered and a
successful registration message will be displayed. The control will be forwarded
to home page.
4.1.3 Functional Requirements
FR: Register User
Function Register user as blood bank member
Description Allows users to enter their profile details and

join the system as Donor.
Inputs First Name
Last Name
Email Address
Password
Confirm Password
Date of Birth
Gender
City
State
Blood group
Agree to terms and conditions(Yes or No)
Source Inputs from fields in user registration form

Outputs User Profile created with unique ID number
Destination User profile page
Action User inputs are validated. If the user inputs

are valid, create user profile and the new
donor will be allowed to login and view the
profile page. If any input is invalid, show an
alert message.
4.2 Login
4.2.1 Description and Priority
Users are required to register to use the system. This is a high priority feature.
4.2.2 Stimulus/Response Sequences

Click on the Login link in the home page of BBMS. A login form will be displayed.
Enter Details and click on the Submit button in the login form. All the entered
details will be validated and error messages will be displayed. If there are no
validation errors, the user will be registered and a successful login message will
be displayed. The control will be forwarded to user profile page.
4.2.3 Functional Requirements
FR: Login
Function User login as donor member
Description Allows users to enter their ID number and

password and login to the system as donor
Inputs ID number
Password
Source Inputs from fields in user login form
Outputs User is logged into the system.

Destination User profile page
Action User inputs are validated. If the user inputs

are valid, member will be allowed to login and
view the profile page.
If any input is invalid, show an alert message.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
 Increase User Satisfaction.

 BB must allow citizens to access BB services 24 hours a day.
 Reduce overall costs.
 The same resources of BBMS can be used many times by number of users.
 We have data backup we any data is deleted we can recover the data.
5.2 Safety Requirements

 Backup, recovery and business continuity BB should ensure adequate backup of data as
may be required by their operations.
 Both data and software should be backed up periodically.
 An off-site backup is necessary for recovery from major failure to ensure business
continuity.
5.3 Security Requirements

 System will use secured database.
 Normal users can just read information but they cannot edit or modify anything except
their personal and some other information.
 System will have different types of users and every user has access constraints.
 Proper user authentication should be provided.
 There should be separate accounts for admin and members such that no member can
access the database and only admin has the rights to update the database.
5.4 Software Quality Attributes

The BBMS shall be available to user everyday having some extended time and on time
response. If the connection between user and system gets broken prior to schedule being
confirmed or cancelled the system enables the user to recover a complete order.
6. Other Requirements
Appendix A: Glossary
BBMS : Blood Bank Management System
Github link for Project:
FaizanKamal1/Blood_Bank_Mangement_System: I develop this project using C# asp.net mvc

framework. (github.com)
Live project on this app

https://freeasphosting.net/register.aspx
Live link
https://faizankamal.bsite.net
Use Case Diagram (AS IS)

(TO BE)
Activity Diagram
To be
Sequence Diagram
To Be
State Diagram
Class Diagram
Collaboration Diagram

Software Requirements Specification

Uploaded by

Copyright:

Available Formats

Software Requirements Specification

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specification

Uploaded by

Copyright:

Available Formats

Software Requirements

BLOOD BANK MANAGEMENT SYSTEM

Version 1.0 approved

11702 Faizan Kamal

Karachi Institute of Economics and Technology

1.2 Document Conventions

Font Style Size

Heading Times New Roman Bold 18

Sub-Heading Times New Roman Bold 14

Other’s Arial Regular 11

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope

● Reduce Blood Bank operating cost

2.1 Product Perspective

2.2 Product Functions

2.3 User Classes and Characteristics

 Blood Bank module:

2.4 Operating Environment

 Windows Operating System(7/8/8.1/10/11)

 Microsoft Visual Studio 2022

2.5 Design and Implementation Constraints

2.6 User Documentation

2.7 Assumptions and Dependencies

3. External Interface Requirements

3.1 User Interfaces

3.2 Hardware Interfaces

3.3 Software Interfaces

3.4 Communications Interfaces

4.1 User Registration and Login

4.1.1 Description and Priority

4.1.2 Stimulus/Response Sequences

4.1.3 Functional Requirements

FR: Register User

Function Register user as blood bank member

Description Allows users to enter their profile details and

Inputs First Name

Agree to terms and conditions(Yes or No)

Source Inputs from fields in user registration form

Outputs User Profile created with unique ID number

Destination User profile page

Action User inputs are validated. If the user inputs

4.2.2 Stimulus/Response Sequences

4.2.3 Functional Requirements

Function User login as donor member

Description Allows users to enter their ID number and

Source Inputs from fields in user login form

Outputs User is logged into the system.

Destination User profile page

Action User inputs are validated. If the user inputs

If any input is invalid, show an alert message.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

 Increase User Satisfaction.

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

Github link for Project:

FaizanKamal1/Blood_Bank_Mangement_System: I develop this project using C# asp.net mvc

Live project on this app

Use Case Diagram (AS IS)