Declaration

I declare that this written submission represents my ideas in my own words

and where other's ideas or words have been included, I have adequately
cited and referenced the original sources. I also declare that I have adhered
to all principles of academic honesty and integrity and have not
misrepresented or fabricated or falsified any idea/data/fact/source in my
submission. I understand that any violation of the above will be cause for
disciplinary action by the Institute and can also evoke penal action from the
sources which have thus not been properly cited or from whom proper
permission has not been taken when needed.

Date:
Place:
 ACKNOWLEDGMENT
After the completion of this work, words are not enough to express my feelings
about all those who helped me to reach my goal; feeling above this is my indebtedness
to the almighty for providing me this moment in my life.

It’s a great pleasure and moment of immense satisfaction for me to express my

profound gratitude to my project guide, Prof. Uday Rote whose constant
encouragement enabled me to work enthusiastically. His perpetual motivation, patience
and excellent expertise in discussion during progress of dissertation work have benefited
me to an extent, which is beyond expression. His depth and breadth of knowledge of
Engineering field made me realize that theoretical knowledge always help to develop
efficient operational software, which is a blend of all core subjects of the field. The
completion of this project would not have been possible without his encouragement,
patient guidance and constant support.

Special thanks to my colleagues and friends for providing me useful comments,

suggestions and continuous encouragement.

Finally, I thank my family members, for their support and endurance during this work.

Mr. _____________________

Application Id:__________
Abstract

So, I am introducing an Android application whose objective is to remind the

patients of their dosage timings through this reminder system. The application
is designed on Android Studio. It can be helpful for users to set-up a reminder
on daily basis or etc., because setting up a reminder depends on the users and
can spread health care awareness. It is life-saving and time saving application
which is easy to use and provides a good user interface. Today everyone has a
smart phone. With this we get an opportunity to use technology in better way
so that it can be made useful to us. And it plays an important part in our daily
life and helps us staying fit in many way as well as this app is mostly develop
for job, business people and senior citizen, in this daily life they are totally get
stuck in their work so they are not able to remind there dosage time so this app
will help them to take their dosage.
 INDEX
1 Introduction
1.1 Motivation
1.2 Scope
1.3 Objective
2 Related Work
2.1 Related Research
3 Analysis and Planning
3.1 Feasibility Study
3.1.2 Economical Feasibility
3.1.3 Technical Feasibility
3.1.4 Operational Feasibility
3.2 Project Scheduling
3.3 Development Methodology
4 Proposal System Design
4.1 UML Diagram
4.1.1 Use Case Diagrams
4.1.2 DFD Level-0
4.1.3 DFD Level-1
4.1.4 Class Diagram
4.1.5 Activity Diagram
4.1.6 State Chart Diagram
4.1.7 Entity Relationship Diagram
5 Specifications
6. Implementation Details
6.1 Implementation
6.2 Relevant Information
6.3 Oreo Operating System
6.4 Android Studio
7 Testing
7 Software testing
7.1.0 Testing Approach
7.1.1 Black box testing
7.1.2 White box testing
7.1.3 Unite Testing
7.1.4 Integration testing
7.1.5 User Acceptance Testing
7.1.6 Functional testing
8 Result Analysis
9 Conclusion Future work
 MEDICINE REMINDER
ANDROID APPLICATION
 Chapter1

Introduction
Patients involve human being of all categories Teachers, Students, Business
man, Housewives, children and also all of us have a hectic schedule. In today’s
life there is full of responsibilities and stress. So, people are prone of diseases of
different types and it is our duty to make ourselves stay fit and healthy. If the
people who stay at home there is someone he or she will look after them
him/her, one is out of the home, is out of the city or stay away from home then
it is hard for the family member to look after them and remind them their
dosage timings every time.

In my developing and technology dependent life we all are totally dependent on

gadgets especially smart phones. In today’s world everyone carries
smartphones. With this we get an opportunity to use technology in a better way
so that we can made it useful to us. And it plays an important part in our daily
life. The remarkable problem is that patients forget to take a medicine at time in
a proper portion.

So we are introducing an Android application whose objective is to remind the

patients of their Dosage time through Alarm Ringing system so that they can
stay fit and healthy. This application focuses on the people who forget to take
medicines on time. It allows user to set an alarm along with date and medicine
description which will allow them to set alarm for multiple medicines at
different time intervals. After setting an alarm it will send u a proper
notification. The user can activate or deactivate the notification accordingly.

This application is designed on Android Studio. So that it will help to user to

