KAVACH

Project Report

Submitted in Partial Fulfillment of the Requirements for the Degree of

BACHELOR OF TECHNOLOGY

In
COMPUTER SCIENCE & ENGINEERING

By

Pooja Saini (2100950100057)

Prachi Singh (2100950100058)

Sasmita Pallai (2100950100073)

Tannu Kumari (2100950100085)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

MGM’s College of Engineering & Technology, Noida

May 2025
 TABLE OF CONTENTS Page No.
CERTIFICATE......................................................................................................................i
DECLARATION...................................................................................................................ii
ACKNOWLEDGEMENT.....................................................................................................iii
ABSTRACT...........................................................................................................................v
LIST OF TABLES.................................................................................................................vii
LIST OF FIGURES...............................................................................................................viii
LIST OF SYMBOLS.............................................................................................................ix
LIST OF ABBREVIATIONS.................................................................................................x
CHAPTER 1 (INTRODUCTION)
1.1. Literature review.......................................................................................................1
1.1.1. Gaps in Literature..................................................................................................5
1.2. Problem definition.....................................................................................................6
1.3. Brief introduction of the project................................................................................7
1.4. Proposed modules….................................................................................................8
1.5. Hardware & Software requirements…......................................................................9
CHAPTER 2 (SYSTEMS ANALYSIS AND SPECIFICATION)
2.1. A functional model...................................................................................................10
2.2. A data model
2.2.1 ER Diagram.......................................................................................................11
2.3. A process-flow model.................................................................................................13
2.3.1 DFD
[Link]. DFD Level 0..........................................................................................14
[Link]. DFD Level 1..........................................................................................15
2.4. A behavioral model.....................................................................................................16
2.4.1. Sequence Diagram.............................................................................................17
2.4.2. Class Diagram....................................................................................................18
2.4.3. Activity Diagram................................................................................................20
2.4.4. Flow diagram......................................................................................................22
[Link]. Find Current Location............................................................................23
[Link]. Track Current Location.........................................................................24
2.5. System Design
2.5.1 Technical feasibility.............................................................................................26
2.5.2 Operational feasibility..........................................................................................27
2.5.3 Economic feasibility............................................................................................28
 CERTIFICATE

This is to certify that Project Report entitled “KAVACH” which is submitted by Pooja
Saini(2100950100057), Prachi Singh(2100950100058), Sasmita Pallai(2100950100073), Tannu
Kumari(2100950100085) in partial fulfillment of the requirement for the award of degree B.
Tech. in Department of Computer Science and Engineering of MGM’s College of Engineering
and Technology which is affiliated by AKTU Lucknow, is a record of the candidate’s own work
carried out by him/her under my supervision. The matter embodied in this report is original and
has not been submitted for the award of any other degree.

Date: Supervisor Signature

Name of Supervisor: Mrs. Karamjeet Kaur

Designation: Head of Department (CSE)

 DECLARATION

I hereby declare that this submission is my own work and that, to the best of my
knowledge and belief, it contains no material previously published or written by another
person nor material which to a substantial extent has been accepted for the award of any
other degree or diploma of the university or other institute of higher learning, except
where due acknowledgment has been made in the text.

Signature:

Name of Student: Pooja Saini

Roll No.: 2100950100057

Date:

Signature:

Name of Student: Prachi Singh

Roll No.: 2100950100058

Date

Signature:

Name of Student: Sasmita Pallai

Roll No.: 2100950100073

Date

Signature:

Name of Student: Tannu Kumari

Roll No.: 2100950100085

Date:
 ACKNOWLEDGEMENT

It gives us a great sense of pleasure to present the report of the B. Tech Project undertaken during
B. Tech. Final Year. We owe special debt of gratitude to Karamjeet Kaur Department of
Computer Science & Engineering, MGM’s College of Engineering and Technology, Noida for
his/her constant support and guidance throughout the course of our work. His/her sincerity,
thoroughness and perseverance have been a constant source of inspiration for us. It is only
his/her cognizant efforts that our endeavors have seen light of the day.

We also take the opportunity to acknowledge the contribution of Mrs. Karamjeet Kaur Head,
Department of Computer Science & Engineering, MGM’s College of Engineering and
Technology, Noida for his/her full support and assistance during the development of the project.

We also do not like to miss the opportunity to acknowledge the contribution of all faculty
members of the department for their kind assistance and cooperation during the development of
our project. Last but not the least, we acknowledge our friends for their contribution in the
completion of the project.

Signature: Date:

Name :Pooja Saini

Roll No.: 2100950100057

Signature:

Name: Prachi Singh

Roll No.: 2100950100057

Signature:

Name: Sasmita Pallai

Roll No.: 2100950100073

Signature:

Name: Tannu Kumari

Roll No.: 2100950100085

 ABSTRACT

Kavach is not merely a safety platform; it embodies a movement towards empowerment and
equality. By leveraging the latest advancements in technology, KAVACH pioneers a new era in
women's safety, where access to assistance and support is just a tap away. Its user-friendly
interface and innovative features redefine the way women perceive and navigate safety in their
daily lives. At the core of Kavach is a commitment to inclusivity and accessibility. Whether in
urban centers or remote areas, Kavach ensures that every woman, regardless of her background
or circumstances, has access to the tools and resources needed to feel secure and empowered.,
Kavach goes beyond the realm of technology to cultivate a sense of belonging and empowerment
among its users. Kavach fosters meaningful connections and empowers women to advocate for
their safety and well-being. By amplifying voices and sharing experiences, Kavach creates a
supportive ecosystem where women can learn from each other, find solidarity, and effect positive
change in their communities. In a world where women continue to face myriad challenges and
threats to their safety, Kavach serves as a beacon of hope and resilience. It is more than just a
platform; it is a movement that empowers women to reclaim their autonomy and live life on their
own terms.

It is said, your security is in your own hands, and this is what “Kavach” safety app enables you
to do. There are times when you anticipate that help might be required e.g. while walking alone
through a forlorn place. The app can come handy in situations like these.“Kavach” is a Women
safety app which allows the user to store up to immediate help numbers. The user is required to
activate the application. Once activated the service will run continuously in the background. The
moment the user press panic button on the device, the application sends an emergency SMS
containing the Location information along with nearby Police-Station information to the
respective emergency mobile numbers configured for help.
KAVACH is a comprehensive women's safety app designed for Women but will include every
person of the society to provide a secure and supportive environment for women to live, work,
and thrive. An app that provides a platform for people to express their thoughts, feelings, and
problems can be very helpful. This app can be especially helpful for those who struggle to talk to
their parents or others about their feelings and problems. It provides a safe and non-judgmental
space for users
to express themselves and work through their thoughts and emotions. This safety app is also
available in different language so , that it can be understand by other .
This app provide a platform for those who can not share their feeling , emotion etc. with their
close once can express their feelings in this app. So, that in case of emergency this data can be
share with the close once and with police. This app also provides the safety tips and and also
educate the young member of the society regarding the good touch and the bad touch.
 List of Figures

