TABLE OF CONTENTS

PARTICULARS PAGE NO
SYNOPSIS
[Link] 1

1.1 OVERVIEW OF THE PROJECT 1

1.2 SCOPE OF THE SYSTEM 3
1.3 SYSTEM SPECIFICATION 4
1.3.1 HARDWARE SPECIFICATION 4
1.3.2 SOFTWARE SPECIFICATION 4
1.4 SOFTWARE ENVIRONMENT 5
1.4.1 FRONTEND 5
1.4.2 JAVA PLATFORM 5
1.4.3 BACKEND 6

[Link] ANALYSIS 9

2.1 EXISTING SYSTEM 9

2.1.1 DRAWBACKS 9
2.2 PROPOSED SYSTEM 10
2.2.1 FEATURES 10

[Link] DESIGN AND DEVELOPMENT 11

3.1 FILE DESIGN 11

3.2 INPUT DESIGN 12
3.3 OUTPUT DESIGN 14
3.4 DATABASE DESIGN 16
3.5 SYSTEM DEVELOPMENT 17
3.5.1 MODULES DESCRIPTION 17

[Link] AND IMPLEMENTATION 18

4.1TEST PLANNING 18
4.2 SYSTEM IMPLEMENTATION 24

[Link] 25
 TABLE OF CONTENTS

PARTICULARS PAGE NO

[Link] FOR FUTURE ENHANCEMENT 26

BIBLIOGRAPHY 27

APPENDICES 28

A. DATA FLOW DIAGRAM

B. ER DIAGRAM
C. TABLE STRUCTURE
D. SYSTEM FLOW DIAGRAM
E. SAMPLE CODING
F. SAMPLE INPUT
G. SAMPLE OUTPUT
 SYNOPSIS

The Project is entitled as “Smart Alzheimer Caregiver”. Alzheimer disease is an

exceptional case of memory loss. It is a memory impairment brought on by brain injury, illness,
or psychological trauma. The use of several sedatives and hypnotic medications might
potentially momentarily impair memory. Due to the severity of the impairment, memory loss
can result in either a complete or partial loss of memory. When a person has amnesia or memory
loss, they may still be able to develop new memories and still be able to recall recent
knowledge. This is known as priming nondeclarative. Nonetheless, a marked decline in the
capacity to pick up new information and recall previous knowledge can be seen.

Alzheimer's disease is characterized by a gradual deterioration in symptoms over

several years. It impairs daily task performance and damages memory. Memory loss makes it
difficult to remember things like names, faces, locations, or other details. The prevalence of
Alzheimer's disease is rising in India, which calls for attention and action. The goal of this work
is to assist people with mild (early-stage) and moderate (middle-stage) Alzheimer's disease so
they can continue to live independently and participate in society. A smartphone app is
proposed that utilizes Google Maps for position detection and incorporates facial recognition
technologies to identify users. By integrating a notification feature, the application enhances
everyday communication while improving the ability to manage daily tasks. Location detection
ensures the safety of Alzheimer's patients and prevents them from getting lost by tracking their
whereabouts. Results indicate that the application has significantly aided individuals
experiencing Alzheimer's symptoms and improved their daily lives. This work highlights the
importance of incorporating artificial intelligence (AI)-based capabilities, particularly facial
recognition, in healthcare applications with the potential for a significant community impact.
 1. INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

Alzheimer's disease is becoming a growing public health concern as aging increases

the risk, leading to more cases in older communities. According to the India Alzheimer's
Disease Association (2019), there are currently an estimated 130,000 people in India who are
living with Alzheimer's disease, and this number is expected to quadruple by 2050. Because
it affects older people, some medical professionals refer to it as the century illness. Simple
daily activities like eating or brushing their teeth might be difficult for those with
Alzheimer's. They might also become disoriented and lose their sense of place and time,
making it simple for them to get lost away from home.

Also, they could forget recent happenings or the names of some of their loved ones.
As a result, these difficulties not only provide a burden for the patient, but also for the
patient's carer. Alzheimer's disease is a severe chronic brain disease that starts with memory
loss and progresses to affects on attention and concentration, planning, thinking, language,
and cognition. We therefore created a smartphone application that enables machine learning
via face recognition algorithms with the intention of helping Alzheimer's sufferers and their
families by making their lives easier. Facial recognition has a variety of practical uses right
now, from public safety to personal security.

It is used to locate and track a potential suspect in a crowd or for identity verification.
Consequently, the application acts as a smart assistant, helping Alzheimer patients recognize
the names and faces of their family members and understand their relationships. A mobile
phone is proposed that can track the patient’s location and send updates to the caregiver,
effectively preventing the risk of the patient getting lost outside the home. Alzheimer's
sufferers experience memory loss, which makes it difficult for them to recall people's names,
faces, or other facts about them, which could put them in awkward circumstances. Also,
individuals have trouble recalling some crucial obligations or appointments that they have to
keep in their daily schedules.

1
 Some patients leave their home and end themselves lost because they can't recall how
to get there. As a result, the patient's family and friends could have to spend a lot of time
looking for them without knowing where they are. Consequently, this application suggests
creating a smartphone app with the ability to recognise individuals by looking up each one in
an album that has been categorised according to their face and showing details about the
patient's relationship with that individual. Patients with Alzheimer's are encouraged to feel
more self-assured by this, which enhances their capacity to carry on having social
interactions.

This is made easier by an application feature that delivers reminders to patients to

remind them of what they need to accomplish on any given day. Additionally, it comes with a
tracking mobile phone that allows the patient's relatives to determine their precise
whereabouts and will help in the case that they become lost. The main goal of this research is
to help Alzheimer's patients in India who are in the early and middle stages of the disease by
making it simpler than it was previously for them to stay involved in society, sending
reminders for daily tasks, providing a tracking mechanism, and boosting their confidence in
their ability to remember every member of their family.

Also, the families do not need to be concerned because the programme may assist in
tracking and supporting the movements of the Alzheimer's patients. The major goal of the
proposed application is to improve the lives of Alzheimer patients so that they and people
around them can cope with the condition more easily. It also outlines how to use machine
learning facial recognition technology to communicate with and recall the faces of those
around them in order to prevent the beginnings of isolation or loneliness. These elements will
enhance not just the daily lives of persons who have Alzheimer's but also of their caretakers
in a variety of ways.