take the medicine on time and it is very convenient for user with a good user-
friendly interface.
1.1 Motivation

To building such kind of product come from the observing the elders in a family
because of stress and work load they are missing their pills in absence of regular
supervision. As well as in our society office going people are not able to look
after their parents due to looking after this all situation. All these happening
motivated me to come up with an easy solution for the aged and the ailing.

1.2 Scope

This application had made on a android studio platform the service of this
application is the medicine reminder this is a free software so that in our society
each and every person could use this software many time we had seen that
medicine intake is provided by doctor is not followed. In our application we
make assure that patient does not take wrong dosage so in the application there
is option where it is written a medicine name. it is going to be free and easy to
access.

1.3 Objective

Objective is based on android operating system which will remind the users to
take medicines on time through notification and automatic alarm ringing
system. Android is the windows-based system which is designed primarily for
touch screen mobile devices such as smart phones and tablet computers,
developed by google.

Information technology supporting patient self-management there medication so

that they cam improve accountability for healthcare outcome by improving
patient. So that in the pandemic time there is lots of people forget to take a
medicine but through this app they could able to take the medicine easily.
CHAPTER 2.
Related work
2.1 Related research:
Android is the most popular OS in the market. Market share of Android is 66%
and IOS is 27%. Windows is third at around 5% and remaining are other OS.
Android is Linux based OS which is specially designed for touch screen
smartphone and tablet computer which were developed by google. Android was
created from ground so it allows creation of various developer for full use of
their smartphone. Android has an ADF (Application Development Framework).
It provides API for development of application. The framework design
simplifies the integration and reuse of the usable components. Android apps
have to be built using XML manifest file which is mandatory. Android being an
open-source system unlike iOS, can be modified to suit our needs by rewriting
the source code.
 CHAPTER 3
Analysis and Planning
3.1 Feasibility Study
The project feasibility study play major role in analysis of the system. It
is undertaken to determine the possibility of either improving the present system
or developing a completely new system. It is process which defines exactly
what a project is and what strategic issues need to be considered to assess its
feasibility, or likelihood of succeeding.

Feasibility study is a process to check possibilities of system development. It is

a method to check various different requirements and availability of financial &
technical resources.

There are three aspects in the feasibility study portion of the preliminary
investigation.
● Economic Feasibility.

● Technical Feasibility.

● Operational / Scheduling Feasibility.

3.1.2 Economical Feasibility

It is considered mainly of two tests:

● Anticipated value of benefit is greater than cost of development.

● Does the organization have adequate cash flow to fund the project?
A determination to economic feasibility of the project requires the row
cost benefit analysis. The cost benefit analysis compares the cost and
benefit to see whether the investment in development of a new system
will be more beneficial than costly.
 Automation leads to reduction of manpower and processing time.
They purchase software with minimum rate. Thus, the system is said
to be economically feasible.

3.1.3 Technical Feasibility

It is based on computer hardware and network software. Additional
peripheral devices are required and funds are available in shop.
The software used for the development of proposed system is Jdk1.6.0 for
Java and SQL workbench.
● Hardware Requirements

● Software Requirements.

3.1.4 Operational Feasibility

This project will provide adequate throughput and response time. The
work can be completed well in time with accuracy and useful
formatted information
The proposed system will be user friendly. Security will be maintained
by preventing unauthorized access.

3.2 Project Scheduling

Gantt Chart:
Gantt chart is a horizontal bar chart that gives a visual view of tasks scheduled
over time. Gantt charts are used for planning projects of all sizes and they are a
useful way of showing what work is scheduled to be done on a specific day.
They also help you view the start and end dates of a project in one simple view.
It typically shows the status of each task in the project.
Reasons to use Gantt chart:
a. Avoid Completion Confusion
b. It keeps all team members on the same page
c. Understand Task Relationships
d. Effectively allocate Resources
e. Gets a handle on future
3.3 Development Methodology
This section describes the project as per the various stages of the
Software Development life cycle. The model in the software development life-
cycle used in this project is the Waterfall Method. It is very simple to
understand and implement. The Waterfall Method consists of a series of very
definite phases, as shown below in figure each one run intended to be started
sequentially only after the last has been completed, with one or more tangible
deliverables produced at the end of each phase of the waterfall method of
SDLC. Essentially, it starts with a heavy, documented, requirements planning
phase that outlines all the requirements for the project, followed by sequential
phases of design, coding, test-casing, optional documentation, verification
(alpha-testing), validation (beta-testing), and finally deployment/release
The phases of the Waterfall Model are as follows:
1. Requirements: All the requirements needed for the project are to be
collected in this phase and documented in a specification document.
Requirements include the dataset, hardware and software requirements, etc

