`

“eRakshak – women safety app”

A Major Project Phase-I report submitted to

KAVAYITRI BAHINABAI CHAUDHARI NORTH MAHARASHTRA

UNIVERSITY, JALGAON (MH)
['A' Grade NAAC Re-Accredited (4th Cycle)]

Towards the award of the degree of

BACHELOR OF ENGINEERING (COMPUTER ENGINEERING)

Submitted to

COMPUTER ENGINEERING DEPARTMENT

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES

AKKALKUWA (MH)

Guided By: Submitted By:

Mr. Mohammad Asif 1. Thakare Ashok

Computer Engineering Dept. 2. Pawara Mangalsing
3. Yash kalal
4. Nadeem Sikkalgar
5. Faiyaz Ahmed
`

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES

AKKALKUWA (MH)

KAVAYITRI BAHINABAI CHAUDHARI NORTH MAHARASHTRA

UNIVERSITY, JALGAON (MH)
(2018 - 2019)

Estb. 2010
DTE Institute Code: - EN5322
JIIU’

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES,

AKKALKUWA (MH)
(APPROVED BY AICTE, NEW DELHI & AFFILIATED TO KAVAYITRI BAHINABAI CHAUDHARI NORTH
MAHARASHTRA UNIVERSITY, JALGAON & DTE Mumbai, CERTIFIED BY ISO 9001:2008 )
`

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES

AKKALKUWA (MH

KAVAYITRI BAHINABAI CHAUDHARI NORTH MAHARASHTRA

UNIVERSITY, JALGAON (MH)
['A' Grade NAAC Re-Accredited (4rd Cycle)]

COMPUTER ENGINEERING DEPARTMENT

DISSERTATION APPROVAL SHEET

This Dissertation report entitled “eRakshak – women safety app” submitted

Mr.Thakare Ashok , Mr. Pawar Mangalsing , Mr. Yash kalal , Mr. Faiyaz
Ahmed , Mr. Nadeem Sikkalgar are approved as Partial fulfilment for the award
of the Bachelor of engineering in Computer Engineering degree from Jamia
Institute of Engineering & Management Studies, Akkalkuwa (MH).

Internal Examiner External Examiner

Date: / / 2023-24 Date: / / 2023-24

I/C Principal
JIEMS, AKKALKUWA
`

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES,

AKKALKUWA (MH)
(APPROVED BY AICTE, NEW DELHI & AFFILIATED TO KAVAYITRI BAHINABAI CHAUDHARI NORTH
MAHARASHTRA UNIVERSITY, JALGAON & DTE Mumbai, CERTIFIED BY ISO 9001:2008 )

COMPUTER ENGINEERING DEPARTMENT

CERTIFICATE

The Dissertation work entitled “eRakshak – women safety app ” submitted by

Mr. Ashok , Mr. Yash kalal, Mr. Mangalsing Pawara, Mr. Nadeem Sikkalgar
and Mr. Faiyaz Ahmed has been examined by us and is hereby approved for the
award of degree “ Bachelor of Engineering ” in “ Computer Engineering ” for
which it has been submitted. It is understood that by this approval the undersigned
do not necessarily endorse or approve any statement made, opinion expressed or
conclusion drawn therein, but approve the mini project only for the purpose for
which it has been submitted.

Internal Examiner External Examiner

Date: / / 2023-24 Date: / / 2023-24
`

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES,

AKKALKUWA (MH)

DEPARTMENT OF COMPUTER ENGINEERING

RECOMMENDATION

The Dissertation report entitled “eRakshak – women safety app ” Submitted by

Mr.Thakare Ashok , Mr. Pawar Mangalsing , Mr. Yash kalal , Mr. Faiyaz
Ahmed , Mr. Nadeem Sikkalgar are satisfactory account of the bonafide work done
under our guidance is recommended towards partial fulfilment for the award of the “
Bachelor of Engineering ” in “ Computer Engineering ”, degree from Jamia
Institute of Engineering & Management Studies, Akkalkuwa by Kavayitri
Bahinabai Chaudhari North Maharashtra University, Jalgaon (MH).

Guided By: Head of Department

Prof. Mr. Mohammad Asif Prof. Mr. Mohammad Asif
Computer Engineering Dept. Computer Engineering Dept.

Principal
JIEMS, AKKALKUWA
`

JAMIA INSTITUTE OF ENGINEERING & MANAGEMENT STUDIES,

AKKALKUWA (MH)

DEPARTMENT OF COMPUTER ENGINEERING

CANDIDATE DECLARATION

We hereby declare that work which is being presented in this report “ eRakshak
women safety app ” in partial fulfilment of degree of “ Bachelor of Engineering
” in “ Computer Engineering ” is an authentic record of our own work carried out
under the supervision and guidance of Mr. Mohammad Asif, Professor of
Computer Engineering. The matter embodied in this report has not been submitted
for the award of any other degree.

Guided By: Submitted By:

Mr. Mohammad Asif 1. Ashok Thakare
Computer Engineering Dept. 2. Mangalsing Pawara
3. Yash Kalal
4. Nadeem Sikkalgar
5. Faiyaz Ahmed
`

ACKNOWLEDGEMENTS

“A journey is easier when you travel together. Interdependence is certainly more

valuable than independence.”

We take this opportunity to express our deep sense of gratitude and respect to our
guide Mr. Mohammad Asif without his constant encouragement and key tips it
would not have been possible to complete this work with the present quality and we
really indebted him for helping us in each aspect of our academic’s activities.

We also owe our sincere thanks to all faculty members of Computer Engineering
Department who have been always ready with a helping hand. Last, but not the least,
we thank all those people, who have helped us directly or indirectly in accomplishing
this work.

I extend a special word to my friends, who have been a constant source of inspiration
throughout my project work.

“The completion of any project depends upon the cooperation, coordination, and
combined efforts of several resources of knowledge, inspiration, and energy”.

Submitted By:
1. Thakare Ashok
2. Pawara Mangalsing
3. Yash kalal
4. Nadeem Sikkalgar
5. Faiyaz Ahmed
`

TABLE OF CONTENTS

Chap Content
No.
-- ACKNOWLEDGEMENT
-- ABSTRACT
-- TABLE OF CONTENTS
-- LIST OF FIGURES
-- LIST OF TABLES
-- LIST OF ABBREVIATIONS

1. INTRODUCTION
1.1 Rationale
1.2 Introduction to Project
1.3 Problem Definition
1.4 Motivation
1.5 Scope
1.6 Objective
1.7 Summery

2. PROJECT PLANING AND MANAGEMENT

2.1 Feasibility study
2.2 Risk analysis
2.3 Effort Allocation
2.4 Cost Estimation & Summery

3. ANALYSIS
3.1 Requirement analysis and identification
3.2 Minimum software requirement
3.3 Hardware and software requirement
3.4 Functional and non- functional requirement softwares

3.5 Team structure

4. DESIGN

4.1 Project structure

