“Blood Finder”

Online Blood Donation Management System

A Project presented to the National University in partial fulfillment of the requirement for
the degree of Bachelor of Science (Hon’s) in Computer Science & Engineering

Supervised By
Poly Bhoumik

Senior Lecturer (Depertment of Computer Science and Engineering)

Daffodil Institue of it

Submitted By
Naziha Shamsuddin
Reg No: 17502005059
Session: 2017-18

Department of Computer Science & Engineering

Daffodil Institute of IT, Dhaka
Under National University, Bangladesh

i
 DECLARATION
We pledge that the project work titled “Blood donation Management system” being
submitted in partial fulfillment for the degree of [Link]. (Hon’s) in Computer Science
Engineering is the original work carried out by me. It has not formed part of any other
project work submitted for any degree or diploma, either in this or any other University.

Naziha Shamsuddin
Reg No: 17502005059
Session: 2017-18

ii
 APPROVAL
The Project “Blood Donation Management system” is submitted to the Department of
Computer Science Engineering, DIIT under National University of Bangladesh in
absolute fulfillment of the requirements for the degree of Bachelor of Science (Hon’s) in
Computer Science and Engineering and approved as to its style and content.

Examiner Examiner

Poly Bhoumik Md. Imran Hssain

Project Supervisor Head of
Senior Lecturer, Department of CSE, Department CSE, DIIT
DIIT

iii
 ACKNOWLEDGMENT
I would like to express my profound gratitude to Almighty. With the blessing of
Almighty Allah, I have successfully planned my project.

My sincere thanks to Prof. Dr. Mohammed Shakhawat Hossain, Principal, DIIT who
has allowed me to do this project and encouragement given to me. Also, thanks for his
valuable guidance and support to meet the successful completion of my project.

I express my gratitude to Poly Bhoumik, Senior Lecturer & Supervisor, DIIT, Dhaka, for
having pro- vided us with the facilities to do the project successfully.

My heartiest thanks Md. Imran Hossain, Head, Department, of the CSE & Coordinator
DIIT, Dhaka, for his patronage and for giving me an opportunity to undertake this
Project.
I express my gratitude to Saidur Rahman,Senior Lecturer, DIIT, Dhaka, for having
provided us with the facilities to do the project successfully.

I express my gratitude to Safrun Nesa Saira, Lecturer, DIIT, Dhaka, for having provided
us with the facilities to do the project successfully.

I express my gratitude to Nusrhat Jahan Sarkar, Lecturer, DIIT, Dhaka, for having
provided us with the facilities to do the project successfully.

I express my gratitude to Mizanur Rahman, Lecturer, DIIT, Dhaka, for having provided
us with the facilities to do the project successfully.

I express my gratitude to Md. Mushfiqur Rahman, Lecturer, DIIT, Dhaka, for having
provided us with the facilities to do the project successfully.

Last but not the least, I extend my sincere thanks to my family members and my friends
for their constant support throughout this project

iv
 ABSTRACT
Blood Donation Management System (BDMS) is a browser-based system that is
designed to store, process, retrieve and analyze information concerned with the
administrative and inventory management within a blood bank. This project aims at
maintaining all the information pertaining to blood donors, different blood groups
available in each blood bank and helps them manage in a better way. Aim is to provide
transparency in this field, make the process of obtaining blood from a blood bank hassle
free and corruption free and make the system of blood bank management effective. Our
client is not interested in blood stocking instead we are stocking blood donors’
information. The donors who are interested in donating blood has to register in the
database. There is no storage of blood so no complications in the project. The software is
fully integrated with CRM (customer relationship management) as well as CMS (content
management system) solution. It is developed in a manner that is easily manageable, time
saving and relieving one from manual works. The requirement of the blood has to be
requested and we supply the information of the donor. The donors can update their status
whether they are available or not.

v
 Table of Contents
Declaration ii
Approval iii
Acknowledgment iv
Abstract v
Table of Content

Chapter 1 : Introduction
04
1.1 Project Introduction 05
1.2 Project Goal and Objective 07
1.3. Feature of the System 08
1.4. Scope of the Project 08
1.5 Proposed System 09
1.6 Limitation
1.7 Advantages
1.8 Why we Select This Project

Chapter 2 :Background Analysis

2.1. Background Study 11
2.2. Existing System 11
2.3. Proposed System 12
2.4. Feasibility Study 13

Chapter 3 : System Design

16
3.1 Agile Method 17
3.2 Advantage & Disadvantage 17
18
3.3 Method
18
3.4 Analysis 19
3.5 Requirements 20
3.6 Flow Chart 21
3.7 Work Flow Diagram 22
3.8 System Architecture 23
23
3.8 Methodology 25
3.9 Entity Relationship (E-R) 29
3.10 Activity Diagram 30
1
 3.11 Sequence Diagram 33
3.12 Data Flow Diagram 36
3.13 Use Case Diagram
39
Chapter 4 : Source Code & Implementation 45
4.1 Source Code
4.2 Implementation

Chapter 5 : Conclusion 49
5.1 Conclusion 50
5.2 Business Prospect
51
Reference

2
 List of Figures
Figure 1: Agile Method 16
Figure 2 : System Flow Diagram 18
Figure 3: Flow Chart Diagram 20
Figure 4: Work Flow Diagram 21
Figure 5: ER Diagram Diagram 27
Figure 6: Activity Diagram 29
Figure 7: Sequence Diagram 32
Figure 8: Data Flow Diagram L0, L1 34
Figure 9: Data Flow Diagram L0, L1 35
Figure 10: Use Case Diagram 37

3
 CHAPTER 1

INTRODUCTION

4
1.1 Project Introduction
A blood donation is a process whereby a person voluntarily has blood drawn to be used
for future transfusions when in need at hospitals for treatment procedures that require
them. Donation may be of whole blood (blood drawn directly from the body) or of
specific components of the blood; such as red blood cells, white blood cells, plasma, and
platelets. Blood banks often participate in the process of collecting blood and other
procedures such as managing stocks, approving blood requests and updating donation
information. The inspiration of this project is to improve blood banks in Bangladesh and
to develop a blood bank information system which focuses on making an online system
that is accessible for both donors and administrators. Donors can directly receive
information regarding their previous blood donations, including their blood results and
donation history, in order to easily schedule their next donations. They can also update
the personal information through the system, without having to contact the blood bank
registry. The system is also developed for the administrators, who are the main authority
in the system. Administrators can add, modify, delete, and query any donation
information if necessary. The administrator is also responsible for responding to the
hospital’s blood requests and checking the stocks in the blood bank’s inventory.