2. Design: Once the requirements are gathered, it is time to design the overall
blue print of the system. The requirement specifications from the first phase are
studied in this phase and the system design is prepared

3. Development: Once the technical analysis has been done, developing the
model is the next step. In this phase, the Machine Learning model is built using
various algorithms and fed with the dataset.
4. Testing: Post development, testing the implementation and finding out the
errors is the next process in the model. Post integration the entire system is
tested for any faults and failures.

5. Deployment: Once the functional and non-functional testing is done; the

project is deployed in the customer environment or released into the market.

6. Maintenance: There are some issues which come up in the client

environment. To fix those issues, patches are released. Also, to enhance the
product some better versions are released. Maintenance is done to deliver these
changes in the customer environment.
 Chapter 4
Proposed System Design

4.1 UML Diagrams

The unified modeling language (UML) is a graphical language for visualization,
specifying, constructing and documenting the artifacts of a software intensive
system. The UML gives a standard was to write system’s blue prints, covering
conceptual things, such as business processes and system function, as well as
concrete things, such as classes return in specific programming language ,
database schemas, reusable software components. There are number of UML
diagrams in unified modeling language, such as
1. Use Case Diagram

2. DFD Level-0

3. DFD Level-1

4. Class Diagram

5. Activity Diagram

6. State Chart Diagram

7. E-R Diagram

4.1.1 Use Case Diagram

Use case diagrams are used to gather the requirements of a system including
internal and external influences. These requirements are mostly design
requirements. Hence, when a system is analyzed to gather its functionalities, use
cases are prepared and actors are identified. represents the use case diagram
wherein the admin handles the basic functionalities of the project such as
collecting the data, using this data to build and train the Machine Learning
model, and using this model to compute the results. Users can view the stock
prices through the dashboard.

The purpose of use case diagram is to capture the dynamic aspect of a system.
but this definition is too generic to describe the purpose.
So, in brief, the purposes of use case diagrams can be as follows:
 Used to gathered requirements of system
 Used to get. an outside view of appllication
 Identify external and internal factors influencing the application
 Show the interacting among the requirement are actors.

4.1.2 DFD Level- 0

Data Flow Diagram (DFD) is also called as „Bubble chart‟. This is a graphical
technique that represents information flow, and transformers those are applied
when data moves from input to output.
DFD represents system requirements clearly and identify transformers those
becomes programs in design.
DFD consists of series of bubbles joined by lines.
4.1.3 DFD Level-1
DFD are used to represent information flow, and the transformers those are
applied when data
moves from input to output. To show the data flow with more details, the DFD
further extended to level 1, level 2, level 3 etc. as per the requirement.
The typical value for the DFD is seven. Any system can be well represented
with the details up to seventh levels.
4.1.4 Class Diagram
The class diagram is a static diagram.it represents the static view of an
application. class diagram is not only used for visualizing, describing and
documenting diff. aspects of a system but also for constructing executable code
of the software application.
The class diagram shows a collection of classes, interfaces, associations,
collaborations and constraints. It is also known as a structural diagram
 study User Interface
+study name +textbox
+qty +has a
+Button
+time +create UI ()
+storeinfo()
+storeImage()
+Viewinfo()

+strong relationship

Alert
+study name
+getCurentTime()
+continousCheckForMatch()

4.1.5 Activity Diagram

Activity diagram is basically a flow chart to represent the flow form one activity
to another activity. The activity can be described as an operation of the system.
Purpose
It captures the dynamic behavior of the system. Activity diagram is used to
show message flow from one activity to another. So, we should identify the
following elements.

4.1.6 State Chart Diagram

In the Unified Modeling Language, a component diagram depicts how
components are wired together to form larger components and or software
systems. They are used to illustrate the structure of arbitrarily complex systems.
Components are wired together by using an assembly connector to connect the
required interface of one component with the provided interface of another
component. This illustrates the service consumer – service provider relationship
between the two components.

4.1.7 Entity Relationship Diagram

An ER model is an abstract way to describe a database. Describing a database
usually starts with a relational database, which stores data in tables.
Some of the data in these tables point to data in other tables – for instance, your
entry in the database could point to several entries for each of the phone
numbers that are yours. The ER model would say that you are an entity, and
each phone number is an entity, and the relationship between you and the phone
number is „has a phone number‟. Diagrams created to design these
entities and relationships are called entity – relationship diagrams or ER
diagrams.
 Chapter 5