Key features include:

● Enhancing interactions with neighbours on a daily basis.

● Locating people with Alzheimer's in order to ensure their safety and stop them from
becoming lost in public places;
● Assisting and making it easier for family or carers of Alzheimer's patients to stay in
touch with them.

2
 By creating an app with capabilities like facial recognition using machine learning,
the suggested application has the potential to help every Alzheimer's patient with a mild-
moderate illness and their caretakers. This aids Alzheimer sufferers in remembering the
people around them and gives carers a mobile GPS monitoring gadget to help them pinpoint
the patient's whereabouts.

1.2 SCOPE OF THE SYSTEM

This proposal's scope is very broad because it can be applied to many different fields
based on the database that the system is given. It can be utilized in the medical industry to
assist patients with memory loss and those who are blind in identifying persons around them;
in this case, the database is made up of the patient's friends and relatives. If the database is
filled with criminal histories of various people, the technology can be utilized to locate
offenders. The system is still in use while its database is being expanded.

The technology can be made accessible to a wide range of people in our culture
because it is portable and affordable. The people can easily provide their data utilising any
devices with a web camera thanks to the utilisation of online applications for data collecting.
To increase the security of the system, only authorised people are used for data collecting. As
there is a backup of the portable device's data in the server database, data loss is not a
problem. As a result, the system is efficient and trustworthy for a variety of users in all
societies.

3
1.3 SYSTEM SPECIFICATION

1.3.1 HARDWARE SPECIFICATION

Processor : Intel Core i3

RAM Capacity : 8 GB

Hard Disk : 1 TB

Mouse : Logical Optical Mouse

Keyboard : Logitech 107 Keys

Monitor : 14 inch

Mother Board : Intel

Speed : 3.3GHZ

1.3.2 SOFTWARE SPECIFICATION

Operating System : Windows 7 Ultimate

Front End : XML

Middleware : Java

Development tool : Android Studio

Back End : Firebase

4
1.4 SOFTWARE ENVIRONMENT
1.4.1 FRONT END: Java
Java has two things: a programming language and a platform. Java is a high-level
programming language that is all of the following
• Simple Architecture-neutral
• Object-oriented Portable
• Distributed High-performance
• Interpreted multithreaded
• Robust Dynamic and Secure

Java is also unusual in that each Java program is both compiled and interpreted. With
a compile you translate a Java program into an intermediate language called Java byte codes
theplatform-independent code instruction is passed and run on the computer. Compilation
happens just once; interpretation occurs each time the program is executed. The figure
illustrates how this works. It is possible to think of Java byte codes as the machine code
instructions for the Java Virtual Machine (Java VM).

Every Java interpreter, whether it’s a Java development tool or a Web browser that
can run Java applets, is an implementation of the Java VM. The Java VM can also be
implemented in hardware. Java byte codes help make “write once, run anywhere” possible.
You can compile your Java program into byte codes on my platform that has a Java compiler.
The byte codes can then be run on any implementation of the Java VM. For example, the
same Java program can run Windows NT, Solaris, and Macintosh.

1.4.2 JAVA PLATFORM

A platform is the hardware or software environment in which a program runs. The

Java platform differs from most other platforms in that it’s a software only platform that runs
on top of other, hardware-based platforms. Most other platforms are described as a
combination of hardware and operating system.

5
1.4.3 BACK END (Firebase)

Firebase is a relational database system. If one can believe many diehard Firebase
fans, Firebase is faster, more reliable, and cheaper -- or, simply put, better -- than any other
database system (including commercial systems such as Oracle and DB2). Many Firebase
opponents continue to challenge this viewpoint, going even so far as to assert that Firebase is
not even a relational database system.

Features of Firebase

The following list shows the most important properties of Firebase. This section is
directed to the reader who already has some knowledge of relational databases. Some
terminology will be used from the relational database world without defining the terms
exactly. On the other hand, the explanations should make it possible for database novices to
understand to some extent.

Relational Database System

Like almost all other database systems on the market, Firebase is a relational database
system.

SQL compatibility

Firebase supports its database language -- as its name suggests – SQL (Structured
Query Language). SQL is a standardized language for querying and updating data and for the
administration of a database. There are several SQL dialects (about as many as there are
database systems). Firebase adheres to the current SQL standard (at the moment SQL:2003),
although with significant restrictions and a large number of extensions. Through the
configuration setting sql-mode one can make the Firebase server behave for the most part
compatible with various database systems. Among these are IBM DB/2 and Oracle.

SubSELECTs

Since version 4.1, Firebase is capable of processing a query in the form SELECT *
FROM table1 WHERE x IN (SELECT y FROM table2) (There are also numerous syntax
variants for subSELECTs.)

6
Client/Server Architecture

Firebase is a client/server system. There is a database server (Firebase) and arbitrarily

many clients (application programs), which communicate with the server; that is, they query
data, save changes, etc. The clients can run on the same computer as the server or on another
computer (communication via a local network or the Internet). Almost all of the familiar
large database systems (Oracle, Microsoft SQL Server, etc.) are client/server systems. These
are in contrast to the file-server systems, which include Microsoft Access, dBase and FoxPro.
The decisive drawback to file-server systems is that when run over a network, they become
extremely inefficient as the number of users grows.

Views

Put simply, views relate to an SQL query that is viewed as a distinct database object
and makes possible a particular view of the database. Firebase has supported views since
version 5.0.

Stored procedures

Stored procedures (SPs for short) are generally used to simplify certain steps, such as
inserting or deleting a data record. For client programmers this has the advantage that they do
not have to process the tables directly, but can rely on SPs. Like views, SPs help in the
administration of large database projects. SPs can also increase efficiency. Firebase has
supported SPs since version 5.0.

Triggers

Triggers are SQL commands that are automatically executed by the server in certain
database operations (INSERT, UPDATE, and DELETE). Firebase has supported triggers in a
limited form from version 5.0, and additional functionality is promised for version 5.1.

Unicode