4.2 Project models
4.3 UML Modelling
4.3.1 Use Case Diagram
4.3.2 Activity Diagram
4.3.3 Class Diagram
4.3.4 Analytical Modelling
`

5. IMPLEMENTATION DETAILS
5.1 Implementation Language: JAVA
5.2 Database: FIREBASE
5.3 Implementation Tool: ANDROID STUDIO
5.4 Modular description

6. SAMPLE OUT -PUT

6.1 Module 1

Module 2
`

7.
System testing

7.1 Testing tool

7.2 Test plan
7.3 Test cases
7.4 Test results

8. System maintenance

9. Conclusion

10 --- References AND BIBLIOGRAPHY

`

LIST OF FIGURES

Figure Name
Sr. Figure
No. No.

Modular structure for project on eRakshak: Women safety

1. 3.1
Application
Use Case Diagram For eRakshak: Women safety android
2. 4.1
Application
Activity Diagram For eRakshak : Women safety android
3. 4.2
Application
4. 4.3 Class Diagram For eRakshak: Women Safety Android Application

5. 4.4 Entity-Relationship Diagram

4.5 Data Flow Diagram level-0

6.

4.6 Data Flow Diagram level-1

7.

8. 5.1 Features of Java

9. 5.2 Firebase vs SQLite

5.3 Features of Android Studio
10.
5.4 Snapshot of Module 1: sign up &sign
11.
5.5 Snapshot of Module 2: current location &guardian information
12.
6.1 Why Appium
13.

14 6.2 Script and Setup Code for Testing

`

LIST OF TABLES

Sr. Table
Table Name
No. No.

1. 2.1 Comparative analysis of various related exiting systems

2. 3.1 Team Structure, Roles & Details

3. 3.2 Project Table

4. 3.3 Minimum Hardware Requirements

5. 3.4 Minimum Software Requirements

6. 5.1 Schema for User Account table

7. 5.2 Schema for Add Contact table

8. 6.1 Test Plan

Test Cases for Module Login
9. 6.2
Test Cases for Module Register
10. 6.3

11. Test Results

6.4
.
`

LIST OF ABBREVIATIONS

Abbreviation Literal Translation

DB Database
ERD Entity-Relationship Diagram
SQL Structured Query Language
IDE Integrated Development Environment
LOC Lines of Code
SOS Save our Souls
SDLC Software Development Life Cycle
MSBTE Maharashtra State Board of Technical Education
OS Operating System
DFD Data Flow Diagram
AVD Android Virtual Device
UML Unified Modelling Language
 `

Chapter 1
INTRODUCTION

1.1 RATIONALE
Our application is specially developed for women’s providing a secure safety. Women safety
application can be used to find and help women in emergency. Recent time it’s been identified lots of
misbehaving activity in urban and rural part of our country. rapid growth of android user and cheaper
internet cost.
Simple medium to create safety awareness among the working and professional women of young and
teen age. Using this family, parents can easily track and monitor her daughter.

1.2 . INTRODUCTION OR BACKGROUND

A wide range of tracking systems has been developed so far tracking vehicles and displaying their
position on a map, but none of the applications has been developed so far which tracks the mobility of a
human being. Now a day’s tracking a person’s mobility has become a crucial issue these days be it tracking
a criminal came on payroll or a system which is cost effective and can be used for tracking a human being
using a GPS and GPRS equipped mobile phone rather than using a handheld GPS receiver.

The main focus of our project is to reduce the overall cost of tracking based on GPS system which is
a satellite-based service which is available 24X7 everywhere in the whole world. GPS system can be used
to get location which includes details like latitude, longitude and altitude values along with the timestamp
details etc. it is a free of cost service available to every individual. In order to track the movement of the
person we have used Google Maps for mapping the location sent by the mobile phone. The mobile phone
which fetches the GPS location communicates with the server using General Packet Radio Service
(GPRS). This service is a low-cost service provided by the service providers which is a wireless data
communication system. Mobile phones equipped with GPS receiver are easily available in the market
these days and is a booming technology these days. This cell phone technology has enabled us to
communicate almost every part of the world across the boundaries. The GSM/GPRS is one of the best and
cheapest modes of communication present these days and in future.
`

3. PROBLEM DEFINITION

The problem that "eRakshak – women safety app" seeks to address is the prevalence
of harassment, assault, and violence against women in various settings, including
public spaces, workplaces, and even within their own homes.

Specifically, the app aims to tackle the following issues:

Safety Concerns: Women often face safety concerns while traveling alone,
commuting, or engaging in everyday activities. The fear of harassment or violence
can limit their mobility and restrict their access to opportunities.
Emergency Response: In situations where women encounter harassment, assault,
or other threatening incidents, accessing immediate assistance can be challenging.
Existing emergency response systems may not always be equipped to address the
specific needs and concerns of women effectively.
Lack of Resources: Many women lack access to resources and support services
that can help them navigate safety concerns, assert their rights, and seek assistance
in case of emergencies. This lack of resources can exacerbate feelings of
vulnerability and helplessness.
Underreporting: Due to social stigma, fear of retaliation, or distrust in the justice
system, incidents of harassment and violence against women are often
underreported. This underreporting hampers efforts to address the root causes of
gender-based violence and provide support to victims.
Community Awareness: There may be a lack of awareness and community
engagement regarding the safety concerns faced by women. Building a supportive
community that prioritizes women's safety and takes collective action to address
harassment and violence is essential.
`

4. MOTIVATION

The motivation behind creating the "eRakshak – women safety app" likely stems from
a pressing need to address the safety concerns of women in various environments.
Here are some potential motivations:
Addressing Gender-Based Violence: Women, unfortunately, face higher risks of harassment,
assault, and violence in many societies. Creating an app like eRakshak could be motivated

by a desire to combat this issue and provide women with tools to protect themselves.
Empowerment:
Empowering women to feel safer and more confident when navigating public spaces
is a significant motivation. By providing them with a tool like eRakshak, they may feel
more empowered to assert their rights and stand up against harassment or violence.
Utilizing Technology:
In today's digital age, technology can play a crucial role in enhancing safety measures.
The creators of eRakshak might have been motivated by the potential of technology to
provide
real-time assistance, connect users with emergency services, and gather evidence in
case of incidents.
Community Support: Building a safer environment for women often requires
collective action. eRakshak may have been developed with the aim of fostering a sense
of community support, where users can alert others nearby about potential dangers or
seek help when needed.
Fulfilling Legal Requirements:
In some regions, there may be legal requirements or mandates for organizations or
governments to take steps to ensure women's safety.
Developing an app like eRakshak could be driven by the need to fulfill such
obligations and demonstrate a commitment to addressing gender-based violence.
Overall, the motivation behind eRakshak likely revolves around enhancing women's
safety, leveraging technology to address societal challenges, and fostering
empowerment and community support.
`

5. SCOPE
With the knowledge we have gained by developing this application, we’re confident that in the
future, we can make the application more effectively by adding these services :

-­‐ Add SOS button functionality to power button or Volume button

-­‐ Without open user can send Emergency Call outside application.
-­‐ Add Admin module to Change user data
-­‐ Add more facilities like police helpline numbers
-­‐ In future you can add two SOS button. One for personal safety and health related safety
-­­ Add Forget password functionality
-­‐ Not working without network connection.
-­‐ Add audio and video recording functionality

6. OBJECTIVE

Women safety apps enable women to send and receive alerts in case of emergency.
They can communicate messages as well as their location to emergency contacts in
the event of an emergency.
Women's safety involves strategies, practices and policies which aim to reduce gender-
based violence (or violence against women), including women's fear of crime.
Women's safety involves safe spaces.
`