1.2 Project Goal and Objective

Goals and objectives are statements that describe what the project will accomplish.
Objectives are lower-level statements that describe the specific, tangible products and
deliverables that the project will deliver. Objectives are concrete statements describing
what the project is trying to achieve. The objective should be written at a lower level, so
that it can be evaluated at the conclusion of a project to see whether it was achieved or
not. Goal statements are designed to be vague. Objectives should not be vague. A well-
worded objective will be Specific, Measurable, Attainable/Achievable, Realistic and
Time-bound. The Purpose of this system is if any critical or emergency situation it will be
more useful to save the lives. Because in this system there is a one method called sending
SMS to the registered donors. Using that function the system users or admin can send a
SMS just clicking one button. And have some other purpose for using this system.
Nowadays hackers and intruders are very disturbance for any kind of system, such as
Standalone or Web based Systems. So, this system is very securing rather than other
systems.
And the earlier day’s hospitals and blood camps were used paper base recording system.
Even though today also they all using Paper recording system. What I’m trying to say is
paper records are not secures, because any one can see the donors’ personal details
without authorized permission, if any natural disaster happened, I mean flood or
something happened then we can’t sure papers are safe in that place. And there are more
and more disadvantages using paper records. If we are using Computerized or Database

5
record will be more secured. Anyone cannot see or update the records without authorized
permission. It will be more useful, and the blood camp authorized people can handle
these problems just simply. Because they all are the people really going to be used this
system. Some main objectives of this project,
 To computerize all details regarding blood donor details & events details.
 To automate the process of sending mail selecting via district.
 To maintain records effectively.
 To manage current blood group of the donors and maintaining new events
 The project has information regarding the fresh blood donors, already
registered blood donor details, events, creating new events details and sending
SMS to already registered blood donors in the system.
 Creating New Admin and Users for the System, only from admin privilege.
 The valuable data can be kept as secure.
 Creating new events to display about when next blood camp?

1.3 Features of Our System

1. User Registration
2. Donor Profiles
3. Search and Match
4. Appointment Scheduling
5. Donation History
6. Blood Inventory Management
7. Notifications
8. Donor Eligibility Check
9. Emergency Requests
10. Feedback and Ratings
11. Privacy and Security
12. Admin Dashboard
13. Analytics and Reporting
14. Mobile Accessibility

1. User Registration and Login: Users can register themselves and create accounts
within the system. They can then log in using their credentials to access the system's
features.
2. Donor Registration and Management: The system allows individuals to register as
blood donors. It collects and stores their personal information, blood type, medical
history, and contact details. Donor management features enable tracking of donor
activities, appointments, and notifications.

6
3. Blood Inventory Management: The system tracks the available blood units in the
inventory. It manages the storage, labeling, and tracking of blood units. The features
include recording details such as blood type, quantity, expiration dates, and testing
information.
4. Blood Donation Scheduling and Reminders: Donors can schedule appointments for
blood donations through the system. The system sends automated reminders to donors,
ensuring a steady supply of blood and maintaining a donor database.
5. Blood Request and Allocation: Medical facilities or individuals can request blood
units through the system. The system facilitates the matching of blood types and allocates
the appropriate blood units based on availability and compatibility.
6. Blood Testing and Quality Control: The system enables tracking and management of
blood testing processes, ensuring the safety and quality of donated blood. It records test
results, tracks expiration dates, and triggers alerts for expired or unsuitable blood units.
7. Delivery and Logistics Management: The system coordinates the transportation and
delivery of blood units from the blood bank to requesting medical facilities or
individuals.
8. Reporting and Analytics: The system generates reports and analytics to provide
insights into blood inventory, donor statistics, blood utilization, and other relevant
metrics. These reports help in decision-making, resource allocation, and monitoring
system performance.
9. Notifications and Alerts: The system sends notifications and alerts to donors, medical
facilities, and administrators for various events such as appointment reminders, low
inventory levels, test results, and system updates.
10. Administrator Dashboard and User Roles: The system provides an administrator
dashboard with features for managing user accounts, permissions, and system settings. It
supports different user roles, such as administrators, donors, and medical facility staff,
with appropriate access levels and functionalities.
11. Security and Privacy: The system incorporates robust security measures to protect
sensitive donor information, blood inventory data, and system transactions. It includes
features like secure login, data encryption, access control, and regular backups.

1.4 Scope of the Project

Anyone who has ever done a project will have tales of how scope changes caused grief.
Scope is bound to change, and this is to be expected. As the detail becomes clearer, more
complications creep in. These are not foreseeable at the start and hopefully I build in a
contingency for what we cannot see. The scope changes that usually cause problems are
those where the perception of what was in and out of scope was different between various
parties. The Scope of the project mean normally expecting the result of something. Scope
is same like the motivation and objectives. But there some more special in this case.
Scope is really expecting, as we take our system, we have to think why we are using

7
computerized system rather other paper base, and we have to think what purpose of that
system. Why we need computerized system, actually today’s world we can’t maintain or
manage the things without proper system or computer. Now computers are merge with
our life. So, the computer-based systems are very popular, and that’s very secure rather
than paper base system. If we tell one example there were happened a flood disaster, and
all the paper-based records can be Drench to the water. Then we cannot recover the
important information. This kind of situation we can recover the information by using
computerized system. Just remove the hard disk and recover the file easily and security is
high, because using computerized system is not allow to use any peoples without their
accounts or authorized permission. So, the paper base is not like that, anyone can see the
information and they can do for that information whatever they want. As my project also
a computerized system called Blood Donor Information System. This system can be used
in the hospitals, blood donor camps, or any other important public places, and etc. Blood
Donor Information System will be more use full for the important medical places,
because if someone need blood immediately, the system will help to identify the blood
donor, and it will be sending a SMS to that donor. So, it will be making a quick
communication with donors. As I told earlier the purpose of this system is send SMS to
the donors in the critical situation. My initial thought is that this scope statement
completely lacks any of the SMART goal features. SMART stands for,
 Specific
 Measurable
 Agreed Upon
 Realistic
 Time Bound

1.5 Proposed System

