SOFTWARE REQUIREMENT SPECIFICATION

FOR

ORGAN DONATOR AND FINDER WEBSITE

PREPARED BY
M.L.PUJASRI
VLSI ‘C’
RMK ENGINEERING COLLEGE

DATE CREATED : 11.10.2023

 INTRODUCTION

PURPOSE
The purpose of the Organ Donor and Finder System is to provide a
platform that connects organ donors with potential recipients,
facilitating the process of organ donation and transplantation. The
system aims to streamline the organ donation process, improve
efficiency, and save lives.

SCOPE
The system will include two main modules: the donor module and
the recipient module. The donor module allows individuals to
register themselves as organ donors, provide information about the
organs they are willing to donate, and maintain their preferences and
availability. The recipient module allows individuals in need of organ
transplantation to register themselves and search for suitable donors
based on their requirements.

OVERVIEW OF THE PROJECT

Organ donation is defined as “When a person allows an organ of
theirs to be removed, legally, either by consent while the donor is
alive or after death with the assent of the next of the kin.”
 DESCRIPTION

PRODUCT PERSPECTIVE
The Organ Donor and Finder System will be a standalone web-based
application. It will interact with a database to store and retrieve
donor and recipient information. The system will also integrate with
external services, such as hospitals and medical centers, for data
validation and verification.

PRODUCT FEATURES
The key features of the system include:
 DONOR REGISTRATION : Allow individuals to register as organ
donors, providing personal information, medical history, and
the organs they are willing to donate.
 RECIPIENT REGISTRATION: Allow individuals in need of organ
transplantation to register themselves, providing personal
information, medical history, and the organs they require.
 DONOR RECIPIENT MATCHING: Provide a search functionality to
match suitable donors with recipients based on various criteria,
such as organ compatibility, geographical proximity, and
medical urgency.
 COMMUNICATION: Enable secure communication between
donors and recipients through the system, allowing them to
exchange information and coordinate the organ transplantation
process.
USER DOCUMENTATION

The Organ Donor and Finder System is an online platform that

connects organ donors with potential recipients, making the organ
donation process more efficient and effective. This document
provides instructions and guidance for organ donors on how to use
the system.

OPERATING ENVIRONMENT

The operating environment of the Organ Donor and Finder System

refers to the software and hardware components required to run the
system effectively. Below are the key components of the operating
environment:
 Web Server
 Database Management System
 Web Browser
 Operating System
 Network
 Security Measures
 Hardware Requirements
 REQUIREMENTS

FUNCTIONAL REQUIREMENTS

 Donor Registration
- The system shall allow individuals to register as organ donors by
providing personal information, medical history, and the organs they
are willing to donate.
- The system shall validate and store the donor information in the
database.

 Donor Preferences
- The system shall allow donors to specify their preferences, such as
organ availability, geographical location, and notification settings.
- The system shall store and maintain donor preferences for
matching purposes.

 Donor Search
- The system shall provide a search functionality for recipients to
find suitable donors based on their requirements, such as organ
compatibility and geographical proximity.
- The system shall display a list of matching donors along with their
contact information.
  Recipient Registration
- The system shall allow individuals in need of organ transplantation
to register themselves by providing personal information, medical
history, and the organs they require.
- The system shall validate and store the recipient information in
the database.

 Recipient Search
- The system shall provide a search functionality for recipients to
find suitable donors based on their requirements, such as organ
compatibility and geographical proximity.
- The system shall display a list of matching donors along with their
contact information.

 Secure Communication
- The system shall provide a secure messaging functionality for
donors and recipients to communicate with each other.
- The system shall ensure the privacy and confidentiality of the
communication.
NON FUNCTIONAL REQUIREMENTS

 Performance
- The system shall be able to handle a large number of users
concurrently without significant performance degradation.
- The system response time for search and communication
functionalities shall be within acceptable limits.

 Security
- The system shall implement appropriate security measures, such
as encryption and access control, to protect user data and ensure the
integrity of the system.
- The system shall comply with relevant data protection and privacy
regulations.

 Usability
- The system shall have a user-friendly interface that is easy to
navigate and understand.
- The system shall provide clear instructions and feedback to users
during the registration, search, and communication processes.
SYSTEM DESIGN
 Donor Registration:

 Procedure: The donor initiates the registration process by

providing personal information, medical history, and the organs
they are willing to donate.
 Steps:
a. The donor accesses the system and navigates to the registration
section.
b. The donor fills in the required personal information, such as name,
address, contact details, and date of birth.
c. The donor provides their medical history, including any relevant
conditions or medications.
d. The donor specifies the organs they are willing to donate.
e. The system validates the donor's information and stores it in the
database.
f. The donor receives a confirmation message indicating successful
registration.

 Donor Preferences:

 Procedure: The donor specifies their preferences regarding

organ availability, geographical location, and notification
settings.
 Steps:
a. The donor accesses their profile or preferences section.
b. The donor indicates the availability of the organs they are willing
to donate (e.g., always available, available upon request).
c. The donor specifies their preferred geographical location for
potential recipients.
d. The donor sets their notification preferences, such as receiving
alerts when there is a potential match.
e. The system stores the donor's preferences in the database.
f. The donor receives a confirmation message indicating successful
preference settings.

 Donor Search:

 Procedure: The donor searches for potential organ recipients

based on their requirements.
 Steps:
a. The donor accesses the search or find recipients section of the
system.
b. The donor selects the organ(s) they are willing to donate.
c. The donor may apply additional filters, such as geographical
proximity or medical urgency.
d. The system retrieves a list of potential recipients matching the
donor's criteria.
e. The donor can view detailed profiles of recipients, including their
contact information.
f. The donor can initiate communication with the chosen recipient(s)
through the system's messaging functionality.
  Communication with Recipients:

 Procedure: The donor communicates with potential organ

recipients to exchange information and coordinate the organ
transplantation process.
 Steps:
a. The donor selects a recipient from the search results.
b. The donor accesses the recipient's profile to view more details.
c. The donor finds the "Contact" or "Message" button to initiate
communication.
d. The donor uses the system's messaging feature to send messages
and exchange information with the recipient.
e. The donor and recipient coordinate the necessary steps for organ
donation, such as medical evaluations, scheduling, and logistics.
f. The donor and recipient continue to communicate through the
system until the organ transplantation process is completed.
SCHEDULE AND BUDGET REQUIRED
 Time duration for completion :
The duration of an organ donation project can range from several
months to multiple years. It depends on factors such as the size of
the system, the number of features and functionalities to be
implemented, the availability of resources, and the complexity of
integrating with existing healthcare systems or databases.

 Budget required :
Determining the budget for an organ donation project requires a
thorough analysis of the project's requirements and scope. The
budget will be influenced by factors such as the size and experience
of the development team, the cost of hardware and software
infrastructure, any licensing or third-party software costs, and
ongoing maintenance and support expenses.
 APPENDICES
GLOSSARY LIST
 Organ Donor System: The software system designed to facilitate the registration, matching,
and communication between organ donors and potential recipients.

 SRS (Software Requirements Specification): A document that outlines the functional and
non-functional requirements of the organ donor system, including system behavior, user
interactions, and system constraints.

 Donor: An individual who voluntarily registers in the organ donor system to offer their organs
for transplantation upon their death.

 Recipient: An individual who is in need of an organ transplant and is registered in the organ
donor system to find a suitable donor.

 Registration: The process by which a potential organ donor provides their personal
information, medical history, and consent to be part of the organ donor system.

 Preference Settings: The configurable options that a donor can set to define their availability,
geographical location preferences, and notification settings for potential organ recipient
matches.

 Matching Algorithm: The algorithm used by the organ donor system to match potential organ
donors with recipients based on compatibility factors such as organ type, blood type, tissue
compatibility, and geographical proximity.

 Communication Module: The module within the organ donor system that enables secure
communication between organ donors and potential recipients, allowing them to exchange
information and coordinate the organ transplantation process.

 Medical Evaluation: The process in which potential recipients undergo medical assessments
and evaluations to determine their suitability for receiving a donated organ.

 Notification: The system's mechanism to inform organ donors and potential recipients about
matches, updates, and relevant events within the organ donor system.
  Database Management System (DBMS): The software system used to store and manage the
organ donor system's data, including donor and recipient profiles, preferences, and
communication records.

 User Interface (UI): The graphical or textual interface through which organ donors and
potential recipients interact with the organ donor system, allowing them to perform various
actions such as registration, search, and communication.

 System Administrator: The user or role responsible for managing and maintaining the organ
donor system, including user accounts, system configuration, and security settings.

 Security Measures: The protocols, mechanisms, and practices implemented in the organ
donor system to protect sensitive data, ensure privacy, and prevent unauthorized access or
misuse.

 System Integration: The process of integrating the organ donor system with external systems
