Project Approval

PROJECT APPROVAL

Project Title: Smarillance

By:
Hira Danish
Somia Anjum
Mahnoor Muzammial

Approval Committee:

___________________________
Name: Ms Ummay Faseeha
Designation: Assistant Professor

___________________________
(Internal Advisor)

___________________________
(Head of the Department)

DEPARTMENT OF COMPUTER SCIENCE AND SOFTWARE ENGINEERING

JINNAH UNIVERSITY FOR WOMEN

i
Abstract

ABSTRACT
Providing safe and secure environment to the humanity is one of the biggest challenges.
People are not safe roaming around whether it is day or night especially for girls and
women; they don’t find them safe anywhere. To address the security and safety issues,
an android based security application is proposed for women. The application will be
started with utmost ease by clicking on the tab situated in the alert button which
identifies the location through GPS/GSM network and alert through SMS containing
geographical coordinates to the listed contacts and also auto dial a call to the listed
contact for the help in case of dangerous situation.
Our framework will be founded on a GPS and GSM based "ladies security
framework", which give alarms and messages on tapping the button on the cell
phone. At whatever point, if somebody is in a tough situation they probably won't
have so much time, all that they need to do is tap the portable. Our framework gives
a feasible, financially savvy answer for issue recognition (Khir, 2015) [1].
Presently a days on account of as of late happened cases like assault by drivers or
associates, thievery and so on. Ladies security, particularly ladies security has
become the premier need of the planet. Framework utilizes the Global Positioning
System (GPS) innovation to discover the area of ladies. The data of ladies position
gave by the gadget are frequently seen on Google maps utilizing Internet. The
salient feature of this application is a panel of emergency numbers which responds on
the spot. Live tracking via SMS help to locate a person swiftly and can be rescued
without harm.

ii
Table of Contents

TABLE OF CONTENTS

PROJECT APPROVAL ................................................................................................................................ i

ABSTRACT ................................................................................................................................................ ii

TABLE OF CONTENTS ............................................................................................................................. iii

TABLE OF FIGURES ................................................................................................................................ vii

ACKNOWLEDGMENT............................................................................................................................. viii

CHAPTER 1 PROJECT OVERVIEW ......................................................................................................... 1

1.1 INTRODUCTION ............................................................................................................................ 1

1.2 PROJECT OBJECTIVES ................................................................................................................. 1

1.3 PROJECT DELIVERABLES ............................................................................................................ 1

1.4 SUMMARY OF RESEARCH PAPERS .............................................................................................. 2

CHAPTER 2 SOFTWARE REQUIREMENT SPECIFICATION (SRS) .......................................................... 3

2.1 PURPOSE ...................................................................................................................................... 3

2.2 PRODUCT SCOPE .......................................................................................................................... 3

2.3 OVERALL DESCRIPTIONS:............................................................................................................ 3

2.3.1 PRODUCT PERSPECTIVE ........................................................................................................ 3

2.3.2 PRODUCT FUNCTIONS ........................................................................................................... 4

2.3.3 USER CLASSES AND CHARACTERISTICS ............................................................................... 4

2.3.4 OPERATING ENVIRONMENT .................................................................................................. 5

2.3.5 DESIGN AND IMPLEMENTATION CONSTRAINTS ................................................................... 5

2.3.6 USER DOCUMENTATION ........................................................................................................ 5

2.3.7 ASSUMPTION AND DEPENDENCIES ........................................................................................ 5

2. 4 SYSTEM FEATURES ...................................................................................................................... 6

2.4.1 REGISTER CONTACTS ........................................................................................................... 6

iii
Table of Contents

2.4.2 CURRENT MAP ...................................................................................................................... 6

2.4.3 EMERGENCY ALERT.............................................................................................................. 6

2.4.4 HELPING CONTACTS ............................................................................................................. 6

2.4.5 ALERT NOTIFICATIONS ......................................................................................................... 6

2.5 FUNCTIONAL REQUIREMENTS ..................................................................................................... 6

2.6 OTHER NONFUNCTIONAL REQUIREMENTS ................................................................................. 7

2.6.1 EFFICIENCY ........................................................................................................................... 7

2.6.2 USABILITY ............................................................................................................................. 7

2.6.3 RELIABILITY.......................................................................................................................... 7

2.6.4 LEARNABILITY ...................................................................................................................... 7

2.6.5 MAINTAINABILITY ................................................................................................................ 7

2.6.6 OPERATES IN ANDROID-BASED PLATFORM ......................................................................... 7

2.6.7 PERFORMANCE REQUIREMENTS: ......................................................................................... 7

2.7 SOFTWARE QUALITY ATTRIBUTES .............................................................................................. 8

2.7.1 CORRECTNESS ....................................................................................................................... 8

2.7.2 EXTENSIBILITY ...................................................................................................................... 8

2.7.3 TESTABILITY ......................................................................................................................... 8

2.7.4 INTEGRITY ............................................................................................................................. 8

2.7.5 INTEROPERABILITY ............................................................................................................... 8

2.8 BUSINESS RULES........................................................................................................................... 8

CHAPTER 3 SYSTEM ANALYSIS AND DESIGN........................................................................................ 9

3.1 RELATIONAL DIAGRAM ............................................................................................................... 9

3.2 UML DIAGRAMS ........................................................................................................................ 10

3.2.1 USE CASE DIAGRAM............................................................................................................ 10

3.2.2 ACTIVITY DIAGRAM ............................................................................................................ 11

iv
Table of Contents

3.2.3 CLASS DIAGRAM ................................................................................................................. 12

3.2.4 ENTITY RELATIONSHIP DIAGRAM........................................................................... 13

3.2.5 DATA FLOW DIAGRAM........................................................................................................ 14

CHAPTER 4 TOOLS AND TECHNOLOGIES ........................................................................................... 15

4.1 SOFTWARE TOOLS & TECHNOLOGY ......................................................................................... 15