Sr. No. Figure Number Figure name Page Number

1 2.1 ER Diagram 11
2 2.2. DFD Level 0 13
3 2.3 DFD Level 1 14
4 2.4 Sequence Diagram 17
5 2.5 Class Diagram 18
6 2.6 Activity Diagram 20
7 2.7 Find Current Location 23
8 2.8 Track Current Location 24
 LIST OF SYMBOLS

[] Integer value

- Hyphen

() Integer value

: Colon

_ Optical distance

, Comma

/ Slash

“” Inverted commas

’ Apostrophe

; Semi colon
 LIST OF ABBREVIATIONS

DFD Data flow Diagram

ER Entity Relationship

API Application Programing Interface

MSG Messages
 CHAPTER 1

Introduction

KAVACH is a comprehensive women's safety app designed to create a secure and supportive
environment for women, while also being accessible to every individual in society. The app
offers a range of features aimed at preventing, responding to, and recovering from safety threats,
such as harassment, violence, or other emergencies. With real-time SOS alerts, location tracking,
mental health support, and direct integration with authorities, KAVACH provides immediate
assistance while empowering users through safety education and community support. The app's
user-friendly interface makes it accessible to individuals of all technical abilities, ensuring that
everyone can benefit from its features, including women, men, senior citizens, and students. By
combining advanced technology with a focus on holistic well-being, KAVACH aims to promote
safety and security for all.

1.1 Literature Review

In this paper “A Mobile Application for Women's Safety: WoSApp” Author: Dhruv Chand, Sunil
Nayak et al., (2015)[1] -This paper introduces a mobile application known as WoSApp (Women's
Safety App) that gives ladies with a reliable thanks to place associate emergency decision to the police.
The user will quickly and discreetly trigger the vocation perform by shaking her phone or by expressly
interacting with the application's program via a straightforward press of a push button on the screen. A
message containing the geographical location of the user, additionally as contact details of a pre-
selected list of emergency contacts, is instantly sent to the police. This paper describes the applying, its
development, and its technical implementation. Need for Women’s Safety Apps: Discuss the socio-
cultural and safety challenges that women face globally, including harassment, assault, and violence.
Highlight the increase in safety concerns that has driven the demand for digital solutions. Some safety
apps provide community support where women can report incidents, access resources, and receive
support.

1
“Abhaya” Author: Ravi Sekhar Yarrabothu, Bramarambika Thota (2015)[2] - This paper presents
Abhaya, associate automaton Application for the security of girls, and this app may be activated by one
click whenever the requirement arises. One click on this app identifies the place's location through GPS.
It sends a message comprising this location uniform resource locator to the registered contacts and calls
on the primary registered contact to assist in dangerous things. The distinctive feature of this application
is to send the message to the registered contacts ceaselessly for each 5 minutes till the "stop" button
within the application is clicked. Continuous location trailing info via SMS helps realize the victim's
location quickly and may be saved safely.

“Mobile-based ladies Protection System” Author: Vallidevi Krishnamurthy, Saranya. S et al.

(2015)[3] A hands-free and internet-free automaton application to assist ladies throughout threatening
things has been developed. the assistance request containing the user's (woman in danger) GPS
coordinates are then forwarded to a network of emergency contacts and police management rooms via
SMS. in contrast to most mobile applications offered within the market, a voice-triggered alarm permits
the user to need facilitate quickly. As future work, the applying may be enforced on different mobile
platforms like iOS and Windows for a wider reach. tho' the applying is primarily meant for ladies, it's
not restricted completely for them and may be utilized by males, females, and children alike.

“Woman Safety Application – MwithU” Author: Abhijeet Singh, Vishnu Barodiya. (2018)[4] Our
application is basically a web based technology so the system requirement is very low for the
application. And as the main data exchange will be happening mostly through geolocation API so low
network speed will also work. MwithU’s requirement for functioning is kept to be low as that it can be
used in almost all the parts of the world with low end devices and weak internet connections. We at start
are mainly focusing on two types of application.

“Android App for Women Safety” Author: Dr. K Srinivas, Dr. Suwarna Gothane et al. (2021)[5]-
This app is developed by AppSoftIndia. The key features of the app are: the user has to save some
details. These details include: Email address andpassword of the user, Email address and mobile number
of the recipient and a text message. Then, app is loaded as a “widget”, so that when the user touches the
app, it alerts the recipient. Another key feature of app is that it records the voice of surroundings for
about 45 seconds and this recorded voice, text message containing location coordinates of the user is
sent to the recipient mobile number.
2
“An Android Based Women Safety App” Author: Manisha Sharma, Akhil Bansal (2022)[6]-
This android application. This will alert the nearby people who having this application by sending
alert messages to them and alert sound in the guardian mobile on shaking of victim mobile. Also
sends messages and alert sound to the saved contacts in the application and police station. Which
also show the location of the victim with the help of GPS tracker system. Which also make sound in
guardian mobile when his/her mobile in silent [Link] this app we can also add as many contacts as
we can.

“Stay Safe” Mr. Indrajeet A. Mane, Miss. Jyotsna R. Babar et al. (2020)[7]-Stay Safe Application
is an innovative safety application for women, senior citizens and anyone who needs assistance in an
urgent situation. This project focuses on providing security to users which includes location-based
services, SMS services, GPS services and system Architecture, provide useful evidences. Since the
system can capture image of incidences which can act as the evidences. This is the “Stay Safe App”
which is very useful application mainly for girl’s safety. When we feel that we are in emergency
situation, for example, travelling alone at night time we can use this application. So that on one click we
can send our location to our family members and to any police stations. So, once we click on activate
button it continuously sends updated locations messages to all authorized persons. So, this application is
having both safety and security which needs the engineering code of conduct which is essential in the
today’s world.

“Advanced women security app: We’RSafe” Author: Tanusri Dey, Upama Bhattacharjee et al.
(2022)[8] - The phrase “Violence against women” is a technical term used to collectively refer to acts
that are primarily or exclusively committed against women to harm them. Woman security is a critical
issue and it is much needed for every individual to act over such issue to safeguard them. When safety
and security is concerned, a smart phone can become a powerful tool to prevent violence against
women. Keeping this in mind, an android app has been developed which is dedicated to provide relief to
the person in trouble. By clicking on a button (provided on the app) alert message is sent to the user’s
already saved contacts. The application shares the user’s location with the registered contacts in the form
of message. The application has other key features like “Alarming neighbours by loud noise”,
“AutoDialing”, “Finding location of nearby police station and hospitals”.