Firebase has supported all conceivable character sets since version 4.1, including
Latin-1, Latin-2, and Unicode (either in the variant UTF8 or UCS2).

7
User interface

There are a number of convenient user interfaces for administering a Firebase server.

Full-text search

Full-text search simplifies and accelerates the search for words that are located within
a text field. If one employs Firebase for storing text (such as in an Internet discussion group),
one can use full-text search to implement simply an efficient search function.

Replication

Replication allows the contents of a database to be copied (replicated) onto a number

of computers. In practice, this is done for two reasons: to increase protection against system
failure (so that if one computer goes down, another can be put into service) and to improve
the speed of database queries.

GIS functions

Since version 4.1, Firebase has supported the storing and processing of two-
dimensional geographical data. Thus Firebase is well suited for GIS (geographic information
systems) applications.

Programming languages

There are quite a number of APIs (application programming interfaces) and libraries
for the development of Firebase applications. For client programming one can use, among
others, the languages C, C++, Java, Perl, Android, Python, and Tcl.

ODBC

Firebase supports the ODBC interface Connector/ODBC. This allows Firebase to be

addressed by all the usual programming languages that run under Microsoft Windows
(Delphi, Visual Basic, etc.). The ODBC interface can also be implemented under Unix,
though that is seldom necessary. Windows programmers who have migrated to Microsoft's
new .NET platform can, if they wish, use the ODBC provider or the .NET interface
Connector/NET.

8
 2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

Dementia is an umbrella term used to describe a range of conditions, typically

associated with impairment in memory, speech, cognition, and problem-solving abilities. This
results in reduced capacity to carry out daily functions. Alzheimer’s disease is the most
common cause of dementia, with prevalence rates rising in recent years.

Increasingly, technological advancements have been found to make a significant

impact on those living with Alzheimer’s, especially at the initial onset of illness. Drawing on
algorithms and relying upon smart devices can help to ad-dress some of the challenges
Alzheimer’s patients typically experience, as well as their caregivers being involved in a
supportive capacity.

2.1.1 DRAWBACKS

People now frequently experience memory loss as a result of stress, despair, and lack
of sleep. Memory loss patients deal with a variety of issues in their daily lives. Even the
places and people they interact with every day escape their memory. Systems like personal
digital assistants that may act as alarms and send alerts to individuals with memory loss are
available to help these folks. Patients with memory loss cannot be helped with medication,
and there is no reliable aid that can help them. To help the patient remember the things and
people around them, they require ongoing care and assistance. By using face recognition to
detect others nearby and notifying them via audio speech, the suggested method addresses
this problem.

9
2.2 PROPOSED SYSTEM

The Alzheimer's Helper application, a proposed tool, assists Alzheimer's patients

in India in living more independently and independently. This is accomplished by
combining a monitoring mobile phone that allows patients and their family to know their
exact location in the event of the patient being lost, providing reminders of daily duties,
recognising people using cameras, and identifying people. For tracking purposes, the
suggested programme will integrate both face recognition and GPS mobile phones.

2.2.1 FEATURES

The main features in proposed system are as follows:

● A mobile phone that gives real-time location

● Saving a photo of each individual in a separate folder
● Recognising people by focusing the camera on them to identify them.

10
 3. SYSTEM DESIGN AND DEVELOPMENT

3.1 FILE DESIGN

One problem that would have to be overcome is how to deal with the relations and
searching to minimize I/O operations. All fields are variable length apart from the id, year &
length. Server should be able to synchronize the database to all clients with minimal
operations. One way to approach this would be to store the date/time each record was last
modified and have the client store the date of the last sync. When a client comes online, all
changes that date sync back to the client. Another way to do this would be to have a separate
table on the server which lists all the operations that have happened and the date they
happened; and sync in a similar fashion.

Fast read operations for clients

Some sort of index will have to be stored for each table for where each record starts.
This could be small enough to load into memory and could be stores in files separate to the
actual tables to avoid issues.

Minimise I/O operations

The server will store an "index" of the tracks database in memory with the id and file
name so read operations are kept to a minimum. The server will also buffer database write
operations so that if it detects that a lot of write operations are going to happen in a short
space of time it will wait and then do a batch write. This is possible because the changes to
the file system will still be there if the database crashes, so it could just reload all changes on
restart. NOT sparse file to keep file size to a minimum. The main problem will be
fragmentation when a record is deleted. Because of the variable length fields, a new record
cannot be added in that place. So fixed length fields should not be used either (as the filename
could be huge for instance).

11
3.2 INPUT DESIGN

Input design is a crucial part of any application as it determines how users enter data into the
system. A well-structured input design ensures accuracy, efficiency, and ease of use. The
main goal is to make data entry simple, reduce errors, and provide a smooth experience for
users.

The Smart Alzheimer Caregiver App is designed with a simple and interactive input
system to help caregivers and patients enter and manage important information easily. The
app features structured forms, dropdown menus, text fields, and image upload options to
ensure smooth data entry. The goal of the input design is to make the process efficient, user-
friendly, and accessible for both caregivers and individuals dealing with Alzheimer's.

The app starts with a sign-in page, where users input their email and password for
authentication. This ensures secure access to the app’s features. After logging in, users are
directed to the dashboard, which contains different options like identifying people, tracking
locations, managing tasks, setting appointments, and cognitive training. Each section includes
input fields that allow users to enter relevant details.

The people identification feature is designed to help Alzheimer’s patients recognize

and remember important individuals in their lives. Caregivers can input the names, phone
numbers, and images of family members, friends, doctors, or caretakers. Since memory loss
is a common challenge for Alzheimer’s patients, this feature acts as a digital memory aid,
allowing users to recall familiar faces and key contacts. If a patient forgets someone, they can
simply check the stored information to recognize them.

For appointments, users can input a doctor’s name, specialization, hospital location,
date, and time. There is also an option to upload medical documents or prescriptions for
better record-keeping. Similarly, the daily routine feature helps caregivers plan activities by
entering a title, date, and time, ensuring that important daily tasks are followed

The location tracking feature allows users to store frequently visited places by
entering a location name and coordinates. This helps in guiding patients safely to familiar
locations. The task management feature enables users to create and manage tasks by