The proposed Blood Donation System project aims to create an efficient and user-
friendly online platform to streamline the blood donation process. This system will serve
as a vital bridge between donors and recipients, offering a seamless experience for both
parties. Donors will be able to register, schedule appointments, and track their donation
history with ease. On the other hand, recipients can swiftly search for available donors in
their vicinity and send requests for blood when urgently needed. The system will also
incorporate features like donor eligibility checks, real-time blood inventory management,
and automated notifications for critical blood requests. By leveraging technology to
connect donors and recipients, this project seeks to make a substantial impact on
improving blood donation rates, ensuring a stable blood supply, and ultimately saving

8
lives within our community.. The people in need of blood can search for the donors by
giving their blood group and city name. It is very flexible and user friendly. The person’s
time and work is reduced very much which prevails in the present system. Easy and
Helpful. The people are not limited to receive or provide services in working hours of the
branch only; he is serviced 24 hours a day, 7 days of week and 365 days of the year.

1.6 Limitation
 This project is not available to those who doesn’t use Internet and Mobile or
Computer
 In this project the contact person’s details are given for the limited cities only.

1.7 Advantages
I provided in the application with various controls. The system makes the overall project
management much easier and flexible. Readily upload the latest updates "allows user to
download the alerts by clicking the URL. It provides high level of security with different
level of authentication
 Users do not have to contact the hospital to know the results of their blood
donation. They can view their results through the website by logging-in with
their username and password.
 The reports and information are kept in electronic form and can be easily
maintained by the administrators, and donors may access their donation records
whenever they want to.
 The reports of donations are kept in electronic files so that they may last longer
and have less chance of being lost or damaged.
 Administrators of the system can easily manage blood stock and blood
withdrawals that have been requested by the hospitals.

1.8 Why we select this Project

We have chosen to undertake the "Blood Donation System - Blood Finder" project for
several compelling reasons. Firstly, it addresses a critical need within our community and
the healthcare sector at large. Blood shortages are a recurring problem, especially during
emergencies and crises. By creating a dedicated platform, we can facilitate a more
efficient and organized process for blood donation, ensuring a stable supply of this life-
saving resource.
Secondly, the project aligns with our commitment to social responsibility and community
welfare. Blood donation is a selfless act that directly contributes to saving lives, and by
developing this system, we can encourage more individuals to become regular donors and
promote a culture of giving back.

9
Furthermore, "Blood Finder" leverages technology to simplify the blood donation process
for both donors and recipients. This modern approach allows for easier appointment
scheduling, real-time inventory management, and quicker responses to urgent blood
requests, making the entire system more accessible and effective.
In sum, we believe that the "Blood Donation System - Blood Finder" project represents
an opportunity to make a tangible impact on our community's health and well-being
while harnessing the power of technology to streamline and modernize blood donation
practices.

10
 CHAPTER 2

BACKGROUND

ANALYSIS

11
2.1 Background Study
The Blood Donor information system is fully computerized system it makes easy to
manage the system by the administrator. And the beginning of this project is research. I
mean researching new things and identify the fact and knowledge about that, focus on the
following areas of study, Project Documentation or the Report will give the brief idea
about the system which has been developed by the developers. In the project
documentation contain many facts, such as software development life cycle and each
stage, I mean explanation of each stage or phase and etc. And the beginning of this
project is research. I mean researching new things and identify the fact and knowledge
about that, focus on the following areas of study, Project Documentation or the Report
will give the brief idea about the system which has been developed by the developers. In
the project documentation contain many facts, such as software development life cycle
and each stage, I mean explanation of each stage or phase and etc.

2.2 Existing System

The existing blood bank management system primarily relies on manual processes and
offline record-keeping, which can be time-consuming, error-prone, and inefficient. This
section discusses the limitations and challenges of the existing system and highlights the
need for an online blood bank management system. The existing system relies on manual
record-keeping, which involves maintaining paper-based records of donor information,
blood inventory, and transfusion records. This manual process is susceptible to errors,
misplacement, and delays in retrieving information. With the existing system, accessing
and updating donor information, blood inventory status, and transfusion records can be
challenging. This limited accessibility hampers timely decision-making, impedes
coordination among different blood banks, and affects the overall efficiency of the
system. Inaccurate Inventory Tracking: The manual tracking of blood inventory can lead
to inaccuracies, making it challenging to maintain an optimal level of blood units. This
can result in wastage due to expired blood units and shortages during high demand
periods.

The existing blood bank management system suffers from limitations related to manual
processes, limited accessibility, inefficient donor management, inaccurate inventory
tracking, lack of timely notifications, and limited reporting capabilities. These limitations
highlight the need for an online blood bank management system that can automate
processes, improve accessibility, enhance donor engagement, streamline inventory
management, facilitate efficient communication and coordination, and provide advanced
reporting and analytics capabilities. By addressing these challenges, an online system can
significantly enhance

12
2.3 Proposed System
The proposed system is an online blood bank management system that aims to replace the
existing manual and offline processes with a comprehensive, efficient, and user-friendly
web-based solution. This section outlines the key features, functionalities, and benefits of
the proposed system. Online registration for donors with the ability to provide necessary
personal and medical information. Secure donor profiles to maintain donor records,
including contact details, blood type, and donation history. Donor eligibility screening
based on medical criteria to ensure safe blood donations. Real-time tracking of blood
units in the inventory, including their types, quantities, and expiration dates. Automated
alerts and notifications for inventory replenishment, expiration, and shortage
management. Efficient matching and retrieval of compatible blood units based on donor
and recipient compatibility. Automated reminders and notifications to donors regarding
upcoming appointments and donation opportunities. Efficient management of donor
appointments, ensuring smooth blood collection processes. Online submission of blood
requests by medical facilities, with detailed information about the recipient and required
blood type. Generation of comprehensive reports and analytics to gain insights into donor
statistics, blood utilization patterns, and inventory management. Visual representation of
data through charts and graphs for better decision-making. Exporting of reports in various
formats (e.g., PDF, Excel) for sharing and further analysis. Different user roles with
varying levels of access and privileges, such as administrators, donors, and medical staff.
Role-based access control to ensure data privacy, security, and integrity. Customizable
permissions and restrictions to manage user actions and data visibility. The proposed
system automates manual processes, reducing errors and saving time. It streamlines
donor registration, appointment scheduling, inventory management, and blood matching,
improving overall operational efficiency. As an online platform, the system enables users
to access and update information from anywhere, anytime. Donors, medical facilities, and
administrators can conveniently interact with the system, enhancing coordination and
responsiveness. The proposed system offers an intuitive and user-friendly interface for
donors, encouraging their active participation. Online registration, appointment
scheduling, and personalized notifications enhance donor engagement, leading to a steady
supply of blood units. The system provides real-time visibility into the blood inventory,
enabling efficient management and reducing wastage or shortages. Automated alerts and
notifications ensure timely replenishment and utilization of blood units. Effective
Communication and Coordination: The system facilitates seamless communication and
coordination between blood banks, medical facilities, and donors. Timely notifications,
updates, and request handling ensure effective collaboration and faster response times.:
The reporting and analytics capabilities of the system enable data-driven decision-
making. Comprehensive reports and visual representations of data provide insights into
donor patterns, blood utilization, and inventory management, supporting efficient