4.1.1 ANDROID STUDIO ................................................................................................................ 15

4.1.2 FIREBASE ............................................................................................................................. 15

4.1.3 GOOGLE MAP SERVICES ...................................................................................................... 15

4.1.4 HYPERTEXT PREPROCESSOR (PHP) .................................................................................. 15

4.1.5 SUBLIME TEXT EDITOR....................................................................................................... 15

4.1.6 JAVASCRIPT/ES6 ................................................................................................................. 15

4.1.7 XAMMP ............................................................................................................................. 15

4.2 DESIGNING TOOLS ..................................................................................................................... 16

4.2.1 JUST IN MIND....................................................................................................................... 16

4.2.2 PHOTOSHOP ......................................................................................................................... 16

4.2.3 JQUERY ............................................................................................................................... 16

4.2.4 BOOTSTRAP FRAMEWORK .................................................................................................. 16

4.2.5 Html 5 & Css (Cascading Style Sheet) ............................................................................. 16

4.3 DOCUMENTATION TOOLS .......................................................................................................... 16

4.3.1 MS WORD............................................................................................................................ 16

4.3.2 CREATELY UML DIAGRAM ................................................................................................ 17

CHAPTER 5 USER INTERFACE DESIGN .............................................................................................. 18

5.1 WEB APPLICATION INTERFACES: ............................................................................................. 18

5.2 MOBILE APPLICATION INTERFACES ......................................................................................... 21

CHAPTER 6 METHODOLOGY............................................................................................................... 30

v
Table of Contents

6.1 METHODOLOGY USED FOR IMPLEMENTATION ........................................................................ 30

6.1.1 INTRODUCTION ..................................................................................................................... 30

6.1.2 REASON TO USE SCRUM IN SMARILLANCE ......................................................................... 30

6.2 SMARILLANCE LIFE CYCLE MODEL ......................................................................................... 31

CHAPTER 7 IMPLEMENTATION ........................................................................................................... 32

7.1 DATA BASE DESIGN.................................................................................................................... 32

7.2 WEB SERVICES ........................................................................................................................... 32

7.2.1 CLIENT SIDE SERVICES ....................................................................................................... 32

7.3 WEBSITE DESIGN ....................................................................................................................... 32

7.4 MOBILE APPLICATION ............................................................................................................... 33

7.5 WEB APPLICATION..................................................................................................................... 34

7.6 DEPLOYMENT ............................................................................................................................. 34

7.6.1 MOBILE APPLICATION DEPLOYMENT ................................................................................ 34

CHAPTER 8 TESTING ........................................................................................................................... 35

8.1 INTRODUCTION........................................................................................................................... 35

8.2 OBJECTIVES................................................................................................................................ 35

8.3 UNIT TESTING ............................................................................................................................ 35

8.4 INTEGRATION TESTING .............................................................................................................. 35

8.5 TESTING APPROACH .................................................................................................................. 35

8.6 TEST CASES ................................................................................................................................. 35

8.4 MOBILE APPLICATION TESTING................................................................................................ 40

CONCLUSION ..................................................................................................................................... 41

APPENDIX A ........................................................................................................................................... 41

GLOSSARY .......................................................................................................................................... 41

REFERENCES .......................................................................................................................................... 45

vi
Table of Figures

TABLE OF FIGURES

Figure 3-1 Relational Diagram ................................................................................................................. 9

Figure 3-2 Use case Diagram ................................................................................................................. 10
Figure 3-3 Activity Diagram .................................................................................................................. 11
Figure 3-4 Class Diagram....................................................................................................................... 12
Figure 3-5 Entity Relationship Diagram ................................................................................................ 13
Figure 3-6 DFD Level 0 ......................................................................................................................... 14
Figure 3-7 DFD Level 1 ......................................................................................................................... 14
Figure 5-1 Admin Login......................................................................................................................... 18
Figure 5-2 Dashboard ............................................................................................................................. 18
Figure 5-3 Edit Users ............................................................................................................................. 19
Figure 5-4 Delete Users .......................................................................................................................... 19
Figure 5-5 Generated Alerts ................................................................................................................... 20
Figure 5-6 User Reports ......................................................................................................................... 20
Figure 5-7 Logout panel ......................................................................................................................... 21
Figure 5-8 Splash Screen ........................................................................................................................ 21
Figure 5-9 Create Account ..................................................................................................................... 22
Figure 5-10 Login................................................................................................................................... 22
Figure 5-11 Dashboard ........................................................................................................................... 23
Figure 5-12 Registration ......................................................................................................................... 23
Figure 5-13 Alert .................................................................................................................................... 24
Figure 5-14 Help .................................................................................................................................... 24
Figure 5-15 Police Location ................................................................................................................... 25
Figure 5-16 Admin Alert ........................................................................................................................ 25
Figure 5-17 Guidance ............................................................................................................................. 26
Figure 5-18 Homepage ........................................................................................................................... 27
Figure 5-19 How it Work ....................................................................................................................... 27
Figure 5-20 Features ............................................................................................................................... 28
Figure 5-21 App Screenshots ................................................................................................................. 28
Figure 5-22 Contact Us .......................................................................................................................... 29
Figure 5-23 Team ................................................................................................................................... 29
Figure 8-1 Message Alert ....................................................................................................................... 40
Figure 8-2 Tracking ................................................................................................................................ 40

vii
Acknowledgment

ACKNOWLEDGMENT
Firstly we would like to thank Almighty who has given us a wonderful Department who
is always behind us no matter what situation it is. He is the one who is showing us the
right direction to follow noble path of kindness.

Department of Computer Science and Software Engineering, Jinnah University for

Women, where we have opportunity to work under the excellent and supportive staff.
We feel great pleasure in submitting this report on the project, “Smarillance”. We
would like to take this opportunity to express our thankfulness to our project guide, Ms
Ummay Faseeha for this support and constant encouragement along with this expert
guidance that helped us to complete the project successfully.