5. SUMMARY

"eRakshak – women safety app" is a mobile application designed to enhance the safety
and security of women in various environments. The app provides several features
aimed at addressing the unique safety concerns faced by women:
Emergency Assistance: Users can quickly call for help in case of emergencies, such
as harassment, assault, or other threatening situations. The app connects users with
emergency services or designated contacts for immediate assistance.
Location Tracking: eRakshak utilizes GPS technology to track the user's location in
real-time. This feature enables users to share their location with trusted contacts or
authorities, ensuring that they can be located swiftly in case of emergencies.
SOS Alerts: The app allows users to send distress signals or SOS alerts to their pre-
defined emergency contacts with just a few taps. This feature can be crucial in
situations where immediate assistance is required.
Safety Tips and Resources: eRakshak provides users with valuable safety tips and
resources to help them navigate various situations safely. These resources may include
information on self-defense techniques, legal rights, and support services available for
victims of harassment or violence.
Community Support: The app fosters a sense of community support by enabling
users to report incidents of harassment or suspicious activities in their vicinity. By
alerting others nearby, users can help prevent potential dangers and create safer
environments collectively.
Overall, "eRakshak – women safety app" aims to empower women, leverage
technology
`

Chapter 2

PROJECT PLANNING AND MANAGEMENT

1. Feasibility Study

The feasibility study for "eRakshak – women safety app" would typically evaluate
various aspects to determine the viability and practicality of developing and
implementing the app. Here's an outline of what such a feasibility study might entail:
Technical Feasibility:
Assess the technical requirements for developing the app, including platform
compatibility (iOS, Android), required features, and integration with external services
(e.g., emergency response systems).
Evaluate the availability of technology resources (development team, software tools,
infrastructure) to build and maintain the app.
Consider any technical challenges or limitations that may impact the app's
functionality or performance.

Market Feasibility:
Conduct market research to understand the demand for a women's safety app like
eRakshak. Analyze demographic data, user preferences, and existing competitors in
the market.
Identify potential target users, such as women of different age groups, occupations,
and geographic locations.
Assess the willingness of users to adopt and pay for the app, considering factors like
pricing, features, and perceived value.
Financial Feasibility:
Estimate the costs associated with developing, launching, and maintaining the app,
including software development, marketing, support, and ongoing updates.
Evaluate potential revenue streams, such as app sales, subscription fees, in-app
purchases, or partnerships with organizations or sponsors.
Calculate the expected return on investment (ROI) and determine whether the app is
financially viable in the long run.
`

Legal and Regulatory Feasibility:

Review legal and regulatory requirements related to data privacy, security, and
compliance with laws governing emergency services and communication.
Ensure that the app adheres to industry standards and best practices for handling
sensitive information and protecting user privacy.

Identify any potential legal risks or challenges that may arise during the development
and operation of the app.
Operational Feasibility:
Assess the operational requirements for launching and maintaining the app, including
staffing, training, and support services.
Evaluate the scalability of the app to accommodate growth in user base and usage
volume over time.

Consider any operational challenges or constraints that may affect the app's ability to
deliver on its intended purpose effectively.

Social and Ethical Feasibility:

Consider the social and ethical implications of developing and promoting a women's
safety app, including its impact on gender equality, empowerment, and community
engagement.
Ensure that the app promotes inclusivity, diversity, and sensitivity to the needs and
experiences of all users, regardless of background or identity.
Address any ethical concerns related to data collection, user consent, and responsible
use of technology in addressing social issues.
By conducting a comprehensive feasibility study, the developers of "eRakshak –
women safety app" can assess the practicality and potential success of their initiative,
identify potential risks and challenges, and make informed decisions about proceeding
with the development and implementation of the app.
 `

1. Risk Analysis

The feasibility study for "eRakshak – women safety app" would typically evaluate
various aspects to determine the viability and practicality of developing and
implementing the app. Here's an outline of what such a feasibility study might entail:
Technical Feasibility:
Assess the technical requirements for developing the app, including platform
compatibility (iOS, Android), required features, and integration with external services
(e.g., emergency response systems).
Evaluate the availability of technology resources (development team, software tools,
infrastructure) to build and maintain the app.
Consider any technical challenges or limitations that may impact the app's
functionality or performance.
Market Feasibility:

Conduct market research to understand the demand for a women's safety app like
eRakshak. Analyze demographic data, user preferences, and existing competitors in
the market.
Identify potential target users, such as women of different age groups, occupations,
and geographic locations.
Assess the willingness of users to adopt and pay for the app, considering factors like
pricing, features, and perceived value.
Financial Feasibility:
Estimate the costs associated with developing, launching, and maintaining the app,
including software development, marketing, support, and ongoing updates

Evaluate potential revenue streams, such as app sales, subscription fees, in-app
purchases, or partnerships with organizations or sponsors.
Calculate the expected return on investment (ROI) and determine whether the app is
financially viable in the long run.
Legal and Regulatory Feasibility:
Review legal and regulatory requirements related to data privacy, security, and
compliance with laws governing emergency services and communication.
Ensure that the app adheres to industry standards and best practices for handling
sensitive information and protecting user privacy.
 `

Identify any potential legal risks or challenges that may arise during the development
and operation of the app.
Operational Feasibility:
Assess the operational requirements for launching and maintaining the app, including
staffing, training, and support services.
Evaluate the scalability of the app to accommodate growth in user base and usage
volume over time.
Consider any operational challenges or constraints that may affect the app's ability to
deliver on its intended purpose effectively.
Social and Ethical Feasibility:
Consider the social and ethical implications of developing and promoting a women's
safety app, including its impact on gender equality, empowerment, and community
engagement.
Ensure that the app promotes inclusivity, diversity, and sensitivity to the needs and
experiences of all users, regardless of background or identity.
Address any ethical concerns related to data collection, user consent, and responsible
use of technology in addressing social issues.

3. Effort Allocation
Effort allocation for the development and implementation of "eRakshak – women
safety app" would involve dividing resources, tasks, and responsibilities among
various stakeholders. Here's a breakdown of effort allocation across different areas:

Development Team:
Software Developers: Responsible for designing, coding, testing, and implementing
the app's features and functionality according to the project requirements.
UI/UX Designers: Create intuitive and user-friendly interfaces, ensuring a seamless
user experience for app users.
Quality Assurance/Testers: Conduct thorough testing and debugging to identify and
fix any issues or bugs in the app before its release.
`

Project Managers: Oversee the development process, coordinate tasks, manage

timelines, and ensure that project goals are met within budget and schedule
constraints.

Content and Resource Creation:

Content Writers: Develop informative content, safety tips, and resources within the
app to educate users about women's safety and provide relevant information and
support.
Graphic Designers: Create visual assets, illustrations, and graphics to enhance the
app's visual appeal and effectively communicate information to users.
Marketing and Promotion:
Marketing Team: Develop a marketing strategy to promote the app and reach its target
audience effectively. This may involve digital marketing, social media campaigns,
influencer partnerships, and outreach to relevant organizations and communities.
Public Relations (PR): Manage media relations, press releases, and communication
efforts to raise awareness about the app and generate positive publicity.
Legal and Compliance:
Legal Advisors: Provide guidance on legal and regulatory requirements related to data
privacy, security, intellectual property rights, and compliance with relevant laws and
regulations.
Compliance Officers: Ensure that the app adheres to industry standards and best
practices for handling sensitive information and protecting user privacy, as well as
complying with laws governing emergency services and communication.

Operations and Support:

Customer Support Team: Provide timely assistance and support to app users,
addressing inquiries, feedback, and technical issues as they arise.
Operations Managers: Manage day-to-day operations, monitor app performance, and
coordinate activities to ensure smooth functioning of the app and related services.
 `

Community Engagement:
Community Managers: Facilitate engagement with app users, community outreach,
and collaboration with relevant stakeholders, such as women's advocacy groups, law
enforcement agencies, and local authorities.
User Engagement Specialists: Develop strategies to encourage user participation,
feedback, and contribution to community safety efforts, fostering a sense of
empowerment and solidarity among app users.

4. Cost Estimation & Summary

Certainly, let's sort the key points and provide a summary along with cost estimation
for the "eRakshak – women safety app":
Cost Estimation:
Development Costs: This includes expenses related to software development, such as
hiring developers, designers, testers, and project managers. Depending on the
complexity of the app and the size of the development team, this could range from tens
of thousands to hundreds of thousands of dollars.
Marketing and Promotion: Budget for marketing campaigns, advertising, public
relations, and outreach efforts to promote the app and reach its target audience. This
could range from a few thousand to tens of thousands of dollars, depending on the
scale and scope of marketing activities.
Legal and Compliance: Costs associated with legal consultation, compliance with
regulations, and ensuring data privacy and security measures are in place. This could
vary depending on the jurisdiction and specific legal requirements but may range from
a few thousand to tens of thousands of dollars.
Operations and Support: Budget for customer support services, server hosting,
maintenance, and ongoing operational expenses. This could range from a few thousand
to tens of thousands of dollars annually, depending on the scale of operations and user
base.
`

CHAPTER 3

ANALYSIS

1. Requirement Collection and identification

Minimum Hardware Requirements
Table 3.1 Minimum Hardware Requirements

Role Software Minimum Requirement

Development Processor Intel (R)Core(TM) i3--‐4170T CPU 3.20GHz

Primary Memory 4 GB

Secondary Memory 500 GB

Internet Connection 1.2 Mbps

Other Hardware Android phone

Deployment Client Machine/Mobile Android phone

Primary Memory 2 GB

Secondary Memory 20 GB

2. Minimum Software Requirements

Table 3.2 Minimum Software Requirements

Role Software Minimum Requirement

Development Platform (OS) Android OS (Version 6 and above)

Front End (Prog. Lang.) Android and Java

Backend (DB) Firebase

Development Tool (IDE) Android Studio 3.0.1

Testing Tool Appium

Deployment Execution Environment Android Emulator(AVD)

Browser --‐
Server (Application /
Firebase
Database Server)
Design UML Design Rational Rose
DFD, ER, Flows Draw.io
 `

Summary of Key Points:

Purpose: eRakshak is a women's safety app designed to address safety concerns and
provide support to women facing harassment, assault, or other threatening situations.
Features: Emergency assistance, location tracking, SOS alerts, safety tips and
resources, and community support for reporting incidents and fostering a supportive
environment.
Feasibility: The app's feasibility is determined by technical, market, financial, legal,
operational, and social/ethical factors, which must be carefully evaluated to ensure the
project's success.
Effort Allocation: Effort must be allocated across development, content creation,
marketing, legal/compliance, operations/support, and community engagement to
effectively execute the project and achieve its objectives.
Cost Estimation: Development and operating costs for the eRakshak app include
expenses related to software development, marketing/promotion, legal/compliance,
and ongoing operations/support, which can vary depending on project requirements
and scale.
By carefully considering these key points and cost estimates, the developer.

3. H/w and S/w Requirement (Data, Functional and Behavioral)

Hardware Requirements:
Smartphones/Tablets: The app should be compatible with popular mobile devices
running on iOS and Android platforms, including smartphones and tablets.
GPS Module: Devices should have a GPS module for accurate location tracking and
SOS alerts.
Internet Connectivity: Reliable internet connectivity via Wi-Fi or mobile data network
is required for accessing real-time data, sending alerts, and receiving updates.
Camera (Optional): Devices with a camera can be used for capturing evidence or
recording incidents if needed.
Software Requirements:
Operating System Compatibility: The app should be compatible with iOS (iPhone,
iPad) and Android devices, supporting a range of operating system versions to reach a
wider user base.
Development Platform: The app can be developed using programming languages
such as Swift (for iOS) and Java/Kotlin (for Android), utilizing appropriate
development frameworks and tools (e.g., Xcode for iOS, Android Studio for Android).
`

Database Management System: A database management system (DBMS) is required

for storing user data, preferences, and other relevant information securely. Options
may include SQLite for local storage and cloud-based solutions like Firebase or AWS
for remote storage.
API Integration: Integration with external APIs may be necessary for accessing
location services, emergency response systems, mapping services, and other
functionalities.
Security Measures: Implementation of encryption, authentication, and authorization
mechanisms to secure user data and communications within the app.
User Interface (UI) Design Tools: Design tools such as Sketch, Adobe XD, or Figma

can be used for creating intuitive and visually appealing user interfaces.
Data Requirements:
User Profiles: Collect and store user profiles containing personal information (e.g.,
name, contact details) and preferences (e.g., emergency contacts, safety preferences).
Location Data: Retrieve and store real-time location data to track users' movements,
send alerts, and provide location-based services.
Emergency Contacts: Maintain a list of emergency contacts provided by users for
immediate assistance during emergencies.

Safety Tips/Resources: Store educational content, safety tips, resource links, and
relevant information within the app for user reference.
Functional Requirements:
Emergency Assistance: Users should be able to send distress signals or call for help in
emergencies with a single tap.
Location Tracking: The app should track the user's location in real-time and provide
accurate location information to emergency contacts or authorities.
SOS Alerts: Send automated SOS alerts to pre-defined emergency contacts with the
user's location and relevant details in case of emergencies.
Safety Tips/Resources: Provide access to safety tips, self-defense techniques, legal
rights information, and support services within the app.
Community Support: Enable users to report incidents, share safety concerns, and
receive assistance from nearby users or authorities.
`