SPECIFICATIONS

Software Requirement

Operating System Server

Windows 10
 Client
Microsoft Internet Explorer

Tools and environment

jdk16

Code Behind
Java, Android

Hardware requirement

Processor
Intel i5 or later

Ram
Minimum 512 MB

Secondary storage
Minimum 80 GB
 Chapter 6

Implementation Details

6.1 Implementation
The Implementation is based on Android Operating system which will remind
the users to take medicines on time through notification and automatic alarm
ringing system. Android is a Linux-based operating system designed primarily
for touch screen mobile devices such as smart phones and tablet computers,
developed by Google in conjunction with the Open Handset Alliance.
Android was built from the ground-up to enable developers to create compelling
mobile applications that take full advantage of all a handset has to offer. The
system is specified on android operating system only because the market share
of Android is high.

Android also comes with an application development framework (ADF), which

provides an API for application development and includes services for building
GUI applications, data access, and other component types. The framework is
designed to simplify the reuse and integration of components. Android apps are
built using a mandatory XML manifest file. The manifest file values are bound
to the application at compile time. This file provides essential information to an
Android platform for managing the life cycle of an application.

Examples of the kinds of information included in a manifest file are descriptions

of the app’s components among other architectural and configuration properties.
Components can be one of the following types: Activities, Services, Broadcast
Receivers, and Content Providers.

Medication Reminder and Healthcare: System Overview

6.2 Relevant Information
This is most popular operating system for mobile devices and tablets and is an
open-source operating system created by Google. Android is a Linux-based
operating system for smart phones and tablets. It includes different interfaces
like touch screen user interface, widgets, camera, network data monitoring and
all other features so to enable a cell to be called as smart phones.
 Android provides efficient platform for creating apps that is stable, bugs free
and take
advantage of the hardware capabilities available on each device.
 It provides various security features and facilities to keep your data safe.
 It’s an open-source technology and easily customizable as per user needs.

6.3 Oreo Operating System

Android 8.0 (API level 26) allows activities to launch in picture-in-picture (PIP)
mode. PIP is a special type of multi-window mode mostly used for video
playback. PIP mode was originally available for Android TV only; Android 8.0
makes the feature available on other Android devices. When an activity is in
PIP mode, it is in the paused state, but should continue showing content. For
this reason, you should make sure your app does not pause playback in its on-
Pause handler. Instead, you should pause video in on Stop, and resume playback
in on Start. For more information, see Multi-Window Lifecycle.

Features of Oreo
 Smooth like butter
 These include more accurate dictionaries, better prediction and correction, and
an easy way to switch languages.
 In Marshmallow notifications are even better, offering far more contextual
information.
 The notifications are expandable and actionable.
 It makes your device work more smoothly and responsively, and it patches up
a few bugs
and issues that emerged in previous operating systems.

6.4 Android Studio

Android Studio is the official integrated development environment (IDE) for
the Android platform.
It was announced on May 16, 2013 at the Google I/O conference. Android
Studio is freely available under the Apache License 2.0
Android Studio was in early access preview stage starting from version 0.1 in
May 2013, then entered beta stage starting from version 0.8 which was released
in June 2014. The first stable build was released in December 2014, starting
from version 1.0. Based on JetBrains' IntelliJ IDEA software, Android Studio is
designed specifically for Android development. It is available for download on
Windows, macOS and Linux and replaced Eclipse Android Development Tools
(ADT) as Google's primary IDE for native Android application development.

Features
 Gradle-based build support
 Android-specific refactoring and quick fixes
 Lint tools to catch performance, usability, version compatibility and other
problems
 ProGear integration and app-signing capabilities
 Template-based wizards to create common Android designs and components
 Chapter 7

Testing

7. Software Testing
Software testing is the process of evaluation a software item to detect
differences between given input and expected output. Also, to assess the
features of a software item. Testing assesses the quality of the product. Software
testing is a process that should be done during the development process. In other
words, software testing is a verification and validation process.

Verification:
Verification is the process to make sure the product satisfies the conditions
imposed at the start of the development phase. In other words, to make sure the
product behaves the way we want it to.

Validation:
Validation is the process to make sure the product satisfies the specified
requirements at the end of the development phase. In other words, to make sure
the product is built as per customer requirements.
Testing has different goals and objectives:
Finding defects Gaining confidence in and providing information about the
level of quality.

