1

1. Introduction
1.1 Purpose
The main purpose of this Software Requirements Specification (SRS) document is to specify requirements of the Blood Donation System (BDS) required by National Blood Transfusion Service. Its role is to describe the problem to be solved; not the solution. That is “what the system must do; not how”.
In this document the requirements are explained very clearly in a way that everyone can understand easily and describes both functional and nonfunctional requirements allocated to the product.
This document is intended to be used mainly by the members of the project team that will implement and verify the correct functioning of the system as well as the client to ensure final product meets the requirements that are stated. All requirements specified here are high priority and committed for release 1.0.

1.2 Document Conventions
The content of this document are written using font “Times New Roman” in 12 pts size, Sub Section Titles using font “Times New Roman” in 14pts size and Main Section Titles using font “Times New Roman” in 18 pts size. The titles are in bold letters to emphasize.
1.3 Intended Audience and Reading Suggestions
The intended audiences of this Software Requirement Specification for blood donation system are

1. The developing team
The team shall refer this document during the implementation phase to verify whether the system is developed according to the functional and non-functional requirements mentioned in this document.

2. Testers
Testing is done after the development of the system. Before the handing over the system the testers check whether the output given by the system is with accordance to what is declared in this document or not.

3. Document writers
When writing the user manual and the final report, this document shall be used.

4. Project Supervisor
The supervisor shall refer this document to find out whether the developing team is working on the project as stated.

5. Relevant personnel in National Blood Transfusion Service who is the client.
If any changes are needed to be made in the system requirements mentioned in this document, the administrator shall use this document for reference and inform the development team about the changes needed. And when Acceptance testing is taken place, soon after the development of the system, client shall refer this document to verify whether the requirements are satisfied or not.

Since the SRS is a legal document between the Client and the Developing Team, it will be frequently reviewed by the above audience to check if the different phases or stages of the project are being completed by meeting the given requirements.

When the Structure of the document is considered,
• To get an overall idea and a better understanding about the system, reading the whole document is suggested.
• To get an idea about the system features and the nonfunctional requirements of the system, reading Section 3 (External Interface Requirements), Section 4 (System Features) and Section 5 (Nonfunctional Requirements) of this document is suggested.
• All the technical terms and acronyms used in the document are described in Appendix A: Glossary(Section 6)
1.4 Project Scope
This web based software system completely replaces the manual effort in serching donors. This will manage database of information of blood donors. Users of BDS are registered donors and system administrator. Donor should register in to the system first by themselves or by providing details to the system admin. When relevant hospitals or doctors request specific blood types system administrator able to identify donors with the blood group as request and can send sms and email to the relevant donors. Once donor received the sms and email can log into the system and indicate the willingness. Those who willing to donate blood will be informed the details of donation that going to take place. Necessary system update will carry out by system admin. The main benefits of this system are efficiency in handling donor information, data security, stability and reliability and report generating capability.
1.5 References
2. Overall Description
2.1 Product Perspective
The proposed Blood donation system is developed to replace a traditional manual process of finding donors to collect blood. The user who uses the system should first log in to the system to perform specific task they assign to do.
2.2 Product Features
There will be only two user level that will be using this product. The features that are available to the administrator are
? Registration of donor.
? Send alerts of blood request
? Withdraw donor from the list.
? Search donors.
? Update database.
? Generate reports.
The features that are available to the donor are
? Get registered in to the system.
? Update own details.
? Withdraw from the registered list.
? View donation history report.

2.3 User Classes and Characteristics

2.4 Operating Environment
This Blood donation system is developed to run on Microsoft windows XP or higher operating systems. To store data system uses database server (Microsoft SQL server 2008). Client machine should have proper internet connection and web browser to access the web site.
2.5 Design and Implementation Constraints
– The system shall use a Pentium IV or Higher CPU, 512MB of RAM and shall be installable on any Windows based computer in the School.
– The system shall have an object oriented database and use Microsoft SQL server as the database engine.
– All programming logic, coding and processing shall be in C# using Microsoft visual studio 2010.
– .NET Framework 2.0 or higher shall be installed in order to run the system.
– System shall use a login facility to restrict unauthorized access.
– The System shall display error messages to the user when an error is detected