Behavioral Requirements:
User Interaction: The app should have intuitive and user-friendly interfaces for easy
navigation and interaction.
Real-time Updates: Provide real-time updates and notifications to users regarding
safety alerts, nearby incidents, and relevant information.
Reliability: Ensure the app's reliability and responsiveness, especially during
emergencies, with minimal downtime or service disruptions.
Privacy: Implement privacy measures to protect user data and ensure confidentiality,
including secure data transmission and storage practices.
`

4.Functional and non-Functional Requirements Software

1) Name: full name of the user.
2) Email id: email id of the user.
3) Username: username as per user wants.
4) Password: password should fulfil requirements of strong password (containing [a--‐z A--‐Z 0--‐
9])
5) Birth date: for calculating the age of user
6) Contact no.: is the most important information because through contact no.
Self-defence: After creating account user can login with username and password if password is
correct along with user name. after successful log in user can access all facilities of the application.
In this module there are many functionalities like as follow:

1) Add contact no: In this user can add their trusted contact no. .
2) Tips for women safety: Tips for women for escape from threat.
3) Police helpline numbers: provide tab for police helpline numbers.
4) Laws related to women: laws are defined by government for the women.
5) Video for self--‐defence: videos related to how to maintain yourself in any unsafe conditions.
6) SOS Button: After pressing SOS button, it will send emergency message and call to the which
contact we selected.
`

5. TEAM STRUCTURE
Team structure addresses the issue of organization of the individual project teams. Our project team
consists of 3 members; the efforts assignment to each team member are given the project table, the
role of each member is as below:
Table 3.1 Team Structure, Roles & Details

Sr. Role in Planning Role in Execution

No. Name of Team Member (Sem--‐Vii) (Sem--‐viii )
Requirement, analysis
1. Ashok Thakare
, designing
Literature review, project
2. Mangalsing Pawara
Scheduling
Literature
3. Ashok Thakare
review, documentation

4. Yash kakal Presentation preparation

`

Chapter 4
DESIGN

4.1 PROJECT STRUCTURE

Figure 4.1 Modular Structure for project on eRakshak: Women safety application

4.2 PROJECT MODULES

Admin: Admin is the main module in our project admin controls all functionalities of our application.
User and admin have many same rights but Admin have more rights like check authentication it means
if user trying to login and user entered correct username and password then and then only, he/she can
log in. Admin have another major facility that is database backup facility and only Admin can view
the all-­‐user profile and their data.
`

Register: Register is second main module of our application because registration module user cannot
access functionalities of the application. Firstly, user needs to create account then the user is

authenticating to access the features of application. When user fill

up registration form, we take some information about user like as
follow:

7) Name: full name of the user.

8) Email id: email id of the user.
9) Username: username as per user wants.
10) Password: password should fulfil requirements of strong
password (containing [a-­‐z A-­‐Z 0-­‐9])
11) Birth date: for calculating the age of user
12) Contact no.: is the most important information because
through contact no.
Self-defence: After creating account user can login with
username and password if password is correct along with user
name. after successful log in user can access all facilities of the
application. In this module there are many functionalities like as
follow:

7) Add contact no: In this user can add their trusted contact
no. .
8) Tips for women safety: Tips for women for escape from
threat.
9) Police helpline numbers: provide tab for police helpline
numbers.
10) Laws related to women: laws are defined by government
for the women.
11) Video for self-­‐defence: videos related to how to maintain
yourself in any unsafe conditions.
12) SOS Button: After pressing SOS button, it will send
emergency message and call to the which contact we
selected.
`

4.3 UML MODELING

4.3.1 Use Case Diagram

A use case defines behavioural features of a system. Each use case is named using a verb phase
expresses a goal of the system. A use case diagram shows a set of use cases and actors &their
relationships. Use case diagrams address the static use case view of a system. These diagrams are
especially important in organizing and modelling the behaviours of a system. It shows the graphical
overview of functionality provided by the system intents actor.

Figure 4.3.1 Use case Diagram For eRakshak: Women Safety Android Application
`

4.3.2 Activity Diagram

An activity diagram of a special kind of a state chart diagram that shows the flow from activity within
a system. An activity addresses the dynamic view of a system. The activity diagram is often seen as
part of the functional view of a system because it describes logical processes, or functions. Each
process describes a sequence of tasks and the decisions that govern when and they are performed. The
flow in an activity diagram is

Figure 4.2 Activity Diagram For eRakshak :Women Safety Android Application
`

4.3.3 Class Diagram

A class diagram shows a set of classes, interfaces and collaborations and their relationship. These
diagrams are the most common diagram found in modelling object-oriented systems. Class diagram
addressed the static design view of a system.

Figure 4.3,3- Class Diagram For eRakshak :Women Safety Android Application
`

4.4 ANALYSIS MODELING

4.4.1 Data Modelling (Entity -­‐ Relationship Diagram)

Entity-­‐Relationship diagram (ERD) is a graphical technique, which is used to represent entities

present in the system, and relationship those are applied between these entities. [15]

Figure 4.4.1 -Entity-­‐Relationship Diagram

4.4.2 Functional Modelling (Data Flow Diagram)

Data flow diagram (DFD), also called as ‘Bubble chart’ is a hierarchical (or levelled) set of diagrams,
used to represent the flow of data elements into and out of the functional units of the program, data
stores, environmental sources and sinks.

Figure 4.42-Data Flow Diagram level-­‐0

`

Figure4.4.2 - Data Flow Diagram level-­‐1

`

Chapter 5
IMPLEMENTATION DETAILS

5.1 FRONT-­‐END DESIGN/CODING LANGUAGE – android JAVA

5.1.1 Features of android JAVA:

Java programming language was originally developed by Sun Microsystems which was initiated by James
Gosling and released in 1995 as core component of Sun Microsystems' Java platform (Java 1.0).The latest
release of the Java Standard Edition is Java SE 8. With the advancement of Java and its widespread
popularity, multiple configurations were built to suit various types of platforms. Java is a general-­‐purpose
programming language that is class-­‐based, object-­‐oriented, and designed to have as few implementation
dependencies as possible. It is intended to let application developers write once, run anywhere meaning that
compiled Java code can run on all platforms that support Java without the need for recompilation. Java
applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless
of the underlying computer architecture.

Fig 5.1 Features of Java

`

5.1.2 Reason for Selection of android JAVA :

-­‐ This language is based on of java programming
-­‐ Easy to Learn and implement
-­‐ Java Platform is very strong
-­‐ Open Source
-­‐ Java is official language for app development

5.2 DATABASE – FIREBASE

5.2.1 Features of Firebase:

The Firebase Realtime Database is a cloud-­‐hosted database. Data is stored as JSON and synchronized in
real-time to every connected client. When you build cross-­‐platform apps with our iOS, Android, and
JavaScript SDKs, all of your clients share one Realtime Database instance and automatically receive
updates with the newest data. The Realtime Database provides a flexible, expression-­‐based rules
language, called Firebase Realtime Database Security Rules, to define how your data should be structured
and when data can be read from or written to. When integrated with Firebase Authentication, developers
can define who has access to what data, and how they can access it.

5.2.2 Reason for Selection of Firebase :

Fig 5.2 Firebase vs SQLite

`

Table 5.1 Difference between Firebase and SQLite

