Our Services

Get 15% Discount on your First Order

[rank_math_breadcrumb]

Saudi Electronic University Homework Help

senior project

Description

Hi, this is the project report with all the information. I just want you to write the code for this project which is a website, the backend will be in JavaScript, and the frontend will be in HTML. With an explanation if possible.

‫| كلية الحوسبة والمعلوماتية‬
College of Computing and Informatics

College of Computing & Informatics (CCI)
SENIOR PROJECT-II REPORT

Blood Link
Author(s):
Student Reg# S210042459

Student Name MAHA AMAN

Student Reg# S210053889

Student Name YARA ALRASHEED

Student Reg# S190245832

Student Name DEEMAH ALTURKI

Student Reg# S180062104

Student Name YARA ALQARNI

Student Reg# S210048402

Student Name REEF ALHARTHI

Project Supervisor:
Maimonah Abdulkareem Eid Alalwani

‫| كلية الحوسبة والمعلوماتية‬
College of Computing and Informatics

Blood Donation Website
By: MAHA AMAN, YARA ALRASHEED, DEEMAH ALTURKI,
YARA ALQARNI, REEF ALHARTHI

Thesis/Project submitted to:
College of Computing & Informatics, Saudi Electronic University, Riyadh, Saudi Arabia.

In partial fulfillment of the requirements for the degree of:

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

Maimonah Abdulkareem Eid
Alalwani

Project Committee Chair

ABSTRACT
The Blood Link project addresses a critical challenge in the healthcare system: the urgent need
for accessible blood supplies. Traditional blood donation methods, such as scheduled drives and
passive outreach, often lead to delays when specific blood types are required. The Blood Link
Initiative, powered by advanced technology, proposes a real-time platform that connects blood
donors with hospitals, facilitating immediate action and significantly improving the effectiveness
of the donation process. This project streamlines various logistical operations and fosters
community involvement in blood donation. Our team has focused on developing an easy-to-use
interface and integrating real-time communication features that enable hospitals to notify
registered donors about urgent needs. This collaborative approach optimizes the donation process
and promotes a proactive culture of healthcare participation. Key benefits of our method include
reduced response times in emergencies, improved inventory management in blood banks, and
increased donor engagement through timely notifications. Reflecting on the project’s outcomes,
we have gained valuable insights into integrating technology in healthcare, enhancing our
software development and project management skills. This experience has deepened our
understanding of user-centered design and highlighted the importance of responsive systems in
addressing real-world health challenges.

DEDICATION
This work is dedicated to our families for their constant encouragement and unwavering support,
which have been the foundation of our success. A special thanks goes to Dr. Maimonah
Abdulkareem Eid Alalwani, our mentor, whose invaluable advice and insights have guided us and
motivated us to reach new heights. We also sincerely appreciate our friends, whose
companionship through the highs and lows of this journey has been invaluable, providing us with
understanding and laughter along the way. Finally, we extend our heartfelt gratitude to the
medical staff—physicians, nurses, and volunteers—whose daily dedication to saving lives
inspires us.

PREFACE
In order to address the urgent need for effective systems for managing and donating
blood, the “Blood Link” initiative is a major advancement. This paper describes the
project’s technological foundation, goals, and vision, which is to link generous donors
with those in immediate need of blood. We want to use technology, which can fill gaps in
healthcare in this day and age, to make the experience of donors and receivers as smooth
as possible.

As this project has progressed, we have come to understand the value of cooperation and
assistance from a range of people. I want to express my sincere appreciation to everyone
who helped out by lending their time, knowledge, and support. Special thanks go out to
my family for their unwavering support, my friends who inspired me throughout difficult
times, and my mentor, Dr. Maimonah Abdulkareem Eid Alalwani, whose advice has been
priceless. Furthermore, I want to thank the medical personnel whose commitment to
saving lives motivated our endeavor.

The purpose of this report is to give a thorough overview of the project, covering its
goals, features, and expected community impact. Every segment explores distinct facets
of the platform, guaranteeing readers’ comprehension and clarity. In addition to reflecting
our efforts, we hope that this paper will act as a call to action for others to join us in this
important cause.

We appreciate you taking the time to look into “Blood Link.” By working together, we
can improve the lives of people who rely on prompt blood donations.

REVISION HISTORY
Name

Date

Reason For Changes

Version

Yara Alrasheed

24/09/24

Final edits to Chapter 1: Introduction

1.0

Yara Alqarni

26/09/24

Additions to Chapter 2: Literature Review

1.1

Maha Aman

01/10/24

Revised Chapter 1 & 2: Introduction &
Literature Review

1.1

Deemah Alturki

27/10/24

Updated Chapter 4: System Analysis

1.2

Reef Alharthi

28/10/24

Final edits to Chapter 4: System Analysis

1.3

Yara Alrasheed

03/11/24

Formatting adjustments, and additional diagrams

1.4

Yara Alqarni

11/11/24

Revised Chapter 5: System Design

1.5

Yara Alrasheed

18/11/24

Additions to Chapter 6: Discussion &
Conclusion

1.6

Maha Aman

27/11/24

Reworked Chapter 3: Methodology

1.7

Deemah Alturki

27/11/24

Fixed diagram in Chapter 5: System Design

1.8

Maha Aman

27/11/24

Final edits and formatting for the entire report

1.9

Yara Alrasheed

27/11/24

Final proofreading and adjustments for clarity

1.9

TABLE OF CONTENTS

CHAPTER 1: INTRODUCTION ………………………………………………………………………………. 7
1.1

Project Background/Overview: ………………………………………………………………………………7

1.2

Problem Description: ……………………………………………………………………………………………7

1.3

Project Scope: ……………………………………………………………………………………………………..7

1.4

Project Objectives: ……………………………………………………………………………………………….9

1.5

Project Structure/Plan: ………………………………………………………………………………………. 10

CHAPTER 2: LITERATURE REVIEW …………………………………………………………………… 13
CHAPTER 3: METHODOLOGY ……………………………………………………………………………. 20
CHAPTER 4: SYSTEM ANALYSIS ………………………………………………………………………… 24
4.1

Product Features: ……………………………………………………………………………………………… 24

4.2

Functional Requirements: …………………………………………………………………………………… 24

4.3

Nonfunctional Requirements……………………………………………………………………………….. 34

4.4

Analysis Models ………………………………………………………………………………………………… 39

CHAPTER 5: SYSTEM DESIGN ……………………………………………………………………………. 41
CHAPTER 6: SYSTEM IMPLEMENTATION ………………………………………………………….. 52
CHAPTER 7: TESTING & EVALUATION………………………………………………………………. 53
CHAPTER 8: RESULTS AND ANALYSIS ………………………………………………………………. 54
CHAPTER 9: CONCLUSION AND FUTURE WORK ……………………………………………….. 55
6.1

Conclusion ……………………………………………………………………………………………………….. 55

6.2

Future Work …………………………………………………………………………………………………….. 55

REFERENCES ……………………………………………………………………………………………………. 56
APPENDIX: Glossary …………………………………………………………………………………………… 59

CHAPTER 1: INTRODUCTION
1.1
Project Background/Overview:
The project proposes an enhancement in the process of blood donation by developing a
web or mobile application for the management and monitoring of donations and stock at
the blood banks, updating information about hospitals, and sending messages to donors
whenever the hospitals need blood, mentioning the groups required and at which
location. Here, donors will sign in; view previous donations; and gather information
about donation time. Requests can be made in emergency cases, too. It also provides
real-time visibility into the inventory of blood at various centers to meet the demand and
avoid shortage situations in hospitals.
This will allow easy facilitation of matching between the donors and the recipients by
showing easy access to the blood bank location using Google Maps. The project ensures
that patient information and donor information is kept securely in compliance with all
health data privacy regulations.

1.2
Problem Description:
In Saudi Arabia, there are many donors and blood banks face challenges in managing
donations due to the difficulty of communicating with blood donors, tracking inventory,
and the lack of simple and effective methods such as websites or applications to help
blood banks, hospitals, and donors help patients faster. Therefore, the idea of our project
helps solve this problem through a website or application where the donor registers with
all his information such as his blood group and medical record with continuous updates
on the donor’s health condition. Thus, when there is a blood shortage, a message will be
sent to him about the location of the hospital that needs blood. This application will help
solve this problem as it will be easy to match between the donor and the patient, avoid
blood shortages in hospitals, and facilitate communication with the donor.
1.3
Project Scope:
Project aims:
The Blood Link initiative seeks to establish a smooth relationship between hospitals in
need of blood supply and blood donors. The following are the main goals:
1. Simplified Donation Administration: Create a website that enables blood banks to
effectively handle contributions, keep track of stock levels, and preserve donor data.
2. Rapid Response System: Depending on the donor’s location and blood type, put in
place a notification system that notifies them of urgent blood requirements at
surrounding hospitals.
3. Improved Accessibility: Make it simple for contributors to learn when and where they
may make a donation, which will make the procedure easier to utilize.
7