We wish to express our sincere thanks to our chairperson (Ms Narmeen Bawany),
internal advisor (Ms Ummay Faseeha) and all Final year project committee teachers,
for their patience, enthusiasm, intuitive comments, invaluable suggestions, helpful
information, practical advice and unceasing ideas which have helped us tremendously
at all times in our project. Their immense knowledge, profound experience and
professional expertise in IT field has enabled us to complete our project successfully.
We are thankful to them for their precious time in guiding us, answering our queries,
correcting and improving the skills in our project. Without their guidance and relentless
help, this project would not have been possible.

Thanks for all your encouragement

viii
Project Overview

Chapter 1 PROJECT OVERVIEW

1.1 INTRODUCTION
Women’s security might be an important issue in this era and it's significantly
required for every person to be acting over such an issue. Our framework will be
founded on a GPS and GSM based "ladies security framework" that gives the
combination of GPS gadget, which give alarms and messages on tapping the button
on the cell phone. At whatever point, if somebody is in a tough situation they
probably won't have so much time, all that they need to do is tap the portable. Our
framework gives a feasible, financially savvy answer for issue recognition.
Presently a days on account of as of late happened cases like assault by drivers or
associates, thievery and so on. Ladies security, particularly ladies security has
become the premier need of the planet. Framework utilizes the Global Positioning
System (GPS) innovation to discover the area of ladies. The data of ladies position
gave by the gadget are frequently seen on Google maps utilizing Internet. The IT
organizations are anticipating the security issue and requires a framework that will
productively assess the issue of ladies security working in night shifts, voyaging
alone. We centers around the proposed model which won’t influence the matter of
security issue of young ladies utilizing GPS and GSM based global positioning
framework.

1.2 PROJECT OBJECTIVES

The main objective of the system is to provide the security to our women through
mobile application. They will be tracked by their family members and friends,
whenever they find any unusual thing the woman can press the button in an app through
which their family members will be informed about her.

1.3 PROJECT DELIVERABLES

To build up a framework for android clients for keeping track through application. This
application utilizes GPS for identifying the area of the individual in a tough situation
and the framework can be divided into two modules:
1. First module can be the user’s phone i.e the root gadget which utilizes 3G/2G
internet connection or SMS for tracking the area of the user through GPS.

1
 2. Second module are the registered contacts that can be either police or friends
which gets the alert containing URL of location an emergency SMS and a
call of victim that's sent from the root device.

1.4 SUMMARY OF RESEARCH PAPERS

Author/Title A Mobile Based Android Based Safety Personal Safety
Women Safety Triggering Application Triggering System On
Application- I Safe (P.Kalyanchakravarthy, Android Mobile Platform
Apps (Mandapati, Lakshmi et al. 2014) (Ramalingam, Dorairaj et
Pamidi et al. 2015) al.)
Operating System Android Android Android
Safety features  On one click,  The victim can  At the point when

individuals directly press the the alert button is

can alerts power. clicked, the

application detects
chosen  Victim can
that user is under
contacts legitimately tap
security danger and
 Shares the wellbeing trusts that the client
location triggering button will press the send
to trigger the button.
application.  On the off chance

 Sending the area that the client isn't

(latitude and intuitive to press the

catch subsequent to
longitude) to all
squeezing the crisis
pre-enlisted
button, the
phone numbers
framework
in the consequently counts
application. down for 14 seconds
and afterward begins
to get the area data
which contains the
scope and facilitates.

2
Software Requirement Specification (SRS)

Chapter 2 SOFTWARE REQUIREMENT

SPECIFICATION (SRS)

2.1 PURPOSE
While facing a potential dangerous circumstance, for example, seizing, robbing or even
theft, the user has next to no delay to think about the most ideal approach to escape
from the circumstance. However, mentioning for help is the most moment strategy for
the user to consider during the basic circumstance. Considering quick worry of
wellbeing issue, mobile applications execution might be reached out into individual
security procedures.
This proposed system is to acquire positive ramifications to the general public the issue
of mentioning for help during emergency circumstances (Kavita Sharma, 2016) [2].
Victim will encounter a more effective and quicker method for help by utilizing this
application as it executes to least technique for help mentioning by utilizing smart
phones.

2.2 PRODUCT SCOPE

The product has a great scope in upcoming future because the world is moving fast and
is depending on the technology everything is based on technology. We can make
something which will be helpful to everyone especially the women of our society.
The product has the following scope:
This application can be integrated with the law enforcement database in future, which
includes all the phone numbers of regional cops. Some use cases such as rescuing victim
when there is no mobile network after initial alert or switch off condition.

2.3 OVERALL DESCRIPTIONS:

2.3.1 PRODUCT PERSPECTIVE
Smarillance is the mobile and web-based product, which can be used by multiple users
i.e. the registered users and admin. This application product provide a user-friendly
interface where registered users can edit their information using their login IDs and can
mark their contacts and can notify them whenever they are in emergency or in trouble.

3
Software Requirement Specification (SRS)

2.3.2 PRODUCT FUNCTIONS

The Smarillance application system would have following basic function:
REGISTER
 The user can register themselves easily as a user.
LOGIN
 The system must able to provide an interface where a user enter their email and
password to sign up.
 The system must able to validate a user’s email and password, If he/she entered
the correct email and password the system will allow to enter the system and
perform their task.
 If user enter an incorrect email and password, the system will not allow the user
to enter into the system and allow the user to go from a forgotten password
option to retrieve a new password or email.
REGISTER CONTACTS

 A user can register their contacts by accessing the contacts in the phone.
CURRENT MAP

 A user will be having a map in which she can get the way to the nearest police
station.

EMERGENCY ALERT

 A user can send emergency alert to the registered contacts having an

emergency call, message and her current location so that they can rescue her
as soon as possible.
HELPING CONTACTS

 A user will be having a panel in which she can call the given emergency