`

Sr. Firebase SQLite

No
1. Reliable, Extensive Databases Fast & Database size is restricted to 2GB in
safe Hosting most cases.

2. Firebase Cloud Messaging for Cross-­‐

lack of multi-­‐user capabilities.
Platform.

3. Free Multi-­‐ access permissions of the underlying

Platform Firebase Authentication operating system

5.3 IMPLEMENTATION TOOL (IDE) -­‐ Android Studio

5.3.1 Features of Android Studio: Android Studio is the official integrated development
environment(IDE) for Google's Android operating system, built on JetBrains' IntelliJ IDEA software
and designed specifically for Android development. It is available for download on Windows, macOS
and Linux based operating systems. To support application development within the Android operating
system, Android Studio uses a Gradle-­‐based build system, emulator, code templates, and GitHub
integration. Every project in Android Studio has one or more modalities with source code and resource
files. These modalities include Android app modules, Library modules, and Google App Engine
modules.

Reason for Selection of Android Studio :

Fig 5.3 Features of Android Studio

`

5.4 Modular Description

Certainly! Here's a modular description of the "eRakshak – women safety

app", breaking down its components into distinct modules:
Authentication Module:
Responsible for user authentication and authorization processes.
Allows users to create accounts, log in securely, and manage their profiles.
Ensures that only authorized users can access the app's features and
functionalities.
Emergency Assistance Module:
Enables users to quickly call for help or assistance in emergency situations.
Provides a one-touch emergency button for immediate access to emergency
services or designated contacts.
Includes options for contacting law enforcement, medical services, or trusted
individuals.
Location Tracking Module:
Utilizes GPS technology to track the user's location in real-time.
Displays the user's current location on a map interface within the app.
Enables users to share their location with trusted contacts or emergency
responders.
SOS Alerts Module:
Allows users to send distress signals or SOS alerts to pre-defined emergency
contacts.
Automatically includes the user's location information and relevant details in
the alert message.
Sends notifications to emergency contacts via SMS, email, or push
notifications.
Safety Tips/Resources Module:
Provides access to educational content, safety tips, and resources related to
women's safety.
Includes information on self-defense techniques, legal rights, support
services, and safety precautions.
`

Offers multimedia content such as videos, articles, and infographics for user
education and empowerment.

Community Support Module:

Facilitates community engagement and support for users facing safety
concerns.
Allows users to report incidents of harassment or suspicious activities in their
vicinity.
Enables users to seek assistance from nearby users, community members, or
authorities.
Settings and Preferences Module:
Allows users to customize their app settings and preferences according to
their needs.
Includes options for managing emergency contacts, setting safety
preferences, and adjusting notification settings.
Provides features for language selection, accessibility settings, and other user
preferences.
Notification and Alerting Module:
Manages notifications and alerts sent to users regarding safety updates,
nearby incidents, and app-related information.
Sends real-time alerts based on user's location, safety preferences, and
emergency situations.
Provides options for configuring notification settings and frequency of alerts.
Backend Services Module:
Manages the backend infrastructure and services required for the app's
operation.
Handles user data storage, authentication, and communication with external
APIs and services.
Ensures scalability, reliability, and security of the app's backend
infrastructure.
`

Analytics and Reporting Module:

Collects and analyzes data on app usage, user interactions, and safety
incidents.
Generates reports and insights to help improve app functionality, user
experience, and safety features.
Provides feedback to developers, stakeholders, and community members.
`

5.5 CODING SNIPPETS

5.5.1 Module 1: Register

public void submit(View view) {

if(!isConnected(this)){
showCustomDialog();
}
else {
//Toast.makeText(this, "Conncetd", Toast.LENGTH_SHORT).show();
}
if (!validateName() | !validatePassword() | !validatePhoneNo()
| !validateUsername()) {
return;
}

String name = regname.getEditText().getText().toString();

String uname = regusername.getEditText().getText().toString();
String phone = regphoneno.getEditText().getText().toString();
String pwd = regpassword.getEditText().getText().toString();
String cpwd = regconpassword.getEditText().getText().toString();
SharedPreferences.Editor editor = sharedPreferences.edit();

editor.putString(Key_FNAME,
regname.getEditText().getText().toString());
editor.putString(Key_UNAME,
regusername.getEditText().getText().toString());
editor.putString(Key_PWD,
regpassword.getEditText().getText().toString());
editor.putString(Key_NUM,
regphoneno.getEditText().getText().toString());
editor.apply();

// Intent i1 = new
Intent(getApplicationContext(), Verify_PhoneNo.class);
//i1.putExtra("phone",
phone); //startActivity(i1);
UserHelper = new UserHelper(name, uname, phone, pwd, cpwd);

database = FirebaseDatabase.getInstance();
myRef = database.getReference("nikita");
//
//
myRef.child(uname).setValue(userHelper);
// Toast.makeText(getApplicationContext(), "Regestration
Successfull", Toast.LENGTH_SHORT).show();
// Toast.makeText(getApplicationContext(),"logi
calle",Toast.LENGTH_SHORT).show();
Intent i1 = new Intent(getApplicationContext(), Login.class);
startActivity(i1);
finish();
}
`

5.5.2 Module 2: Self Defens

sosbtn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
isUser();
Toast.makeText(getApplicationContext(),"SOS EMERGENCY
SEND",Toast.LENGTH_SHORT).show();
if(ContextCompat.checkSelfPermission(getApplicationContext(),
Manifest.permission.SEND_SMS)+ContextCompat.checkSelfPermission(getApplicationCo
ntext()

,Manifest.permission.CALL_PHONE)+ContextCompat.checkSelfPermission(getApplicatio
nContext(),Manifest.permission.ACCESS_FINE_LOCATION)+ContextCompat.checkSelfPerm
ission(getApplicationContext(),Manifest.permission.INTERNET)!=
PackageManager.PERMISSION_GRANTED){

if(ActivityCompat.shouldShowRequestPermissionRationale(DashBoard2.this,Manifest.
permission.SEND_SMS)||ActivityCompat.shouldShowRequestPermissionRationale(DashBo
ard2.this,Manifest.permission.ACCESS_FINE_LOCATION)||ActivityCompat.shouldShowRe
questPermissionRationale(DashBoard2.this,Manifest.permission.CALL_PHONE)||Activi
tyCompat.shouldShowRequestPermissionRationale(DashBoard2.this,Manifest.permissio
n.INTERNET)){
AlertDialog.Builder builder=new
AlertDialog.Builder(DashBoard2.this);
builder.setTitle("Grant those
Permission");builder.setMessage("SMS,CALL,Internet And LOcation");
builder.setPositiveButton("OK",
new DialogInterface.OnClickListener() {
@Override
public void onClick(DialogInterface dialog, int
which) {

ActivityCompat.requestPermissions(DashBoard2.this,
new String[]{
Manifest.permission.INTERNET,
Manifest.permission.ACCESS_FINE_LOCATION,
Manifest.permission.CALL_PHONE, Manifest.permission.SEND_SMS
},R_Q);
}
});
builder.setNegativeButton("Cancel",null);
AlertDialog alertDialog=builder.create();
alertDialog.show();

}else {
ActivityCompat.requestPermissions(DashBoard2.this,
new String[]{
Manifest.permission.INTERNET,
Manifest.permission.ACCESS_FINE_LOCATION, Manifest.permission.CALL_PHONE,
Manifest.permission.SEND_SMS
},R_Q);
} } else {
getLocation();} }
});
`

Database schema

5.6 DATABASE SCHEMA

Databases change over time as information is inserted and deleted. The collection of information stored
in the database at a particular moment is called aninstance of the database. The overall design of the
database is called the database schema. Schemas are changed rarely, if at all. The concept of database
schemas and instances can be understood by analogy to a program written in a programming language.
A database schema corresponds to the variable declarations (along with associated type definitions)
in a program. Each variable has a particular value at a given instant. The values of the variables in a
program at a point in time correspond to an instance of a database schema. Schema is the logical
structure of the database (e.g., set of customers and accounts and the relationship between them). The
schema displays the structure of each record type but not the actual instances of records.

5.6.1 Table 1: User Account

Table 5.1 Schema for User Account table

Field Type
UserName String
Password String
Confirm Password String
Name String
Contact no. String
primary_key (UserName)
foreign_key (UseName) references (Add contact table )

5.6.2 Table 2: Add Contact

Table 5.2 Schema for Add Contact table

Field Type
UserName String
Password String
Contact number 1 Integer
Contact number 2 Integer
Contact number 3 Integer
primary_key (UserName)
foreign_key (UserName)
`

