Online Blood Donation System (OBDS)

Software Requirements Specification

Asif Amin 10-CS-07 (M)
Mariam Salamat 10-CS-30 (E)

Table of Contents

Introduction ..................................................................................................................................... 3
Purpose ........................................................................................................................................ 3
Scope ........................................................................................................................................... 3
Overall Description ......................................................................................................................... 4
Functional Requirements ................................................................................................................ 6
User Accounts and Login ........................................................................................................... 6
Library Data Maintenance ........................................................................................................... 6
Viewing Books ........................................................................................................................... 6
Bookings and Waitlists................................................................................................................ 7
Alerts and Notifications .............................................................................................................. 7
Reviews ....................................................................................................................................... 7
Non Functional Requirements ........................................................................................................ 7
Usability ...................................................................................................................................... 7
Reliability .................................................................................................................................... 8
Performance ................................................................................................................................ 8
Design Contents .......................................................................................................................... 9
Online Help and Documentation ................................................................................................. 9









Introduction
Purpose
This document is meant to delineate the features of OBDS, so as to serve as a guide to the
patients especially patients of the Hemophilia, Thalassemia, Cancer, Anaemia and many other
blood diseases. The Online Blood Donation System (OBDS) web application is intended to
provide complete solutions for patients as well as donors through a single get way using the
internet. It will enable patients to enter the detail information of the patient, keep searching the
donors and contact with donors; Donors to browse a needy patient to donate; management to
make an appointment with donors and patients for blood circulation, maintain the data base
online.
The purpose of this Software Requirements Specification (SRS) document is to
describe the overall behavior of the OBDS. This SRS defines and describes the operations,
performance, and quality assurance requirements of the FYPR that is to be developed. This
document also describes the nonfunctional requirements. It also describes the design constraints
and technologies that are to be considered when the system is to be designed, and other
factors necessary to provide a complete description of the requirements for the system. This
Software Requirements Specification (SRS) captures the complete software requirements
for the system. Requirements described in this document will be used as guidelines to develop
the OBDS.
Scope
The Online Blood Donation System (OBDS) web application is intended to provide
complete solutions for patients as well as donors through a single get way using the internet. It
will enable patients to enter the detail information of the patient, keep searching the donors and
contact with donors; Donors to browse a needy patient to donate; management to make an
appointment with donors and patients for blood circulation, maintain the data base online.
The features that are described in this document will be used in the future phases
of the software development cycle. The features described here meet the needs of all the users.
The success criteria for the system is based in the level up to which the features
described in this document are implemented in the system.
Goal
Goal of this purposed system is to provide blood to all patients having blood diseases so
that they dont have to suffer for their life.
Additional Information
The system works on internet server, so it will be operated by any end user who has the
internet access.
Overall Description
General Description
Our proposed system is a Web-based system Online Blood Donation System (OBDS)
which will replace the current manual system. The manual system is messy and time consuming
with lack in efficiency. The main objective of this project is to engage all parties in one
collaborative online system as a medium in exchanging information for donation of blood. The
system will consist of detail of available donors, detail information of patients, reports of blood
donations, appointment detail of patients and donors as well as graph of last few years blood
donations. The system will also be used for the communication between the donor, patient and
administration which are working to manage this system. The patients can report any donor if
S/He is not available. Administration committee can view all the reports and take some steps
about the donors and patients to solve the problem. The donor can view their blood information
to whom it is given and patients can view the detail of donors for their perspective.
Administrator will be managing the system with the task of handling user registrations
and accounts. User verification will secure the system. This web enabled project and its
associated features are strongly worth, feasible and relevance in fulfilling the endeavours of the
parties concerned.
User characteristics
The users of the system are Patients, Donors and administration (doctors, blood bankers
etc.) who maintain the system. The donors and patients are assumed to have basic knowledge of
the computers and Internet browsing. The administrators of the system will have more
knowledge of the internals of the system and will be able to rectify the small problems that may
arise due to disk crashes, power failures and any other reasons. The proper user interface
and online help must be sufficient to educate the users on how to use the system without any
problems.
Constraints
The information of all the users must be stored in a central database that is
accessible by the OBDS.
The OBDS is hosted on one main server and is running all 24 hours a day.
The users can access the OBDS from any computer that has Internet browsing
capabilities and an Internet connection.
The users must have their correct usernames and passwords to enter into the
OBDS.
The system must provide correct real world data and should take care of concurrency
issues.
Functional Requirements
Donor creates an account.
Patient creates an account (Optional).
Donor and Patient can update his/her personal information.
System must accurately update the donors list on daily basis.
Data base must be updated when a donation has been occurred.
System must be able to search for a donor with some aspects e.g. cities, blood
group etc.
List of donors will be available on a single click.
Detailed information of patients and donors for interaction in between them.
Easy access to the management.
Description
Registration
Donors and Administration must get registered and patients have an option to get register
or not. They may upload information without registration; unregistered user will have limited
access, can just see a short detail.
Login
Users login to the system by entering valid user id and password.
Data maintenance
The system will provide interfaces to access and maintain data related to various
aspects of system.
Viewing information
The system will provide a clear and neat interface to access and view detail depending upon
blood group, city, and patient.
Alerts and Notifications
Automatic alerts will be sent to the students, advisor and project committee.
Interface Requirement
Various interfaces for the product could be-
1. Login Page
2. Registration Form
3. There will be a screen displaying information about donors, patients and reports of
donations held.
4. The progress of the donations made make by the donors.