numbers on tap for the rescue operations.
ALERT NOTIFICATIONS

 A user will get any emergency alerts send by the Admin.

2.3.3 USER CLASSES AND CHARACTERISTICS

The product can easily be used by any person but it is specifically designed for the
women as they commonly are unaware of routes and usually faces harassment as

4
Software Requirement Specification (SRS)

compared to men in a society. They can’t even walk alone through a busy street or
through a park freely without any care because of security issues and the increasing
numbers of crimes reporting, they always are in need of man who protect them.

2.3.4 OPERATING ENVIRONMENT

Platform: Android
Database: Firebase
2.3.5 DESIGN AND IMPLEMENTATION CONSTRAINTS
 The project will be mobile based application.
 The application must be implemented in Java.
 Users have to download the application on their phone in order to use it.
 The database will be generated on firebase.

2.3.6 USER DOCUMENTATION

The primary goal of Smarillance is to facilitate the user with easy functioning and
simple environment of the application so that user can achieve their various tasks. The
application is made with such a mind that will be easy for the user to understand every
task and to implement them effectively. For the help of the user, in this application we
have provided assistance through which they can help in every situation if user do not
understand.
Smarillance application system or product will include user manual for helping and
provide guidance about system to the users. The user manual would guide the user in a
step by step method which give an ease to the user in understanding the whole
application and it’s using facilities in a short time. The victim manual will incorporate
product outline, total design of the pre-owned software, techniques, backup
methodology and contact data which will incorporate email address. The system will
be compatible or operate with the following Web browsers: Google Chrome and
Internet Explorer.

2.3.7 ASSUMPTION AND DEPENDENCIES

Supposition that is something that you acknowledge as obvious beyond a shadow of a
doubt or confirmation. Presumption can essentially rely upon the information, current
data and designer experience. That includes:

5
Software Requirement Specification (SRS)

2.3.7.1 TECHNICAL ASSUMPTION

We are working on the latest software tools and technologies (for example
Android Studio 4.0).

2.3.7.2 BUSINESS ASSUMPTION

Product develops in the determined budget and covers all the project expenses,
so that user can purchase them easily in their budget.

2.3.7.3 ASSUMPTION ABOUT USER

Every person can easily use our all module without any difficulty because it is
user-Friendly.

2. 4 SYSTEM FEATURES
2.4.1 REGISTER CONTACTS
A user can register their contacts by accessing the contacts in the phone.

2.4.2 CURRENT MAP

A user will be having a map in which she can get the way to the nearest
police station.
2.4.3 EMERGENCY ALERT
A user can send emergency alert to the registered contacts having an emergency
call, message and her current location so that they can rescue her as soon as possible.

2.4.4 HELPING CONTACTS

A user will be having a panel in which she can call the given emergency
numbers on tap for the rescue operations.

2.4.5 ALERT NOTIFICATIONS

A user will get any emergency alerts send by the Admin.

2.5 FUNCTIONAL REQUIREMENTS

Functional requirements might be figuring, techniques, information control and
handling and other specific usefulness that define what a framework should achieve.
 Useful for the people who want to need information even when they are on the
move.
 Also it should provide access to various functions through Mobile.
 It will provide the user to get any notifications from the server at any time.
 It will give the flexibility to the user.
 It will allow the user to check the notifications.

6
 Software Requirement Specification (SRS)

 Maintains the information of different services.

 No manual intervention
 No time is consumed

2.6 OTHER NONFUNCTIONAL REQUIREMENTS

2.6.1 EFFICIENCY
The system will be efficient enough to perform tasks and returns the result in
minimum amount of time as it will take no time in responding.

2.6.2 USABILITY
The interface of mobile application must be accessible for every user rather than
intimidating and frustrating; it must be easy to use. As we have design it very simple
keeping the design principles in mind.

2.6.3 RELIABILITY
Smarillance must be reliable under load. It should not stop working when used in
real environment.

2.6.4 LEARNABILITY
The system will be easy to learn for user by its consistent and simple user interface.

2.6.5 MAINTAINABILITY
The data used at the back of the system must be maintained and updated time to time.

2.6.6 OPERATES IN ANDROID-BASED PLATFORM

Android is chosen as the development tool because it is more reliable compared to
other OS.

2.6.7 PERFORMANCE REQUIREMENTS:

The system will be efficient enough in performance that it will take no delay in
operating. Smarillance will be easy to access on any device.

2.6.8 SECURITY REQUIREMENTS

Security frameworks want database stockpiling simply like numbers of other
applications. Client approval and information encryption are significant security
prerequisites of the undertaking. Clients are giving their delicate information like
contact list and current location. This touchy information must be shielded from any

7
 Software Requirement Specification (SRS)

assaults or misfortune. Framework should store client information on database safely

and set access authorizations to these information cautiously.

2.7 SOFTWARE QUALITY ATTRIBUTES

2.7.1 CORRECTNESS
The system must be according to its specifications for correctness to satisfy the customers
need and must be appropriate to work independently. Smarillance provide you better and
easy interface which you can easily operate the application.

2.7.2 EXTENSIBILITY
Smarillance will be extensible so that the changes should be made without causing any
side effects and disturbance in its smooth working.

2.7.3 TESTABILITY
Smarillance have a modularize structure so that testing and debugging could easily be
done to monitor system behavior at different conditions.

2.7.4 INTEGRITY
The system integrity or security must be followed. Smarillance would be free from any
sort of viruses, privacy and data loss threats.

2.7.5 INTEROPERABILITY
Smarillance will be interoperable. Its modules should communicate well for data sharing
If needed.

2.8 BUSINESS RULES

 The user should have a valid Email Address.
 The user should know how to login or enter into the system.
 The user must be notified with the alert send by the admin panel.
 The user must register the contacts for an emergency situation.
 The user must tap the button to send the emergency alerts.
 The user must have the balance in her mobile.
 The registered contacts must be notified by the alerts send by the users.
 The emergency numbers must be notified by the alerts send by the user.
 The user must get the location of the nearest police station.