3
“LifeCraft” Author: R. R. Khandoker, S. Khondaker et al. (2019)[9] -Women have ensured the
stability, progress and long-term development of the nations throughout the history. If women are
subjected to violence and harassment, they cannot be genuinely included in society. With increasing
heinous incidents involving women and children, an advanced system is needed to serve the purpose of
getting help as soon as possible. At present time, the use of smartphones has increased rapidly, making it
possible to use a smartphone efficiently for security or other protective purposes. All the recent atrocious
incidents have made us think about to go for the safety issues. The crimes against women can be
minimized with the help of our application “LifeCraft”. It is an application for android for women’s
safety though men can also use it at a distress situation. It can be activated by voice command or SOS
key. An alert message with location is sent to the user defined numbers in every five minutes until the
system is turned off. Many cases remain mysterious due to insufficient evidence. So, we have kept audio
recording option to keep evidence. Continuous location tracking, showing the victim safe zone, offline
mode is some of the most useful features of this system.

“An Implementation and Efficient Way” Author: Mr. Kalyan D Bamane, Nelofer kousar et al.
(2018)[10] - Safety for women is one of the most pressing issues of our time that should have been a
fundamental, undeniable concept for any civilized society centuries ago. Denying fundamental rights to
safety, personal choices, freedom to pursue, whatever lifestyle they wish to, sexual and physical
empowerment are not new issues – but have strangely not managed to be eradicated even in today’s
times. This is a privacy security app having troop of features; GPS tracking, emergency & important
contact numbers, directions to safe locations, pins displaying danger zone area and a Safety Score. It
drives in advance of exemplary women safety apps, and presents a vast range of features, so that, they
will help to practically plan and can give a counter attack to those spots in the locality. When a person is
moving to a new locality that is unknown to her and if she needs to know the safe areas, then this app
will be much helpful, providing the user, a map-based view of the locality along with its safety score

4
1.1.1 Gaps in Literature

While the mention applications have introduced useful tools for improving women’s safety, several
limitations persist across current solutions:

Real-Time Response Deficiency: Many existing applications focus on alert systems that rely on
delayed police responses or notifications to contacts, without guaranteeing immediate assistance. Apps
often fail to ensure real-time tracking and coordination, which delays intervention.

Complex User Interfaces: Current apps, though well-intentioned, often feature complex interfaces that
limit their accessibility to users, especially those in rural or underdeveloped areas with lower
technological literacy.

Lack of Integration with Authorities: The coordination between safety apps and local law
enforcement remains weak, often delaying help or making the app less effective during emergencies.
There is a need for a more direct and integrated approach to ensure faster action.

Limited Mental Health Support: Few apps address the emotional and psychological trauma women
face following a safety incident. Providing immediate support in the form of access to counselors and
resources is essential but missing from many existing apps.

Specialized, Non-Comprehensive Solutions: Many apps focus on isolated functions—either incident

reporting, location sharing, or emergency alerts—but fail to offer a full range of safety- related features,
such as self-defense education or community-building resources.

Lack of Anonymity: Reporting incidents can be intimidating, especially when there is a lack of
anonymity. Many current apps do not provide anonymous reporting options, which can deter victims
from seeking help.

5
Cultural Sensitivity in Design and Functionality: Language and Localization: Effective safety apps
need to be available in multiple languages and dialects, especially in countries with high linguistic
diversity. Localized language settings, including regional terms or emergency phrases, can make the app
more accessible and usable.

6
1.2 Problem Definition

Despite significant advancements in technology, women's safety remains a critical concern globally. The
lack of accessible, comprehensive, and effective tools to prevent, respond to, and recover from
harassment, violence, and other safety threats exacerbates the problem. Current solutions, such as
mobile safety apps, often have limitations, including:
Inadequate Emergency Response Systems: Many existing apps rely on delayed emergency
notifications or response times, failing to provide real-time assistance when it is most urgently needed.
Limited Accessibility and User Friendliness: Complex interfaces and the reliance on advanced
technological literacy make many apps inaccessible to a wide range of users, particularly those in rural
or underserved areas.

Ineffective Incident Reporting Mechanisms: Reporting incidents can be cumbersome or intimidating,

often lacking anonymity, which discourages women from reporting incidents, especially in sensitive
situations.

Lack of Comprehensive Features: Existing apps typically focus on isolated functions such as sending
an alert or sharing a location, without addressing the broader needs of safety, such as mental health
support, community-building, or self-defense education.
Insufficient Support Networks: Many solutions do not provide sufficient access to support networks or
the ability to easily connect with local authorities or guardians, leaving women vulnerable and
unsupported in critical moments.

7
1.3 Brief introduction
KAVACH is a comprehensive women's safety app designed for Women but will include every person
of the society to provide a secure and supportive environment for women to live, work, and thrive. An
app that provides a platform for people to express their thoughts, feelings, and problems can be very
helpful. The offline mode feature ensures that users can access the app's features. This app can be
especially helpful for those who struggle to talk to their parents or others about their feelings and
problems. It provides a safe and non-judgmental space for users to express themselves and work through
their thoughts and emotions

1.4 Proposed Modules of the KAVACH Project

The KAVACH app is designed with several key modules that work together to ensure user safety,
provide real-time assistance, and offer holistic support. Each module plays a specific role in fulfilling
the app's objectives, ensuring a comprehensive safety experience for users.

User Registration and Profile Management: This module allows users to create and manage their
accounts by entering basic personal details and emergency contact information. It includes the option to
update profile information and configure trusted contacts. Users can customize settings, such as
notification preferences and privacy controls.

SOS Emergency Alert System: The core safety feature of the app, enabling users to send SOS alerts in
emergencies with a single tap. Instantly sends real-time alerts to pre-selected emergency contacts,
including their live location. Integrates with local authorities or law enforcement for immediate
assistance.
Real-Time Location Sharing: This module continuously tracks and shares the user’s live location with
their trusted contacts during an emergency or when the user feels unsafe. It also offers periodic check-
ins and location sharing options, allowing users to update their location at specific intervals.
Anonymous Reporting: Enables users to report incidents anonymously to local authorities or trusted
contacts, ensuring privacy and encouraging victims to report safety threats without fear of

8
exposure. Users can submit detailed incident reports with the option to include media such as photos,
videos, or audio recordings.

Self-Defense and Safety Education: This module provides users with safety tips, self-defense tutorials,
and awareness materials designed to educate and empower them. Includes video tutorials, articles, and
infographics that focus on physical and digital safety. Users can also participate in safety-related quizzes
and activities to stay informed.

Guardian Mode: A feature that allows trusted contacts (guardians) to track the user’s location in real
time when activated. Guardians can receive alerts and updates in emergency situations, including live
tracking of the user's movements.

Integration with Local Authorities: Direct communication with law enforcement or emergency
services via an integrated system that can relay real-time location data and incident details. Facilitates
quick response from local authorities during emergencies.

Notifications and Alerts: Provides customizable alert settings for notifications, including safety
warnings, community safety updates, or notifications of nearby threats. Allows users to configure when
and how they receive alerts, including silent alerts during emergencies.
Community Support and Forum: A dedicated space where users can connect with others in their
community, share safety tips, and discuss safety concerns. Facilitates peer-to-peer support and
information sharing to foster a safer community environment.
Admin Dashboard and Analytics: Provides app administrators with access to user data, incident
reports, and location analytics for better management and decision-making. Helps monitor user activity,
improve app performance, and ensure compliance with security protocols.

