BloodLink

Bijoy V Babu,
Rosh Roy George,
Ryan Chalappuram,
Sreejith K S
(Group 13)
June 4th, 2023

1
Contents
1 Introduction 3

2 Overall Desccription 3

3 System Design 3
3.1 User Registration and Authentication . . . . . . . . . . . . . . . 3
3.2 Blood Donation Requests . . . . . . . . . . . . . . . . . . . . . . 4
3.3 Messaging and Communication . . . . . . . . . . . . . . . . . . . 4
3.4 Donor and Recipient Profiles . . . . . . . . . . . . . . . . . . . . 4

4 Component-level Design 4
4.1 User Registration and Authentication Component . . . . . . . . 4
4.2 Blood Donation Requests Component . . . . . . . . . . . . . . . 5
4.3 Messaging and Communication Component . . . . . . . . . . . . 5
4.4 Donor and Recipient Profiles Component . . . . . . . . . . . . . 5

5 Interface Design 5
5.1 Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2 Upload Audio Screen . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.3 Meeting Summary Screen . . . . . . . . . . . . . . . . . . . . . . 6
5.4 Settings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.5 Navigation Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

6 Data Flow 6

7 UML Diagrams 7
7.1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.2 DFD Level 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.3 DFD Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2
1 Introduction
The purpose of this document is to define the software requirements for a prac-
tical website. This website will be developed to provide users with a platform to
manage Blood donation activities. This document outlines the functional and
non-functional requirements for the website.

2 Overall Desccription
System Overview of The BloodLink system consists of the following modules:
• User Registration and Authentication Module: This module allows users
to create accounts, log in, and manage their profiles,implements authen-
tication mechanisms to verify user identity.
• Blood Donation Requests Module: Allow blood banks, hospitals, or indi-
viduals in need to create donation requests specifying blood type, quantity,
and urgency.Notify potential donors who match the requested blood type
and location.

• Messaging and Communication Module: Provide a messaging system for

secure communication between donors and Admin using Telegram Chat-
bot.
• Donor and Recipient Profiles Module: Provide users with the ability to
create and manage their profiles.Collect and store information such as
blood type, contact details, medical history, and donation preferences.

3 System Design
The BloodLink system modules work together to create a blood donation app
that allows users to register, authenticate, create and respond to donation re-
quests, communicate securely through messaging, and manage their profiles.
The system design ensures the security and privacy of user data, facilitates ef-
fective communication, and streamlines the process of matching donors with
recipients in need of blood donations.

3.1 User Registration and Authentication

1. Design a user registration form that collects necessary information such
as name, email, password.
2. Implement validation checks to ensure data integrity and verify email ad-
dresses.
3. Implement authentication mechanisms like token-based authentication to
verify user identity.

3
 4. Generate and manage user sessions or tokens to maintain user sessions
across Web usage.

3.2 Blood Donation Requests

1. Create a form for blood banks, hospitals, or individuals to create donation
requests.
2. Store donation requests in a database, associating them with the respective
requesters.
3. Implement a matching algorithm that compares the blood type and loca-
tion of potential donors with the requested blood type ,location and last
donated date.
4. Allow donors to view and respond to donation requests, indicating their
availability and willingness to donate.

3.3 Messaging and Communication

1. Integrated a Telegram Chatbot API to enable secure messaging between
donors and the admin.
2. Implement chatbot functionalities to automate certain interactions and
provide quick responses to frequently asked questions.

3.4 Donor and Recipient Profiles

1. Design a user interface for users to create and manage their profiles.
2. Store profile information securely in a database, associating it with the
respective users.
3. Allow users to update their profiles.
4. Use the profile information to match donors with donation requests and
provide relevant notifications

4 Component-level Design
4.1 User Registration and Authentication Component
1. Registration Form:Design and implement a form that collects user reg-
istration data such as name, email, password.
2. Authentication Manager:Develop the logic to verify user credentials
during the login process, including password hashing and token generation.
3. Email Verification:Implement email verification functionality to confirm
the user’s email address during the registration process.

4
4.2 Blood Donation Requests Component
1. Donation Request Form: : Create an interface to capture donation
request details, including blood type, quantity, and urgency level.
2. Matching Algorithm: This subcomponent will Design and implement
an algorithm that matches potential donors with donation requests based
on blood type and location criteria.
3. Notification Service: : This subcomponent will integrate a notifica-
tion component to send notifications to potential donors when a matching
request is created.

4.3 Messaging and Communication Component

1. Telegram Chatbot Integration module: This subcomponent will in-
tegrate the Telegram Chatbot API to enable secure messaging between
donors and the admin.
2. Topic modeling module:This subcomponent will identify the main top-
ics discussed in the meeting.
3. Chatbot Logic module: This subcomponent will implement the logic
to handle user messages, provide automated responses, and facilitate com-
munication between users and the admin.
4. Database module: This subcomponent will Store messages securely in
a database, associating them with the respective users and conversations.

4.4 Donor and Recipient Profiles Component

1. Profile Management Interface module: This subcomponent will al-
low users to create and manage their profiles, including information such
as blood type, contact details, medical history, and donation preferences.
2. Search and Filtering module: This subcomponent will implement
search and filtering functionality to help users find potential donors or
recipients based on specific criteria.

5 Interface Design
5.1 Login Screen
The login screen will allow users to enter their login credentials or create a new
account.

5
5.2 Upload Audio Screen
The upload audio screen will allow users to upload an audio file of the meeting
they want to summarize. Users will be able to select the file from their device
and upload it to the system.

5.3 Meeting Summary Screen

The meeting summary screen will display the summary of the meeting generated
by the system. The summary will include the main topics discussed in the
meeting, action items assigned during the meeting, decisions made during the
meeting, and the overall sentiment of the meeting. Users will be able to view
and download the summary.

5.4 Settings Screen

The settings screen will allow users to customize the system settings, such as
the language used for speech recognition and the output format of the meeting
summary.

5.5 Navigation Bar

The navigation bar will allow users to switch between different screens, including
the upload audio screen, meeting summary screen, settings screen etc..

6 Data Flow
• Audio input is captured by microphones or recording devices.
• The audio input is processed by the speech recognition component to
produce text.
• This text is preprocessed to remove optimise it for NLP like removing stop
words etc
• The text is analyzed by the natural language processing component to
extract key information.
• The extracted information is used by the machine learning component to
generate a summary of the meeting.
• The summary is displayed in the user interface.

6
7 UML Diagrams
7.1 Use Case Diagram

7
7.2 DFD Level 0

8
7.3 DFD Level 1