13
resource allocation and planning. The proposed online blood bank management system
offers a comprehensive solution to replace the existing manual and offline processes.
With features such as donor registration, blood inventory management, appointment
scheduling, blood requests, and reporting, the system enhances efficiency, accessibility,
and coordination.

2.4 Feasibility Study

The feasibility of an online blood bank management system refers to its practicality and
viability in terms of technical, economic, operational, and schedule factors. Evaluating
the feasibility of the system helps determine whether it is worth pursuing and if it can be
successfully implemented. Here are some key aspects of feasibility for an online blood
bank management system:

1. Technical Feasibility: This aspect assesses whether the necessary technology,

infrastructure, and resources are available to develop and deploy the system. It includes
considerations such as the availability of suitable software development tools, database
management systems, hosting platforms, and integration capabilities with existing
systems. Technical expertise and support for system development and maintenance are
crucial factors in determining technical feasibility.

2. Economic Feasibility: Economic feasibility evaluates the financial viability of the

system. It involves analyzing the costs and benefits associated with developing,
implementing, and maintaining the online blood bank management system. The costs
may include software development, hardware infrastructure, licensing, training, and
ongoing maintenance expenses. The benefits can include improved operational
efficiency, reduced paperwork, better inventory management, and enhanced donor and
recipient satisfaction. Conducting a cost-benefit analysis helps determine if the system's
benefits outweigh the associated costs.
3. Operational Feasibility: Operational feasibility assesses whether the online blood
bank management system aligns with the organization's operations and can be smoothly
integrated into existing workflows. It considers factors such as the readiness and
willingness of staff to adopt and adapt to the system, potential resistance to change, and
the impact on daily operations. Stakeholder engagement and proper change management
strategies are essential to ensure operational feasibility.

4. Schedule Feasibility: Schedule feasibility determines whether the project can be

completed within the desired timeline. It involves assessing the availability of resources,
setting realistic milestones, and estimating the time required for each phase of the project,
such as requirements gathering, development, testing, and deployment. A thorough
project plan, effective task management, and regular progress tracking are essential for
achieving schedule feasibility.

14
5. Legal and Regulatory Feasibility: Legal and regulatory compliance is a critical
aspect of any blood bank management system. It is necessary to ensure that the system
adheres to relevant laws, regulations, and standards related to data privacy, security,
patient confidentiality, and blood safety. Compliance with regulations, such as the Health
Insurance Portability and Accountability Act (HIPAA) or General Data Protection
Regulation (GDPR), is essential for the system's feasibility.

6. User Acceptance: User acceptance is a significant factor in determining the feasibility

of an online blood bank management system. It involves gathering feedback from
potential users, such as blood donors, medical facilities, and administrators, regarding
their needs, expectations, and satisfaction with the system. User acceptance testing and
user involvement throughout the development process help ensure that the system meets
their requirements and is user-friendly.

A comprehensive feasibility study should be conducted during the initial stages of the
project to evaluate these factors and determine the overall feasibility of the online blood
bank management system. It helps in making informed decisions and mitigating risks
associated with the system's implementation and operation.[1]

15
 CHAPTER 3

SYSTEM DESIGN

16
3.1 Agile Method

The Agile methodology represents a paradigm shift in project management and software
development. Unlike traditional, linear approaches, Agile emphasizes adaptability,
collaboration, and customer-centricity. It's characterized by iterative development cycles,
known as "sprints," which allow for continuous refinement and improvement of a
project's deliverables.
One of Agile's key strengths lies in its ability to accommodate changing requirements. As
business landscapes evolve rapidly, Agile projects can pivot swiftly to meet new
demands and market shifts. It fosters regular interactions between development teams and
stakeholders, ensuring that the end product aligns closely with customer needs.
Moreover, Agile promotes a collaborative culture. Cross-functional teams work closely
together, breaking down silos that can impede progress in traditional models. This
collaboration not only enhances communication but also boosts creativity and problem-
solving.
Transparency is another hallmark of Agile. Progress is visible through regular
demonstrations of working software, and any roadblocks or challenges are identified and
addressed promptly. This transparency enhances accountability and empowers teams to
take ownership of their work.
In essence, the Agile methodology embodies a flexible, customer-focused, and
collaborative approach to project management. Its principles and practices have found
application far beyond software development, proving effective in various industries
where adaptability and responsiveness are paramount to success.[2]

17
3.2 Advantage & Disadvantage of Agile Method

Advantage
The advantages of Agile are simplicity, adaptability, and customer focus. Agile simplifies
complex projects by breaking them into manageable parts. It adapts well to changes,
ensuring the project stays aligned with evolving requirements. Moreover, it keeps the
customer at the center, leading to a product that better meets their needs and expectations.

Disadvantage
The main disadvantage of Agile is that it might not work well for all projects or teams. It
requires a lot of communication and flexibility, which can be challenging in some
situations. Also, it can be less predictable in terms of project timelines, making it harder
to set fixed deadlines. Finally, it requires experience and training to use effectively, and
new teams may struggle to implement it smoothly.

3.3 Method
This paper is aimed to develop online blood donation information. The entire work has
been developed keeping in view of the distributed client server computing technology, in
mind. The system is to create an e-Information about the donor and organization that are
related to donating the blood. Through this application any person who is interested in
donating blood can register himself as a donor. Moreover, if any general consumer wants
to make request blood online, he can also take the help of this site. The work has been
planned to be having the view of distributed architecture, with centralized storage of the
database. The application for the storage of the data has been planned. Using the
constructs of SQL Server, all the user interfaces have been designed using mysql
technologies. The database connectivity is planned using the “SQL Connection”
methodology . The standards of security and data protective mechanism have been given
a big choice for proper usage. The application takes care of different modules and their
associated reports, which are produced as per the applicable strategies and standards that
are put forwarded by the administrative staff. The system has been developed keeping in
view of the distributed client server computing technology, in mind. The specification has
been normalized up to 3NF to eliminate all the anomalies that may arise due to the
database transaction that are executed by the general users and the organizational
administration . The user interfaces are browser specific to give distributed accessibility
for the overall system. The internal database has been selected as SQL server 2008. The
basic constructs of table spaces, clusters and indexes have been exploited to provide
higher consistency and reliability for the data storage. The SQL server 2008 was a choice
as it provides the constructs of high-level reliability and security. The total front end was
dominated using the [Link] technologies. At all proper levels high care was taken to
check that the system manages the data consistency with proper business rules or
validations. The database connectivity was planned using the latest “SQL Connection”
technology provided by Microsoft Corporation. The authentication and authorization