9
 1.5 Hardware and Software requirements

1. Hardware Requirements :
RAM : 4GB minimum or more2. Processor : Intel i3 minimum or more3.

Storage : SSD with at 128 GB

Network: Ethernet / Wi-Fi capacity

2. Software Requirements:
Android Studio: The main IDE used for developing the W-Safe Android application.
Java / XML: Programming and markup languages used to develop the frontend and application logic.
For backend services: Firebase was integrated to manage essential features. It provided a real-time
database to store user and guardian information, handled authentication processes such as login and
registration, and enabled cloud messaging for sending critical alerts.
Google Maps API: Integrated for real-time location tracking and sharing location with guardians.
Firebase Cloud Messaging (FCM): Used to send notifications to guardians during emergencies.

10
 CHAPTER 2

2.1 FUNCTION MODEL

It describes function the function of internal processes with the help of DFDs. DFD is the graphically
representation of data. It shows the input, output and processing of the system. When we are trying to
create our own business, websites, system, project then there is need to find out how information passes
from one process to another so we all are done by DFD. A function model is a graphical representation
of a system'sfunction within a defined scope. The purposes of the function model are to describe the
functions and processes, assist with discovery of information needs, help identify opportunities, and
establish a basis for determining product and service costs. A function model, similar with the activity
model or process model, is a graphical representation of an enterprise's function within a defined scope.
The purposes of the function model are to describe the functions and processes, assist with discovery of
information needs, help identify opportunities, and establish a basis for determining product and service
costs.

2.2 DATA MODEL

Data models are visual representations of an enterprise’s data elements and connections between them.
By helping to define and structure data in the context of relevant processes, models support the
development of effective information systems. Data models play a key role in bringing together all
segments of an enterprise-IT, business analysis, management and others-to cooperatively design
information systems (and the databases they rely on). These systems require properly defined and
formulated data, and models shine a clear light on what data is required and how it must be structured to
support the desired business processes. By explicitly determining the structure of our data, these models
support a variety of use cases, including database modelling, information system design, and process
different types of data models. Each will serve a different purpose as you work through the data
modeling process.

11
2.2.1ER Diagram

Entity-Relationship Data Model: An ER model is the logical representation of data as objects and
relationships among them. These objects are known as entities, and relationship is an association among
these entities. This model was designed by Peter Chen and published in 1976 paper. It was widely used
in database designing. A set of attributes describe the entities. A set of the same type of entities is known
as an Entity set, and the set of the same type of relationships is known as relationship set.

Figure 2.1 : ER Diagram

12
In this ER Diagram the user first access the system interface by doing Login on the platform. User can
create their password for authentication. They can choose the different options like SOS Key, Send msg
Alert Button and any of them to perform the action in case of emergency and the stored data will be
shared to the government security centers and the closed relatives saved in the contacts.
User attributes :- user id, user address, user name and user phone number and email optional. System
attributes :- SOS key, Message Sender and app Id.
Police attributes:- Location Decoder, Fast Action Team, Emergency Team and Emergency Request
Id.

2.3 PROCESS-FLOW MODEL

Work flow:-In general workflow refers to the series of sequential tasks those are performed to achieve
certain goal. Each workflow step is defined by three parameters i.e. input, transformation and output. In
workflow process a series of actions are performed to achieve a business outcome. Software-Process:-
Workflows Software process is the set of related activities those are performed to get a software product
as an outcome and there the software process workflows leads the software development in the a linear
way by performing series of sequential tasks. Process flow diagrams allows you and your team to see
each task that comes next, must finish in order to reach a goal. Although their original purpose was
industrial Process flowcharts and engineering are becoming essential tools for corporate projects
oversight. Additionally, it's a set of actions you take with your group to fulfill your aim. Visualizing
Using your process flows, you can find unnecessary steps, repetitive tasks, and bottlenecks.

2.3.1 Data Flow Diagram

In Software Engineering DFD (data flow diagram) can be drawn to represent the system of different
levels of abstraction. Higher-level DFDs are partitioned into low levels-hacking more information and
functional elements. Levels in DFD are numbered 0,1 or beyond. Here, we will see mainly 2 levels in
the data flow diagram, which are: 0-level DFD and 1-level DFD.

13
[Link] Level -0 DFD/Context Diagram
It is also known as a context diagram. It’s designed to be an abstraction view, showing the system as a
single process with its relationship to external entities. It represents the entire system as a single bubble
with input and output data indicated by incoming/outgoing arrows. In Level 0, represent the entire
system as a single process and show its interactions with external entities.
Components:-Process: Kavach ( Safety App)
External Entities: User: The woman using the app, Help provided by:- Police, Friends and Family
(Contacts the user can notify)

Figure 2.2 :DFD level 0

Data Flow Diagrams for a safety app involves breaking down its functionalities into clear processes. In
the Level 0 DFD, the app is represented as a single entity called "Kavach (Safety App)" interacting with
two main external entities: the User, help provided . The User interacts with the app by sending requests
for help and sharing their location. In response, the app alerts Emergency Services with the user's
location and sends notifications to the user's chosen contacts, ensuring immediate assistance.

[Link] Level-1 Data Flow Diagram

In 1-level DFD, the context diagram is decomposed into multiple bubbles/processes. In this level, we
highlight the main functions of the system and breakdown the high-level process of 0-level DFD into
subprocesses. Each sub-process is depicted as a separate process on the level 1 DFD. The data flows
and data stores associated with each sub-process are also shown. Level 1 DFD

14
depicts basic modules in the system and flow of data among various modules. It also mentions basic
processes and sources of information.

Figure 2.3 :DFD level 1

we can break down the main process into several subprocesses to provide a more detailed view of the
app's internal workings. These subprocesses include User Registration/Login, calling/message, SOS,
Contact Notifications.
The User starts by registering or logging into the app, creating a user profile that is central to the system.
When the User activates an emergency alert, the system processes this request, triggers the alert to
Emergency Services, and prompts the location-sharing process to send the user's precise location.
Additionally, the app can notify designated Friends and Family members, ensuring they

15
receive a distress message. Each of these subprocesses communicates with one another, illustrating how
the app coordinates to enhance user safety effectively.
This structured approach helps visualize how the app operates and ensures that users have a reliable
safety tool at their fingertips.