Benefits:
The Blood Link solution has a number of noteworthy advantages.
1. Faster Blood Supply: Hospitals may obtain the necessary blood types more quickly by
promptly alerting local donors, which might save lives in an emergency.
2. Better Resource Management: Blood banks will be able to allocate resources more
efficiently thanks to improved control of their donor database and inventory.
3. Community Engagement: By bringing donors and hospitals together and promoting
consistent giving, the platform promotes a feeling of community.
4. Greater Donor Participation: More people are probably going to donate blood if it’s
simple to get alerts about urgent needs.
Expected Outcomes:
The Blood Link project is anticipated to produce a fully working website that satisfies
the requirements of donors, hospitals, and blood banks. The website’s salient elements
will comprise:
•
•
•
•

Donors have the option to build user profiles that contain their location, blood
type, and personal details.
Blood banks have the ability to check stock levels, handle incoming donations,
and keep a database of donors.
Notification System: By providing the necessary blood type and the hospital’s
location, hospitals may notify registered donors.
Search Features: Donors may quickly locate nearby blood drives or hospitals that
require blood donations.

Selection of Platform:
For the most part, the Blood Link solution will be created as a website. Many factors
have been taken into account in making this decision:
1. Greater Accessibility: It is simpler for people to interact with a website when it is
accessible from a variety of platforms (desktops, laptops, tablets, and smartphones)
without the need for downloads or installs.
2. Easy Maintenance and Updates: Websites make it possible to perform rapid
maintenance and updates without requiring users to install new versions, guaranteeing
that all users have access to the newest data and features.

3. Integration Capabilities: By making it easier to integrate, a web-based platform may
improve overall functioning with current hospital databases and systems.
1.4
Project Objectives:
Predetermined Results or Achievements:
1. Streamlined Donor Registration:
– Develop an intuitive registration process for donors, enabling them to easily sign up
and create a personal profile.
– Provide a user-friendly interface for donors to view their donation history, including
dates, blood types, and eligibility for future donations.
2. Emergency Notification System:
– Implement a robust messaging system that allows hospitals to send urgent requests to
registered donors with matching blood types within a specified radius.
– Track response rates and donor engagement during emergencies to evaluate the
effectiveness of the notification system.
3. Real-Time Blood Inventory Management:
– Create a centralized dashboard for blood banks and hospitals to monitor current
blood supply levels in real-time.
– Enable automated alerts for low inventory levels, ensuring timely communication
with donors and proactive management of resources.
4. Efficient Donor-Recipient Matching:
– Develop an algorithm that facilitates easy matching of donors with recipients based
on specific needs and available inventory.
– Allow both donors and hospitals to search for available blood resources quickly,
minimizing delays in critical situations.
5. Location-Based Services for Donors:
– Integrate Google Maps to provide donors with directions and information about the
nearest blood banks and upcoming donor drives.
– Offer features that allow users to filter and locate donation events based on distance
and availability.
6. Privacy and Security Compliance:
– Ensure that all personal data of donors and patients is securely stored in compliance
with health data privacy regulations (e.g., HIPAA).
– Implement encryption methods and access controls to protect sensitive information
from unauthorized access.
7. User-Friendly Emergency Donation Request:
9

– Allow donors to easily request donations during emergencies, providing a quick way
to mobilize support when needed.
– Track the success of these requests to identify areas for improvement in
communication and outreach.
8. Comprehensive Reporting and Analytics:
– Develop reporting tools for blood banks and hospitals to analyze donation trends,
inventory turnover, and donor engagement metrics.
– Use analytics to inform strategies for improving donor recruitment and resource
management.
9. Community Awareness Initiatives:
– Create educational content within the platform to raise awareness about the
importance of blood donation and how users can contribute.
– Partner with local organizations to promote donor drives and events through the
platform, fostering community involvement.
10. Scalability and Future Enhancements:
– Design the platform architecture to be scalable, accommodating increasing user
numbers and expanding hospital networks.
– Plan for future enhancements based on user feedback and technological
advancements, ensuring the platform remains effective and relevant.
By achieving these objectives, Blood Link aims to create a seamless connection between
blood donors and those in need, ultimately improving the efficiency of blood donation
processes and saving lives through timely access to blood supplies.
1.5
Activity

Project Structure/Plan:
Start Date

Finish Date

Duration
(Days)

Resources Required

1. Project Initiation and September 4,
Choosing Topic
2024

September
17, 2024

Project Team,
Stakeholders

2. Introducing the
Project

September
18, 2024

September
24, 2024

Project Team,
Presentation Tools

3. Literature Review

September
25, 2024

September
30, 2024

Research Materials,
Project Team

4. Methodology

October 1,
2024

October 9,
2024

Documentation Tools,
Project Team

5. System Analysis

October 10,
2024

October 27,
2024

Analysis Tools, Project
Team
10

6. System Design

October 28,
2024

November 4,
2024

Design Tools, Project
Team

7. Discussion &
Conclusion

November 5,
2024

November 20, 15
2024

Project Team, Report
Writing Tools

Table 1.1 Activities Table

Textual Description of Activities
1. Project Initiation and Choosing Topic (September 4 – September 17, 2024):
o

Activities during this phase include defining project objectives, identifying
stakeholders, and selecting the topic for the Blood Link project.

Duration: 13 days

Resources Required: Project team members and stakeholder input.

2. Introducing the Project (September 18 – September 24, 2024):
o

This phase involves presenting the project to stakeholders and gathering initial
feedback.

Duration: 6 days

Resources Required: Presentation tools and project team members.

3. Literature Review (September 25 – September 30, 2024):
o

Conducting a review of existing literature related to blood donation systems and
health information management.

Duration: 5 days

Resources Required: Research materials and project team.

4. Methodology (October 1 – October 9, 2024):
o

Developing the methodology for the project, particularly focusing on the
Waterfall Model.

Duration: 8 days

Resources Required: Documentation tools and project team.

5. System Analysis (October 10 – October 27, 2024):
o

Analyzing system requirements and functionalities based on stakeholder input and
project objectives.

Duration: 17 days
11

Resources Required: Analysis tools and project team.

6. System Design (October 28 – November 4, 2024):
o

Designing the system architecture, user interfaces, and database schemas.

Duration: 7 days

Resources Required: Design tools and project team.

7. Discussion & Conclusion (November 5 – November 20, 2024):
o

Final discussions regarding project outcomes, lessons learned, and compiling the
final report.

Duration: 15 days

Resources Required: Project team and report writing tools.

Figure 1.1 Gantt Chart

This Gantt chart for the Blood Link project serves as a visual representation of the project
timeline, outlining key activities, their durations, and interdependencies. It is a vital project
management tool that organizes activities, clarifies timelines, and enhances communication
among team members and stakeholders. By visually mapping out the entire project, it ensures
that all participants are aware of their roles, responsibilities, and deadlines, ultimately
contributing to the project’s success.
In summary, this well-structured project plan not only lays the groundwork for the successful
execution of the Blood Link project but also provides a framework for ongoing monitoring and
evaluation, ultimately ensuring that the project meets its goals of improving blood donation
processes and enhancing healthcare delivery.

CHAPTER 2: LITERATURE REVIEW
Blood donation plays a crucial role in healthcare systems worldwide, yet challenges remain in
ensuring a consistent and reliable supply. As technology evolves, there are emerging
opportunities to enhance the blood donation process, improve donor engagement, and address
gaps in current practices.
This literature review examines recent studies and reports that explore innovative solutions,
including blockchain technology, machine learning, and user-centered design, to optimize blood
management practices. By synthesizing the findings from various sources, this review identifies
critical gaps in knowledge and areas for application, ultimately providing a foundation for the
“Blood Link” project, which aims to create a more efficient, accessible, and engaging platform
for blood donation.
Several studies explore the application of blockchain technology to enhance transparency and
traceability within blood supply chains. For example, a study on real-time blood wastage
management using blockchain and IoT highlights how blockchain integration can reduce
wastage and improve distribution efficiency (SpringerLink, 2024). Additionally, research
on transforming blood donation processes using blockchain and IoT emphasizes the potential of
this technology to improve safety, efficiency, and transparency in the donation process (IEEE
Xplore, 2024). Implementing such technology in the “Blood Link” project could ensure secure
13