12
inputting a title and description. This helps caregivers in organizing daily responsibilities
effectively and ensuring nothing is forgotten.

The input design of the Smart Alzheimer Caregiver App is made to be simple, easy
to use, and efficient. It includes clear input fields, validation checks, and accessibility options
to help caregivers enter patient information quickly and accurately. This design helps prevent
mistakes and ensures that all important details are recorded properly. By making data entry
smooth and error-free, the app becomes a useful and reliable tool for caregivers, helping them
manage the care of Alzheimer’s patients more effectively.

Fig 3.1 Login Page

13
3.3 OUTPUT DESIGN

The output design of the Smart Alzheimer Caregiver App is focused on displaying
information in a clear, structured, and easy-to-understand manner. It ensures that
caregivers and patients can quickly access necessary details without confusion. The app
provides different types of outputs that help in tracking tasks, reminders, appointments,
and familiar people effectively.

One of the main features of the output design is the Appointment Display, which
shows upcoming medical visits along with doctor details and appointment dates. This helps
caregivers and patients stay informed about scheduled check-ups and treatments.

Another important feature is the Reminder System, which provides alerts for tasks
like medication intake, daily activities, and important events. These reminders appear on
the screen with clear text and notifications to ensure that no task is missed.

The Location Display presents a list of saved locations that are frequently visited by
the patient. It helps caregivers and patients identify safe places with ease. This feature
enhances navigation and reduces the risk of disorientation.

Additionally, the People Identification System displays photos, names, and contact
details of familiar individuals. This helps Alzheimer’s patients recognize their loved ones
and caregivers more easily, providing them with a sense of comfort and familiarity.

Overall, the output design ensures that all essential details are presented in a user-
friendly, visually clear, and accessible format, making it easier for both caregivers and
patients to manage daily tasks effectively.

14
Fig 3.2 User Profile

15
3.4 DATABASE DESIGN

A database is a collection of interrelated data stored with minimum redundancy to

serve many users quickly and effectively. After designing the input and output, the analyst
must concentrate on database design or how data should be organized around user
requirements. The general objective is to make information access easy, quick, inexpensive
and flexible for other users. Designing a relational database takes more planning than flat file
databases.

With flat files, it is possible to add information, as you deem necessary. With
relational databases, it is required to be careful to store data in tables such that the
relationships make sense. Building a relational database is dependent upon the ability to
establish a relational model. The model must fully describe how the data is organized, in
terms of data structure, integrity, querying, manipulation and storage.

Relational databases allow defining certain record fields, as keys or indexes, to

perform search queries, join table records and establish integrity constraints. Search queries
are faster and more accurate when based on indexed values. Table records can be easily
joined by the indexed values. Integrity constraints can be established to ensure that table
relationships are valid. Relational databases offer more robust reporting with report
generators that filter and display selected fields.

If the project is able to establish a one-to-many relationship in the data tables,

relational database should be used because a flat file is not sufficient to handle the data
processing needs. Relational databases offer the capability to build own reporting modules.
Most relational databases also offer the capability to import and export data from other
software.

16
3.5 SYSTEM DEVELOPMENT

The Alzheimer's Helper application is designed to help Alzheimer’s patients live more

independently and safely. The application is divided into different modules, each serving a

specific purpose to improve the patient’s day-to-day life and provide support for caregivers.

These modules work together to ensure that the patient’s safety, memory, and well-being are

well-managed. The main modules in the system are:

● Home Page
● Photo Album Page
● Add Photo Page
● Location Page
● Reminders Page

3.5.1 Description of modules

● Home page: The patient first visits this home page. They can easily navigate the
full application through the page.
● Photo album page:This page shows important people whose photos have been
uploaded and identified using face recognition. Each person has a named folder
storing their images, which the patient can view easily.
● Add photo page: The user can submit a photo, tag the person in it, and add it to
the photo album in the appropriate folder so that the patient can see it thanks to
this feature, which is available on the interface.
● Location page:The UI shows this feature if the tracking phone is connected,
allowing the carer to monitor the patient’s location and receive alerts if they
leave a specific area.

● Reminder page: Through this module, reminder notifications can be sent to

patients and to caregivers through SMS in emergency situations.

17
 4. TESTING AND IMPLEMENTATION

The common view of testing held by users is that it is performed to prove that there
are no errors in a program. This is extremely difficult since designers cannot prove to be one
hundred percent accurate. Therefore, the most useful and practical approach is with the
understanding that testing is the process of executing a program with explicit intention of
finding errors that make the program fail.

Testing has its own cycle. The testing process begins with the product requirements
phase and from there parallels the entire development process. In other words, for each phase
of the development process there is an important testing activity. Successful testing requires a
methodical approach. It requires focusing on basic critical factors:

● Planning
● Project and process control
● Risk management
● Inspections
● Measurement tools
● Organization and professionalism

4.1 TEST PLANNING

Before going for testing, first we have to decide upon the type of testing to be carried
out. The following factors are taken into consideration:

● To ensure that information properly flows into and out of program

● To find out whether the local data structures maintain its integrity during all steps
in an algorithm execution
● To ensure that the module operate properly at boundaries established to limit or
restrict processing
● To find out whether error - handling paths are working correctly or not
● To find out whether the values are correctly updated or not
● Check for validations

18
UNIT TESTING

Unit or module testing is the process of testing the individual components

(subprograms or procedures) of a program. The purpose is to discover discrepancies between
the modules interface specification and its actual behaviour. In our system each module must
be tested independently for validation.

VALIDATION TESTING

Validation testing provides the final assurance that software meets all functional,
behavioural and performance requirements. The software once validated must be combined
with other system elements. System testing verifies that as elements combine properly and
that overall system function and performance is achieved.

INTEGRATION TESTING

Integration testing is the process of combining and testing multiple components

together. The primary objective of integration testing is to discover errors in the interfaces
between the components. In our system each of the modules mentioned above, are tested for
checking the integration between them, after each of them are tested individually.

The results of the usability testing process are as follows:

● To ensure that data being entered or extracted is accurate, Alzheimer Assistant has
a verification system in place.
● Users showed trust in their ability to utilise the system and their perception of its
efficacy.
● Users said they could control the system, particularly when entering or extracting
data.
● It was determined that the programme was easy to use.
● It was regarded as a quick and effective system.