16
2.4 BEHAVIORAL MODEL
The purpose of the behavioral model is to help us understand platform behavior and the factors that
affect it. A diagram is used to explain and illustrate the behavior of a platform or system. We refer to
this diagram as the state transition diagram. It is a synthesis of conditions and occurrences. It typically
explains the general states that a system may be in as well as the circumstances that lead to a system's
state changing. Thus, in response to a certain event, a state transition diagram is used to illustrate the
necessary course of action. Businesses use behavioral modeling as a tool to better understand and
forecast customer behavior. Utilizing current consumer and company expenditure data, behavioral
modeling projects future behavior in particular circumstances. Developers and businesses also employ it
as a strategy to better comprehend and forecast customer behavior. Utilizing current consumer and
company expenditure data, behavioral modeling projects future behavior under particular conditions.
Behavioral modeling is used by financial institution to estimate the risk associated with providing funds
to an individual or business and by marketing firms to target advertising. Behavioral modeling attempts
to explain why an individual makes a decisions and the model is then used to help predict future
behavior. Companies use behavioral modeling to target offers and advertising to customers.

2.4.1 Sequence Diagram

A sequence diagram is the most commonly used interaction diagram. Interaction diagram is used to
show the interactive behavior of a system. Since visualizing the interactions in a system can be
cumbersome task, we use different types of interaction diagrams to illustrate the various features of the
application module. It is showing the sequence if our application that first user logged in, then place
order and make the payment. A sequence diagram is a type of interaction diagram used in software
engineering and systems design to visually represent how objects or components interact with each other
over time to accomplish a specific task or process. It is a part of the Unified Modeling Language (UML)
and is commonly used to document the flow of control and data among objects, components, or
subsystems in a system. Actors and Objects: Represented as boxes at the top of the diagram, these can
be users, components, or systems.

17
Figure 2.4 : Sequence Diagram

18
2.4.2 Class Diagram
Class diagrams are a type of UML (Unified Modeling Language) diagram used in software engineering
to visually represent the structure and relationships of classes within a system i.e. used to construct and

visualize object-oriented systems.

Figure 2.5 : Class Diagram

19
Class diagrams provide a high-level overview of a system’s design, helping to communicate and
document the structure of the software. They are a fundamental tool in object-oriented design and play a
crucial role in the software development lifecycle.
This class diagram illustrates a personal safety and location tracking system with core entities like User,
Account, Location, and Profile. The User entity manages personal details, authentication, and location
tracking. Accounts hold account data, including emergency contacts and a registration method. Location
stores current and frequent locations, offering tracking features, while Profile keeps user profile
information. Supporting entities include Friends/Relatives and Emergency List for emergency contacts,
Contacts for general contact management, SMS for messaging, Alert for location-based danger
notifications, G_maps for Google Maps integration, and My_DB_helper for database operations.
Relationships connect User to Account and Location, facilitating data flow and system functionality

20
2.4.3 Activity Diagram
We use activity diagram to illustrate the flow of control in a system and refer to the steps involved in the
execution of a use case. Activity diagrams are used to model both concurrent and sequential activities.
Thus, we essentially focuses’ on condition of flow and the sequence in which it happens. An activity
diagram shows the software functions as a series of steps. Activity diagrams are used to record the
execution of system activities, as well as to characterize business processes and use cases

Figure 2.6 :Activity Diagram

21
The activity diagram for a women safety app visually outlines the user interactions and flow of activities
within the application. It begins with the "Start" node, indicating that the user has opened the app. The
first significant step involves user authentication, where the user is prompted to either register if they are
new or log in if they already have an account. This ensures that only authorized individuals can access
the app’s features. Once authenticated, the user is directed to the main menu, which offers several
options: activating an emergency alert, sharing their location, managing contacts, and viewing their
profile.
If the user selects the option to activate an emergency alert, the app performs several critical actions,
such as sending an alert to Emergency Services, sharing the user's real-time location, and notifying pre-
selected friends or family members. This feature is crucial for providing immediate assistance in
emergencies. Additionally, users can opt to share their location independently, ensuring that emergency
contacts or services can locate them quickly. The option to manage contacts allows users to add or
modify emergency contacts, which is vital for effective communication during a crisis. They can also
view and update their profile information to ensure that all data is current.
The diagram concludes with an "End" node, indicating that users can log out or close the app, thus
ending their session. This structured flow emphasizes the app's primary goal of enhancing user safety
through efficient emergency response features. Overall, the activity diagram not only provides clarity on
user interactions but also serves as a valuable tool for improving user experience, analyzing
requirements, and facilitating communication among the development team.

22
2.4.4 FLOW DIAGRAM
Flowcharts are the visual representations of an algorithm or a process. Flowcharts use symbols/shapes
like arrows, rectangles, and diamonds to properly explain the sequence of steps involved in the
algorithm or process. Flowcharts have their use cases in various fields such as software development,

business process modelling, and engineering.

[Link] Find Current Location

Where are you? Your Friend is out somewhere for a late night party . How could you check where is
that respective person? Where are you features allows the user to see the recent location of the friends
and family when needed without disturbing the person being tracked.
While first request is send by the user. The user will have to select the “Where Are You” icon and then
dialog box of “Pick your Close Friend” will open up. The sender could select anyone from the Close
Friend list and the request will be sent to the receiver. The receiver will accept that request from their
end and a message will be sent to the receiver with the present location of the sender.

23
Figure 2.7:Find current location

24
[Link] Flow Diagram of Track current Location

Figure 2.8 : Track current location

25
Track Me: The track me feature allows the user to view the exact dynamic location of the victim using
the application on that time.
User needs to send the request first to track at the receiver end .

Friends List : This list shows all the contact numbers of family and friends which are added by the user
through contacts. This could be done by selecting the contact icon on the bottom right corner of the
friends list.

26
2.5 SYSTEM DESIGN
2.5.1 Technical Feasibility
This refers to whether the app can be built with existing technology and [Link] Aspects to
Consider:

Platform Compatibility: The app should be developed for both Android and iOS to maximize reach.
Cross-platform frameworks like React Native and flutter could be used to save development time.

Location Tracking: GPS: The app should make use of real-time GPS tracking for location-based
features like emergency alerts and routing. This will require integrating reliable GPS services (e.g.,
Google Maps API, Apple Maps).

Real-Time Communication: The app should allow real-time communication between the user and
emergency responders or trusted contacts. This requires integrating real-time communication tools
(Firebase).

Push Notifications: Implementing push notifications is crucial for alerting users and their emergency
contacts. Services like Firebase Cloud Messaging (FCM) or One Signal are commonly used for this
purpose

Data Security & Privacy: Protecting sensitive user data is essential. The app must comply with global
privacy laws and should be implemented to protect user data.

Battery Efficiency: Continuous location tracking and emergency alerts can drain the battery. Efficient
algorithms that optimize battery usage will be required. Options like low-energy GPS or periodic
location updates can help minimize power consumption.

Offline Functionality: Some features (like sending pre-set emergency messages) should work offline if
there's no network connectivity. Using SMS as a fallback for emergency alerts in low connectivity
situations could be essential. Conclusion: Technically, the app is highly feasible with current
technology. The challenges mainly lie in ensuring real-time, reliable communication, minimizing battery
drain, and protecting user data.
27
2.5.2 Operational Feasibility
This assesses whether the app can be successfully integrated and sustained in real-world conditions. Key
Aspects to Consider:

User Experience (UX) Design: The app must be intuitive, easy to use, and quick to navigate. In high-
stress situations, users should be able to activate emergency features with just a few taps. The UI should
also be accessible (e.g., larger fonts, colour contrast for visibility).

Data Management: The app will need to handle significant amounts of data from users, including
location data, user profiles, and communication logs. Implementing robust cloud storage solutions (e.g.,
AWS, Google Cloud) will help scale operations.

Support Infrastructure: For emergency response features, you may need to partner with local law
enforcement agencies, ambulance services, and NGOs. You must establish protocols for how to handle
alerts and coordinate responses.

Customer Support: Offer support channels (help instruction and direct support lines) users issues with
the app. This ensures smooth onboarding and helps users feel confident using the app in emergencies.

Training & Awareness: Operational success will depend on awareness campaigns and training
programs. Users need to know how to use the app and what features to trust. Educational content (like
videos, tutorials) within the app can be helpful.

2.5.3 Economic Feasibility

This evaluates whether the app can be built, scaled, and sustained financially. Key Aspects to
Consider:

Development Costs: Initial costs include development (for iOS, Android, and backend systems), UX/UI
design, testing, and security integration. Depending on complexity, initial development.

Cloud Hosting: Hosting and storage costs for user data, especially GPS data, could be significant.
Services like AWS or Google Cloud offer scalable storage but at a recurring cost.

28
Push Notifications: If using third-party services like Firebase, there may be costs associated with high-
volume notifications or real-time data syncing.

Maintenance: Regular updates and bug fixes will require ongoing investment. This will involve
developer costs, UI/UX improvements, and potential customer support. Women’s safety is a growing
concern globally, and there is a significant potential market. The app could appeal to women in urban
areas, travellers, students, and those in high-risk environments. According to a Statista report, the global
market for safety apps is projected to grow steadily, making this a promising venture.

Monetization Challenges: While offering premium features or partnering with government and
corporate organizations can generate revenue, monetization should be handled carefully to avoid
alienating users, especially if the core safety features become paywalled.
Conclusion: The economic feasibility of the app depends on finding a sustainable balance between
initial development costs, operational expenses, and ongoing monetization strategies. It's a capital-
intensive project initially, but the market demand and possible partnerships make it financially viable in
the long term.

Final Thoughts: Designing a women’s safety app is technically, operationally, and economically
feasible. The key challenges will be ensuring reliability, creating strong partnerships for emergency
response, and balancing development costs with potential revenue. With the right planning, resources,
and execution, it could have a significant impact on improving safety and providing peace of mind to
women in various environments.

29
 CHAPTER 3
MODULE IMPLEMENTATION & SYSTEM INTEGRATION
This chapter outlines the development and seamless integration of the functional modules within the
WSafe application. Each module serves a specific purpose aimed at enhancing women's safety and
together forms a robust, interconnected safety system. The development focused on ensuring modular
functionality, user-friendliness, and high responsiveness during emergency scenarios.

3.1 MODULE IMPLEMENTATION

The WSafe application was designed with multiple interdependent modules, each implemented using
specific technologies to fulfill distinct roles. The User Authentication Module is responsible for
managing user registration and login using Firebase Authentication. It features email and password-
based sign-in, real-time form validation, and persistent user sessions to enhance usability and security.
Technologies used include Firebase Authentication, Java, and Android SDK.

The Emergency Alert Module (SOS) is the core safety feature of the app. It allows users to send
instant alert messages with real-time GPS locations to registered emergency contacts by tapping a single
SOS button. The module, implemented using Android’s SMS Manager and LocationManager API, can
function even offline, leveraging the device’s native messaging capabilities. It operates under high-
priority permissions to access location and SMS functionalities efficiently.

The Real-Time Location Tracking Module continuously monitors the user’s geographic location and
uploads the data to Firebase Realtime Database. This location data is accessible to both emergency
contacts and administrators, ensuring constant situational awareness. Using the Google Maps API, this
module enables live tracking with periodic updates while dynamically managing location permissions
during runtime.

To manage emergency contacts, the Contact Management Module allows users to add, edit, or remove
trusted individuals. It uses Firebase Realtime Database to store contact data securely and integrates
tightly with the SOS module for dynamic alert delivery. The UI was developed to provide an intuitive
experience for contact management through basic CRUD operations.

30
The Police Station Locator Module is designed to help users identify and navigate to the nearest police
stations using Google Maps. It features automatic location detection and displays nearby stations with
options to call or navigate. Technologies like Google Places API and Google Maps SDK were used to
offer a reliable and interactive map interface for user assistance.

Finally, the Admin Panel Module is restricted to authorized personnel and enables real-time monitoring
of SOS alerts. Admins can view recent alerts, access users’ profiles, contact lists, and location data, all
stored in the Firebase Realtime Database. This ensures that authorities can act swiftly and maintain
records for future reference.

3.2 SYSTEM INTEGRATION

After the individual modules were fully developed, they were integrated into a unified, cohesive system.
The integration process focused on ensuring uninterrupted communication between components, a
consistent user interface, and streamlined data exchange across modules.

3.2.1 INTEGRATION PROCESS

The integration began with establishing secure authentication through Firebase, which connected the
login and registration systems to manage user access. Next, all critical data—such as emergency
contacts, GPS locations, and alert messages—was configured to sync with the Firebase Realtime
Database to enable smooth, real-time operations. The Google Maps and Location Services APIs were
integrated for accurate GPS tracking and for identifying nearby police stations. The SMS functionality
was connected to the contact management module to ensure that emergency alerts could be dynamically
sent to trusted contacts. Lastly, admin-level privileges were carefully configured to grant access to
sensitive information only to authorized personnel, balancing functionality with user privacy.

31
3.2.2 TESTING AND VALIDATION
Integration testing was conducted to confirm the reliability of interactions between modules. This
included validating seamless transitions between features, real-time synchronization of data, and
efficient permission handling. Special attention was given to failover scenarios, such as the absence of
internet connectivity or disabled GPS, to ensure the system could still respond appropriately. Multiple
test cases were executed to simulate emergency conditions and verify that alerts, location updates, and
user notifications functioned as intended. The overall validation process ensured a stable, secure, and
responsive application ready for deployment in real-world environments.

32
 CHAPTER 4
4. TESTING AND EVALUATION
Testing and evaluation are critical stages in the software development lifecycle, playing a crucial role in
verifying the proper functioning and requirement fulfillment of the developed system. The testing phase
encompasses a thorough examination of the system's functionality, usability, reliability, and
performance. Subsequently, the evaluation process allows both developers and stakeholders to assess the
application's overall effectiveness.

4.1 TESTING STRATEGIES EMPLOYED FOR WSAFE APPLICATION