8
System Analysis and Design

Chapter 3 SYSTEM ANALYSIS AND DESIGN

3.1 RELATIONAL DIAGRAM

Figure 3-1 Relational Diagram

In the following relational diagram, we have three related entities, User, person
and Admin. To understand the relationship better we define the each entity.
User and person these two entity has one to many relationship as one person can
track many users.
Admin entity has one to many relationship because Person, and user has one admin
to manage all the activities of user and person.
Admin and person these two entity has one to many relationship as admin can send
many notification alerts to the user.

9
System Analysis and Design

3.2 UML DIAGRAMS

3.2.1 USE CASE DIAGRAM

Figure 3-2 Use case Diagram

In the above 1st use case diagram there is a user who can register, login and
can register the contact .After this she can send alert and can find herself too
police station. The second actor named person can interact with remaining
use cases .An emergency manage receiver can receive emergency call and
track the location.
Now in the above diagram there is only Admin. An admin can add user,
remove user and can send notification to the user.

10
System Analysis and Design

3.2.2 ACTIVITY DIAGRAM

Figure 3-3 Activity Diagram

An activity diagram is used by engineers to understand the flow of programs on a high

level. An Application runs in the background now user can face any emergency
situation so user can tap the button, so application can detect the current location of the
user and send emergency messages and call to the user. If the user doesn’t tap the button
in the application so, application does not work in the background and app doesn’t send
any emergency message to the marked ones.

11
System Analysis and Design

3.2.3 CLASS DIAGRAM

Figure 3-4 Class Diagram

In the proposed class diagram,

Users: User will be having a name, phone number, location and password and can
send the current location.
Person: person will be having a name, phone number and password and can check
the current location.
Admin: Admin will also have an id number, name and can edit the users

12
System Analysis and Design

3.2.4 ENTITY RELATIONSHIP DIAGRAM

Figure 3-5 Entity Relationship Diagram

In the following Entity Relationship diagram, we have three related entities, User,
Person and Admin. To understand the relationship better we define the each entity.
User and person these two entity has one to many relationship as one user can track
many person.
User and route these two entity has one to many relationship as one user mange
many routes.
Admin entity has one to many relationship because Person and user has one admin
to manage all the activities of user and person.
Admin and person these two entity has one to many relationship as admin can send
many notification to the user.

13
 System Analysis and Design

3.2.5 DATA FLOW DIAGRAM

Figure 3-6 DFD Level 0

Figure 3-7 DFD Level 1

Level-0 DFD explains that on the acknowledgment or on approaching the police or

the registered contact will get the alert.

Level-1 DFD explains that the user will first register the contact and on emergency
situation the user will send alert consisting of emergency message, current location
and call. So that the person can manage and rescue the user. We are also having the
current location and the help panel in our system.
Admin can delete and the user and can also send the alert to users.

14
Tools and Technologies

Chapter 4 TOOLS AND TECHNOLOGIES

4.1 SOFTWARE TOOLS & TECHNOLOGY

4.1.1 ANDROID STUDIO
Android Studio is Android's official IDE. Its motivation is to work for Android to
quicken your turn of events and help you assemble the highest-quality applications
for every Android gadget. It is used in developing the Mobile Application of our
project which is main in our project.

4.1.2 FIREBASE
Firebase is a mobile and web application stage that give engineers plenty of
administrations to help in growing excellent applications. The Firebase Real-time is
cloud-facilitated NoSQL information base that lets designer to store and matchup
between the users progressively. Mobile apps need a backend. They store settings &
data and generate statistics. Our whole Admin panel is being developed on the firebase
which will monitor the activity and keep the credentials private of every user.

4.1.3 GOOGLE MAP SERVICES

Google Maps is a Web-based service that gives detailed information about countries
and sites round the world. Google Map services are used to locate the user easily.
It has been used in a project to locate the user easily anywhere in emergency situation.

4.1.4 HYPERTEXT PREPROCESSOR (PHP)

PHP is used for dynamic website development.

4.1.5 SUBLIME TEXT EDITOR

Sublime is text editor and it is used for website development coding.

4.1.6 JAVASCRIPT/ES6
JavaScript is used for dynamic web content and making website responsive.

4.1.7 XAMMP
XAMPP is a product distribution which gives the Apache web worker, MySQL data
set, PHP and Perl (as order line executables and Apache modules) across the board
bundle. It is accessible for Windows, MAC and Linux frameworks. XAMPP is utilized
to run the pages of site. It is utilized to run the site on server.

15
Tools and Technologies

4.2 DESIGNING TOOLS

4.2.1 JUST IN MIND
We used JUST IN MIND software for make the prototypes of our mobile application
and it helped us a lot to make a rough draft and design of our application. Through this
we made designs of application and website which we were thinking in our mind, we
plot our ideas on to this. Making prototypes of them so we decided how it will look
alike, is it sufficient or not. Understandable or not. Is the interface being good for user’s
perspective or not. Or then we decided what we should do to make our system efficient
and effective for users.

4.2.2 PHOTOSHOP
We used PHOTOSHOP for making the poster of ours. We create our project logo
through Photoshop and making pamphlet for publicity of our project which defines the
purpose of our system and where mention the features and functionalities of our project.
And design a business card for users so they can contact us through email and phone
number.

4.2.3 JQUERY
JQuery is used for website to make it more interactive and attractive. It is also used to
add effects and animation in the website.

4.2.4 BOOTSTRAP FRAMEWORK

Bootstrap used for front end designing.

4.2.5 Html 5 & Css (Cascading Style Sheet)

HTML and CSS used for creation of website template.

4.3 DOCUMENTATION TOOLS

4.3.1 MS WORD
Microsoft Word permits you to make proficient quality reports. We've utilized
Microsoft word for documentation because of its highlights including spell check,
syntax check, text and textual style arranging, picture uphold, progressed page design
etc. It permits us to type words, sentences and passages fundamentally the same as a
typewriter.