tracking of blood donations and enhance trust among donors and recipients, ultimately leading to
improved blood management outcomes.
Recent research has indicated that machine learning algorithms can improve donor recruitment
strategies by identifying prospective donors and forecasting their donation behaviors. For
example, McElfresh et al. (2021) developed algorithmic matching techniques that effectively
connect donors with nearby donation opportunities, significantly increasing the number of
donations. This promising result highlights the potential of technology to make a meaningful
impact in healthcare. Similarly, Epifani et al. (2023) employed Bayesian models to profile
donors and predict their donation behaviors, facilitating more targeted recruitment and retention
efforts. Integrating these machine learning techniques into the “Blood Link” project could
improve donor engagement and enable more effective campaign targeting, ultimately leading to
a more reliable blood supply.
Recent technological innovations in blood donation processes, such as automated donor
screening and data management systems, are essential for improving efficiency and, most
importantly, donor engagement. For example, a study by AlZu’bi et al. (2022) proposes an
intelligent system that optimizes blood donation by preventing shortages and minimizing waste
by proactively recruiting available donors on short notice. Similarly, Niklas et al. (2023) discuss
the impact of digital transformation on blood donation, emphasizing that a well-designed blood
donation app can streamline processes and attract new donors. These advancements highlight the
importance of integrating user-friendly interfaces to enhance participation rates, aligning with the
goals of the “Blood Link” project and fostering a sense of connection and commitment among
donors.
The importance of user experience (UX) design in blood donation platforms has been
highlighted in recent studies. For example, research on optimizing blood donation apps with
gamification through user-centered design revealed that poor UX significantly reduces donor
retention while intuitive interfaces enhance engagement and satisfaction (ResearchGate, 2023).
Similarly, a design science approach to developing blood donation apps demonstrated that
thoughtful UX design improves donor interaction and streamlines the donation process
(SpringerLink, 2022). These findings underline a key development focus for the “Blood Link”
project, ensuring a user-friendly platform that fosters participation and trust.
Current studies have revealed essential challenges that prevent young adults from donating
blood, including misconceptions about the donation process and a widespread lack of awareness.
For instance, a study examining young adults’ blood donation knowledge found that
misunderstandings and misinformation greatly hinder participation rates (PLOS Journals, 2023).
Additionally, research on voluntary blood donation knowledge, attitudes, and practices among
adults indicates that targeted educational campaigns can effectively address these barriers and
enhance donor participation (Frontiers, 2023). These insights are especially relevant for the
“Blood Link” project, which aims to engage younger potential donors through informed and
targeted strategies.
14

The concept of gamification in health applications has shown significant potential to enhance
user engagement. For example, Edwards et al. (2016) note that adding game-like elements to
health promotion apps can motivate users to adopt healthier behaviors by making the experience
more interactive and rewarding. Similarly, Aschentrup et al. (2024) highlight the effectiveness of
gamified interventions in encouraging sustained engagement in health-related activities. These
insights suggest that gamification could be effectively integrated into the ‘Blood Link’ project to
encourage repeat donations, promote long-term donor retention, and foster a sense of community
among donors.
In a systematic review, Green, T. (2022) assesses various online blood donation systems,
identifying their strengths and weaknesses. The study reveals that while many platforms have
improved accessibility, gaps remain in outreach to certain demographics. This evaluation
provides a solid foundation for the “Blood Link” project to build upon, ensuring that it addresses
existing shortcomings in current systems.
Research highlights how integrating blood donation data with electronic health records (EHRs)
offers the potential for improved donor management while reducing the risk of errors. For
instance, Keshta and Odeh (2020) discuss the challenges of securing EHR systems and stress the
importance of adherence to data privacy regulations such as GDPR and HIPAA. Similarly,
Yüksel et al. (2017) explore privacy and security concerns related to electronic health services,
emphasizing the critical role of encryption and access controls. Implementing such integration in
the “Blood Link” project could enhance donor tracking and streamline management processes,
provided that comprehensive data privacy safeguards are established.
The American Red Cross (2024) reports that its platform is widely utilized and excels in
appointment scheduling and donor management. However, user feedback collected from
platforms like JustUseApp indicates areas for improvement in the mobile app’s user interface
(UI) and navigation, particularly in terms of ease of use and functionality (JustUseApp, 2024).
These insights are particularly relevant for the “Blood Link” project, which aims to enhance
donor engagement and streamline blood donation processes by learning from the strengths and
weaknesses of existing platforms.
NHS Blood and Transplant (2024) states that the GiveBlood platform features a streamlined
appointment booking system and provides comprehensive information on eligibility and
donation procedures. Nevertheless, its functionality is limited to the UK, highlighting a need for
globally accessible platforms. These insights are crucial for the “Blood Link” project, which aims
to develop a more inclusive platform that addresses the needs of diverse populations worldwide.
NIST (2024) emphasizes that implementing robust data encryption and security protocols is
paramount to protect user data. This includes secure storage and transmission of sensitive
information. Such measures are critical for the “Blood Link” project, as ensuring data security
will build trust among users and encourage greater participation in blood donation initiatives.
Project Management Institute (2024) states that employing a suitable project management
methodology, such as Agile, ensures efficient development and timely completion. This
15

approach is particularly beneficial for the “Blood Link” project, as it allows for iterative
improvements and flexibility in addressing user feedback throughout the development process.
Social media marketing (2024) emphasizes that leveraging social media platforms for donor
recruitment and awareness campaigns can significantly increase reach. This strategy is
particularly beneficial for the “Blood Link” project, as it can enhance community engagement
and raise awareness about donation needs, ultimately driving higher participation rates.
API Documentation (2024) states that integrating with blood bank databases through APIs
allows for real-time updates on blood supply and donor information. This capability is essential
for the “Blood Link” project, as it enables timely responses to blood shortages and enhances the
overall efficiency of donor management and distribution.
Design Principles (2024) asserts that a visually appealing and consistent brand identity enhances
user trust and engagement. This is particularly important for the “Blood Link” project, as a
strong brand identity can foster trust among users and encourage greater participation in blood
donation initiatives.
Nielsen Norman Group (2023) emphasizes that employing user-centered design principles,
including usability testing and iterative design, is essential for creating a user-friendly and
intuitive platform. This approach is crucial for the “Blood Link” project, as it ensures that the
platform effectively meets the needs of users, ultimately enhancing donor engagement and
satisfaction.
Privacy-enhancing technologies (2024) state that techniques for data anonymization and
aggregation should be employed to protect individual privacy while still allowing for data
analysis and reporting. Implementing these techniques in the “Blood Link” project is vital for
ensuring compliance with data privacy regulations and maintaining user trust while facilitating
effective data analysis for improving blood donation strategies.
Health Analysis for Donors (2024) suggests that, in addition to the act of donating blood,
providing donors with a comprehensive health analysis based on samples taken during donation
can offer added value. Insights into key health indicators can incentivize donors to engage
regularly, promoting both blood donation and proactive health monitoring among participants.
This approach aligns with the goals of the “Blood Link” project, as it enhances donor motivation
and fosters long-term engagement.
Predictive analytics in healthcare (2024) states that advanced analytics can help predict blood
demand based on various factors, improving supply chain management. Utilizing these analytics
in the “Blood Link” project can enhance the accuracy of blood supply forecasts, ensuring that
donation efforts are aligned with actual demand and reducing the risk of shortages.
Market Research (2024) emphasizes that understanding the demographics and needs of the target
audience (potential donors) is crucial for designing a user-centered website. This understanding
is particularly important for the “Blood Link” project, as it enables the development of features
16

and content that effectively engage potential donors and address their specific motivations and
concerns.
As suggested by XR technologies in healthcare (2024), virtual reality (VR) and augmented
reality (AR) could enhance user experience and education around blood donation. Integrating
these technologies into the “Blood Link” project could provide interactive and immersive
experiences, helping to educate potential donors about the donation process and its impact,
thereby increasing engagement and participation.
BloodConnect (2024) effectively connects donors and recipients within India. However,
challenges remain regarding scalability and integration with national blood banks, necessitating
further development. Addressing these challenges in the “Blood Link” project will be crucial for
creating a scalable platform that can facilitate connections between donors and recipients on a
broader, potentially global scale.
Digital transformation in blood banking has revealed several challenges within regional blood
bank systems, particularly concerning user interface (UI), user experience (UX), information
presentation, and functionality. For instance, the e-Raktkosh platform in India, which integrates
regional blood bank services, has played a crucial role in addressing issues related to
standardization and user experience. However, it continues to encounter implementation
challenges at the local level (Kulsum & Gopal, 2024).
As highlighted by MarketingProfs (2023), effective communication systems, including SMS and
email, are vital for reminding donors of appointments and providing updates on blood supply
needs. Implementing a robust and reliable communication infrastructure is essential for the
“Blood Link” project, as it will enhance donor engagement and ensure timely information
dissemination, ultimately contributing to increased donation rates.
Incorporating gamification techniques and incentives into blood donation platforms can
significantly improve user engagement and encourage more frequent donations. For example, a
study on gamified mobile blood donation applications found that features like badges and
redeemable points effectively motivate donors, particularly among younger demographics who
are essential for the future of blood donation (SpringerLink, 2021). Additionally, research on
gamification in healthcare management highlights its potential to alter behaviors and increase
participation in health-related activities (SAGE Journals, 2021). By integrating these gamified
elements, the “Blood Link” platform can cultivate a community of dedicated donors, thereby
enhancing the overall effectiveness of blood donation campaigns.
Home Blood Donation Services (2024) highlight that offering home blood donation services,
where a medical team visits donors’ homes for blood collection, can enhance convenience and
encourage donations from individuals who may face barriers to visiting donation centers.
Implementing a safe and efficient process for home donations could broaden the reach of
potential donors and contribute to the blood supply chain. This approach aligns with the goals of
the “Blood Link” project, as it seeks to increase donor participation by removing barriers to
access.
17