During the development of the WSafe application, a multi-faceted approach to testing was implemented,
incorporating the following key strategies:

 Unit Testing: This involved the individual testing of each component and function within the
application to ensure their correctness. Specific modules such as user authentication, location
tracking, emergency alerts, and notification services underwent rigorous unit testing.

 Integration Testing: Following the successful completion of unit testing, the various components
were integrated and tested collectively. This phase aimed to identify and resolve any interface
defects that might arise between different modules as they interacted.

 System Testing: The complete WSafe application was subjected to comprehensive testing within an
environment closely resembling the final production setup. This involved evaluating end-to-end
workflows, including user login procedures, emergency alert triggering mechanisms, location
sharing functionalities, and the process of contacting guardians.

 User Acceptance Testing (UAT): To ensure the application met the needs and expectations of its
intended users, the WSafe application was provided to a representative group of users for testing.
Their valuable feedback was actively sought and collected to pinpoint any usability concerns and
potential areas for feature enhancements.

33
4.2 TEST CASES
Several test cases were defined for major functionalities of the system. The following table shows a
sample of test cases:

Test Case ID Description Expected Result Actual Result Status

TC01 User logs in with User is redirected Pass Success

correct credentials to home screen

TC02 User enters Display error Pass Success

incorrect message
password

TC03 Trigger Location is sent Pass Success

emergency alert and alert is
triggered

TC04 Guardian receives Guardian gets Pass Success

alert notification message and
location info

TC05 App handles lack Shows error and Pass Success

of internet retries connection

4.3 BUGFIXES
During the testing process, several bugs were identified and subsequently fixed to improve the
application's stability and reliability. One critical issue was a login crash that occurred when users
attempted to log in without entering any credentials; this has been resolved. Furthermore, the process for
sending location updates has been optimized to ensure more reliable and timely reporting. Finally, a
notification bug that prevented guardians from receiving alerts when the application was running in the
background has also been addressed, ensuring that critical notifications are consistently delivered.

34
4.4 PERFORMANCE EVALUATION
The application's performance was thoroughly evaluated across several key metrics to ensure a smooth
and efficient user experience. Response time, a crucial factor for user satisfaction, was consistently
observed to be within the range of 1 to 2 seconds for various user actions. Furthermore, resource usage,
specifically memory and CPU consumption, remained within acceptable limits even when running on
mid-range devices, indicating efficient resource management. Finally, significant attention was paid to
battery impact, and the location tracking feature was specifically optimized to minimize battery
consumption, addressing a common concern for mobile applications.

4.5 USER FEEDBACK

Feedback gathered from User Acceptance Testing (UAT) participants provided valuable insights into the
application's strengths and areas for potential improvement. Participants generally offered positive
remarks regarding the user interface, highlighting its simplicity and the application's quick
responsiveness. In terms of suggestions for future enhancements, a notable request was the addition of a
feature that would automatically trigger alerts based on predefined scenarios. Additionally, several users
requested the implementation of a night mode to improve visibility and reduce eye strain during
nighttime usage.

35
(1) Home Page View

Fig. 4.1 – HOME PAGE VIEW

(2) SMS Service View

Fig. 4.2 – SMS SERVICE VIEW

36
(3) Helplines Feature View

Fig. 4.3 – HELPLINES FEATURE VIEW

(4) Contents and Nearby Feature View

Fig. 4.4 – CONTENTS AND NEAR BY FEATURE VIEW

37
(5) Laws Feature View

Fig. 4.5 – LAWS FEATURE VIEW

(6) Law Displayer View

Fig. 4.6 – LAW DISPLAYER VIEW

38
(7) Self Defense Feature View

Fig. 4.7 – SELF DEFENSE FEATURE VIEW

(8) Panic Button View

Fig. 4.8 – PANIC BOTTON VIEW

39
 CHAPTER 5

TASK ANALYSIS AND SCHEDULE OF ACTIVITIES

5.1 TASK DECOMPOSITION
To facilitate a structured and efficient development process for the WSafe application, the entire project
was systematically broken down into a series of manageable tasks. This task decomposition strategy
allowed for improved tracking of progress, clear assignment of responsibilities, and effective scheduling
of the workload. The major components of the project were categorized into distinct phases, beginning
with Requirement Gathering, which involved a thorough understanding of the problem domain and the
identification of both user needs and essential system requirements. Following this, the System Design
phase focused on creating the application's architecture, encompassing the front-end and back-end
design, the underlying database schema, and the overall interaction flow. The Implementation phase was
further divided into several key modules, including User Authentication, Real-time Location Tracking,
the Emergency Alert Trigger System, the Guardian Notification System, and the UI Design and Front-
end Logic. Rigorous Testing was conducted through various stages, including unit testing, integration
testing, system testing, and user acceptance testing, to ensure the quality and reliability of the
application. The Deployment phase involved finalizing the application for production release, setting up
the necessary server infrastructure, and ensuring the application's scalability. Finally, comprehensive
Documentation and Report Writing were undertaken to prepare technical documentation, user
manuals, and the final project reports.

5.2 PROJECT SCHEDULE

The development schedule was organized using a Gantt chart to visualize the timeline and dependencies
of tasks. The project spanned approximately 16 weeks, structured as follows:

Week Task

1–2 Requirement Analysis & Literature Review

3–4 System Design and Architecture

5–9 Implementation Phase

10–11 Testing and Debugging

12 User Acceptance Testing

40
13 Final Optimization and Deployment

14–15 Documentation and Report Writing

16 Final Submission and Presentation

5.3 TASK SPECIFICATION

Each task was further specified in terms of:
 Goals: What the task is intended to accomplish
 Inputs: Information, resources, or tools needed
 Outputs: Expected results
 Estimated Effort: Man-hours required
 Duration: Timeline to complete
 Dependencies: Preceding tasks that must be completed first

Here is a breakdown of key tasks:

Task Goal Input Output Effort Duration Dependencies

(Hours)

T1 Define system User Requirement 10 1 week None

requirements interviews, doc
research

T2 Design Requirements System 15 1 week T1

architecture design docs

T3 Implement Design docs Working 20 1.5 weeks T2

user auth auth module
module

T4 Implement API access, Location 25 2 weeks T2

Location Maps module
tracking

T5 Implement Design, Alert 25 2 weeks T2

41
 Alter system Triggers functionality

T6 Testing Test cases Bug reports 30 2 weeks T3-T5

T7 Final Test code Live app 15 1 week T6

deployment

T8 Documentation App, Reports, 20 2 weeks T7

Features manuals

42
 Chapter 6
PROJECT MANAGEMENT

6.1 MAJOR RISKS AND CONTINGENCY PLANS

Every software project faces potential risks that could affect its success, particularly those involving real-
time emergency features and sensitive data handling. The KAVACH application development team
identified the following major risks along with their respective mitigation strategies:

Risk Description Impact Likelihood