16
Tools and Technologies

4.3.2 CREATELY UML DIAGRAM

It offers a wide assortment of implicit shapes, articles, and stencils to work with.
The designs that are utilized in creately are standard pictures used by flowcharts,
decision charts, playbooks, and even network graphing. We have utilized creately
UML outline to characterize the general progression of our tasks utilizing different
UML graphs.

17
User Interface Design

Chapter 5 USER INTERFACE DESIGN

5.1 WEB APPLICATION INTERFACES:

Figure 5-1 Admin Login

Figure 5-2 Dashboard

This is the Dashboard that how many users have used the application.

18
User Interface Design

Figure 5-3 Edit Users

We can edit the users

Figure 5-4 Delete Users

We can delete the users

19
 User Interface Design

Figure 5-5 Generated Alerts

We can see all the generated notifications over here

Figure 5-6 User Reports

This is the user report that shows how many users are registered in the application.

20
User Interface Design

Figure 5-7 Logout panel

This is how we can logout form the panel.

5.2 MOBILE APPLICATION INTERFACES

Figure 5-8 Splash Screen

This is the 1st screen of the mobile application

21
User Interface Design

Figure 5-9 Create Account Figure 5-10 Login

Login page

22
User Interface Design

Figure 5-11 Dashboard Figure 5-12 Registration

Registration page of user

23
User Interface Design

Figure 5-13 Alert Figure 5-14 Help

Alert would be send on hitting this This is the help panel where the user
alert can call

the emergency numbers on just click

24
User Interface Design

Figure 5-15 Police Location

Figure 5-16 Admin Alert

This is the current location of the user, This is the alert which we get by the
she can get to the nearest police station. admin.

the emergency numbers on just click

25
User Interface Design

Figure 5-17 Guidance

It will guide you how to use the

application.

26
User Interface Design

5.3 WEBSITE INTERFACES

Figure 5-18 Homepage

Figure 5-19 How it Work

27
User Interface Design

Figure 5-20 Features

Figure 5-21 App Screenshots

28
User Interface Design

Figure 5-23 Team

Figure 5-22 Contact Us

29
Methodology

Chapter 6 METHODOLOGY

6.1 METHODOLOGY USED FOR IMPLEMENTATION

6.1.1 INTRODUCTION
Smarillance has been developed using the Agile Methodology “Scrum” because it
essentially eliminates the probabilities of absolute project failure. Working in sprints
from the very beginning allows us to develop a working product from the start, or fail
fast and take another approach. With Agile software development, we have quickly
adapt to requirements changes without negatively impacting evaluation date. Not only
that, Agile helps reduce technical debt, improve project satisfaction and develop a
better quality product.

6.1.2 REASON TO USE SCRUM IN SMARILLANCE

6.1.2.1 SCRUM OFFERS FREEDOM OF IMPLEMENTATION
Smarillance is an application which is design to facilitate general public
while designing the application it was require to implement different
framework and events which was very easy to use in scrum.
6.1.2.2 SCRUM IS EASY TO USE AND LEARN
Being the developers of Smarillance, scrum was an easy approach to
learn and implement as our roles were defined being an product owner,
team and scrum master to work on the requirement that is vision of
Smarillance and build the product to accomplish the result.

6.1.2.3 SCRUM EMBRACES CHANGE

Smarillance was designing incrementally so it was very easy to change the
requirement after each evaluation so that functional requirement of the project
is clear.

6.1.2.4 SCRUM REDUCES THE RISK BUILDING THE PRODUCT

BY INCREMENTS

As from the start when we select the approach scrum Smarillance was in a
working state so it reduces the risk of failure which help us to improve the
product with certain increment and timely changes

30
Methodology

6.1.2.5 SCRUM OPTIMIZES THE TEAM’S EFFICIENCY AND

EFFICACY

In the development of Smarillance, each group members has assign

some task which need to be completed and evaluated so each member
know what we have achieved, what is going to be next goal and what
are problems Smarillance can face and how to resolve it.

6.1.2.6 SCRUM LETS THE CUSTOMER TO USE THE PRODUCT

After each task completion Smarillance is tested in sprint review to

check user point of view and validate weather the product satisfy the
requirements.
6.1.2.7 SCRUM IS CONTINUOUS IMPROVEMENT
Smarillance has improved very much after the sprint retrospective meeting
where each requirement of module are tested and evaluate to make it a better
platform for the purpose it is design.

6.2 SMARILLANCE LIFE CYCLE MODEL

The proposed Smarillance lifecycle is a blend of agile model.
 Project Management Agile Wrap was adopted for projects management because it can
optimize distributed development process through its modules.
 Sprints and Tasks: The supervisor acted as scrum master for the project. The sprint
plans and user stories were defined by supervisor. Depending upon the sprint duration
and tasks complexity a project was distributed into three to four weeks release
plans. The scholars were required to form the merchandise log at the project
management website and identify the tasks for every user story of the sprints. They
were required to estimate the work hours for every task and justify their estimate. It
absolutely was mandatory for the scholars to update daily work. Individual effort of
every member of the group was discussed in scrum meetings. We had to demonstrate
the running software to the supervisor for evaluation after each sprint.
 Sub-Versioning and Project Tracking Sub-versioning was introduced to facilitate the
distributed group development environment. Students were allotted space on central
repository to put their code and were encouraged to figure on the updated code in
repository. The repository was utilized by the supervisor to research the project
progress, code review including standard practices, quality of the code and issues
resolution.

31
Implementation

Chapter 7 IMPLEMENTATION

7.1 DATA BASE DESIGN

Database design is based on the User data. It store the email and password and other
details. All the data of user are stored in database
We have the following table:
User Entity:
Field Name Explanation
Primary key Email Unique identifier for
each individual user.
Other Attributes Username User full name
(required)
password User password
(required)

