Blood Bank System

Software Requirements Specification

Version 1.0

Group Id: F1902E334F (BC140401378)

Supervisor Name: Mukaram Shah

 Revision History
Date Version Description Author
(dd/mm/yyyy)
20/11/2019 1.0 Introduction of the project BC140401378
 Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS Document

Scope of Project:

“And whoever saves one - it is as if he had saved mankind entirely”. Al-Quran

We all know that blood is an important factor/element that is very vital in the life of
every human being living on this earth. Nowadays, we see that lots of people lose their
precious life without getting the blood at the right time. Sometimes, proper contact or
record of the blood donors is not available at the time of need. To solve all these
problems on time, it is necessary that there must be a blood bank related mobile
application, which can be of great help in this regard. It can also help in saving the
precious lives of the people, by getting the blood at the right time.

Functional and non Functional Requirements:

Functional Requirements:
This system should have the following features.
1. The system should have a user registration process in order to get login into the
system.

Non-Functional Requirements:
1. Android Studio and MySQL required for development of this application.
2. It has scalability, capacity and availability.
3. It has maintainability
4. All the app data should be secured and be encrypted with minimum needs so that
it’s protected from outside environment also from internal attack.
5. Application should be responsive to the user Input or to any external interrupt
which is of highest priority and return back to same state
6. There should be a common plane where the user can access your application to
install and look for regular updates give feedback e.g. Play Store
7. Interface should be user friendly.

Use Case Diagram(s):

<Provide here the use case diagram of your system>

Usage Scenarios:

<Provide here the usage scenarios of all use cases in table format explaining
Use Case title, Use Case Id, Actions, Description, Alternative Paths, Pre and
Post Conditions, Author, Exceptions. You are supposed to provide a usage
scenario for each of use case shown in use case diagram>
Adopted Methodology
<Write here detail about the adopted methodology for your project. You
must choose VU Process Model which is a combination of waterfall and
spiral models. More or combining two or more methodologies is explained
in SE2 (CS605) handouts. >

Work Plan (Use MS Project to create Schedule/Work Plan)

<Provide Gantt chart of your final project>