The System must run over the internet, all the hardware shall require to connect internet
will be hardware interface for the system. As for e.g. Modem, WAN LAN, Ethernet Cross-
Cable.
Software Interface
Asp.Net (MVC)
C#.Net
HTML5 / CSS3
SQL
Coral Draw / Adobe Photoshop (optional)
Design Constrain
The system shall be built using a standard web page development tool that conforms to
Microsofts GUI standards like HTML, XML etc.
1. Design Constraints
a. Software Language Used
The languages that shall be used for coding the Online Blood Donation System
are Asp.Net, C#, HTML/CSS and MYSQL database.
b. Development Tools
We will make use of the available .Net Framework. Also we will make use of the
online references available for developing programs in .Net Framework and
MVC.
Non Functional requirement
Security
1. The system use SSL (secured socket layer) in all transactions that include any
confidential customer information.
2. The system must automatically log out all customers after a period of inactivity.
3. The system should not leave any cookies on the customers computer containing the
users password.
4. The systems back-end servers shall only be accessible to authenticated administrators.
5. Sensitive data will be encrypted before being sent over insecure connections like the
internet.
Reliability
1. The system provides storage of all databases on redundant computers with automatic
switchover.
2. The reliability of the overall program depends on the reliability of the separate
components. The main pillar of reliability of the system is the backup of the database
which is continuously maintained and updated to reflect the most recent changes.
The system has to be very reliable due to the importance of data and the damages that can be
caused by incorrect or incomplete data.

Availability
The system should be available at all times, meaning the user can access it using a web
browser, only restricted by the down time of the server on which the system runs. In case of a
hardware failure or database corruption, a replacement page will be shown. Also in case of a
hardware failure or database corruption, backups of the database should be retrieved from the
server and saved by the administrator. Then the service will be restarted. It means 24/7
availability.
Maintainability
A commercial database is used for maintaining the database and the application server
takes care of the site. In case of a failure, a re-initialization of the program will be done. Also the
software design is being done with modularity in mind so that maintainability can be done
efficiently.
Portability
The application is HTML and scripting language based. So the end-user part is fully
portable and any system using any web browser should be able to use the features of the system,
including any hardware platform that is available or will be available in the future.
An end-user is using this system on any OS; either it is Windows or Linux.
The system shall run on PC, Laptops, and PDA etc.
Usability
The system shall allow the users to access the system from the Internet
using HTML or its derivative technologies like XML/CSS. The system uses a
web browser as an interface.
Since all users are familiar with the general usage of browsers, no special
training is required.
The system is user friendly and online help makes using the system easy.
Accuracy
The system should accurately provide real time information taking into consideration
various concurrency issues.
Operational Scenario
The customer wants to buy item. The system shows all product categories to customer. If
customer select item then they listed in shopping cart for buying.
The payment will made with credit card or bank check. If customer wants to cancel the
order before shipping then he or she can cancel it.
Customer can see the buying report on account detail.

*****