2nd BOOKS
2nd BOOKS
2nd BOOKS
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.
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
4. Generate and manage user sessions or tokens to maintain user sessions
across Web usage.
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.
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.
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