19
TEST CASES

Sign in page

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_001 Sign-in Verify user login User should be User successfully Pass
Page with valid successfully logged in logged in and
credentials. and redirected to the redirected to
dashboard. dashboard.
TC_002 Sign-in Verify user login User should see an error Error message Pass
Page with invalid message for incorrect displayed
credentials. credentials. correctly.
TC_003 Sign-in Verify user login User should be User successfully Fail
Page with valid successfully logged in logged in but not
credentials. and redirected to the redirected to
dashboard. dashboard.
TC_004 Sign-in Verify user login User should see an error Error message is Fail
Page with invalid message for incorrect not displayed
credentials. credentials. correctly.

User dashboard

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_005 User Verify if the Dashboard should Dashboard loaded Pass
Dashboard dashboard loads display all key sections successfully with
correctly after login. such as appointments, all sections visible.
tasks, people, locations.
TC_006 User Verify if the Dashboard should Dashboard is not Fail
Dashboard dashboard loads display all key sections loaded with all
correctly after login. such as appointments, sections visible.
tasks, people, locations.

20
Appointments

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_007 Appointm Verify adding a new Appointment should be Appointment Pass
ents appointment. successfully added and added and
displayed in the displaying in the
appointment list. list.
TC_008 Appointm Verify adding a new Appointment should be Appointment Fail
ents appointment. successfully added and added but not
displayed in the displaying in the
appointment list. list.
TC_009 Appointm Verify viewing User should be able to All added Pass
ents existing see all added appointments
appointments. appointments in the list. displayed
correctly.
TC_010 Appointm Verify viewing User should be able to All added Fail
ents existing see all added appointments not
appointments. appointments in the list. displayed
correctly.

Routine

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_011 Routine Verify adding a new Routine should be Routine added and Pass
routine. successfully added and appears in the
visible in the daily routine list.
routine list.
TC_012 Routine Verify adding a new Routine should be Routine added and Fail
routine. successfully added and not appears in the
visible in the daily routine list.
routine list.

21
Locations

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_013 Locations Verify adding a new Location should be Location added Pass
location. successfully added and and visible in the
visible in the locations list.
list.
TC_014 Locations Verify adding a new Location should be Location added but Fail
location. successfully added and not visible in the
visible in the locations list.
list.

People identification

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_015 People Verify adding a new Person should be Person added and Pass
Identificat person to identify. successfully added and visible in the list.
ion visible in the identify
list.
TC_016 People Verify adding a new Person should be Person added but Fail
Identificat person to identify. successfully added and not visible in the
ion visible in the identify list.
list.

22
Tasks

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_017 Tasks Verify adding a new Task should be Task added and Pass
task. successfully added and showing in the list.
visible in the to-do list.
TC_018 Tasks Verify adding a new Task should be Task added but not Fail
task. successfully added and showing in the list.
visible in the to-do list.

Alarm

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_019 Alarm Verify if the alarm Alarm should activate Alarm activated Pass
triggers correctly. and play the set tone. and played the
correct tone.
TC_020 Alarm Verify if the alarm Alarm should activate Alarm activated Fail
triggers correctly. and play the set tone. but not played the
correct tone.
TC_021 Alarm Verify if the alarm Alarm should stop Alarm stopped Pass
stops when playing when the stop successfully upon
dismissed. button is pressed. dismissal.
TC_022 Alarm Verify if the alarm Alarm should stop Alarm is not Fail
stops when playing when the stop stopped
dismissed. button is pressed. successfully upon
dismissal.

23
Profile

Test Test Test Description Expected Result Actual Result Status

Case ID Object
Name
TC_023 Profile Verify if user details Profile section should User details Pass
are correctly display the correct user displayed
displayed in the information. correctly.
profile section.
TC_024 Profile Verify if user details Profile section should User details is not Pass
are correctly display the correct user displayed
displayed in the information. correctly.
profile section.

4.2 SYSTEM IMPLEMENTATION

System implementation is the important stage of a project when the theoretical design
is tuned into a practical system. The main stages in the implementation are as follows:

● Planning
● Training
● System testing and Changeover planning

Planning is the first task in the system implementation. Planning is deciding on the
method and the time scale to be adapted. At the time of implementation of any system people
from different departments and system analysis are involved. They are confirmed to be a
practical problem of controlling various activities of people outside their own data processing
departments. The line manager controlled through an implementation co-ordinate committee.
The committee consists of ideas, Problems and complaints of the user department. It must
also consider,

● The implementation of the system environment.

● Self-selection and allocation for implementation tasks.
● Consultation with unions and resources available.
● Standby facilities and channels of communication.

24
 5. CONCLUSION

The software is completely menu driven and extremely user friendly since it is
developed in an efficient front-end tool. Appropriate error messages are provided to guide
the user in a proper and user-friendly manner. Time consumptions are reduced to a great
extent and the user has less complexity in handling the system. End users will be very
much satisfied with the software. Tables are designed with primary keys and foreign keys
in order to establish relationship between tables. In order to get ideas for implementation,
flow diagrams have been designed. All types of updating can be made through the system
whenever necessary. The software created is attractive and user-friendly. It is highly
interactive too. The software appears more flexible, which is completely menu-driven, it
gives advantage, as it needs less typing by the user. It maintains data consistency. The
system reduces workload and produces adequate and timely information as and when
required. Software has been developed and tested.

The Alzheimer Assistant app was created specifically to help Alzheimer's patients
identify people by looking at the album on the app, which has classified each person by
their face and displayed information about their relationship; and by giving them a
tracking mobile phone that enables the patient's family to find them in the event that they
get lost and lose their way. As a result, our programme encourages Alzheimer's sufferers
to feel more secure when taking part in routine tasks, which enhances their capacity to
regularly participate in social events. This application has successfully shown that it can
support the relatives and carers of Alzheimer's patients. The absence of a feature that
would allow carers to check on patients remotely would prevent this application from
receiving the official endorsement of the Alzheimer's Patients Association of India.

25
 6. SCOPE FOR FUTURE ENHANCEMENT