7.2 WEB SERVICES

A help offered by an electronic gadget to another electronic gadget, speaking with one
another by means of the World Wide Web, or a server running on a PC.

7.2.1 CLIENT SIDE SERVICES

S. No User API Status
1. Login API Implemented
2. Google API Implemented
3. Police Location API Implemented

7.3 WEBSITE DESIGN

The website is designed using HTML, CSS and Bootstrap framework for
responsiveness and jQuery for animation and PHP is used to make it dynamic.

32
Implementation

7.4 MOBILE APPLICATION

To build up a framework for android clients for keeping track through a few
applications [4].
This application utilizes GSM for recognizing the area of the individual in a tough
situation and the framework can be partitioned into three modules:
A. Notification to the Emergency Numbers: First module consists of phone
numbers of the authorized forces which are present in there so that they can act
upon right then.
B. Notify the registered contact: Second module is the cell phone of enrolled
contacts either companions or relatives get the call and message containing URL
of area of user that is sent from the root gadget.
C. Current Location: Third module is the current location where the user can
check her location and the list of nearest police stations will appear so that she
can reach there.
The proposed system is based on android platform. Android uses a custom virtual
machine that was intended to improve memory and equipment assets in a cell phone.
Android doesn’t separate between the Phone’s core applications and outsider
applications [3] (Yarabothu, 2015). Any application that is manufactured will have
equivalent admittance to a phone’s capacities providing users with an expansive range
of utilizations and services. The fundamental focus of the proposed system is to
minimize the general expense of following dependent on GPS framework, it does
liberate from cost administration accessible to each person. To follow the development
of the individual, Google Maps have been for locating the area sent by the cell phone.
This administration gave by the specialist service provides which is a wireless data
communication system. Mobile phones equipped with GPS recipient are adequately
available on the lookout and is thundering advancement these days [4] (Harikiran,
2016). This phone advancement has engaged us to bestow practically all parts of the
world over the cutoff points. The GSM/GPRS is really extraordinary and most
affordable techniques for correspondence present these days and in future.

33
Implementation

7.5 WEB APPLICATION

The proposed system is having the admin panel on the firebase as it helps to manage
and store the data feasibly without having any difficulty. The mobile application is
integrated with the firebase.
A. Manage Users: The admin can manage the data of all the users registered
having the information of their email id, user id, when they log in or log out, he
can also add or delete the users and can disable the user as well.
B. Trigger Alerts: The admin can trigger the alerts as well if there is any mishap
in any particular area or the area is red zoned because of any issue to prevent
the users from going in the particular area.
Firebase is Google’s mobile platform, it has helped in the easy storing and retrieval of
dynamic content and has provided a real-time database and back-end as a service. The
service gives proposed framework engineers an API that permits application
information to be synchronized across customers and put away on Firebase's cloud.

7.6 DEPLOYMENT
Provide the Android Application on play store and Host Web services for Customized
Application on request on Google.

7.6.1 MOBILE APPLICATION DEPLOYMENT

Smarillance mobile application is on its development phase. Soon it will be
successfully deploy on play store.
For Users:
 Mobile application with user panel only.
 Each panel would contain different functionality according to the user need.
 Smarillance application would be simple to use with an easy interface that a
common people can easily use it.

34
Testing

Chapter 8 TESTING

8.1 INTRODUCTION
Smarillance application is tested to ensure that its quality under test is in line with the
requirement of the target market i.e. ladies. Software testing is carried out in a
systematic manner with the intent of finding defects in a system. It is required for
evaluating the system. To evaluate each aspect different types of testing are conducted.

8.2 OBJECTIVES
The objective of the testing is finding as many software defects as possible; that can
be occur when user use Smarillance and ensure that the Application is bug free before
a user uses it. Create the hypothesis and test case to make sure that each scenario is
defect free.

8.3 UNIT TESTING

Unit testing of Smarillance is being done by testing the two modules separately and
making sure that it works properly and tracking is smooth. Each class is tested to make
sure there is no errors i.e. a user is being register properly.

8.4 INTEGRATION TESTING

In integration testing after the modules result were accurate we have combined the two
module that are register the contact and send alert and vice versa with registration and
other activity to make sure that the application all together is working in the same flow
as it was differently.

8.5 TESTING APPROACH

Smarillance has been tested by a normal user to evaluates each module and make sure
that it is providing a smooth two way communication for each user. Thus this process
validate the purpose of application which it has been developed for.

8.6 TEST CASES

35
Testing

Project Name: Smarillance

Test Priority: High Test Designed by: Hira
Danish

Module Name: Smarillance Sign Up screen Test Designed date: 18-

Feb-2021
Test Executed by: Somia
Anjum
Test Execution date: 20-
Feb-2021
Test Test Case Test Step Test Data Expected Result Actual Result Status
Case Description
ID
SignU Verify sign Navigate to Able to see the As expected Pass
p_01 up sign up sign up screen
functionality page
by enter
email
without @
Enter email Email: Credentials can As expected Pass
without @ hira18danis be entered
h@gmail.c
om
Click on “Invalid email” Please include Pass
sign up Error message an @ in the
button should be display email address
SignU Verify sign Navigate to Able to see the As expected Pass
p_02 up sign up sign up screen
functionality page
by enter
same
password in
choose a
password
and confirm
password
Enter valid Password:* Credential can be As expected Pass
password ******* entered
in choose a
password
Enter valid Password:* Credential can be As expected Pass
password ******* entered
in confirm
password
Click on Sign up Sign up Pass
sign up successfully successfully
button
SignU Verify Navigate to Able to see sign As expected Pass
p_03 signup sign up up screen
functionality page
by enter
different
passwords in
choose a
password
and confirm
password

36
Testing

Enter valid Password:* Credential can be As expected Pass