18
were crosschecked at all the relevant stages. The user level accessibility has been
restricted into two zones namely.[3]

3.4 Analysis
In this system, users can search donors and make request for blood. Donors can login to
their own profiles and update information. They can search donor, request for blood and
send message to other donors. Admin can maintain system management tasks. The use
case diagram and class diagram of the system are shown in the Figure 2 and Figure 3
respectively.

19
3.5 Requirements:
1. User Registration: Allow users to sign up and create accounts easily.
2. Donor Information: Collect basic donor details like name, contact info, and blood
type.
3. Appointment Booking: Let donors schedule donation appointments online.
4. Blood Inventory: Keep track of available blood types and quantities.
5. Search for Donors: Allow hospitals to search for available donors.
6. Notifications: Send reminders on Mail.
7. Feedback: Allow users to provide feedback on their experience.
8. Security: Ensure user data is kept safe and private.
9. Support: Offer user assistance and guidance.
10. Compliance: Follow local blood donation regulations.
These simplified requirements cover the essential functions of a Blood Donation System,
making it easier to understand and implement.

20
 Flow Chart Diagram
This flowchart represents a simplified overview of the user interactions and
functionalities of a Blood Donation System. In practice, the system might have more
detailed processes and sub-processes depending on its specific requirements. You can use
flowcharting software or tools to create a more detailed and visual representation tailored
to your project's needs.[12]

21
 Work Flow Diagram
This workflow provides a simplified representation of how blood donation and inventory
management processes could work within the Blood Donation System. In practice, the
system's workflows may be more detailed and interconnected, depending on the specific
requirements and processes of the organization managing the system. [12]

22
3.8 System Architecture
The software architecture model used in the online blood bank management system is the
Model-View-Controller (MVC) pattern. MVC is a widely adopted architectural design
pattern that separates the application's concerns into three distinct components: the
Model, View, and Controller. Let's explore how each component of the MVC pattern is
utilized in the online blood bank management system:

1. Model: The Model represents the underlying data and business logic of the system. In
the online blood bank management system, the Model component is responsible for
handling data-related operations such as storing and retrieving donor information,
managing blood inventory records, and handling business rules and validations. It
encapsulates the functionality and rules that govern the system's core operations.
For example, the Model component manages the database interactions using a framework
like Laravel and establishes the necessary data structures, relationships, and constraints to
ensure data integrity. It may also include classes or modules that define the business
logic, such as donor registration, appointment scheduling, blood unit matching, and
inventory management.

2. View: The View component handles the presentation layer of the system, responsible
for displaying information to the users and receiving user inputs. In the online blood bank
management system, the View component encompasses the user interface (UI) elements
presented to the administrators, donors, and medical staff. It includes web pages, forms,
and graphical components that allow users to interact with the system.
The View component is implemented using HTML, CSS, and JavaScript, combined with
front-end frameworks such as Bootstrap or [Link]. It fetches the necessary data from the
Model component and presents it in a user-friendly and intuitive manner. For example,
the View component may display donor registration forms, blood inventory lists,
appointment scheduling interfaces, and reports.

3. Controller: The Controller acts as an intermediary between the Model and View
components, facilitating the flow of data and controlling the system's behavior. It
receives user inputs from the View, processes the requests, interacts with the Model to
retrieve or update data, and determines the appropriate View to present to the user.

In the online blood bank management system, the Controller component handles user
interactions and manages the system's logic and flow. It processes actions such as donor
registration submissions, appointment scheduling requests, blood unit matching, and
inventory updates. It also coordinates the communication between the View and Model
components, ensuring data consistency and integrity.

23
The Controller component is implemented using server-side scripting languages like PHP
in conjunction with a framework such as Laravel. It routes incoming requests, invokes
the appropriate methods in the Model to handle data operations, and determines the
appropriate View to render as a response.
Benefits of the MVC Architecture Model:

The use of the MVC architecture model in the online blood bank management system
offers several benefits, including:

1. Separation of Concerns: MVC separates the concerns of data management, user

interface, and system logic, allowing for easier maintenance, code reusability, and
scalability.

2. Modularity: The clear separation between Model, View, and Controller components
enables independent development and testing of each component, promoting code
organization and maintainability.
3. Flexibility: MVC provides flexibility in UI design and allows for the easy
modification of user interface elements without impacting the underlying data or system
logic.

4. Code Reusability: By separating the concerns, components developed using the MVC
pattern can be reused in other projects or scenarios with minimal modifications.

5. Collaboration: The MVC architecture promotes collaboration among developers, as

they can work on different components simultaneously without stepping on each other's
toes.

In conclusion, the adoption of the MVC architecture model in the online blood bank
management system ensures a clear separation of concerns, enhances code organization,
promotes code reusability, and allows for flexibility and scalability. It enables efficient
development, testing, and maintenance of the system, contributing to its overall
effectiveness and usability.[2]

3.9 Methodology
The Agile methodology is a flexible and iterative approach to software development that
emphasizes collaboration, adaptability, and delivering value in short development cycles.
It is well-suited for the project of developing an online blood bank management system.
Here's an overview of how the Agile methodology can be applied to the project:

24
1. Iterative Development:
Agile promotes iterative development, breaking the project into smaller increments called
sprints. Each sprint typically lasts for a few weeks and focuses on delivering a specific set
of functionalities or features. For the online blood bank management system, each sprint
could address key aspects such as donor registration, appointment scheduling, blood
inventory management, and reporting.
2. User Involvement and Collaboration:

Agile methodology emphasizes frequent communication and collaboration between the