The Smart Alzheimer Caregiver App has the potential for several future
enhancements to further improve its functionality, usability, and effectiveness in supporting
caregivers and Alzheimer patients. As technology continues to advance, integrating new
features can enhance the caregiving experience and provide better patient care.

● An essential enhancement is Advanced Facial Recognition with Deep Learning,

which improves the accuracy of user identification even in low-light conditions,
different angles, or partial obstructions. This advancement enhances security by
preventing unauthorized access and ensuring better user authentication.

● Another key feature is Geo-Fencing and Emergency Alerts, where caregivers can
set safe zones, such as home or familiar surroundings, using GPS-based geo-fencing.
If a user moves beyond these zones, automatic alerts notify caregivers, reducing the
risk of wandering and ensuring timely intervention.

● To help users maintain a structured routine, Medication and Daily Task Reminders
provide AI-powered notifications for medication schedules and daily activities. These
reminders can be personalized based on user needs and integrated with voice
assistance for ease of use.

● Additionally, Health Monitoring with Wearable Device Integration enables real-

time tracking of vital signs such as heart rate, sleep patterns, and activity levels
through smartwatches and other wearable devices. If abnormal health patterns are
detected, caregivers receive alerts, ensuring timely medical attention.

● Lastly, Multi-User Access for Caregivers and Family Members enhances

collaborative care by allowing multiple caregivers, family members, or medical
professionals to monitor the user’s location, health data, and schedule through a
shared dashboard. This feature improves communication and coordination, ensuring
comprehensive support for individuals with Alzheimer's.

26
 BIBLIOGRAPHY

BOOK REFERENCES

1. Alpaydin, E. (2020). Introduction to Machine Learning. MIT Press.

2. Alzheimer’s Helper (2019). Available at: [Link]
helper/id1458210176?l=ar.
3. Ambler, S. W. (2014). User Interface Design Tips, Techniques, and
Principles,Ambysoft Inc. Available at: [Link] essays/userInterface
[Link].
4. Android Studio (2020). Available at: [Link]
5. AngleSense (2019). Available at: [Link]
6. Arnowitz, J., Arent, M. and Berger, N. (2007). Effective prototyping for software
makers. Elsevier.
7. Cloud Firestore (2020). Available at: [Link]
8. Cohen, A. D. et al. (2019). Fluid and PET biomarkers for amyloid pathology in
Alzheimer’s disease. Molecular and Cellular Neuroscience, 97, pp. 3–17.
9. Design Phase - ZMQ Development (2019). ZMQ Development.
10. Dospinescu, O. and Popa, I. (2016). Face Detection and Face Recognition in Android
Mobile Applications. Informatica Economica, 20(1/2016), pp. 20–28. DOI:
10.12948/issn14531305/ 20.1.2016.02.

WEB REFERENCES

● [Link]
● [Link]/manual/en/[Link]
● [Link]/Java
● [Link]
● [Link]
● [Link]

27
 APPENDICES

A. DATA FLOW DIAGRAM

A data flow diagram is a graphical tool used to describe and analyze movement of
data through a system. These are the central tool and the basis from which the other
components are developed. The transformation of data from input to output, through
processing, may be described logically and independently of physical components associated
with the system. These are known as the logical data flow diagrams.

The physical data flow diagrams show the actual implements and movement of data
between people, departments and workstations. A full description of a system actually
consists of a set of data flow diagrams. Each component in a DFD is labeled with a
descriptive name. Process is further identified with a number that will be used for
identification purposes. The development of DFD’S is done in several levels. Each process
in lower-level diagrams can be broken down into a more detailed DFD in the next level. The
top-level diagram is often called a context diagram. It consists of a single process bit, which
plays a vital role in studying the current system. The process in the context level diagram is
exploded into another process at the first level DFD.

The idea behind the explosion of a process into more processes is that understanding
at one level of detail is exploded into greater detail at the next level. This is done until further
explosion is necessary and an adequate amount of detail is described for analyst to understand
the process. A DFD is also known as a “bubble Chart” and has the purpose of clarifying
system requirements and identifying major transformations that will become programs in
system design. So it is the starting point of the design to the lowest level of detail. A DFD
consists of a series of bubbles joined by data flows in the system.

DFD symbols

In the DFD, there are four symbols

● A square defines a source(originator) or destination of system data

● An arrow identifies data flow. It is the pipeline through which the information
flows
● A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.

28
 ● An open rectangle is a data store, data at rest or a temporary repository of data.

SYMBOL DESCRIPTION

Process that transforms data flow

Source or Destination of data

Data flow

Data Store

Constructing a DFD

Several rules of thumb are used in drawing DFD’S

● Processes should be named and numbered for an easy reference. Each name
should be representative of the process.
● The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to destination although they may flow back to the
source. One way to indicate this is to draw a long flow line back to a source.
● An alternative way is to repeat the source symbol as a destination. Since it is used
more than once in the DFD it is marked with a short diagonal. When a process is
exploded into lower-level details, they are numbered.
● The names of data stores and destinations are written in capital letters. Process and
dataflow names have the first letter of each work capitalized.

A DFD typically shows the minimum contents of a data store. Each data store should
contain all the data elements that flow in and out. Exams should contain all the data elements

29
that flow in and out. Missing interfaces redundancies and like is then accounted for often
through interviews.

Salient features of DFD’s

● The DFD shows flow of data, not of control loops and decision are controlled
considerations that do not appear on a DFD.
● The DFD does not indicate the time factor involved in any process whether the
data flowtakes place daily, weekly, monthly or yearly.
● The sequence of events is not brought out on the DFD.

Current physical

In current physical DFD process label include the name of people or their positions or
the names of computer systems that might provide some of the overall system-processing
label that includes an identification of the technology used to process the data. Similarly,
data flows and data stores are often labeled with the names of the actual physical media on
which data are stored such as file folders, computer files, business forms or computer tapes.

New logical

This is exactly like a current logical model if the user were completely happy with the
user were completely happy with the functionality of the current system but had problems
with how it was implemented typically through the new logical model will differ from current
logical model while having additional functions, absolute function removal and inefficient
flows recognized.

New physical