Identified Gaps in Knowledge and Areas of Application
1. Standardization of User Experience:
•

Gap: The current state of regional blood bank systems needs urgent improvement.
The lack of consistency in UI/UX design, information presentation, and
functionality leads to fragmented and suboptimal user experiences. For instance,
the e-Raktkosh platform in India, despite its efforts to standardize blood bank
services, still struggles to provide a seamless user experience across local
implementations (Kulsum & Gopal, 2024).

•

Application The “Blood Link” project will address these challenges by
developing a unified, standardized platform that prioritizes intuitive UI/UX design
and consistent functionality. Your involvement and support are crucial in this
endeavor. By streamlining user interactions and ensuring accessibility across
diverse demographics, the project aims to enhance user engagement and donor
retention.

2. Engagement of Younger Donors:
•

Gap: Research indicates that misconceptions and a lack of awareness prevent
young adults from donating blood. Studies have shown that a poor understanding
of the donation process and prevalent misconceptions significantly hinder
participation among this demographic (PLOS Journals, 2023; Frontiers, 2023).

•

Application: The ‘Blood Link’ project can implement targeted educational
campaigns to address these barriers. The project can effectively engage younger
donors by combining these efforts with gamification strategies. Such approaches
have the potential to foster a culture of regular donation by making the process
more accessible, informative, and rewarding, which offers hope for increased
blood donation rates.

3. Integration of Advanced Technologies:
•

Gap: The potential of blockchain, machine learning, and XR technologies is
widely acknowledged, yet the absence of comprehensive frameworks for their
integration into blood donation systems is a pressing issue. This gap, as identified
by SpringerLink, 2024; McElfresh et al., 2021; and XR Technologies in
Healthcare, 2024, underscores the urgency and importance of our proposal.

•

Application: The ‘Blood Link’ project, with its focus on creating a roadmap for
integrating these technologies, holds immense potential. Blockchain can enhance
transparency and traceability, machine learning can improve donor behavior
predictions and recruitment strategies, and XR technologies can provide
18

immersive donor education experiences. This potential is a source of confidence
and excitement for the future of blood donation systems.
4. Data Privacy and Security:
•

Gap: The importance of data security in blood donation systems is widely
acknowledged (NIST, 2024; Privacy-Enhancing Technologies, 2024). However,
transparent methodologies for implementing effective security measures and
ensuring compliance with regulations such as GDPR and HIPAA are still not
well-defined (Keshta & Odeh, 2020; Yüksel et al., 2017).

•

Application: The “Blood Link” project aims to establish best practices for data
anonymization, encryption, and secure communication protocols to protect
sensitive donor information and maintain user trust.

5. Home Donation Services:
•

Gap: While home blood donation services are recognized as a means to increase
convenience, detailed operational frameworks and safety protocols are often
lacking (Home Blood Donation Services, 2024).

•

Application: Our project could create a detailed model for implementing home
donation services within the “Blood Link” initiative, tackling logistical challenges
and ensuring safety.

Given the identified gaps, our work in the “Blood Link” project is crucial for advancing the
blood donation landscape. By focusing on standardization, engaging younger donors, and
integrating advanced technologies, our project will not only fill these knowledge gaps but also
create a more inclusive and efficient blood donation ecosystem.
Furthermore, by prioritizing data privacy and exploring innovative service models like home
donations, our work will enhance donor trust and participation. Ultimately, the “Blood Link”
project aims to foster a sustainable blood supply chain that is responsive to the needs of both
donors and recipients, thereby addressing critical public health challenges.
Through this approach, our project can serve as a model for future initiatives, demonstrating the
importance of combining technology, user-centered design, and strategic outreach in enhancing
blood donation practices.

CHAPTER 3: METHODOLOGY
3.1 Introduction
The “Blood Link” project intends to provide an online platform that links blood donors with
blood-needy hospitals. The donation process will be streamlined by this technology, which will
enable blood banks to efficiently handle contributions and inventory while giving hospitals upto-date donor information. Our approach of choice for accomplishing these goals is the Waterfall
software development life cycle (SDLC). In relation to the “Blood Link” project, this chapter
describes the distinct Waterfall model stages and the primary tasks that must be completed in
each.
3.2 Waterfall Software Development Life Cycle
A methodical and sequential approach to software development, the Waterfall model places a
strong emphasis on careful planning and documenting at every turn. Because it enables precise
deliverables and milestones, this technique is especially well-suited for the “Blood Link” project,
20

guaranteeing that all needs are satisfied before proceeding to the next stage. The main stages of
the Waterfall model that are especially suited for this project are listed below.
1. Analysis of Requirements
Principal Activities:
•

Identification of Stakeholders: Determine and involve important parties, such as blood
banks, hospitals, blood donors, and regulatory agencies.

•

Conditions Collecting: To obtain comprehensive system requirements, interview and
survey stakeholders. Important features include of:
• Donors’ user registration
• Hospital emergency notification system
• Blood bank blood inventory management
• Donor drive location services using Google Maps

•

Documentation: To ensure clarity and consensus among stakeholders, create a thorough
requirements specification document that lists all functional and non-functional needs.

Justification: By clearly defining the goals of the system, this phase makes sure that all
stakeholder needs are recorded and approved before moving forward.

2. System Design
Principal Activities:
•

Architectural Design: Describe the application’s general architecture, including its
database structure, server-side and client-side technologies, and integrations with thirdparty services (like Google Maps).

•

Database Design: Model the database, which will include donor data, blood inventory,
and hospital demands, using an Entity-Relationship Diagram (ERD).

•

User Interface Design: Create mockups and wireframes for important interfaces, like:
• Managing donor profiles and registering them
• Hospital blood inventory dashboard
• An interface for notifications on urgent requests

•

Design Documentation: To help developers throughout implementation, record all
design choices in a design specification document.

Justification: A well-defined design minimizes misunderstandings and reworks during
implementation by giving developers a clear blueprint to follow.

3. Implementation Phase
Principal Activities:
•

Coding: Based on the design parameters, start coding. Important elements to develop are:
• A system for registering donors that lets users register, see previous contributions, and
get alerts about upcoming contributions.
• A system for managing blood inventories that tracks available blood types in real time.
• An emergency notification system that uses the blood type of nearby registered donors
to transmit notifications.

•

Unit Testing: To guarantee functionality and dependability, run unit tests on distinct
components as they are being produced.

Justification: Unit testing aids in detecting problems early in the development process, making
this stage essential for converting design specifications into a workable application.

4. Testing Phase
Principal Activities:
•

Component Integration: Assemble all produced components into a unified application
to guarantee smooth system-to-system communication.

•

System Testing: Conduct thorough testing, which includes: * Functional testing to
confirm that all functions (such as inventory management and donor registration) operate
as intended.
• Performance testing to evaluate the application’s performance when it is loaded, such as
during periods of high donation volume.
• Security testing to make sure sensitive data is handled securely and in accordance with
health data privacy laws.

•

User Acceptance Testing (UAT): Involve stakeholders in the system’s testing to ensure
that it satisfies their needs and expectations.

Justification: To guarantee a high-quality product that satisfies user needs, extensive testing is
necessary to find and fix flaws prior to distribution.
5. Deployment Phase
Principal Activities:
•

Deployment Planning: Create a thorough plan for the platform’s launch that includes
user training sessions, support materials, and communication tactics.

•

Production Deployment: Make the program available to users in a live setting.

•

Post-Deployment Monitoring: Throughout the initial launch phase, keep a careful eye
on user input and system performance to handle any pressing problems.

Justification: A well-organized deployment procedure minimizes interruptions by guaranteeing
that users are ready to use the platform efficiently right away.

6. Maintenance Phase
Principal Activities:
•

Ongoing Support: Offer users technical assistance and deal with any problems that crop
up after deployment.

•

Frequent upgrades: Based on user feedback, plan frequent maintenance upgrades to add
new features, address issues, and improve security.

•

Compliance Audits: To guarantee ongoing adherence to health data privacy laws,
conduct audits on a regular basis.

Justification: Constant upkeep is essential to guaranteeing that the platform stays secure,
relevant, and user-responsive throughout time.
23

Requirement

Design

Implementation

Maintenance

Deployment

Testing

Figure 3.1 Waterfall Model of Software Development

CHAPTER 4: SYSTEM ANALYSIS
4.1

Product Features:

The Blood Link website will be for organizing the process of donation among multiple
people (etc.). It will have the following major product features:
1. Managing Donor Profiles and Registration
• Enables users to check donation history, create new donors, and manage their profiles.

2. Requests for Emergency Donations
24

• Notifies local donors when certain blood types are urgently needed by a hospital.
3. Management of Blood Inventory
• Gives blood banks and hospitals up-to-date information on blood supply levels and
expiration dates.
4. Assigning Recipients to Donors
• Makes it easier for donors and receivers to connect based on location and blood type.
5. Donor Drive Locations
• Helps users find local blood banks or donation events by integrating with Google
Maps.
6. Compliance with Privacy and Security
• Ensures that all personal information is safely maintained while following laws
pertaining to the privacy of health data.

