PDF Archive

Easily share your PDF documents with your contacts, on the Web and Social Networks.

Share a file Manage my documents Convert Recover PDF Search Help Contact



16001095 .pdf


Original filename: 16001095.pdf
Title: Software Requirement Specification
Author: Sanjaya Hashan

This PDF 1.5 document has been generated by LaTeX with hyperref package / pdfTeX-1.40.17, and has been sent on pdf-archive.com on 10/11/2017 at 13:46, from IP address 112.135.x.x. The current document download page has been viewed 242 times.
File size: 485 KB (17 pages).
Privacy: public file




Download original PDF file









Document preview


Web Based Blood Donation System

2016/CS/109

SOFTWARE REQUIREMENTS
SPECIFICATION
for
Web Based Blood Donation
System
Prepared by Perera R.S.H.
Assignment 1
16001095
2016/CS/109
November 10, 2017

1

Contents
1. Introduction
1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2. Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3. Definitions, Acronyms and Abbreviations . . . . . . . . . . . . . . . . . .

3
3
3
3

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

.
.
.
.
.
.

4
4
5
5
5
6
6

3. Specific Requirements
3.1. Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7
7

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

4. External Interface Requirements
13
4.1. User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Other Nonfunctional Requirements
5.1. Performance Requirements . .
5.2. Safety Requirements . . . . . .
5.3. Security Requirements . . . . .
5.4. Software Quality Attributes . .

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

14
14
14
14
14

A. Appendix A: Use Case Diagram

15

A. Appendix B: Class Diagram

16

2

1. Introduction
1.1. Purpose
Main purpose of this system is to help the patients who need blood by finding them a
suitable donor.
This document is meant to delineate the features of WBBDS, to serve as a guide to the
developers on one hand and a software validation document for the prospective users on
the other.

1.2. Project Scope
In Scope :
• Managing Donors and Patients
• Giving alerts to the blood donors
• Providing a option to indicate about the donors decision

1.3. Definitions, Acronyms and Abbreviations
• WBBDS - Web Based Blood Donation System
• SRS - Software Requirements Specification
• HC - Health Certificate
• MB - Mega Byte
• MHz - Mega Hertz
• Domain - The website which is hosting the system

3

2. Overall Description
2.1. Product Perspective
This system mainly focuses on donors and how to encourage them towards donating
blood. The system will help the blood banks to make connection bertween them and
Donors.
The system also have some hardware and software requirements as well. A printer, a
SMS indicator, SMS Gateway, Email Gateway.

4

Web Based Blood Donation System

2016/CS/109

2.2. Product Functions
Class of Use cases
Use cases related to
system authorization of
admin
Use cases related to
registration of a donor

Use cases related to
login of a donor
Use cases related to
change details of a
donor
Use cases related to
withdraw details of a
donor
Use cases related to inform donation
Use cases related to
health certificates
Use cases related to
Printing

Use cases
Admin Login
Change admin password
Register the donor by
himself
Register the donor by
system admin
Login of donor
Change password
Change details by donor
himself
Change details by system admin
Withdraw details by
donor himself
Withdraw details by
system admin
Send blood donation details to the relevant
donor
Replace donors’ health
certificates
Print Details

Description
Log administrator into the system
Change the login password of system administrator
Store personal, contact, medical details of donors
Store personal, contact, medical details of donors
Log donor into the system
Change password and update
database
Change Blood, personal details of
the donor and update the database
Change Blood, personal details of
the donor and update the database
Delete the donor details from the
DB
Delete the donor details from the
DB
Inform the donors with required
blood group
Update the current health conditions of a perticular donor
Print the details of the registered
donors

2.3. User Classes and Characteristics
• The main system users are system admin and registered donors. Donors should
get used to the UI of the system in order to use the system efficiently.
• Donor should be able to attend the donation in a very short notice and time

2.4. Operating Environment
The software is Web Based so it should also be compatible with mobile browsers. (formatted)

CHAPTER 2. OVERALL DESCRIPTION

5

Web Based Blood Donation System

2016/CS/109

2.5. Design and Implementation Constraints
• The system will be written mainly using php, SQL, HTML, javascript
• The developed system will run on a web server
• Users will need internet to use the system
• Every user will get an username and password

2.6. Assumptions and Dependencies
• Every donor has a mobile phone and email acoount
• The system will not keep information about the collected blood
• WBBDS is a single user software

CHAPTER 2. OVERALL DESCRIPTION

6

3. Specific Requirements
3.1. Functional Requirements
Use Case 1 :
Primary actor
Pre Condition
Main scenario

Admin Login
: System Administrator
: Internet connection should be available
:

1. Visit the system domain
2. Click login command
3. The system will ask for the username and password
4. User enters the login details asked
5. The system will do the user authorization
6. Redirect to the admin home
Alternate Scenario:
1. Failed Authorization
a) If the authorization fails, the system will display a message
b) 3 login attempts will be given to enter the correct login credentials
2. New passwords doesn’t match
a) A message will be displayed
Use Case 2 : Change Admin Login password
Primary actor : System Administrator
Pre Condition : Internet connection should be available
Main scenario :
1. Admin log into the system using the current username and password
2. Admin selects the option to change the current password
3. The system will ask to type the current password in use
4. then the new password twice

7

Web Based Blood Donation System

2016/CS/109

5. system authenticates
6. The new password will be stored in the system
Alternate Scenario:
1. Failed Authorization
a) The system will display a message
2. New passwords don’t match
a) Allow the Admin to re enter password
Use Case 3 : Donor Registration
Primary actor : User (Donor)/ Admin
Pre Condition : Internet connection should be available
Main scenario :
1. User visits the domain
2. User click on ’register new user’
3. The user will be redirected to the forms and questionnaires
4. User input the answers
5. system authenticates
6. System will ask for the health certificate
7. User submits the relevant documents
8. system authenticates
9. documents will be sent to the relevant parties through email for confirmation
10. The relevant parties will send approval
11. Details will be inserted into the DB.
12. a confirmation email and SMS will be sent to the donor including username and
password
Alternate Scenario:
1. Unanswered Questions
a) The system will display a message
2. Invalid email/ Phone
a) The system will display a message

CHAPTER 3. SPECIFIC REQUIREMENTS

8

Web Based Blood Donation System

2016/CS/109

3. Non submission of documents
a) 1.The system will display a message
4. Rejected Document approval
a) The user will be informed to re-register
b) The entered data will not be stored
Use Case 4 : Donor Login
Primary actor : User (Donor)
Pre Condition : Internet connection should be available
Main scenario :
1. Visits the domain
2. Select login as a user
3. The system will ask for the login credentials
4. User provides the information
5. system authenticates
6. User will be redirected to the Home
Alternate Scenario:
1. Failed Authorization
a) If the authorization fails, the system will display a message
b) 3 login attempts will be given to enter the correct login credentials
Use Case 5 : Change Donor Login password
Primary actor : Donor
Pre Condition : Internet connection should be available
Main scenario :
1. Donor log into the system using the current username and password
2. Selects the option to change the current password
3. The system will ask to type the current password in use
4. then the new password twice
5. system authenticates
6. The new password will be stored in the system
Alternate Scenario:

CHAPTER 3. SPECIFIC REQUIREMENTS

9


Related documents


16001095
wire frame document for donation website pdf
05203910
48i16 ijaet0916939 v6 iss4 1869to1875
eye donation in gurgaon
egg donation program pdf


Related keywords