The new physical represents only the physical implementation of the new system.

Current logical

The physical aspects of the system are removed as much as possible so that the
current system is reduced to its essence to the data and the processors that transform them
regardless of actual physical form.

Process

No process can have only outputs. No process can have only inputs. If an object has
only inputs then it must be a sink. A process has a verb phrase label.

30
Data store

Data cannot move directly from one data store to another data store, a process must
move data. Data cannot move directly from an outside source to a data store, a process, which
receives, must move data from the source and place the data into the data store. A data store
has a noun phrase label.

Source or sink

Source is the origin or destination of data. Data cannot move directly from a source to
sink it must be moved by a process. A source or sink has a noun phrase land.

Levels of DFD

The complexity of the business system means that it is responsible to represent the
operations of any system in a single data flow diagram. At the top level, an Overview of the
different systems in an organization is shown by way of a context analysis diagram. When it
exploded into DFD. The input and output data shown should be consistent from one level to
the next.

Level-0 System input/output level

A level-0 DFD describes the system-wide boundaries, dealing inputs to and outputs
from the system and major processes. This diagram is similar to the combined user-level
context diagram.

Level-1 Subsystem level data flow

A level-1 DFD describes the next level of details within the system, detailing the data
flows between subsystems, which make up the whole.

Level-2 File level detail data flow

All the projects are feasible given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of the project at the earliest possible time.
Feasibility and the risk analysis are pertained in many ways if project risk is great.

31
DFD Level 0

User Alzheimer Admin

App

Level 1

Enters
1.0
User
Registration

1.1
User
Login

1.2

Manage Photo
photo

Reports

32
Level 2

Enters
2.0
User
Registration

2.1
User
Login

2.2

Manage Photo
people

2.3
Location
Manage
Location

2.4

Reminder
Reminder

Reports

33
B. ER DIAGRAM

An entity-relationship diagram is a data modeling technique that creates a graphical

representation of the entities, and the relationships between entities, within an information
system. The three main components of an ERD are as follows.

The entity is a person, object, place or event for which data is collected. For example,
if the information system for a business is considered, entities would include not only
customers, but the customer's address, and orders as well. The entity is represented by a
rectangle and labelled with a singular noun.

The relationship is the interaction between the entities. In the example above, the
customer places an order, so the word "places" defines the relationship between that instance
of a customer and the order or orders that they place. A relationship may be represented by a
diamond shape, or more simply, by the line connecting the entities. In either case, verbs are
used to label the relationships.

The cardinality defines the relationship between the entities in terms of numbers. An
entity may be optional: for example, a sales rep could have no customers or could have one or
many customers; or mandatory: for example, there must be at least one product listed in an
order.

There are several different types of cardinality notation; crow's foot notation, used
here, is a common one. In crow's foot notation, a single bar indicates one, a double bar
indicates one and only one (for example, a single instance of a product can only be stored in
one warehouse), a circle indicates zero, and a crow's foot indicates many. The three main
cardinal relationships are: one-to-one, expressed as 1:1; one-to-many, expressed as 1:M; and
many-to-many, expressed as M:N.

The steps involved in creating an ERD are:

● Identify the entities.

● Determine all significant interactions.
● Analyze the nature of the interactions.
● Draw the ERD.

34
Symbols & their meaning in ERD

SYMBOLS DESCRIPTION

Relationship

Weak entity is an entity which depends on

strong entity attribute’s, it does not have its
own

Attribute

Multi valued attribute is an attribute which

has more than one values

Derived attribute

Relationship

35
ER diagram

Ufname Ulname Email

Pwd

Umobile User

pid
Email Email
rdtime
pdate

Reminder Photo

Maintains

rname pname
pmobile
rid
Location

locid

Email

lname
ldate
location

36
 C. TABLE STRUCTURE

Table Name : user

Primary key : user_email

Field name Data type Description Constraint

user_email Varchar(35) Email ID of the user Primary key, Not null
first_name Varchar(25) First name of the user Not null
last_name Varchar(25) Last name of the user Not null
user_mobile Int Mobile number of the user Not null
user_pwd Varchar(25) Password of the user Not null

Table Name : location

Primary key : loc_id Foreign key : user_email

Field name Data type Description Constraint

user_email Varchar(35) Email ID of the user Foreign key, Not null
loc_id Int Location ID Primary key, Not null
loc_date Datetime Location added date Not null
loc_name Varchar(25) Name of the location Not null
location Varchar(50) Google map location Not null

Table Name : photo

Primary key : p_id Foreign key : user_email

Field name Data type Description Constraint

user_email Varchar(35) Email ID of the user Foreign key, Not null
p_id Int Photo ID Primary key, Not null
p_date Datetime Photo added date Not null
p_name Varchar(25) Name of the person Not null
p_mobile Int Mobile number of person Not null

37
 Table Name : reminder

Primary key : r_id Foreign key : user_email

Field name Data type Description Constraint

user_email Varchar(35) Email ID of the user Foreign key, Not null
r_id Int Reminder ID Primary key, Not null
r_datetime Datetime Reminder date and time Not null
r_name Varchar(25) Name of the reminder Not null

38
D. SYSTEM FLOW DIAGRAM

Start

Profile creation

Reminders Locations People and Photo

Stop

The system flow diagram illustrates the process starting from profile creation, branching into

reminders, locations, and people & photos, and ultimately leading back to the start. It visually

represents a structured workflow for managing user information and interactions within the

system.

39
E. SAMPLE CODING

Mainactivity

package [Link]

import [Link]

import [Link]

import [Link]

import [Link]

import [Link]

import [Link]

import [Link]