password ******* entered
in choose a
password
Enter Password:* Credential can be As expected Pass
invalid ********* entered
password **
in confirm
password
Click on “Password does The password Pass
sign up not match” Error confirmation
button message should does not match
be display
SignU Verify Navigate to Able to see sign As expected Pass
p_04 signup sign up up page
functionality page
by enter
email which
has already
been taken
Enter email Email: Credentials can As expected Pass
hira18danis be entered
h@gmail.c
om
Click on “The email has Message Pass
sign up already been displayed
button taken” Error
message should
be display
SignU Verify sign Navigate to Able to see sign As expected Pass
p_05 up sign up up screen
functionality page
by enter less
than eleven
digits in
phone
Enter 10 030456789 Credentials can As expected Pass
digits 0 be entered
Click on Invalid input The phone Pass
sign up must be
button between 11
and 15 digits.
SignU Verify sign Navigate to Able to see sign As expected Pass
p_06 up sign up up screen
functionality page
with more
than 15
digits
Enter 16 030421717 Credentials can As expected Pass
digits 2619212 be entered
Click on Invalid Input The phone Pass
sign up must be
button between 11
and 15 digits

37
 Testing

Project Name: Smarillance

Test Priority: High Test Designed by: Hira Danish
Module Name: Smarillance login screen Test Designed date: 15-Feb-2021
Test Executed by: Somia Anjum
Test Execution date: 16-Feb-2021
Test Case Test Case Test Test Data Expected Actual Status
ID Description Step Result Result
Login_01 Verify login Navigate Able to see the As Pass
functionality with to login login screen expected
valid email and page
password
Enter Email:hira18da Credential can As Pass
valid nish@gmail.co be entered expected
email m
Enter Password:**** Credential can As Pass
valid **** be entered expected
password
Click on Login Login Pass
login successful Successful
button
Login_02 Verify login Navigate Able to see the As Pass
functionality with to login login screen expected
valid email and page
invalid password
Enter Email:hira18da Credential can As Pass
valid nish@gmail.co be entered expected
email m
Enter Password:**** Credential can As Pass
invalid ********** be entered expected
password
Click on “These Message Pass
login credentials do displayed
button not match our
records” Error
message
should be
display
Login_03 Verify login Navigate Able to see As Pass
functionality with to login login screen expected
invalid email and page
valid password
Enter Email:hira18da Credential can As Pass
invalid nish@gmail.co be entered expected
email m
Enter Password:**** Credential can As Pass
valid **** be entered expected
password
Click on “These Message Pass
login credentials do displayed
button not match our
records” Error
message
should be
display
Login_04 Verify login Navigate Able to see As Pass
functionality with to login login page expected
page

38
 Testing

valid email and

password is blank
Enter Email:hira18da Credentials can As Pass
valid nish@gmail.co be entered expected
email m
Do not Credentials As Pass
enter cannot be expected
password entered
Click on “Please fill out Message Pass
login this field” displayed
button Error message
should be
display
Login_05 Verify login Navigate Able to see As Pass
functionality with to login login page expected
valid password and page
email is blank
Do not Credentials As Pass
enter cannot be expected
email entered
Enter Password:**** Credentials can As Pass
valid **** be entered expected
password
Click on “Please fill out Message Pass
login this field” displayed
button Error message
should be
display
Login_06 Verify login Navigate Able to see As Pass
functionality with to login login page expected
empty email and page
password
Do not Credentials As Pass
enter cannot be expected
email entered
Do not Credentials As Pass
enter cannot be expected
password entered
Click on “Please fill out Message Pass
login this field” displayed
button Error message
should be
display

39
Testing

8.4 MOBILE APPLICATION TESTING

Testing phase includes the screenshots of the running application. When the user sends
the alert, the call and the message containing the URL of the current location is sent to
the registered contact so the she can be tracked eventually

Figure 8-1 Message Alert Figure 8-2 Tracking

It shows the message alert has been
received by the registered
Figure 5.5.3User Alert
It shows on opening the URL of the
current location of the user can get
and can be safely rescued. For this
purpose Google Map is used for the
exact direction
It shows on opening the URL of the
current location of the user can get
and can be safely rescued. For this
purpose Google Map is used for the
exact direction
It shows the URL of the current
location of the user and she can be
safely rescued. For this purpose
Google Map is used.

e alert has been received by the

registered contact containing the
URL.
40
CONCLUSION

CONCLUSION
This is the "Android Application for ladies security framework" which is helpful
application, essentially for young lady's safety. At the point when we feel that we are
in critical situation, for example traveling alone in the Auto/Cab at night we can use
this application, so that on a click we can send our area to our loved ones and to any
authority [5] (Dey, 2017). This application has a future scope as well as it can be
integrated with the regional cops. It can also be developed on the IOS and windows
platform. Thus, the application will be really helpful for every women who is present
anywhere.

APPENDIX A
GLOSSARY
 Actor: A user interacting with the system.
 Admin: A person who manages the web application.
 Authorize: To allow or give official permission to someone to do something or
allow user to perform their task.
 Help: The user can send emergency call to the authorities on one tap.
 Notification: The action of notifying someone or something. In system term,
the system notify registered contacts.
 One to one alert: A process of sending and receiving messages.
 Track: The registered contacts will track the user.
 Vulnerable area: An area which will be highlighted by the admin.

41
Appendix A

TURNITIN REPORT

42
Appendix A

43
Appendix A

44
References

REFERENCES
Dey, T. (2017). Advanced women security app: We’RSafe. Howrah: IIETA.
Harikiran, G. C. (2016). Security solution for women based on internet of things.
Chennai,India: IEEE.
Kavita Sharma, A. M. ( 2016). Android Application for women security. Indore,India:
International Journal of Advanced Research in Computer Engineering & Technology
(IJARCET).
Khir, M. S. (2015). Emergency Push Notification Mobile Application. PERAK: utpedia.
Yarabothu, R. S. (2015). Abhaya, An Android App for the safety of women. Vadlamudi:
Research gate.

45