development team and stakeholders, including blood bank administrators, medical staff,
and donors. Regular meetings, such as daily stand-ups and sprint reviews, allow
stakeholders to provide feedback, prioritize features, and ensure that the system meets
their requirements effectively.
3. Continuous Feedback and Adaptation:
Agile encourages continuous feedback loops to gather input from stakeholders
throughout the development process. This feedback helps refine and adjust the system's
functionality and design, ensuring that it aligns with the stakeholders' evolving needs.
Regular demos and user acceptance testing (UAT) sessions enable stakeholders to
evaluate the system's progress and make necessary adjustments.
4. Prioritization and Incremental Delivery:

With Agile, the project team collaboratively prioritizes the system's features and
functionalities based on their value and urgency. This allows for the delivery of the most
critical and high-value components early in the development process, ensuring that
stakeholders can start realizing benefits sooner. For example, the initial sprints could
focus on basic donor registration and appointment scheduling, followed by blood
inventory management, blood matching, and reporting in subsequent sprints.
5. Adaptive Planning:

Agile embraces change and acknowledges that requirements can evolve over time. The
development team, along with stakeholders, can adapt the project's scope and priorities as
new insights emerge or requirements change. This flexibility enables the system to
evolve organically and ensures that it remains aligned with the needs of the blood bank
management.
6. Continuous Integration and Testing:

Agile places importance on continuous integration and testing to identify and address
issues early in the development cycle. Regular integration of code and automated testing

25
help maintain the system's stability, reliability, and quality. This ensures that the online
blood bank management system performs as intended and meets the stakeholders'
expectations.
7. Continuous Improvement:

Agile methodology promotes a culture of continuous improvement. Retrospectives, held

at the end of each sprint, provide an opportunity for the development team to reflect on
the sprint's successes and challenges and identify areas for improvement. The feedback
gathered during retrospectives helps refine processes, enhance collaboration, and
optimize the overall development approach.

By adopting the Agile methodology for the online blood bank management system, the
development team can respond to changing requirements, deliver incremental value,
foster collaboration with stakeholders, and ensure a high-quality system that meets the
evolving needs of blood bank management.

3.9 Entity-Relationship (ER)

An Entity-Relationship (ER) diagram for an online blood bank management system
represents the entities, relationships, and attributes involved in the system. It provides a
visual representation of the database structure and helps in understanding the data model.
Here is a brief description of the main components typically included in an ER diagram
for an online blood bank management system:

1. User Entity: This entity represents the users of the system, such as donors, medical
facilities, and administrators. It may include attributes like User_ID, Name, Email, and
Contact Number.

2. Donor Entity: This entity represents the blood donors registered in the system. It may
have attributes like Donor_ID, Name, Blood Type, Address, and Medical History.

3. Blood Bank Entity: This entity represents the blood bank or collection center. It may
have attributes like BloodBank_ID, Name, Address, and Contact Number.

4. Blood Unit Entity: This entity represents the individual units of blood available in the
inventory. It may include attributes like BloodUnit_ID, Blood Type, Expiry Date, and
Donation Date.

5. Request Entity: This entity represents the blood requests made by medical facilities or
individuals. It may include attributes like Request_ID, Request Date, Blood Type,
Quantity, and Delivery Address.

6. Relationship: The ER diagram will depict relationships between entities. For example,
there may be a "Donates" relationship between the Donor and Blood Unit entities,

26
indicating that a donor can donate multiple blood units. Similarly, there may be a
"Manages" relationship between the User and Blood Bank entities, indicating that a user
(administrator) manages a blood bank.

7. Cardinality and Constraints: The ER diagram may include cardinality and

constraints to define the relationship between entities. For example, a donor can have a
one-to-many relationship with blood units (one donor can donate multiple units), and a
blood unit can have a many-to-one relationship with the blood bank (multiple units can
belong to a single blood bank).

It's important to note that the specific entities, attributes, and relationships may vary
depending on the requirements and scope of the online blood bank management system
being designed. The ER diagram serves as a visual representation to model the data
structure and relationships within the system, aiding in database design and
implementation

27
 ER Diagram

An Entity-Relationship (E-R) diagram is a visual representation used in database design

and modeling to depict the entities (objects or concepts) in a system, their attributes, and
the relationships between them. E-R diagrams help in designing the structure of a
relational database by illustrating the logical organization of data. [12]

28
3.10 Activity Diagram
An activity diagram for an online blood bank management system represents the flow of
activities and actions within the system. It focuses on the behavior and sequence of
actions that occur during the operation of the system. Here is a brief description of the
main components typically included in an activity diagram for an online blood bank
management system:

1. User Registration: The activity diagram may start with the user registration process,
where individuals provide their personal information, create login credentials, and
register as users of the system.
2. Blood Donor Registration: This activity represents the process of blood donor
registration, where donors provide their personal details, blood type, and any relevant
medical history to be included in the system.

3. Blood Inventory Management: This activity encompasses various actions involved in

managing the blood inventory. It includes activities such as blood donation collection,
blood testing, labeling, and storage. The diagram may depict the flow of actions from
blood collection to inventory update.
4. Blood Request: This activity represents the process of requesting blood from the
online blood bank system. It includes actions like specifying the blood type, quantity, and
delivery details.

5. Blood Matching and Allocation: This activity represents the system's actions to
match the requested blood type with the available inventory and allocate the appropriate
blood unit. It may include activities like searching the inventory, checking compatibility,
and assigning a blood unit to the request.
6. Blood Delivery: This activity represents the process of arranging the transportation
and delivery of the allocated blood unit to the requesting medical facility or individual. It
includes activities like coordinating with logistics services, generating delivery orders,
and updating the delivery status.

7. Donor Management: This activity represents the management of donor-related

activities. It may include actions like sending notifications to donors, scheduling donation
appointments, and updating donor information in the system.
8. Reporting and Analytics: This activity represents the generation of reports and
analytics to track various metrics related to blood utilization, inventory levels, donor
statistics, and system performance. It includes activities like data analysis, report
generation, and visualization.

29
9. System Administration and Security: This activity represents actions related to
system administration, user access management, and data security measures. It may
include activities like user authentication, access control, and system maintenance.

It's important to note that the specific activities and actions may vary depending on the
requirements and features of the online blood bank management system being
implemented. The activity diagram provides a visual representation to understand the
flow of activities and interactions within the system, facilitating the analysis, design, and
implementation of the system's behavior. [12]

Activity Diagram