7.1.0 Test Approach

Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test. Software
testing also provides an objective, independent view of the software to allow the
business to appreciate and understand the risks of software implementation.

7.1.1 Black box testing

In black box testing we test the system at random for some random
functionalities and depending on the output that we get we come to the
conclusion that whether the system we have built is right or wrong. Internal
system design is not considered in this type of testing. Tests are based on
requirements and functionality.

7.1.2 White box testing

This testing is based on knowledge of the internal logic of an application code.
Also known as Glass box Testing. Internal software and code working should
be known for this type of testing. Tests are based on coverage of code
statements, branches, paths, conditions. All the modules are tested for their
logic whether it functions properly or not. Code is checked by inserting
different inputs to check its functionality.

7.1.3 Unit Testing

Unit Testing is a level of the software testing process where individual
 units/components of a software/system are tested. The purpose is to validate that
each unit of the software performs as designed.

A unit is the smallest testable part of software. It usually has one or a few inputs
and usually a single output. In procedural programming a unit may be an
individual program, function, procedure, etc. In object-oriented programming,
the smallest unit is a method, which may belong to a base/super class, abstract
class or derived/child class.

Test Cases for Unit Testing of our Application

Test case No. Test Description Test Data Expected Actual Result
Result Result

Testcase_01 Verify installation Apk file Should install Installed apk Pass
add app in android apk successfully
phone. successfully

Testcase_02 Verify calendar NA App should On click app Pass

functionality display showing
working. calender calender

Testcase_03 Verify working of Ignored and App should App showing Pass
report (All, Taken, take some display report all medicine
Ignored) medicine on regarding all perfectly
mentioned medicine
time

Testcase_04 Verify user able to Add medicine App should App showing Pass
add medicine for details with display successfully
timer time medicine added added alert
successfully with medicine
in listing

Testcase_05 Verify user to accept Add medicine On reminder App showing Pass
or ignored medicine for timer notification app accept and
reminder should ignore option
displayed on reminder
medicine
details with
accept or
ignored option.

Testcase_06 Verify app showing Add medicine Mentioned App showing Pass
notification on for reminder time app notification
entered timing. should display reminder with
notification alarm tones
reminder
7.1.4 Integration Testing
Integration testing is a software testing methodology used to test individual
software components or units of code to verify interaction between various
software components and detect interface defects. Components are tested as a
single group or organized in an iterative manner. After the integration testing
has been performed on the components, they are readily available for system
testing.

7.1.5 User Acceptance Testing

User acceptance testing of the system is the key factor for the success of any
system. A system under consideration is tested for user acceptance by
constantly keeping in touch with the prospective system at the time of
development and making changes whenever required. This
is done with regard to the input screen design and output screen design. Here we
will test whether the proposed system has a well-defined UI so that the citizens
can interface the application more easily.

7.1.6 Functional Testing

Functional testing is a technique in which all the functionalities of the program
are tested to check whether all the functions that were proposed during the
planning phase are fully fulfilled. This is also to check that all the functions
proposed are working properly. This is further done in two phases One before
the integration to see if all the unit components work properly. Second to see if
they still work properly after they have been integrated to check if some
functional compatibility issues arise.
 Chapter 8

Result Analysis
Here is a type of medicine
Taken medicine shown
Here is a ignored medicine
Ignored and Taken medicine shown in All Medicine
Here is a all stats
Here is a medicine alert
 Chapter 9

Conclusion and Future Work

9.1 Conclusion
Now days, using smart phones and mobile applications are
increased dramatically, so developing mobile applications in health services can
create the desired effect in the community. Although there are various
medication reminder mobile applications a native mobile application is essential
that is developed on the basis of the specialist’s ideas in the field. In addition to
remind the medication administration time and dose, while Existence of these
functions in the medication reminder mobile application prevents medication
errors by patients and increases medication adherence.

Undoubtedly Medicine reminder app can play an important role in patient

health to improvement with the suitable friendly interfaces, data processing,
correct calculation of formulas and appropriate responds, the display of the
medication pictures and descriptions. Therefore, we suggest that health care
providers increase patient’s awareness and introduce them medication reminder
mobile applications to promote these applications utilization and to improve
medication adherence as well as decreasing medication errors.

The patients will get the schedule of medicine in-take time with medicine
description, starting and ending date of medicine, notification through automatic
alarm ringing system and navigation system.

9.2 Future work

For the Future work we had decided that we will add the fitness
feature in application so that it will keep a track the patient or a user had done
the exercise or how many steps he had walked.