4.2

Functional Requirements:

Create a Donor Account
Identifier

UC-1

Purpose

To enable users to sign up to donate blood.

Priority

High

Pre-conditions

The user must have a working email address and internet
connection.

Post-conditions

Donor profile initialization and user account creation.

Typical Course of Action
25

Actor Action

System Response

A user completes the registration form.

shows a confirmation message.

Form submission by the user.

A verification email is sent by the
system.
Alternate Course of Action
3

verifies information and establishes an
account.
Verifies registration after email
confirmation.

Actor Action

System Response

The user gives an invalid email.

shows the error message.

Email is not verified by the user.

The account is not active until it is
validated.

Table 4.1 Use-Case 1 of Create a Donor Account

UC-2

Purpose

To enable users to access their donor accounts.

Priority

High

Pre-conditions

The user must have a registered account.
26

Post-conditions

The user is authenticated and granted access to their account.

Typical Course of Action
S#

Actor Action

System Response

The user navigates to the login page.

Displays the login form.

The user enters their credentials.

Validates the credentials.

The user submits the login form.

Authenticates the user and redirects
them to their dashboard.

Alternate Course of Action
S#

Actor Action

System Response

The user enters invalid credentials.

Displays an error message indicating
incorrect username or password.

The user forgets their password.

Provides a link to reset the password.

Table 4.2 Use-Case 2 of Log In

View Donation History
Identifier

UC-3

Purpose

To allow donors to view their past blood donations and related
information

Priority

Medium

Pre-conditions

The user must be logged into their donor account.

Post-conditions

The donor’s donation history is displayed.
27

Typical Course of Action
S#

Actor Action

The donor navigates to the donation
history section.
The donor selects a specific donation
record.

2
3

System Response

The donor logs out or returns to the main
menu.

Displays the user’s donation history.
Shows detailed information about the
selected donation.
Saves any changes and returns to the user
dashboard.

Alternate Course of Action
S#

Actor Action

System Response

The donor’s account has no donation
history.

Displays a message indicating no donations
found.

Table 4.3 Use-Case 3 of View Donation History

Request an Urgent Donation
Identifier

UC-4

Purpose

To alert nearby donors about critical blood requirements.

Priority

High

Pre-conditions

The hospital must be in dire need of blood.

Post-conditions

Donors who are notified receive alert messages.

Typical Course of Action
S#

Actor Action

System Response
28

The hospital makes an urgent request.

Verifies that the request was received.

Eligible donors are identified by the
system.

Notifies the designated contributors

The donor is notified.

Shows the specifics of the request and
hospital information.

Alternate Course of Action
S#

Actor Action

System Response

No qualified donors were discovered in
the system.

Sends a message saying that there are
no donors available.

Table 4.4 Use-Case 4 of Request an Urgent Donation

Control the Blood Supply
Identifier

UC-5

Purpose

To Control and track the amount of blood in stock.

Priority

Medium

Pre-conditions

Post-conditions

Accurate inventory is updated.

Typical Course of Action
S#

Actor Action

System Response
29

Employees access the inventory
management system.

The blood stock is updated by staff.

The system looks for expiration dates
that are approaching.
Alternate Course of Action
3

Shows the stock levels as of right now.
Verifies updates and considers system
modifications.
notifies employees of impending
expirations.

Actor Action

System Response

Employees attempt to upgrade without
permission.

Shows an error message.

Table 4.5 Use-Case 5 of Control the Blood Supply

Manage Donor Notifications
Identifier

UC-6

Purpose

To allow donors to manage their notification preferences
regarding blood donation alerts.

Priority

Medium

Pre-conditions

The user must be logged into their donor account.

Post-conditions

The donor’s notification preferences are updated successfully.

Typical Course of Action
30

Actor Action

System Response

The donor navigates to notification
settings.
The donor updates their preferences
(e.g., email, SMS).

Displays the current notification
preferences.
Saves the changes and shows a
confirmation message.
Updates preferences and confirms the
change.

2
3

The donor opts in or out of specific alerts
(e.g., urgent requests).

Alternate Course of Action
S#

Actor Action

System Response

The donor attempts to save preferences
without making changes.
The donor provides invalid contact
information.

Displays a message indicating no
changes were made.
Shows an error message indicating the
issue.

Table 4.6 Use-Case 6 of Manage Donor Notifications

Generate Reports
Identifier

UC-7

Purpose

To allow authorized personnel to generate reports on blood
donations, inventory levels, and donor demographics.

Priority

Medium

Pre-conditions

The user must be logged in as authorized personnel.

The requested report is generated and made available for viewing
or download.
Typical Course of Action
Post-conditions

Actor Action

The authorized user selects the report
type.
The user specifies report parameters
(e.g., date range, donor type).

2
3

System Response

The user requests the report.

Displays available report options.
Processes the request and compiles
data.
Generates the report and displays it for
viewing or download.

Alternate Course of Action
S#

Actor Action

System Response

The user selects invalid report
parameters.
The system encounters an error while
generating the report.

Displays an error message indicating
the issue.
Shows an error message and suggests
retrying.

Table 4.7 Use-Case 7 of Generate Reports

Schedule Donation Appointments
Identifier

UC-8

Purpose

To allow donors to schedule appointments for blood donation.

Priority

High

Pre-conditions

The user must be logged into their donor account.

The appointment is scheduled, and the donor receives
confirmation.
Typical Course of Action
Post-conditions

Actor Action

System Response

The donor navigates to the appointment
scheduling section.

The donor selects a preferred time slot.

The donor submits the appointment
request.

Displays available time slots for
donations.
Confirms the selection and prepares to
save the appointment.
Shows a confirmation message and
sends a reminder email.

Alternate Course of Action
S#

Actor Action

System Response

The selected time slot is no longer
available.
The donor cancels the appointment
request.

Displays a message indicating the
unavailability.
Returns to the appointment scheduling
section without saving.

Table 4.8 Use-Case 8 of Schedule Donation Appointments

Track Donor Eligibility
Identifier

UC-9

Purpose

To allow donors to check their eligibility for blood donation based
on guidelines.

Priority

Medium

Pre-conditions

The user must be logged into their donor account.

Post-conditions

The donor’s eligibility status is displayed.
33

Typical Course of Action
S#

Actor Action

The donor navigates to the eligibility
section.
The donor inputs relevant information
(e.g., age, health status).

2
3

System Response

The donor submits the information.

Displays current eligibility criteria.
Analyzes the information and
determines eligibility.
Shows the eligibility status and any
recommendations.

Alternate Course of Action
S#

Actor Action

System Response

The donor provides incomplete
information.
The donor does not meet eligibility
criteria.

Displays an error message indicating
missing fields.
Shows a message explaining why they
are ineligible.

Table 4.9 Use-Case 9 of Track Donor Eligibility

4.3

Nonfunctional Requirements

Performance Requirements
•
Overview: Define the expected performance levels under different conditions (loading, usage
scenarios).
•
Examples:
•
Response Time: Specify the maximum acceptable response time for user actions (“The system
should respond to user queries within 2 seconds under normal loading”).
•
Throughput: State the expected number of transactions or requests the system should handle per
minute/hour.
•
Resource Utilization: Specify limits on CPU, memory, and network usage to ensure optimal
performance.
34