30
3.11 Sequence Diagram
A sequence diagram is a type of UML (Unified Modeling Language) diagram that
visually represents the interactions and order of messages exchanged between objects or
components in a system. It illustrates the flow of communication and the sequence of
actions that occur during a particular scenario or use case. Here's a brief explanation of a
sequence diagram:
Components of a Sequence Diagram:

1. Lifelines: Lifelines represent the objects or components involved in the sequence

diagram. Each lifeline is depicted as a vertical line, and it represents an instance of a class
or an actor in the system.

2. Messages: Messages indicate the communication between lifelines. They show the
interactions and information flow between different components. Messages can be of
various types, such as synchronous, asynchronous, or return messages.

3. Activation Boxes: Activation boxes represent the period of time during which an
object or component is performing a particular action or method call. They are depicted
as a rectangular box along the lifeline and show the duration of an operation or method
execution.

4. Conditions and Loops: Sequence diagrams can also include conditions and loops to
depict alternative flows or repeated actions. Conditions are represented by using a guard
condition notation, such as "if" or "else," and loops are shown using iteration notations
like "for" or "while."
Benefits of Sequence Diagrams:

1. Visualization of Interactions: Sequence diagrams provide a visual representation of

how different components or objects interact with each other during a particular scenario.
This helps in understanding the order of message exchanges and the flow of actions in the
system.

2. Communication Design: Sequence diagrams assist in designing the communication

and collaboration between various components or objects. They help identify the required
interactions and ensure that the system functions as intended.

3. Requirement Analysis: By analyzing sequence diagrams, stakeholders can validate

and refine system requirements. They provide a clear overview of how different
components work together and help identify potential bottlenecks or areas for
improvement.

31
4. Documentation: Sequence diagrams serve as effective documentation artifacts that
can be used to communicate system behavior to developers, designers, and other
stakeholders. They capture the essential aspects of interactions and can aid in future
maintenance and troubleshooting.

5. Integration Testing: Sequence diagrams can be used as a basis for designing and
executing integration tests. By simulating the interactions shown in the sequence
diagram, developers can verify that the components work together correctly and identify
any integration issues.

Sequence diagrams are valuable tools for visualizing and understanding the interactions
and message exchanges between components or objects in a system. They help in
designing and communicating system behavior, analyzing requirements, and supporting
integration testing. By using sequence diagrams, developers and stakeholders can gain
insights into the system's dynamics and ensure effective collaboration and
communication between different parts of the system. [12]

32
Sequence Diagram

33
3.12 Data Flow Diagram (DFD)
A Data Flow Diagram (DFD) for an online blood bank management system represents
the flow of data between different components of the system. It provides a visual
representation of how data moves through the system, from its sources to its destinations.
Here is a brief description of the main components typically included in a DFD for an
online blood bank management system:

1. External Entities: These represent the external entities interacting with the system.
Examples include blood donors, medical facilities, and administrators. They are the
sources or recipients of data within the system.
2. Processes: Processes represent the activities or functions performed within the system.
They transform the incoming data into meaningful outputs. In the context of an online
blood bank management system, processes can include user registration, blood donation
management, inventory management, blood request processing, and reporting.

3. Data Flows: Data flows represent the movement of data between external entities and
processes. They show how data is passed from one entity or process to another. Examples
of data flows in an online blood bank management system can include donor information,
blood unit details, blood request information, and report outputs.

4. Data Stores: Data stores represent the repositories where data is stored within the
system. In the context of a blood bank management system, data stores can include donor
databases, blood unit inventories, and request records.

5. Data Transformations: Data transformations represent the processes that manipulate

or modify the data. For example, data transformations can include filtering donor
information, updating blood inventory levels, matching blood requests with available
units, and generating reports.

6. Data Flow Diagram Levels: DFDs can be represented at different levels of detail. The
initial high-level DFD provides an overview of the system's major processes and data
flows. It can be further decomposed into lower-level DFDs, where processes and data
flows are broken down into more detailed sub-processes and data elements.

It's important to note that the specific components and data flows may vary depending on
the requirements and functionality of the online blood bank management system being
designed. The DFD provides a visual representation to understand the flow of data within
the system, facilitating the analysis, design, and implementation of the system's data
structure and interactions. [12]

34
DFD Diagram Level 0

DFD Diagram Level 1

35
.13 Use Case Model:
 The unified modeling language allows the software engineer to express an analysis
model using the modeling notation that is governed by a set of syntactic semantic and
pragmatic rules.
 A UML system is represented using five different views that describe the system
from distinctly different perspective. Each view is defined by a set of diagrams,
which is as follows.
 User Model View
 This view represents the system from the user’s perspective.
 The analysis representation describes a usage scenario from the end-user’s
perspective.
Structural model view
 In this model the data and functionality are arrived from inside the system.
 This model view models the static structures.
Behavioral model view
It represents the dynamic of behavioral as parts of the system, depicting the interactions
of collection between various structural elements described in the user model and
structural model view.
Implementation Model View
In this the structural and behavioral as parts of the system are represented as they are to
be built.
Environmental Model View
In these the structural and behavioral aspects of the environment in which the system is to
be implemented are represented.
UML is specifically constructed through two different domains they are
• UML Analysis modeling, which focuses on the user model and structural model
views of the system.
• UML design modeling, which focuses on the behavioral modeling,
implementation modeling and environmental model views.
Use case Diagrams represent the functionality of the system from a user’s point of view.
Use cases are used during requirements elicitation and analysis to represent the
functionality of the system. Use cases focus on the behavior of the system from external

36
point of view.
Actors are external entities that interact with the system. Examples of actors include users
like administrator, bank customer …etc., or another system like central database[12]

Use Case Diagram

37
 CHAPTER 4

Source Code
and
Implementation

38
4.1 Source Code
The source code of a project refers to the set of human-readable instructions and
statements written in a programming language that make up a computer program or
application. This source code is what developers create to instruct a computer on how to
perform specific tasks and functions within a software project.
Source code is typically composed of text-based instructions and can be written in
various programming languages such as Python, Java, C++, JavaScript, and many others,
depending on the technology stack and requirements of the project,

39
40
41
42
43
44
4.2 Implementetion
Implementation refers to the phase in which the planned activities and strategies are put
into action to execute the project plan. It involves turning the project's design,
specifications, and plans into a functional and tangible result. Implementation is a critical
step in the project lifecycle and typically follows the planning and design phases.

Fig: Homepage

Fig: Donation Request Page

45
Fig: Profile Page

Fig: Donor List

46
Fig: Donation Request FormPage

Fig: Donation Details Page