Technical Failures Bugs, crashes, or High Medium
malfunctioning sensors
like GPS or shake
detector.
Permission Denial User denies access to High High
location or SMS features.
Internet Unavailability Alerts or location tracking High Medium
may fail without internet.
Battery Drain Continuous GPS and Medium Medium
background activity may
drain battery.
False Alarms Unintended emergency Medium Medium
alerts due to device
shaking.

Data Privacy Breach Unauthorized access to High Medium

location and emergency
contact data.
Hardware Dependency Some devices may lack Medium Medium
required sensors (e.g.,
accelerometer).

Compliance Issues App must follow regional High Low

laws (e.g., data
protection).

43
 6.2 PRINCIPAL LEARNING OUTCOMES

The development of the KAVACH women safety application offered a rich learning experience in
technical, practical, and social dimensions. Key takeaways from the project are summarized below:

1. Real-World Problem Solving Through Technology

The project highlighted how mobile apps can directly address societal issues, like women’s safety,
through technology.

2. Android Application Development Proficiency

Hands-on experience with Android Studio, Java, XML, Firebase, and UI/UX best practices provided
core development skills.

3. Third-Party API Integration

Integration of services like Google Maps API and Firebase Real-time Database enhanced practical
knowledge of working with cloud tools.

4. Sensor Integration and Event Handling

implementing features like shake detection deepened understanding of hardware-based programming
using accelerometers.

5. Location-Based Services
Developed accurate, real-time GPS tracking and geolocation features using Google Maps and Android
location services.

6. UI/UX Design Focus

Created accessible, user-friendly interfaces tailored for high-stress situations, emphasizing inclusive
design principles.

7. Security and Privacy Best Practices

Emphasized ethical data handling, encryption, and compliance with privacy standards to build user trust.

8. Software Testing and Quality Assurance

Applied unit, integration, system, and user acceptance testing for bug-free, stable software delivery.

9. Project Management and Teamwork

Task delegation, version control, and progress tracking helped manage timelines and workload
efficiently.

10. Effective Documentation and Reporting

Developed comprehensive technical documentation, user manuals, and reports to support the project
lifecycle and final submission.

44
 CONCLUSION

The development of the W-Safe application has addressed the critical need for women's safety in
today's society. By leveraging advanced technologies such as Android Studio, Java, and XML, W-Safe
offers a comprehensive solution to empower women and enhance their personal security and safety.
The application incorporates features like a shake detector, panic button, SOS alerts, and location
tracking to ensure prompt assistance during emergencies. Additionally, the integration of nearby police
stations and hospitals, women safety laws, self-defense videos, and national helpline numbers provides
users with valuable resources and information. The user-friendly interface and seamless functionalities
make W-Safe accessible and easy to navigate, further enhancing its effectiveness. The successful
implementation of the project showcases the potential of technology in promoting women's safety and
creating a safer environment. W-Safe serves as a significant step forward in safeguarding women and
raising awareness about their rights and well-being.

45
DRILLBIT REPORT

46
47
48
49
50
CERTIFICATES

51
52
53
54
55
 APPENDIX A

APPLICATION FEATURES SUMMARY

This appendix provides a concise summary of the core features offered by the KAVACH (WSafe)
application, aimed at enhancing the safety and well-being of women through real-time technology.

1. User Authentication Module

Users can securely register and log in to the app using their email credentials. This ensures that only
authorized users can access the platform.

2. Emergency SOS Alert

The central feature of the app allows users to send an emergency alert to their trusted contacts along
with their real-time location during a distress situation.

3. Real-Time Location Sharing

Users can share their dynamic location with guardians or emergency contacts. This helps in tracking
and providing timely help.

4. Police Station Locator

The app includes a feature that displays the nearest police stations based on the user's current
location, allowing faster access to assistance.

5. Self-Defense and Safety Education

This module includes useful safety tips and educational material to spread awareness about self-
defense, safe practices, and emergency preparedness.

6. Helpline Directory
A built-in directory provides quick access to national and state-level helpline numbers, covering
police, emergency services, and women’s support lines.

7. Anonymous Reporting
Enables users to report safety threats or incidents without revealing their identity, encouraging more
users to report misconduct without fear.

8. Community Support Forum

A safe space for users to share experiences, raise concerns, and connect with others for support and
guidance.

56
 APPENDIX B

PROJECT DEVELOPMENT OVERVIEW

This appendix outlines the key phases and tools used during the development lifecycle of the KAVACH
application.
1. Requirement Analysis
The development began with a detailed study of existing safety apps, identification of their
limitations, and gathering of user needs through secondary research.

2. Design and Planning

The system architecture, data models, flow diagrams, and UI/UX layouts were designed to ensure
ease of use, responsiveness, and functionality.

3. Technology Stack
a. Frontend: Android (Java/XML)
b. Backend: Firebase (Authentication, Realtime Database)
c. APIs Used: Google Maps API, Firebase Cloud Messaging (FCM)

4. Development Strategy
Modular development was followed to ensure that each feature (e.g., SOS, location sharing, contact
management) was independently designed, tested, and then integrated into the overall system.

5. Testing Methodology
a. Unit testing of individual modules
b. Integration testing for module interaction
c. System testing to ensure end-to-end functionality
d. User Acceptance Testing (UAT) with feedback collection

6. Deployment and Optimization

Post-testing, the app was finalized for deployment. Special focus was placed on performance tuning,
battery optimization, and offline usability.

7. Project Tools Used

a. IDE: Android Studio
b. Version Control: Git
c. Documentation: MS Word, [Link] (for diagrams), Excel

57
 REFERENCES

1. “WoSApp” A Mobile Application for Women's Safety: Author: Dhruv Chand, Sunil Nayak
et al., (2015)[1] [Link]
2. “Abhaya” Author: Ravi Sekhar Yarrabothu, Bramarambika Thota (2015)[2]
[Link]
3. “ Mobile-based ladies Protection System” Author: Vallidevi Krishnamurthy, Saranya. S et al.
(2015)[3] [Link]
4. “Woman Safety Application – MwithU” Author: Abhijeet Singh, Vishnu Barodiya. (2018)
[4] [Link]
5. “Android App for Women Safety” Author: Dr. K Srinivas, Dr. Suwarna Gothane et al. (2021)
[5] [Link]
6. “An Android Based Women Safety App” Author: Manisha Sharma, Akhil Bansal
i. (2022)[6] [Link]
7. “Stay Safe” Mr. Indrajeet A. Mane, Miss. Jyotsna R. Babar et al. (2020)[7]
[Link]
8. “Advanced women security app: We’RSafe” Author: Tanusri Dey, Upama Bhattacharjee et al.
(2022)[8] [Link]
9. “LifeCraft” Author: R. R. Khandoker, S. Khondaker et al. (2019)[9] [Link]
10. “An Implementation and Efficient Way” Author: Mr. Kalyan D Bamane, Nelofer kousar et al.
(2018)[10] [Link]

58
59