class MainActivity :AppCompatActivity() {

lateinit var fragment: Fragment

override fun onCreate(savedInstanceState: Bundle?) {

[Link](savedInstanceState)

setContentView([Link].activity_main)

init()

private fun init() {

supportActionBar?.setBackgroundDrawable([Link]([Link]))

loadFragment(DashbaordFragment())

40
findViewById<BottomNavigationView>([Link].bottom_navigation).setOnNavigationItemSele
ctedListener { item ->

when ([Link]) {

[Link].navigation_dashboard -> {

fragment = DashbaordFragment()

supportActionBar?.title = [Link]([Link])

[Link].navigation_daily_routine -> {

fragment = DailyRoutineFragment()

supportActionBar?.title = [Link]([Link].daily_routine)

[Link].navigation_profile -> {

fragment = ProfileFragment()

supportActionBar?.title = [Link]([Link])

loadFragment(fragment)

private fun loadFragment(fragment: Fragment): Boolean {

if (fragment != null) {

[Link]()

41
.replace([Link].fragment_container, fragment)

.commit()

return true

return false

[Link]

<?xml version="1.0" encoding="utf-8"?>

<RelativeLayoutxmlns:android="[Link]

xmlns:app="[Link]

xmlns:tools="[Link]

android:layout_width="match_parent"

android:layout_height="match_parent"

android:background="@drawable/bg_gradient"

tools:context=".SignupActivity">

<RelativeLayout

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_above="@id/input_group"

android:layout_alignParentTop="true"

android:layout_margin="10dp"

42
android:orientation="vertical">

<[Link]

android:id="@+id/signup_image_upload"

android:layout_width="250dp"

android:layout_height="250dp"

android:layout_centerInParent="true"

android:elevation="10dp"

android:padding="2dp"

android:scaleType="centerCrop"

android:src="@drawable/user"

app:shapeAppearanceOverlay="@style/roundedImageViewRounded"

app:strokeColor="@color/white_shadow"

app:strokeWidth="2dp" />

<TextView

android:id="@+id/image_error_text"

style="@style/[Link]"

android:layout_width="wrap_content"

android:layout_height="wrap_content"

android:layout_below="@id/signup_image_upload"

android:layout_centerInParent="true"

android:gravity="center"

android:text="@string/select_your_photo"

43
android:textColor="@color/white_shadow"

android:textStyle="bold"

android:visibility="gone" />

</RelativeLayout>

<LinearLayout

android:id="@+id/input_group"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_alignParentBottom="true"

android:layout_marginLeft="20dp"

android:layout_marginRight="20dp"

android:layout_marginBottom="20dp"

android:gravity="center"

android:orientation="vertical">

<EditText

android:id="@+id/signup_name"

style="@style/[Link]"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:background="@drawable/edt_top"

android:hint="@string/name"

44
android:inputType="text"

android:padding="15dp"

android:textColor="@color/purple_light"

android:textColorHint="@color/edit_text_color" />

<EditText

android:id="@+id/signup_dob"

style="@style/[Link]"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:background="@drawable/edt_middle"

android:hint="@string/dob"

android:inputType="date"

android:maxLines="1"

android:padding="15dp"

android:textColor="@color/purple_light"

android:textColorHint="@color/edit_text_color" />

<EditText

android:id="@+id/signup_email"

style="@style/[Link]"

android:layout_width="match_parent"

android:layout_height="wrap_content"

45
android:background="@drawable/edt_middle"

android:hint="@string/email"

android:inputType="textEmailAddress"

android:padding="15dp"

android:textColor="@color/purple_light"

android:textColorHint="@color/edit_text_color" />

<EditText

android:id="@+id/signup_password"

style="@style/[Link]"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:background="@drawable/edt_middle"

android:hint="@string/password"

android:inputType="textPassword"

android:padding="15dp"

android:textColor="@color/purple_light"

android:textColorHint="@color/edit_text_color" />

<EditText

android:id="@+id/signup_password_confirm"

style="@style/[Link]"

android:layout_width="match_parent"

46
android:layout_height="wrap_content"

android:background="@drawable/edt_bottom"

android:hint="@string/confirm_password"

android:inputType="textPassword"

android:padding="15dp"

android:textColor="@color/purple_light"

android:textColorHint="@color/edit_text_color" />

<Button

android:id="@+id/signup_btn"

style="@style/[Link]"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_marginTop="10dp"

android:background="@drawable/button"

android:foreground="?attr/selectableItemBackground"

android:gravity="center"

android:text="@string/signup"

android:textColor="@color/purple_700" />

<TextView

android:id="@+id/signin_text"

style="@style/[Link].Body2"

47
android:layout_width="wrap_content"

android:layout_height="wrap_content"

android:layout_marginTop="3dp"

android:fontFamily="sans-serif"

android:gravity="center"

android:padding="10dp"

android:text="@string/signinNow"

android:textAllCaps="true"

android:textColor="@color/white_shadow"

android:textStyle="bold" />

</LinearLayout>

</RelativeLayout>

[Link]

<?xml version="1.0" encoding="utf-8"?>

<[Link]:android="[Link]
[Link]/apk/res/android"

xmlns:app="[Link]

xmlns:tools="[Link]

android:layout_width="match_parent"

android:layout_height="match_parent"

android:background="@drawable/main_bg"

tools:context=".MainActivity">

48
<FrameLayout

android:id="@+id/fragment_container"

android:layout_width="match_parent"

android:layout_height="match_parent"

android:animateLayoutChanges="true"

app:layout_behavior="[Link]$ScrollingViewBe
havior" />

<[Link]

android:id="@+id/bottom_navigation"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_gravity="bottom"

android:background="@color/purple_light"

app:layout_behavior="@string/hide_bottom_view_on_scroll_behavior"

app:menu="@menu/bottom_navigation_menu" />

</[Link]>

49
F. SAMPLE INPUT

Fig F.1 Adding Appointments

Allows users to schedule appointments by entering details like doctor’s name, specialty,

location, hospital, date, and time.

50
 Fig F.2 Adding Location

This feature lets users save a location by entering a name and its corresponding latitude-

longitude details. It helps in easily identifying and accessing frequently visited places.

51
 Fig F.3 Adding people to identify

This feature allows users to add and remember people by entering their name and phone

number.

52
G. SAMPLE OUTPUT

Fig G.1 Viewing appointments

This feature displays scheduled appointments with details like doctor’s name, specialty,

hospital, date, and

53
 Fig G.2 Viewing people

This feature displays the list of identified people with their images and names for easy

recognition.

Fig G.3 Viewing locations

This feature lets users save a location by entering a name and latitude-longitude details.

54
 Fig G.4 After alarm activated

This feature notifies users when a scheduled routine alarm is activated.

55