•
Rationale: Explain why these performance metrics are essential, such as enhancing user
experience, ensuring reliability, or meeting regulatory standards.
•
Real-Time Considerations If applicable, outline specific timing relationships necessary for realtime systems (“Critical alerts must be processed within 1 second”).
Safety Requirements
1. Security and Privacy of Data
• Need:
Guard private donor and recipient data from breaches and illegal access.
• Protective measures:
Use end-to-end encryption while sending data.
Make use of safe database storage techniques, such as encryption when at rest.
• Preventative Measures:
Refrain from keeping extra personal data.
Use robust user authentication procedures to stop unwanted access.
• External Regulations and Policies:
The General Data Protection Regulation (GDPR), an EU law pertaining to privacy and data protection.
The Health Insurance Portability and Accountability Act (HIPAA) is a law in the United States that
governs the privacy of health information.
• Certifications for safety:
Information security management (ISO/IEC 27001.
2. Access Control and User Authentication
• Requirement:
Make sure that sensitive application features are only accessible by authorized workers.
• Protective measures:
Put multi-factor authentication (MFA) into practice.
Adapt access controls according to user roles on a regular basis.
• Preventative Measures:
Prevent users from exchanging login information.
• External Regulations and Policies:
Access control guidelines from the National Institute of Standards and Technology (NIST).
Security Requirements
1. Data Protection and Privacy
•

Data Encryption: All sensitive information, such as donor and patient data, must be encrypted
during transmission (using HTTPS/TLS) and while stored (utilizing AES-256 encryption).
35

•

Access Control: Establish rigorous access controls to guarantee that only authorized personnel
can access sensitive information. Role-based access control (RBAC) should be implemented to
restrict access according to user roles.
Collect and retain only the essential personal information needed for managing and monitoring
blood donations. Refrain from gathering unnecessary data.

2. User Identity Verification
•

Multi-Factor Authentication (MFA): Mandate MFA for all user accounts (including donors,
hospital personnel, and blood bank managers) to strengthen account protection.
• Password Security: Implement robust password regulations, such as:
1. A minimum password length of 12 characters.
2. Incorporation of uppercase and lowercase letters, digits, and special symbols.
3. Regular updates to passwords, with a maximum allowable lifespan of 90 days.
4. User Account Validation: Utilize email or SMS verification for newly registered users to
authenticate their identity.
3. Adherence to External Policies and Regulations
•
•

•

The application must adhere to applicable data protection laws, including:
Health Insurance Portability and Accountability Act (HIPAA): To safeguard health information
in the U.S. (if relevant).
General Data Protection Regulation (GDPR): For any processing of personal data pertaining to
EU citizens.
Saudi Arabian Personal Data Protection Law: Follow local rules regulating personal data privacy.

•

Periodic audits should be performed to ensure continual compliance with these laws.

•

4.Certifications for Security and Privacy
•
•
•
•

The application should strive to acquire pertinent certifications, including:
ISO/IEC 27001: Certification for systems managing information security.
SOC 2 Type II: Certification that shows effective controls regarding security, availability, and
confidentiality.
NIST Cybersecurity Framework: Conform to best practices in handling cybersecurity risks.

5. Incident Response and Reporting
•
•

Incident Response Strategy: Create and uphold a written incident response strategy that details
the steps for identifying, reporting, and addressing data breaches or security incidents.
User Reporting System: Ensure users have a straightforward and accessible method to report
security incidents or vulnerabilities.

6. Training and Awareness
•

Implement ongoing security training and awareness initiatives for all individuals (donors, hospital
staff, and blood bank personnel) to make sure they comprehend security best practices and their
responsibilities in safeguarding sensitive information.

7. Data Retention and Disposal
36

•
•

Data Retention Policy: Develop specific guidelines for data retention, making sure that personal
information is kept only as long as necessary for its intended purposes.
Secure Data Disposal: Adopt safe practices for the disposal of personal information that is no
longer needed, guaranteeing that it cannot be recreated or recovered.

By adopting these security measures, the project will safeguard sensitive information, adhere to relevant
regulations, and maintain users’ trust in the blood donation management system.
Software Quality Attributes
1. Usability
•
•

User Interface (UI) Design: The application should achieve a System Usability Scale (SUS) score
of no less than 85 to guarantee a strong level of user satisfaction.
Ease of Use: New users should be able to complete essential tasks (e.g., registering, viewing
previous donations, making a donation request) within 3 minutes, emphasizing ease of use over
learnability.

2. Availability
•
•

Uptime: The application must ensure an uptime of 99.9% throughout a rolling 12-month period to
provide consistent access for users, particularly during emergencies.
Response Time: The system should respond to user requests within 2 seconds for 95% of
interactions, ensuring timely service.

3. Reliability
•
•

Error Rate: The application should maintain an error rate of below 1% during standard operation,
ensuring dependable functionality for essential features.
Data Integrity: The system must guarantee data integrity through automated backup processes
every 24 hours, allowing for recovery with no more than 1 hour of data loss in the event of a
failure.

4. Maintainability
•
•

Code Clarity: Aim to keep the cyclomatic complexity score for critical modules under 10, making
maintenance and updates more manageable.
Documentation: A minimum of 90% of functions and classes should be thoroughly documented,
aiding developers in understanding and modifying the code.

5. Flexibility
•

•

Feature Modularity: The application should enable the addition of new features or modifications
to existing ones with minimal impact on the current codebase, specifically less than 15%,
allowing for quick adaptations to evolving needs.
Settings Customization: Users should be able to adjust notification settings in no more than three
steps, enhancing their flexibility.

6. Interoperability

•

API Compatibility: The application must offer RESTful APIs that adhere to industry standards,
allowing integration with at least three third-party services (such as Google Maps and SMS
gateways).
Data Format Support: The application should support common data formats (like JSON and
XML) to ensure seamless data exchange with external systems.

7. Portability
•
•

Cross-Platform Compatibility: The application must function smoothly across major platforms
(iOS, Android, and web), providing a uniform user experience no matter the device used.
Simple Deployment: The application should be deployable on a standard cloud platform within
half an hour, minimizing setup complexity.

8. Testability
•

•

Coverage of Automated Testing: A minimum of 80% of the codebase needs to be covered by
automated tests (unit, integration, and functional tests) to guarantee effective testing and quality
control.
Defect Rate: Keep the defect rate to less than 0.5 defects per 1,000 lines of production code,
reflecting high-quality standards and testability.

9. Robustness
•
•

Error Handling: The system must manage at least 95% of anticipated error situations without
crashing, offering users clear messages and options for recovery.
Input Validation: All inputs from users should be checked, aiming for a failure rate of below 1%
for unhandled exceptions to improve resilience against invalid data.

10. Reusability
•
•

Component Design: Components should be crafted for reuse throughout various sections of the
application, aiming for at least 70% code reusability across similar functions.
Library Utilization: Utilize existing libraries and frameworks whenever possible to shorten
development time and improve dependability.

Focusing on these quality attributes will ensure the blood donation management application provides an
excellent user experience while effectively serving both donors and healthcare providers.
Other Requirements (Optional)
1- Database Requirements
The system shall utilize MySQL database in maintaining data of users and data of other applications.
Data backups shall be scheduled daily to maintain the integrity and availability of data.
2- External Interface Requirements
The system must be compatible with external hardware devices; for instance, barcode scanners used
within the inventory system.
38

3- Internationalization Requirements
The system shall provide its services in multiple languages to accommodate a large group of users,
including but not limited to English, Spanish, and French.
4- Legal Requirements
It shall be designed to process users’ data based on the regulations of GDPR. Terms of Service and
Privacy Policy documents shall be provided for and agreed to by the users upon account creation.
5- Reusable Objectives
Coding shall be modularized and reusable so that future software development projects, targeted at the
organization, can be done in an easy manner.
Documentation shall be provided for reusable components so that proper documentation is readily
available for easy incorporation into other projects.
Other Requirements These provide the background and information pertinent to the successful execution
and deployment of the software product.

4.4

Analysis Models

Use Case Diagram for Blood Link System
Description:
The use case diagram visually represents the interactions between various actors (such as donors, hospital
staff, and system administrators) and the system’s functionalities in the Blood Link system. It identifies
the key use cases, such as creating a donor account, logging in, viewing donation history, and requesting
urgent donations, providing a clear overview of the system’s requirements.

Actors
•
•
•

Donor: Individuals who can create accounts, log in to access their personal accounts, view their
donation history, manage notifications, schedule appointments, and track eligibility.
System Administrator: Manages the overall system, logs in to manage user accounts and
permissions, monitors donor activities, generates operational reports, and oversees user access.
Hospital Staff: Alerts donors about urgent needs, logs in to access the system for scheduling
appointments, notifies donors about critical blood requirements, and manages blood supply
requests.

Use Cases
•

Create a Donor Account: Enables users to register and set up their profiles for blood donation.
39

•

View Donation History: Allows donors to check their past donations and relevant statistics.

•

Schedule Donation Appointments: Lets donors and hospital staff manage specific times for
blood donations.

•

Manage Donor Notifications: Provides an option for donors to customize their notification
preferences.

•

Request an Urgent Donation: Facilitates hospitals in notifying donors about critical blood
requirements.

•

Track Donor Eligibility: Automatically checks each donor’s eligibility based on their donation
history.

•

Control the Blood Supply: Ensures accurate tracking and management of blood inventory.

•

Generate Reports: Creates detailed reports on blood supply, donation frequency, and expiration
dates.

Visual Representation:

CHAPTER 5: SYSTEM DESIGN
5.1 Component Diagram
5.1.1 Blood Link Platform
Our Blood Link Platform acts as the main interface for users, which includes Donors, Hospital Staff, and
System Administrator. Key subcomponents consist of:
•

Donor Search: This feature enables users to locate potential donors based on criteria like
location and blood type. It interacts with the Blood Inventory to ensure that available matches are
presented.

•

Donation Management: This component oversees the requests and scheduling of blood
donations. It is responsible for tracking donation requests and coordinating with both Blood
Inventory Management and Notification Services to provide timely updates.

•

Authentication: This module manages user registration, login processes, and access control. It
ensures secure access to platform features according to user roles (donors, hospital staff, system
administrator).

5.1.2 Blood Inventory Management
The Blood Inventory Management component is tasked with monitoring and updating blood stocks
throughout the system. It includes:
•

Blood Inventory: This part manages details regarding inventory, including blood type
availability, storage locations, and alerts for low stock levels. It connects with the Donor Search
to supply information about available blood types and interacts with Notification Services to
inform stakeholders when supplies are running low.

5.1.3 Reporting and Analytics
The Reporting and Analytics component empowers the platform to monitor and analyze critical metrics,
providing valuable insights for healthcare providers. It includes:
•

Donation History: This maintains records of all donation events, such as dates, donor
information, and locations. This data is essential for generating reports and observing donation
trends.

•

Registered Users: This module manages user information, including donor profiles and details of
hospitals/blood banks. It supports notification-related interactions by storing specific user data.

5.1.4 Notification Services
The Notification Services component is specifically designed for delivering alerts and reminders. It
consists of:
•

Send Donation Reminders: This feature sends notifications to donors based on their donation
history, informing them when they are eligible to donate again.
41

•

User Notifications: This sends updates to registered users regarding new donation requests,
reminders for profile completion, or alerts about inventory levels based on current stock.

This component-based architecture enables the Blood Link system to be modular and scalable, with each
component dedicated to a particular function. The interconnections between components facilitate
efficient data sharing and real-time updates, ensuring a seamless user experience and effective
management of blood donations and inventory.
Visual Representation:

Diagram 5.1: Component Diagram

5.2 Deployment Diagram
The deployment diagram represents the physical architecture of the system, illustrating how different
components are distributed across hardware nodes. The diagram showcases the key infrastructure
components including the Web Server hosting the Blood Link Platform interface, Application Server
managing business logic and inventory systems, and Database Server handling data persistence for user
and inventory information. Communication between these nodes is clearly specified through standard
protocols – HTTPS for client-server communication, TCP/IP for internal server communication, and
JDBC for database connectivity. This architecture ensures secure, efficient, and reliable system operation
while maintaining clear separation of concerns across different system layers.

Diagram 5.2: Deployment Diagram

5.3 Design Level Sequence Diagram
This sequence diagram illustrates the interactions between a user, an admin, the system, a database, and
the Google Maps API for a blood donation application. It outlines two main scenarios: standard
registration and donation request, and emergency donation request.
Scenario 1: Standard Registration and Donation Request
1. Sign Up: The user initiates the sign-up process.
2. Store User Information: The system stores the user’s information in the database.
3. Confirm Storage: The database confirms successful storage, and the system informs the user of
successful registration.
43

4. View Past Donations: The user can view their past donation history.
5. Retrieve Donation History: The system retrieves the user’s donation history from the database.
6. Display Donation History: The system displays the donation history to the user.
7. Request Donation (Alternative Flow – User Wants to Donate): If the user wants to donate,
they submit a donation request.
8. Check Eligibility: The system checks the user’s eligibility to donate.
9. Eligibility Status: The system informs the user whether they are eligible to donate.
10. Donation Request Approved: If eligible, the system approves the donation request.
Scenario 2: Emergency Donation Request (Alternative Flow)
1. Initiate Emergency Request: The user initiates an emergency donation request.
2. Match Donors in Proximity: The system searches for matching donors in proximity using
location data.
3. Donor Matches Found: The system identifies potential donors.
4. Send Emergency Message: The system sends an emergency message to the matched donors.
5. Locate Blood Bank: The system locates the nearest blood bank.
6. Get Location: The system requests the location of the blood bank from the Google Maps API.
7. Location Details: The Google Maps API returns the location details to the system.
8. Display Blood Bank Location: The system displays the blood bank location to the user.
9. Manage Blood Inventory: The admin manages the blood inventory.
10. Update Inventory Records: The system updates the inventory records in the database.
11. Inventory Updated: The database confirms the inventory update, and the system notifies the
admin.
The diagram clearly shows the flow of information and actions between the different actors and
components involved in both standard and emergency donation scenarios. It highlights the use of the
database for persistent storage, the Google Maps API for location services, and the different roles of the
user and the admin.

Diagram 5.3: Design Level Sequence Diagram

5.4 Complete Class Diagram
Donor
The Donor class represents individuals who volunteer to donate blood.

Attributes:
– donorID: int: Unique identifier for each donor (Private)
+ name: String: Full name of the donor (Public)
+ bloodGroup: String: Blood type of the donor (Public)
+ contactInfo: String: Contact details (Public)
– medicalHistory: String: Donor’s health information (Private)
Methods:
+ register(): Allows new donors to sign up (Public)
+ updateHealthInfo(): Updates health information (Public)
+ viewDonationHistory(): Displays past donations (Public)
Relationships:
Association: The Donor class is associated with the Donation class, as a Donor can have multiple
Donation objects.
Multiplicity: “ 1 to * “(one donor can have multiple donations)

BloodBank
The BloodBank class manages the inventory and operations of blood banks.
Attributes:
– bankID: String: Unique identifier for the blood bank (Private)
+ location: String: Geographic location of the blood bank (Public)
– inventory: List : List of available blood donations (Private)
Methods:
+ updateInventory(): Updates blood stock (Public)
+ sendRequest(): Sends requests to donors (Public)
+ getInventoryStatus(): Provides inventory status (Public)
Relationships:
46

Aggregation: The BloodBank class aggregates the Donation class, as a BloodBank can have multiple
Donation objects in its inventory.
Multiplicity: “1 to * ” (one blood bank can have multiple donations)

Hospital
The Hospital class represents healthcare facilities that require blood.
Attributes:
– hospitalID: int: Unique identifier for the hospital (Private)
+ name: String: Name of the hospital (Public)
+ location: String: Address of the hospital (Public)
+ contactInfo: String: Contact details (Public)
Methods:
+ requestBlood(): Initiates a blood request (Public)
+ updatePatientStatus(): Updates patient information (Public)
Relationships:
Association: The Hospital class is associated with the Donation class, as a
Hospital can request multiple Donation objects.
Multiplicity: “1 to * ” (one hospital can request multiple donations)
Dependency: The Hospital class depends on the Notification class to send notifications to donors or staff.
Multiplicity: “1 to * “(one hospital can send multiple notifications)

Donation
The Donation class captures details of each blood donation event.
Attributes:
– donationID: int: Unique identifier for each donation (Private)
– donorID: int: Identifier linking to the donor (Private)
+ bloodType: String: Type of blood donated (Public)
+ date: Date: Date and time of donation (Public)
+ location: String: Location of the donation (Public)
Methods:
47

+ recordDonation(): Logs a new donation (Public)
+ getDonationDetails(): Retrieves donation details (Public)
Relationships:
Aggregation: The Donation class is aggregated by the BloodBank class, as a BloodBank can have
multiple Donation objects in its inventory.
Association: The Donation class is associated with the Donor class, as a Donor can have multiple
Donation objects.
Multiplicity: “1 to * “ (one donor can have multiple donations)

Notification
The Notification class handles the communication between the system and users.
Attributes:
– notificationID: int: Unique identifier for each notification (Private)
– recipientID: int: Identifier for the recipient (Private)
+ message: String: Content of the notification (Public)
+ timestamp: Date: Date and time of notification (Public)
Methods:
+ sendNotification(): Sends a message to the recipient (Public)
+ viewNotifications(): Displays notifications to users (Public)
Relationships:
Dependency: The Notification class is depended upon by the Hospital class, as a Hospital can send
multiple Notification objects.
Multiplicity: “ * to 1” (multiple hospitals can send notifications to one notification)
Association: The Notification class is associated with the Donor class, as a Donor can receive multiple
Notification objects.

Diagram 5.4: Complete Class Diagram

5.5: Entity-relationship diagram.
This is an Entity-Relationship Diagram (ERD) for a “Blood Link”. It visually represents the database
schema, showing the tables (entities) and how they relate to each other.
Here’s a breakdown of the diagram:
Entities:
donations: Represents individual blood donations.
id: Primary key (unique identifier).
bloodBankId: Foreign key referencing blood_banks.
date: Date of donation.
quantity: Amount of blood donated.
donorId: Foreign key referencing donors.
blood_banks: Represents blood banks.
id: Primary key.
name: Name of the blood bank.
location: Location of the blood bank.
contactInfo: Contact information for the blood bank.
donors: Represents blood donors.
id: Primary key.
49

name: Name of the donor.
bloodType: Blood type of the donor.
contactInfo: Contact information for the donor.
lastDonationDate: Date of the donor’s last donation.
notifications: Represents notifications sent to users (likely donors or blood banks).
id: Primary key.
donorId: Foreign key referencing donors.
message: Content of the notification.
dateSent: Date and time the notification was sent.
hospitalId: Foreign key referencing hospitals.
hospitals: Represents hospitals.
id: Primary key.
name: Name of the hospital.
location: Location of the hospital.
contactInfo: Contact information for the hospital.
Relationships:
The lines connecting the entities represent relationships, with cardinality (the number of instances
involved) indicated by numbers:
1: * (One-to-Many): A blood bank (blood_banks) can have many donations (donations), but a donation
belongs to only one blood bank.
1: * (One-to-Many): A donor (donors) can have many donations (donations), but a donation is from only
one donor.
1: * (One-to-Many): A donor (donors) can receive many notifications (notifications), but a notification is
sent to only one donor.
1: * (One-to-Many): A hospital (hospitals) can have many notifications (notifications), but a notification
is related to only one hospital.
Data Types:
The diagram also specifies data types for each attribute (e.g., string, integer, date, string pk for primary
key).
In summary, this ERD provides a clear and concise representation of the database structure for the Blood
Link Project, outlining the entities and their relationships to manage information about blood donations,
blood banks, donors, hospitals, and notifications.

Diagram 5.5: Entity-relationship diagram

CHAPTER 6: SYSTEM IMPLEMENTATION

CHAPTER 7: TESTING & EVALUATION

Identifier

TC-1

Priority

High

Related
requirements(s)

UC-1

Short description

User Create account

Pre-condition(s)

Welcome page

Input data

(Full name, user name, Department, Email, phone
number)

Detailed steps

…

Expected result(s)

Registration page

Post-condition(s)

User granted access

CHAPTER 8: RESULTS AND ANALYSIS

CHAPTER 9: CONCLUSION AND FUTURE WORK

6.1

Conclusion

6.2

Future Work

REFERENCES
•
•
•

•

•
•

•

SpringerLink. (2024). Real-time-based blood wastage management using IoT and blockchain
technology. Cluster Computing.
IEEE Xplore. (2024). Transforming blood donation processes with blockchain and IoT
integration. Retrieved from
McElfresh, D. C., Kroer, C., Pupyrev, S., Sodomka, E., Sankararaman, K., Chauvin, Z., Dexter,
N., & Dickerson, J. P. (2021). Matching algorithms for blood donation. Proceedings of the 21st
ACM Conference on Economics and Computation, 431–432.

Epifani, I., Lanzarone, E., & Guglielmi, A. (2023). Predicting donations and profiling donors in a
blood collection center: A Bayesian approach. Flexible Services and Manufacturing Journal,
35(4), 1187–1208.
AlZu’bi, S., Al-Maolegi, M., & Hammad, M. (2022). An intelligent system for optimizing blood
donation process: Preventing shortages and minimizing wastage. Cluster Computing, 25, 12341248.
Niklas, S., Brandl, A., & Seifried, E. (2023). The impact of digital transformation on blood
donation: Insights into donor behavior and digital solutions. Transfusion Medicine and
Hemotherapy, 50(6), 531-540.
ResearchGate. (2023). Optimizing the blood donation app with gamification using user-centered
design. Proceedings of the Human-Computer Interaction Conference, 42(3), 123–134. Retrieved
from
SpringerLink. (2022). A design science approach to blood donation apps: Enhancing user
engagement through UX design. Lecture Notes in Computer Science, 1331, 223–235.

PLOS Journals. (2023). Knowledge and misconceptions about blood donation among young
adults. PLOS ONE, 18(8), e0295600.
Frontiers. (2023). Voluntary blood donation knowledge, attitudes, and practices among adults: A
cross-sectional study. Frontiers in Public Health, 11, Article 1141544.

Edwards, E. A., Lumsden, J., Rivas, H., Steed, L., Edwards, L. A., Thiyagarajan, A., & Sohanpal,
R. (2016). Gamification for health promotion: systematic review of behaviour change techniques
in smartphone apps. BMJ Open, 6(10), e012447.
Aschentrup, L., Steimer, P. A., Dadaczynski, K., Mc Call, T., Fischer, F., & Wrona, K. J. (2024).
Effectiveness of gamified digital interventions in mental health prevention and health promotion
among adults: a scoping review. BMC Public Health, 24(1), 69.
Green, T. (2022). Online blood donation systems: A systematic review of accessibility and
demographic outreach. Journal of Health Informatics, 15(4), 123-135.

Keshta, I., & Odeh, A. (2020). Security and privacy of electronic health records: Concerns and
challenges. Egyptian Informatics Journal, 21(1), 61-72.

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

Yüksel, B., Küpçü, A., & Özkasap, Ö. (2017). Research issues for privacy and security of
electronic health services. Future Generation Computer Systems, 68, 1-13.

SpringerLink. (2021). Gamified mobile blood donation applications: Motivating donors through
rewards and engagement. Proceedings of the Human-Computer Interaction Conference, 125,
145-156.
SAGE Journals. (2021). Gamification in health care management: Motivating behavior change
and increasing participation. SAGE Open, 11(4), 1-10.

American Red Cross. (2024). Blood donation services. American Red Cross Website. Retrieved
from
JustUseApp. (2024). Blood Donor American Red Cross reviews. Retrieved
from
NHS Blood and Transplant. (2024). GiveBlood platform overview. NHS Blood and Transplant
Website. Retrieved from
National Institute of Standards and Technology (NIST). (2024). Data encryption and security
protocols. NIST website.
Project Management Institute. (2024). Project management methodologies: Agile. PMI Website.
Retrieved from
Social Media Marketing. (2024). Strategies for donor recruitment. Social Media Marketing
Website. Retrieved from
API Documentation. (2024). Integrating with blood bank databases. Retrieved from

Design Principles. (2024). The importance of brand identity in user engagement. Retrieved from

Nielsen Norman Group. (2023). User-centered design principles for effective platforms. Nielsen
Norman Group Website. Retrieved from
Privacy-enhancing Technologies. (2024). Data anonymization and aggregation methods.
Retrieved from
Health Analysis for Donors. (2024). Benefits of health insights for blood donors. Retrieved from

Predictive Analytics. (2024). Predicting blood demand and improving supply chain management.
Retrieved from
Market Research. (2024). Understanding your audience: Key strategies for user-centered design.
Retrieved from
XR Technologies in Healthcare. (2024). Enhancing user experience and education through VR
and AR. Retrieved from
BloodConnect. (2024). Connecting donors and recipients in India. BloodConnect Website.
Retrieved from
Kulsum, S. T., & Gopal, K. M. (2024). Digital transformation in blood banking: The story of eRaktkosh. International Journal of Future Medicine and Research, 6(2), 1–10.

MarketingProfs. (2023). Effective communication strategies for donor engagement.
MarketingProfs Website. Retrieved from
57

•
•

Home Blood Donation Services. (2024). Enhancing blood donation through home collection
services. Retrieved from
Pal, S. K. (2024, October 18). Waterfall model – Software engineering. GeeksforGeeks. Retrieved
from

APPENDIX: Glossary
This glossary is a crucial resource that defines the essential terms, acronyms, and abbreviations
used in the Blood Link project’s Software Requirements Specification. Understanding these
terms is not just important; it is integral to all stakeholders interpreting the document
and effectively contributing toward the project’s success.
Blood Link is not just a project name; it’s a mission. Blood Link would connect blood donors
with hospitals in real time and inspire us all to make a difference in healthcare.
SRS: This is more than just a document; it’s our guiding light. It meticulously describes the
intended purpose, functionality, and features of the software to be developed, providing a clear
roadmap for our journey and instilling confidence in our actions.
API: The collection of rules and protocols that allows the development and interaction of
software applications, enabling different systems to communicate. In the Blood Link project, the
API will help in real-time communication between the donor’s mobile application and
the hospital’s blood bank system.
UI: How users interact with a computer system or application, including the screens, buttons,
and other visual elements.
Real-time Communication: Users can send and receive information instantly, enabling
immediate responses during emergencies.
Donor: An individual who voluntarily gives blood for medical use.
Blood Bank: A facility that collects, stores, and distributes blood and blood products.
Emergency Notification: A message informing registered donors of urgent hospital blood
needs.
Stakeholder: Any person or party that has a direct interest in the project, including donors,
hospitals, healthcare professionals, and members of the project team.
Inventory Management: This is the process involved in storing and issuing blood
supplies within a blood bank.
Proactive participation: Engaging oneself in health initiatives without having to be prompted.
Proactive participation in the Blood Link project would translate to regular blood
donations, being current with emergency notifications, and proactive project promotion among
potential donors and hospitals.
Dashboard: A visual display of critical information and metrics, thus allowing users to monitor
and manage the activities related to blood donations.
Mobile Website: A website optimized to be viewed through smartphones and
tablets, thus allowing donors the convenience of access.
59

User-Centered Design: This is more than just a design philosophy; it’s a commitment. It
puts the end-users needs, preferences, and behaviors at the forefront, ensuring that the project is
truly for them.
This glossary is a vital tool that will help clarify the terms used throughout the SRS. By
ensuring effective communication among all project stakeholders, it will foster a sense of
inclusion and integral contribution to the project’s success.

Purchase answer to see full
attachment

Share This Post

Order a Similar Paper and get 15% Discount on your First Order

Our Services

senior project

Description

Share This Post

Related Questions

Strategic Management (MGT 401)

Module 07: Introduction

discussion RES500

Power bi simple report someone knows how to use it please

212 solve new

181 solve

311 ass 5

314 ass 9

314 ass 10

215 ass 1

215 ass 2

Management Question

Management Question

Management Question

Management Question

Management Question

MGT521 M6-Discussion Forum: Navigating Change Through Formal Structures and Systems

MGT530 M6-Discussion Forum: Reliability and Decision Theory