0% found this document useful (0 votes)
192 views4 pages

SRS

The document outlines a proposed online system called iDONATE to manage donors, recipients, and charity activities. The system would allow users to register as donors or recipients and interact to raise or request donations. It would also manage blood donations and ambulance driver hiring. Key functions include sharing user locations, sending notifications by SMS/email, and allowing users to make and search for donation requests. The system would be built using PHP with a SQL database on a Windows platform. It aims to provide an easy-to-use and convenient application to facilitate charity services.

Uploaded by

Sevleena B Joy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
192 views4 pages

SRS

The document outlines a proposed online system called iDONATE to manage donors, recipients, and charity activities. The system would allow users to register as donors or recipients and interact to raise or request donations. It would also manage blood donations and ambulance driver hiring. Key functions include sharing user locations, sending notifications by SMS/email, and allowing users to make and search for donation requests. The system would be built using PHP with a SQL database on a Windows platform. It aims to provide an easy-to-use and convenient application to facilitate charity services.

Uploaded by

Sevleena B Joy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Requirements Specification for <iDONATE> Page 1

1. Introduction

1.1 Purpose

The purpose of this proposed work is to build an online system to manage donors and
recipients to ease the communications for charity. The donors and recipients will register in the
system and interact with each other and raise/requests donations. The system consists of two other
modules. One for managing blood donations and the other for hiring ambulance drivers at
emergencies.

1.2 Product Scope

The scope of the proposed system is to ease charity services and to create a convenient and
easy-to-use application for users, trying to donate to charity organizations or to get help from
people. The system is based on a relational database with its user profiles management and user
requests management functions. We will have a system supporting charity organizations as well as
users interested in charity activities. Above all, the system provides a comfortable user experience in
other modules: blood bank and ambulance driver hiring. There will be separate storage in the
database for each module.

2. The Overall Description

2.1.1 Product Perspective

A proposed system stores the following information:

 Organizations:
It includes the registrations for organizations in the system, along with the interaction with
other organizations as well as users to donate or get help. Only organizations can register as
recipients.
 Individuals:
It includes individual user registration. They also will interact with each other and
request/raise donations.
 Requests:
It includes the management of donation requests from the recipients as well as donation
broadcasts from donors.

2.1.2 Product Functions

 Shares locations of users when needed.


 Sends OTP to the mobile number while user registers in the system.
Software Requirements Specification for <iDONATE> Page 2

 Sends important notifications to users as SMS/email.


 Users can raise/request donation services, blood donation and ambulance services.

2.1.3 Operating Environment

Hardware requirements

The minimum hardware requirements are:


o Processor: Intel Pentium
o Storage: 1.5 GB Hard Disk space
o Memory: 1 GB RAM
Software requirements
o Operating system: Windows
o Database: SQL database
o Platform: PHP
o Software used: Adobe Dreamweaver CS6, WAMP

3. Functional Requirements
 The functions that will be performed by various types of users of the product are listed 
below:
o ADMIN MODULE

 Views the registration requests from the users and accept the requests
 Can remove the user profiles at any time, view the feedbacks from users

o USER MODULE

 Donor
 Can be individuals or organizations
 Can raise notifications about donations
 This notification will reach every users home page (those who
registered as recipients/both)
 Provide details about the donation
 Search recipients: individual/organization who wants help
 Automatically/manually removes the raised notifications after
completion of the required task
 Shares the contact/location details to a recipient who first accepts the
request
 Recipient
 Can be individuals or organizations
 Can raise their needs as requests to the ‘donor’ category users
 Search donors: who already raised notifications on our current needs
 Automatically/manually removes the need requests
Software Requirements Specification for <iDONATE> Page 3

 Shares the contact/location details to a donor who first accepts the


request

o OTHER MODULES

 Blood Bank
 Blood donor
o It can be normal users of the system.
o They can login and view blood requests from other users or
from hospitals.
o They can get the location if they respond to the request.
 Blood recipient
o It can be normal users or organizations such as hospitals.
o Can register profile and request other users by specifying the
blood groups, quantity needed, etc.
o Notification goes to the users with that particular blood group.
o Recipient location will be shared to the donors when the donor
responds to the request.

 AMBULANCE DRIVER HIRING


 User
o Search for ambulance drivers
o Shares the location
o Requests for service
 Ambulance drivers
o Receives requests
o View and accept request
o Shares contact information to the user

4. Nonfunctional Requirements

4.1 Performance Requirements

The main performance requirements that the product should satisfy are:

- Accuracy: Accuracy in functioning and the nature of user-friendliness should be maintained in


the system.
- Speed: The system must be capable of offering speed.

4.2 Quality Requirements

The most important quality requirements that the system should satisfy are:
Software Requirements Specification for <iDONATE> Page 4

- Scalability: The software will meet all of the functional requirements without an unexpected 
behavior.
- Maintainability: The system should be maintainable. It should keep backups to atone for 
system failures, and should log its activities periodically.
- Reliability: The acceptable threshold for down­time should be long as possible. i.e. mean 
time between failures should be large as possible. And if the system is broken, time required
to get the system back up again should be minimum.
- Testability: The proposed system should be properly tested under various circumstances in 
order to assure its reliability.  

5. Conclusions
With the busy lifestyle of people, iDONATE will be more and more essential now-a-days,
where donor can easily search and find places that he can donate money, organs, food, etc. and the
recipient can search and find the donors of the things he need. iDONATE also solves the problem of
users finding difficult to communicate with people in emergency cases such as need of blood, need of
ambulance, etc. All these activities are together available at your fingertips while using the system.
The design of this system is very simple and user-friendly too, which make it more efficient. Thus, we
can say that iDONATE has a great scope in future for the users and the charity organizations.

You might also like