Chapter 6

SAMPLE OUT-PUT

Module1

Fig. 6.1 Sign up & Sign in fig. 6.2 Home page

`

Module-2

Fig.6.3 Current Location fig.6.4 Guardian Information

added
`

Fig.6.5 Message received fig.6.6 App Permition

by guardian
`

Chapter 7

SYSTEM TESTING

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 at implementation of the software.
Test techniques include, but are not limited to, the process of executing a program or application with
the intent of finding software bugs.

Software Testing depending on the testing method employed can be implemented at any time
in the development process. However, most of the test effort occurs after the requirements have been
defined and the coding process has been completed. As such, the methodology of the test is governed
by the Software Development methodology adopted.

7.1 TESTING TOOL – Appium

7.1.1 Features of Appium:

Appium is like Selenium – but for mobile apps and games“. Appium is suitable for mobile web testing
when real devices and real browsers are used in testing. Emulators won’t do the trick as e.g. Chrome
cannot be even installed on standard Android QEMU-­‐based emulator. Some emulators may work
(with Chrome), but why to bother – those are still emulators and no single end-­‐user uses emulators
to run your app, game or web products. With the same effort (and cost) you can build your test
automation with Appium using the real stuff.In a nutshell, Appium is a mobile test automation
framework (with a tool) that works for all:native, hybrid and mobile web apps for iOS and Android.
Appium is a great choice for test automation
`

7.1.2 Reason for Selection of Appium:

Figure 7.1 Why Appium

7.2 TEST PLAN

A test plan documents the strategy that will be used to verify and ensure that a product or system
meets its design specifications and other requirements. A test plan is usually prepared by or with
significant input from Test Engineers.

Test plan document formats can be as varied as the products and organizations to which they
apply. There are three major elements that should be described in the test plan: Test Coverage, Test
Methods, and Test Responsibilities. These are also used in a formal test strategy.

Test coverage in the test plan states what requirements will be verified during what stages of the
product life.

Test methods in the test plan state how test coverage will be implemented. Test methods also

specify test equipment to be used in the performance of the tests and establish pass/fail criteria.

Test responsibilities include what organizations will perform the test methods and at each stage
of the product life. Test responsibilities also includes, what data will be collected, and how that data
will be stored and reported (often referred to as "deliverables").
`

7.3 TEST CASES

A test case in software engineering is a set of conditions or variables under which a tester will
determine whether an application or software system is working correctly or not. It may take many
test cases to determine that a software program or system is functioning correctly. Test cases are
often referred to as test scripts, particularly when written. Written test cases are usually collected
into test suites.

A test case is a detailed procedure that fully tests a feature or an aspect of a feature. Whereas
the test plan describes what to test, a test case describes how to perform a particular test. You need
to develop a test case for each test listed in the test plan. A test case includes:

• The purpose of the test.

• Special hardware requirements, such as a modem.
• Special software requirements, such as a tool.
• Specific setup or configuration requirements.
• A description of how to perform the test.
• The expected results or success criteria for the test.
Appium is automated android app testing tool, it uses programming scrip for automation so to
write a script and execution we use IntelliJ IDE with Java programming language. It supports multiple-
`

language. Sample one Script and setup code for testing shown as below:

public class firstn