or databases, such as healthcare providers' systems or organ transplantation organizations,
to exchange relevant data and ensure seamless operation.

ISSUE LIST
 User Registration Issue:

 Description: Users are experiencing difficulties during the registration process.

 Priority: High
 Resolution: Investigate and fix any errors or usability issues in the registration workflow to
ensure a smooth and error-free registration experience.

 Matching Algorithm Issue:

 Description: The current matching algorithm is not accurately matching organ donors with
potential recipients.
 Priority: High
 Resolution: Analyze and improve the matching algorithm to consider compatibility factors
such as organ type, blood type, tissue compatibility, and geographical proximity for more
accurate matches.
 Performance Issue:

 Description: The system is experiencing slow response times and performance degradation
during peak usage periods.
 Priority: Medium
 Resolution: Identify and optimize any bottlenecks in the system architecture, database
queries, or network connections to improve overall system performance.

 Security Issue:

 Description: The system lacks robust security measures to protect sensitive donor and
recipient data.
 Priority: High
 Resolution: Implement appropriate security mechanisms such as encryption, access controls,
and secure communication protocols to safeguard user data and prevent unauthorized
access.

 User Interface Issue:

 Description: Users find the current user interface confusing and unintuitive.
 Priority: Medium
 Resolution: Conduct user interface redesign and usability testing to improve the user
experience, ensuring that the system is user-friendly and intuitive for both organ donors and
potential recipients.

 Notification Issue:

 Description: Users are not receiving timely notifications and updates regarding potential
matches or important system events.
 Priority: Medium
 Resolution: Review and optimize the notification system to ensure that users receive timely
and relevant notifications through appropriate channels (e.g., email, SMS) based on their
preferences.

 Database Management Issue:

 Description: Database inconsistencies and data integrity issues are affecting the accuracy and
reliability of the system.
 Priority: High
  Resolution: Perform a thorough database audit, identify and resolve any data
inconsistencies, and implement proper data validation and integrity checks to maintain a
reliable and consistent database.

 Accessibility Issue:

 Description: The system does not meet accessibility standards, making it difficult for users
with disabilities to access and use the system.
 Priority: Medium
 Resolution: Ensure compliance with accessibility guidelines (e.g., WCAG) by implementing
features such as keyboard navigation, alternative text for images, and appropriate color
contrast to make the system accessible to users with disabilities.

SUPPORTING INFORMATION
 Purpose of the System:

Describe the overall purpose and objectives of the organ donor system, such as facilitating the
registration, matching, and communication between organ donors and potential recipients.

Explain the significance and potential impact of the system in improving organ transplantation
processes and saving lives.

 Stakeholder Identification:

Identify and describe the different stakeholders involved in the organ donor system, such as organ
donors, potential recipients, healthcare professionals, system administrators, and regulatory
authorities.

Clarify their roles, responsibilities, and expectations within the system.

 User Personas:

Create fictional user personas representing typical organ donors and potential recipients.

Include their demographic information, motivations, goals, and challenges to provide a better
understanding of user needs and behavior.

 Functional Requirements:
Provide a detailed list and description of the system's functional requirements, specifying the
features, actions, and behaviors expected from the organ donor system.

Include use case scenarios or user stories to illustrate how users will interact with the system and
accomplish specific tasks.

 Non-Functional Requirements:

Outline the non-functional requirements that define the system's qualities and constraints, such as
performance, security, reliability, usability, accessibility, and scalability.

Specify any industry or regulatory standards that need to be adhered to, such as HIPAA compliance
for handling sensitive medical data.

 System Architecture:

Provide an overview of the system architecture, including the high-level components, modules, and
their interactions.

Describe any external interfaces or systems that the organ donor system needs to integrate with,
such as healthcare provider systems or organ transplantation databases.

 Data Model:

Present a conceptual data model depicting the main entities, attributes, and relationships relevant to
the organ donor system.

Define the data structure required to support the system's functionalities, such as donor profiles,
recipient profiles, organ types, and matching algorithms.

 User Interface Design:

Include wireframes, mockups, or visual representations of the user interface design to illustrate the
proposed layout, navigation, and interaction patterns.

Specify any design guidelines or branding requirements to ensure consistency and usability.

 Constraints and Assumptions:

Identify any constraints or assumptions that may impact the system's development, deployment, or
operational aspects.

Document any limitations, external dependencies, or technological constraints that need to be

considered.
THANK YOU