Android Application for VU Blood Donation Society

Software Requirements Specification

Version 1.0

Group Id: S2402907B1 (BC210205874,BC210206522)

Supervisor Name : Abdur Rafay

 Revision History
Date Versio Description Author
(dd/mm/yyyy n
)
20/05/2024 1.0 The Software Requirements Specifications (SRS), Bc21020587
also referred to as SRS, constitutes a
comprehensive exposition detailing the software
product slated for development. It serves as a
foundational element within the software
development lifecycle (SDLC), akin to a
navigational blueprint steering towards the ultimate
product realization.

The "Android Application for VU Blood Donation

Society" endeavors to revolutionize and optimize
blood donation management via an automated
system. This initiative confronts the deficiencies
entrenched within conventional blood bank
methodologies, notably archaic data input
methodologies and the conspicuous absence of
online donor repositories. It endeavours to rectify
these shortcomings by furnishing a dynamic
platform facilitating real-time interactions between
donors and recipients.
 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:
The "Android Application for VU Blood Donation Society” aims to create
an easy-to-use platform for managing blood donation tasks. It will enable
smooth communication between donors, patients, and administrators.

User Registration and Authentication

Donor Registration and Approval
Donors sign up by providing their details, and admins approve their accounts
for accuracy and security.
Patient Registration:
Patients register by giving personal and medical info for blood request
managing their profiles like donors.

Donor Profile Management:

Donors update their profiles, including personal info and donation history.
The app keeps track of their last donation date, frequency, and eligibility.
These changes provide a simplified overview while maintaining the
necessary details.

Non Functional:-

1. Performance:

 Response time: The system should respond to user interactions

within 2 seconds.
 Throughput: The system should handle at least 1000 concurrent user
requests per minute.
 Scalability: The system should be able to scale horizontally to
accommodate increasing user loads.
 Resource usage: The system should not consume more than 50% of
CPU and memory resources under normal operation.

2. Reliability:

 Availability: The system should be available 99.99% of the time,

excluding scheduled maintenance.
  Fault tolerance: The system should continue to operate in the event
of hardware or software failures.
3. Security:

 Authentication: Users should be required to authenticate with a

username and password.
 Authorization: Access to sensitive data should be restricted based on
user roles and permissions.

4. Usability:

 User interface: The user interface should be intuitive and easy to

navigate.

5. Scalability:
 The system should be able to handle a tenfold increase in user traffic
without significant performance degradation.

Use Case Diagram(s):

Usage Scenarios:

Use Case Title Donor Registration

01
Use Case Id

User
Actors
Donor registers with the application providing necessary details.
Description

Donor fills out registration form.

Actions

Alternative N/A
Paths
Pre-Conditions Donor must not be registered previously.
Post Conditions Donor is registered successfully.
Author BC210205874
Registration form submission failure due to network issues or
Exception server errors.
Use Case Title Donor Login

02
Use Case Id

User
Actors
Donor logs in to the application using their credentials.
Description

Donor enters username and password.

Actions

Alternative N/A
Paths
Pre-Conditions Donor must be registered and approved by the administrator.
Post Conditions Donor successfully logged in.
Author BC210205874
Incorrect username/password combination, account not yet
Exception approved by administrator.
Use Case Title Donor Profile modifification

03
Use Case Id

User
Actors
Donor updates their profile information or donation history.
Description

Donor navigates to profile settings.

Actions

Alternative N/A
Paths
Pre-Conditions Donor must be logged in.
Post Conditions Donor profile is updated successfully.
Author BC210205874
Failure to save changes due to server errors or invalid data
Exception format.
Use Case Title Blood Donation Notification

04
Use Case Id

User
Actors
Donor receives notifications regarding blood donation requests
Description matching their blood group and location preferences.

Donor enables notification settings.

Actions

Alternative N/A
Paths
Pre-Conditions Donor must be logged in.
Post Conditions Donor receives relevant notifications.
Author BC210205874
Failure to receive notifications due to device settings or app
Exception permissions.
Adopted Methodology

Agile methodology is a good fit for creating the PHP-Based Web Page Speed Analysis
Tool for SEO.

Here's why:

1. Flexibility:

Agile methods, like Scrum, are great for projects like building a PHP-based web tool for
page speed analysis because they’re flexible. Here’s why:

1. **Step-by-Step Development**: Agile breaks the project into smaller parts called
sprints, each delivering a usable piece of the tool. This way, we can keep
improving it based on user feedback.

2. **Teamwork**: Agile stresses teamwork among developers, testers, and

stakeholders. Since this project involves different areas like web development and
SEO, good teamwork is key.

3. **Listening to Users**: Agile encourages getting feedback from users early and
often. This helps ensure the tool meets their needs, providing useful insights for
SEO and an easy-to-use interface.

4. **Staying Up-to-Date**: In the fast-changing world of web tech and SEO, Agile
lets us adapt quickly. We can add new tech or practices as they emerge.

WATER FALL MODEL:

The Waterfall Model is the first Process Model introduced in software development. It’s
straightforward and follows a step-by-step approach. Each phase must finish before the
next one starts, with no overlap. It’s like following a set path with no turning back. This
model represents the software development process in a linear sequence, meaning each
phase begins only after the previous one ends.

SPIRAL MODEL:
The Spiral Model is adopted in software development to manage risks effectively. It
features two dimensions: the Radial dimension tracks cumulative costs, while the
Angular dimension monitors progress. This model runs development and maintenance
concurrently, making it ideal for large-scale and in-house software projects.
VU PROCESS MODEL:
The VU Process Model serves as a structured framework in software development,
providing guidance throughout the development journey. It stands on the principles of
validation and updating, emphasizing the cyclical and iterative nature inherent in
software development endeavors. This model is often utilized in tandem with established
methodologies such as the V-Model or other software development lifecycle models,
enhancing the development process’s efficiency and effectiveness.

The VU Process Model encompasses several discernible phases, each contributing to the
overall development process:

1. Validate Requirements:
In this initial phase, thorough scrutiny is applied to the project’s requirements.
The aim is to ensure that they are comprehensive, coherent, and realistically
achievable within the project’s constraints. This validation step lays the
groundwork for subsequent development activities, establishing a clear
understanding of what needs to be accomplished.

2. Validate Design:
Following the validation of requirements, the focus shifts towards evaluating the
proposed design solutions. Here, the design is scrutinized to verify its alignment
with the validated requirements and its technical feasibility. This phase acts as a
bridge between conceptualization and implementation, ensuring that the design
blueprint is robust and capable of realizing the project’s objectives.

3. Validate Implementation:
The final phase of the VU Process Model centers on validating the actual
implementation of the software solution. This involves rigorous testing and evaluation to
ascertain that the developed software aligns with the validated requirements and operates
effectively in real-world environments. Any discrepancies or issues identified during this
phase are addressed promptly, ensuring the delivery of a high-quality and reliable
software product.

By adhering to the principles of validation and updating throughout its iterative phases,
the VU Process Model facilitates the systematic development of software solutions,
ultimately leading to enhanced project outcomes and stakeholder satisfaction.

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