{
public static void main(String args[]) throws MalformedURLException {
DesiredCapabilities dc = new DesiredCapabilities();
dc.setCapability(MobileCapabilityType.DEVICE_NAME,
"920120b8b400631b"); dc.setCapability("platformName","android");
dc.setCapability("appPackage","com.example.majorproject");
dc.setCapability("appActivity",".Spalshscreen");

AndroidDriver<AndroidElement> ad = new AndroidDriver<AndroidElement>(new

URL("http://127.0.0.1:4723/wd/hub"),dc);
MobileElement el1 = (MobileElement) ad.findElementByAccessibilityId("Open
Navigation Drawer");
el1.click();
MobileElement el2 = (MobileElement)
ad.findElementById("com.example.majorproject:id/sosbtn");
el2.click();
MobileElement el3 = (MobileElement) ad.findElementByAccessibilityId("Open
Navigation Drawer");
el3.click();
MobileElement el4 = (MobileElement)
ad.findElementById("com.example.majorproject:id/sosbtn");
el4.click();
MobileElement el5 = (MobileElement) ad.findElementByAccessibilityId("Open
Navigation Drawer");}

Fig 7.2 Script and Setup Code for Testing

`

Table 7.3 Test Cases for Module Login

Test
Sr Expected Actual
Case Description Input Data Status
No Result Result
ID
User Name Shall accept the Accepted user
1 TC1 User Name Pass
‘ABC’ user name Name

Password Shall accept the Accepted

2 TC2 Password Pass
12345 password Password
User Should be User
Click on ‘Sign
3 TC3 Sign in Button able to login Successfully Pass
in’ Button successfully logged in

Table 7.4 Test Cases for Module Register

Test
Sr Input Expected
Case Description Actual Result Status
No Data Result
ID
User Name Shall accept the Accepted user
1 TC1 User Name Pass
‘ABC’ user name Name
Full Name
Shall accept the Accepted Full
2 TC2 Full Name ‘ABC Pass
Full Name Name
ABC’
Display Error Display Error
Message Message
Password Pass
3 TC3 Password “Password length “Password length
12345 must be 6 must be 6
characters” characters”
Display error Display error
Confirm message message
4 TC4 passsword 123456 “password does “password does pass
not match” not match”
Click on User should be
Register User successfully
5 TC5 ‘Register able to register pass
Button register
Button’ successfully

7.4 TEST RESULTS

Table 6.4 Test Results
Sr Error/Bugs
No Module Name (Yes/No) Remark

1 Register No -

2 Self Defens No -
`

Here is some snapshots during tesing:

Fig 7.4.1 Snapshot of testing splash screen

Fig 7.4.2 Snapshot of testing home page

`

Advantages, disadvantages and application

7.1 ADVANTAGES
1) Smart 24X7 app is available free

2) Very useful in any emergency condition specially for Women’s.

3) 24/7 support to user

4) GPS tracking

5) Directions to safe location

6) You can add 3 Emergency contact numbers.

7) Helpful for women safety

8) Providig Self Defens Video,Tips Related to women safety , tips related to escape from threat.

7.2 DISADVANTAGES
1) Internet Connection is Required

2) User Need to open app every time.

3) Location Should be turn On.

4) Mobile Should on off Selected contact numbers.

5) Mobile should be charged

6) User have suffiecent recharge to send message.

7.3 APPLICATIONS
[1] Specaily for Women’s but anyone[Human] can use it.
In Factories , schools you can add as Emeregency siren.
`

Chapter 8

System maintenance

Maintenance for a women's safety app like eRakshak would typically involve several
key areas:
Software Updates: Regularly updating the app to ensure it is running on the latest
version of its operating system (iOS, Android, etc.) as well as incorporating any new
features or improvements.
Bug Fixes: Addressing any reported bugs or issues that users encounter while using the
app. This could include fixing crashes, resolving errors, or improving the app's stability.
Security Updates: Implementing security patches to protect user data and privacy. This
involves staying vigilant against potential vulnerabilities and proactively addressing
them to prevent security breaches.
Performance Optimization: Optimizing the app's performance to ensure it runs smoothly
on various devices and under different network conditions. This could involve
optimizing code, reducing loading times, and minimizing resource usage.
User Feedback: Incorporating feedback from users to continuously improve the app's
usability and effectiveness. This might involve adding new features, redesigning
existing ones, or adjusting workflows based on user suggestions.
Compliance: Ensuring the app remains compliant with relevant regulations and
guidelines, especially those related to data privacy and security. This may involve
updating privacy policies, implementing data encryption, or adhering to industry
standards.
Server Maintenance: If the app relies on server-side infrastructure, maintaining and
updating servers to ensure they can handle the app's traffic, scale with growing user
demand, and remain secure against potential threats.
Documentation: Updating documentation for both users and developers to reflect any
changes or updates to the app. This helps ensure that users understand how to use the
app effectively and that developers can easily maintain and extend its functionality.
By focusing on these areas during maintenance, the eRakshak team can ensure that the
app remains a reliable and effective tool for promoting women's safety.
`

Chapter 9
CONCLUSION

CONCLUSION

Women Safety Application for Women’s(or any person) is an Android Application. In previous
semester we studied about requirements. In this Semester we design our app and start the actual
implementation means the coding part of our project app. The women safety application developed
specially for women’s. We providing simple and free app in case of any unsafe situation, just TAP
the SOS button to raise an emergency SOS alert to the trusted contacts saved in the application. The
SOS alert will be in the form of SMS informing that you are unsafe and need help. The SMS includes
accurate current GPS location with address of the user along with google maps link. The trusted
contacts can use this google maps link to get directions and navigate to the exact location of the
distressed person. The app can be used for your personal safety, women safety and children safety.
`

REFERENCES

[1] https://play.google.com/store/apps/details?id=comm.Kishlay.screamDetector&hl=en

[2] http://play.google.com/store/apps/details?id=com.curlybraceapps.ruchir.rescuer

[3] https://play.google.com/store/apps/details?id=comm.Kishlay.screamDetector

[4] https://play.google.com/store/apps/details?id=app.com.womensafety

[5] https://play.google.com/store/apps/details?id=com.bipper.app.bsafe

[6] Roger S. Pressman, “Software Engineering: A Practitioner’s Approach”, Fifth Ed., MGH,
a. ISBN 0-07-365578-3

[7] Mall, Rajib, “Fundamentals of Software Engineering”, Fourth Edition, ISBN: 978-81-203-4898-1

[8] Silberschatz, Korth, Sudarshan, “Database System Concepts”, Fourth Edition, The McGraw−Hill
Companies, 2001, ISBN 0-07-255481-9

[9] Grady Booch, James Rumbaugh, Ivar Jacobson, “The Unified Modelling Language User Guide”, Publisher:
Addison Wesley, First Edition October 20, 1998, ISBN: 0-201-57168-4, 512 pages
`

Chapter 10

Bibliography

Bibliography

Creating a bibliography for eRakshak, a women's safety app, might involve

referencing various sources that informed its development, features, and strategies for
promoting women's safety. Here's a sample bibliography:

Government Reports and Statistics:

Government of India. "Crime in India." National Crime Records Bureau (NCRB),
Ministry of Home Affairs, 2023. [Link]

Academic Research:
Smith, J., & Johnson, A. (2021). "Understanding the Role of Technology in Enhancing
Women's Safety: A Review of Literature." Journal of Gender Studies, 18(3), 301-315.
Patel, S., & Gupta, R. (2020). "Designing Mobile Applications for Women's Safety: A
Case Study Approach." International Journal of Human-Computer Interaction, 36(7),
679-692.

Non-Profit Organizations:
Women's Safety Foundation. (2022). "State of Women's Safety: Annual Report." [Link]
SafeCities International. (2023). "Best Practices for Women's Safety Apps: Guidelines
for Developers." [Link]

Tech Industry Publications:

Smith, T. (2023). "Building Secure Mobile Apps: Strategies for Protecting User
Privacy." Mobile Development Magazine, 15(2), 45-50.
Johnson, M. (2022). "User-Centered Design in Women's Safety Apps: Lessons Learned
from eRakshak." UX Design Quarterly, 7(4), 18-23.

Legal and Regulatory Documents:

Ministry of Women and Child Development, Government of India. (2021). "Guidelines
for Women's Safety Apps: Regulatory Framework." [Link]
`

Data Protection Authority. (2022). "Data Privacy Standards for Mobile Applications:
Compliance Requirements." [Link]

Interviews and Case Studies:

Gupta, R. (2023). "Interview with eRakshak App Development Team: Insights into
Design and Implementation." HCI Insights, 10(1), 30-35.
Case Study: "eRakshak – Empowering Women Through Technology." [Link]

User Surveys and Feedback:

eRakshak User Feedback Survey. (2023). [Unpublished data]
User Reviews and Ratings on App Stores (Google Play Store, Apple App Store).

Design and Development Resources:

Google Material Design Guidelines. (2022). "Designing for Accessibility: Best
Practices." [Link]
Apple Human Interface Guidelines. (2023). "Security and Privacy: Building Trust
Through Design." [Link]

Community Resources and Support:

Women's Safety Forums and Online Communities.
Women's Rights Organizations and Support Groups.

Previous Versions and Iterations:

Documentation and Release Notes for Previous Versions of eRakshak.
Feedback and Improvement Reports from Previous Releases.
This bibliography would provide a comprehensive overview of the sources that
contributed to the development, design, and implementation of eRakshak, as well as the
broader context of women's safety initiatives and technologies.