47
 CHAPTER 5

CONCLUSION

48
5.1 CONCLUSION
In conclusion, the development of an online blood bank management system brings
numerous benefits and potential improvements to the management of blood banks. The
system's benefits include: The online blood bank management system streamlines
processes, automates tasks, and reduces manual paperwork, resulting in increased
operational efficiency. It allows for quick and easy access to donor information, blood
inventory status, and facilitates faster response to blood requests. The system enables
efficient donor registration, tracking, and communication. It simplifies the appointment
scheduling process and sends timely reminders to donors, promoting regular donations
and ensuring a steady supply of blood units. With the system's capability to track blood
inventory in real-time, blood banks can better manage their stock levels, reduce wastage,
and ensure optimal utilization of available blood units. This leads to improved inventory
management and cost savings. The system facilitates the matching of blood types and
compatibility, ensuring that the right blood units are allocated to requests promptly. This
feature saves valuable time, especially in emergency situations where the timely
availability of blood can be critical. The system generates reports and provides analytics
on donor statistics, blood utilization, and inventory levels. These insights enable data-
driven decision-making, resource planning, and identification of trends or areas for
improvement. The system promotes effective communication and collaboration among
blood donors, medical facilities, and administrators. It allows for seamless exchange of
information, timely notifications, and alerts, improving overall coordination and ensuring
smooth operation of the blood bank.
Despite its benefits, the online blood bank management system has certain limitations,
which should be considered:
1. Technical Requirements: The system's implementation requires technical
infrastructure, including servers, hosting, and reliable internet connectivity. Ensuring
these requirements are met may involve additional costs and resources.
2. Training and Adoption: Proper training and education are crucial to ensure smooth
adoption of the system by blood bank staff. Resistance to change or lack of familiarity
with the technology can hinder the system's effectiveness.
3. Data Security and Privacy: Protecting sensitive donor information, complying with
data privacy regulations, and implementing robust security measures are essential
considerations. Failure to address these concerns adequately can lead to data breaches
and loss of public trust.
4. System Maintenance: Ongoing maintenance and updates are necessary to ensure the
system remains secure, functional, and up-to-date. This requires dedicated resources and
continuous support.

49
In conclusion, the online blood bank management system offers numerous benefits, such
as improved efficiency, enhanced donor management, real-time inventory tracking, quick
blood matching, reporting capabilities, and improved communication. However, it is
important to address the system's limitations, including technical requirements, training,
data security, privacy, and maintenance, to maximize its potential and ensure its long-
term success.

5.2 BUSINESS PROSPECTS

The business prospect of a blood bank management system can be quite promising,
considering the critical role blood banks play in healthcare systems. Here are some key
factors that contribute to the business potential of a blood bank management system:
1. Demand for Blood Management Systems: Blood banks are vital for hospitals,
medical facilities, and emergency services. An efficient blood bank management system
can streamline operations, improve inventory management, and ensure the timely
availability of blood products. There is a growing demand for technology solutions that
enhance the overall efficiency and effectiveness of blood banks.
2. Improved Efficiency and Accuracy: A robust blood bank management system can
automate various tasks, such as blood donor registration, inventory management, blood
testing, cross-matching, and tracking blood product distribution. This automation reduces
manual errors, improves data accuracy, and enhances operational efficiency. Hospitals
and blood banks are increasingly adopting such systems to optimize their processes.
3. Regulatory Compliance: Blood bank operations are subject to strict regulatory
standards and guidelines to ensure the safety and quality of blood products. A
comprehensive blood bank management system can help meet these compliance
requirements by tracking and documenting the entire lifecycle of blood units, including
donor screening, testing, storage, and distribution. Compliance with regulations is a
critical factor for blood banks, making a reliable management system highly valuable.
4. Donor Relationship Management: Blood banks rely on blood donations from
individuals and organizations. A blood bank management system can assist in
maintaining a database of donors, tracking their donation history, sending reminders for
future donations, and managing communication with donors. Building strong
relationships with donors can lead to a steady supply of blood and foster a sense of
community involvement.
5. Data Analytics and Reporting: An advanced blood bank management system can
provide real-time data analytics and reporting capabilities. By analyzing data on blood
utilization, inventory levels, donor demographics, and trends, blood banks can make
informed decisions to optimize their operations, anticipate demand, and reduce wastage.
Data-driven insights are valuable for improving resource allocation and enhancing overall
performance.
6. Integration with Healthcare Systems: Integration of a blood bank management
system with hospital information systems and electronic health records can streamline
workflows and improve patient care. Seamless data exchange between systems ensures
accurate and timely information sharing, reduces duplication of effort, and enhances
coordination among healthcare professionals.

50
7. Future Expansion and Scalability: As healthcare systems evolve, the demand for
integrated solutions and interoperability between different systems continues to grow. A
blood bank management system with the flexibility to adapt to changing requirements
and integrate with other healthcare technologies positions itself well for future expansion
and scalability.
It's important to note that the success of a blood bank management system business also
depends on factors such as market competition, pricing strategy, marketing efforts, and
the quality of the product and service provided. Conducting thorough market research
and understanding the specific needs of blood banks in your target market will be
essential to develop a competitive advantage and maximize the business prospect of your
blood bank management system

51
 REFERENCE

1. K. M. A. Ali, I. Jahan, Md. A. Islam, et al.,” Blood Donation Management System by

Institute of Information Technology, American Journal of Engineering Research,”
vol. 4, no. 6, pp.123-136, 2015.
2. SDLC 3.0: Beyond a Tacit Understanding of Agile: Towards the Next Generation of
Software Engineering: Volume 1 Paperback – 18 Jan. 2010
3. Polack, Jennifer (December 2009). "Planning a CIS Education Within a CS
Framework". Journal of Computing Sciences in Colleges 25 (2): 100–106. ISSN
1937-4771.
4. Tutorial on semi-structured data by Peter Beneman from Symposium on Principles of
Database System, 1997
5. Database System Concepts by Silberschatz, Korth and Sudarshan.
6. PHP (programming language) retrieved date: [13, January, 2023], online available at
[Link]
7. PHP Documentation), retrieved date: [6, March, 2023], online available at
[Link]
8. JavaScript Documentation, retrieved date: [15, February, 2023], online available at
[Link]
9. HTML Documentation at
[Link]
10. Laravel (PHP Framework) Documentation at
[Link]
11. Image (Laravel Package) documentation at
[Link]
12. For diagrams
[Link]

52