WOW Report2016

“World of Women (WOW)”
A PROJECT REPORT
Submitted by
KAPADIA SAGRIKA D. (131110107022)
GHELANI DIPEN S. (141113107002)
JASOLIYA MILAN V. (141113107005)
KACHHADIYA ASHISH K. (141113107006)
In fulfilment for the award of the degree of
BACHELOR OF ENGINEERING
In
Computer Department
Guided by
Mr. Pranav Rangwala

Assistant Professor
Department of Computer Engineering
Mahavir Swami College of Engineering & Technology, Surat

Gujarat Technological University, Ahmedabad
2016-17
Department of Computer Engineering
2016 - 17
CERTIFICATE
Date:
This is to certify that the dissertation entitled “World of Women (WOW)” has
been carried out by Kapadia Sagrika Dineshbhai, Ghelani Dipen Shantibhai,
Jasoliya Milan Vinubhai, Kachhadiya Ashish Kanubhai under my guidance in
fulfilment of the degree of Bachelor of Engineering in Computer Engineering
(8th Semester) of Gujarat Technological University, Ahmedabad during the
academic year 2016-17.
Mr. Pranav Rangwala Dr. S.V. Patil Ms Bhavika Patel

Asst. Professor Principal Head of the department
(Internal Guide) (Principal) (Head of Department)

COMPANY PROFILE
Company Name Raksh Infotech

Company Director Mr. Kaushik Patel
Company Website www.rakshinfotech.com
Company Email info@rakshinfotech.com
Type of Business This business mainly work on InfoTech solutions.
Business Address 4040,4th floor, palladium mall, yogi chowk, varachha, surat-3951010
BRIEF OVERVIEW / HIGHLIGHTS

 Introduction
Raksh InfoTech Best Quality in Web Development, E-Commerce Solution, Mobile Application
Development, SEO, Digital Marketing, Domain & Hosting and Software Development for
individual's, companies & corporate sectors. Raksh Infotech is believing in Work. Our Work is
our passion, which help us to do things creatively, professionally and properly.
 Mission
We believe in effective technology rather than cheap technology. We believe in building long-
term customer relationships and working with them to identify their needs and provide solutions.
SERVICES & TECHNOLOGY

 Website Development
 Software Development
 Digital Marketing
 Mobile Application Development
 Domain Registration
Computer Engineering
2016 – 17
PROJECT-II APPROVAL CERTIFICATE
This is to certify that the Project-II entitled “WOW” submitted by Kapadia

Sagrika (131110107022), Ghelani Dipen (141113107002), Jasoliya Milan
(141113107005), Kachhadiya Ashish (141113107006) in partial fulfilment of the
requirements for the award of the degree of “Bachelor of Engineering ” in
Computer Engineering during the academic year 2016-17 (8th Semester), of the
Mahavir Swami College of Engineering &Technology, Surat is approved.
Examiners:
1.
2.
Date: Head of the department

ACKNOWLEDGEMENT
The success of any task relies on the efforts made by person but it cannot be achieved
without cooperation of other persons which are being helpful. So, we would like to thank
MAHAVIR SWAMI COLLEGE OF ENGINEERING AND TECHNOLOGY and Raksh
InfoTech Technologies for giving us the opportunity of doing this project.
The entire session of our phase-I completion was a great experience providing us with the
insight & invocation into learning various software engineering concepts & benefits of team
work. We would like to take this opportunity to express our sincere thanks to all those people
without whose support and co-operation, it would have been difficult to complete this project.
Primarily, we are very much thankful to our project guide Asst. Prof. Pranav Rangwala
And Mr. Kaushik Patel for his leading guidance and sincere efforts throughout project work.
They took keep interest in simplifying the difficulties. Also they have been consistent source of
inspiration for us.
We also express thanks to Asst. Prof. Mrugesh Patel class coordinator for his personal
involvement, constructive suggestion and thoughtful idea for betterment of the project.
We are grateful to our H.O.D. Asst. Prof. Bhavika Patel and our beloved Principal
Dr. S. V. Patil for providing us deep knowledge and all necessary resources.
We are also thankful to our Friends and Non-teaching Staff for their valuable time and help for
completion project.
Once again we are grateful to all those without whom this this work would not have been
successful.
Team Members
Kapadia Sagrika D. 131110107022
Ghelani Dipen S. 141113107002
Jasoliya Milan V. 141113107005
Kachhadiya Ashish K. 141113107006
i
ABSTRACT
This application will be based on android system which is use for women, basically this app
provides rights of women, Laws in favours of women, Security of Women, Help Line number,
Safety steps taken during an emergency, Nearby Location etc. And many more and also provide
different modules related to location tracking like nearby. This app also provides the module
women to learn online books
The application provides information of some law, traffic rules, women rights and many more
information which is universally need in daily routine. app provide the help line number using
that number user not need to find the number on Google or not need to waste the time also user
can directly call and SMS from the app.
ii
LIST OF TABLES
Table No Table Description Page No
Table 3.1 Project Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 3.2 Development Criteria . . . . . . . . . . . . . . . . . . . . . . 25
Table 3.3 Project development chart . . . . . . . . . . . . . . . . . . . 26
Table 4.1 Hardware Requirement (Mobile) . . . . . . . . . . . . . . 27
Table 4.2 Hardware Requirement (Developer) . . . . . . . . . . . . 27
Table 4.3 Software Requirement (Mobile) . . . . . . . . . . . . . . . 27
Table 4.4 Software Requirement (Developer side) . . . . . . . . . 27
Table 4.5 Difference between High, Middle and Low Level
Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 4.6 Difference between Structure, Object and Non
structure Oriented . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 5.1 Data Entering at Registration. . . . . . . . . . . . . . . . . . 64
Table 5.2 Login into System. . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 5.3 Checking Change Password . . . . . . . . . . . . . . . . . . 65
iii
LIST OF FIGURES
Figure No Figure Description Page No
Figure 2.1 Context level Data Flow Diagram . . . . . . . . . . . . . . . 8
Figure 2.2 1st Level Data Flow Diagram . . . . . . . . . . . . . . . . . . 9
Figure 2.3 2nd Level DFD for Registration & Login . . . . . . . . . . . . 10
Figure 2.4 2nd Level DFD for Laws . . . . . . . . . . . . . . . . . . . . . 11
Figure 2.5 2nd Level DFD for Health . . . . . . . . . . . . . . . . . . . . . 12
Figure 2.6 2nd Level DFD for Helpline . . . . . . . . . . . . . . . . . . . . 13
Figure 2.7 2nd Level DFD for Education . . . . . . . . . . . . . . . . . . 14
Figure 2.8 2nd Level DFD for Feedback . . . . . . . . . . . . . . . . . . 15
Figure 2.9 AEIOU Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 2.10 Empathizing Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 2.11 Ideation Canvas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 2.12 Product Development Canvas . . . . . . . . . . . . . . . . . . 19
Figure 2.13 Business Model Canvas (BMC). . . . . . . . . . . . . . . . . 20
Figure 3.1 Waterfall Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 4.1 Android OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 4.2 Android Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 4.3 Android Version (Development) . . . . . . . . . . . . . . . . 31
Figure 4.4 Android Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 4.5 Firebase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
iv
Figure 4.6 JSON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 4.7 PHP Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 5.1 Splash Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 5.2 Login Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 5.3 Registration Activity . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 5.4 Edit Profile Activity . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 5.5 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 5.6 Helpline Number Activity . . . . . . . . . . . . . . . . . . . . . 41
Figure 5.7 Helpline Number Detail . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 5.8 Call from Helpline Number . . . . . . . . . . . . . . . . . . . . 42
Figure 5.9 Travel Safety Activity. . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 5.10 Health Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 5.11 Fitness Details Activity. . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 5.12 Nearby Activity . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 5.13 Nearby Hospitals Details . . . . . . . . . . . . . . . . . . . . . . 44
Figure 5.14 Hospital Details . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 5.15 Education Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 5.16 BCA College Details . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 5.17 GYM Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 5.18 GYM Tips Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 5.19 Women Law Activity . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 5.20 Details of Women Rights . . . . . . . . . . . . . . . . . . . . . . 48
Figure 5.21 School Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
v
Figure 5.22 Detail of Gujrati Medium School. . . . . . . . . . . . . . . . 49
Figure 5.23 Kitchen Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 5.24 Details of Cateress . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 5.25 Pregnancy Guide Activity . . . . . . . . . . . . . . . . . . . . . 50
Figure 5.26 Tips For Pregnancy . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 5.27 English Speech Activity . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 5.28 Speech Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 5.29 Achievement Activity. . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 5.30 Details for Post Achievement . . . . . . . . . . . . . . . . . . 53
Figure 5.31 Reminder Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 5.32 Add a Reminder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 5.33 Daily Quotes Activity. . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 5.34 Details of Daily Quotes. . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 5.35 News Feed Activity . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 5.36 Personal Dairy Activity . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 5.37 Add an Important Note . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 5.38 Feedback Activity . . . .. . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 5.39 Give Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 5.40 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 5.41 Black-box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
vi
ABBREVIATIONS
Short Form Full Form Page No
WOW World Of Women . . . . . . . . . . . . . . . . . . . . . . . . . 2
SMS Short Message Service . . . . . . . . . . . . . . . . . . . . . 3
MMA Mobile Messaging Application. . . . . . . . . . . . . . . 6
JDT JAVA Development Tools. . . . . . . . . . . . . . . . . . . 31
SDK Software Development Kit. . . . . . . . . . . . . . . . . . 33
PHP Hypertext Pre-processor. . . . . . . . . . . . . . . . . . . . 32
SDK Software Development Kit . . . . . . . . . . . . . . . . . . 33
vii
Table of contents
Title Page No
ACKNOWLEDGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II
LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IV
ABBREVIATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VI
CHAPTER 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Project Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Purpose: Goals & Objective. . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1 Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.2 objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Scope Of system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Problem Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Literature Review & Prior Art Search (PAS). . . . . . . . . . . . . . 4
1.5.1 Prior Art Search (PAS) . . . . . . . . . . . . . . . . . . . . . . 4
CHAPTER 2 SYSTEM ANALYSIS & DESIGN . . . . . . . . . . . . 7
2.1 Case Study Of Current System . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Problem and Weakness of Current . . . . . . . . . . . . . . . . . . . . 7
2.3 Requirement of New System . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6 Observation Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
viii
2.6.1 AEIOU Framework . . . . . . . . . . . . . . . . . . . . . . . . 16
2.7 Empathizing Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.8 Ideation Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.9 Product Development Canvas . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.10 Business Model Canvas (BMC) . . . . . . . . . . . . . . . . . . . . . . 20
CHAPTER 3. PROJECT MANAGMENT . . . . . . . . . . . . . . . . . 21
3.1 Project Planning & Scheduling . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1 Project Development Approach (Process
Paradigm)And Justification . . . . . . . . . . . . . . . . . . . 21
3.1.2 Project plan including Milestones . . . . . . . . . . . . . 23
CHAPTER 4. SYSTEM REQUIREMENTS STUDY . . . . . . . 27
4.1 Hardware And Software Requirements . . . . . . . . . . . . . . . . . . 27
4.1.1 Minimum Hardware Requirements. . . . . . . . . . . . . 27
4.1.2 Minimum Software Requirements . . . . . . . . . . . . . . 27
4.2 Technology To Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3 Android Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.4 Programming Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4.1 Language Difference . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4.2 Language Standard . . . . . . . . . . . . . . . . . . . . . . . . . 37
CHAPTER 5. IMPLEMENTATION . . . . . . . . . . . . . . . . . . . 38
5.1 Implementation of System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.2 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.2.1 Testing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
ix
5.2.2 Testing Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.2.3 Testing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2.4 Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2.4.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2.4.2 Required Input & Expected Result. . . . . . . . . . 64
REFERENCES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
APPENDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
x
Project Id: - 57350 Introduction
CHAPTER 1: INTRODUCTION
A woman refers to increasing and improving the social, economic, political and legal strength of
the women, to ensure equal-right to women, and to make them confident enough to claim their
rights.
freely live their life with a sense of self-worth, respect and dignity, have complete control of their
life, both within and outside of their home and workplace, to make their own choices and
decisions, have equal rights to participate in social, religious and public activities, have equal
social status in the society, have equal rights for social and economic justice, determine financial
and economic choices, get equal opportunity for education, get equal employment opportunity
without any gender bias, get safe and comfortable working environment.
1.1 PROJECT SUMMARY
WOW is designed to server mainly two goal for the women. The first one is to send SMS to
his/her relative when she is in any critical situation. User set the 3 mobile number and emergency
SMS in application and when she is in critical situation then using slide to panic module she send
a SMS to her relative which SMS number and SMS are set in application. The second is when
any women are travelling in her private or public vehicle than user are directly send the vehicle
number, source and destination address to her relative which is set in application so user safely
travel.
Right now days all women are not known all the laws and rights of women. We are trying to
cover all the law and right of women which is need any women any time in her life.
In app we cover maximum help line number, Toll Free number and also if user is need to call
and SMS to this number then it can directly call from the application.
In App we also make one module in which user can easily find her/her nearby place like hospital,
police station, restaurant, college etc.
M.S.C.E.T. (CO) Page 1

1.2 PURPOSE: GOALS & OBJECTIVE

1.2.1 Goals:
 The primary goal of “WOW” application to send a SMS to relative mobile phone which
is already set in the application when user are in any critical situation.
 Provide a travel safety means when user are travelling at a time user set a source and
destination address and vehicle number and vehicle type in the app and this information
send to user relative number which is set in the application so user are safely travel.
 Provide a information about all the laws and rights of women.
 In any critical situation if user need any help line number than using app easily call and
SMS to this number direct from the application.
 Provide the reminder to remind the any task and any work which is important.
 Its provide all nearby location of user like police station, hospitals, restaurants etc.
 We also provide the basic information like address, phone number and name about the
hospitals, school, college etc.
1.2.2 Objectives:
To provide information about the laws and rights of the women this is related to women. In app
we have main two goal. The first one is to send SMS to his/her relative when she is in any
critical situation. User set the 3 mobile number and emergency SMS in application and when she
is in critical situation then using slide to panic module she send a SMS also her location to her
relative which SMS number and SMS are set in application. The second is when any women are
travelling in her private or public vehicle than user are directly send the vehicle number, source
and destination address to her relative which is set in application so user safely travel. Provide
the maximum help line number and user directly call and SMS from the application also provide
the laws and rights of women so at right time women can take a decision.also provide different
modules related to location tracking like nearby like hospital, bank, police station.
1.3 SCOPE OF SYSTEM
A WOW is mobile application that can be used in the general people using app user are send the
SMS to his/her relative to when he/she is in any critical situation. Also using travel safety user
are safely travel at any place.

This application is provide the some law and rights of women also provide the helpline number
which is need in general life and using app use can call and SMS direct from application.
Provide nearby location of user like hospitals, police station, bank, restaurants, blood bank. Also
provide some tips of beauty and so many more.
 Travel safety,
 Laws and rights of women,
 Provide help line number and direct call and SMS from application,
 Provide Nearby Location of Current location,
 Provide basic information of hospital, police station, bank, college like name,
number, address and directly call and SMS from application,
 Using reminder user set the reminder notification to remind some important task.
WOW is android applications using this app user are feel safe at travel time and also at any place
where he/she is alone. Using some special module user are take a right decision and learn about
some laws like traffic laws, rights of women etc. and also search and find place and also get the
some helpline number which is generally use in routine life.
1.4 PROBLEM SPECIFICATION

There are a few problem statements that project try to solve it. Such as:
 Not feel safe when women is alone
Nowadays when any women are at late night and where any place she is alone at that
time for any emergency she wants to manually call or SMS to any relative and not easily
get helped from her relative.
 Hardly find helpline number
Sometime user need the helpline number and toll free number which is not easily find
and waste the time for finding the helpline number and toll free number.
 Not known exact laws and rules
People are not know all the laws like traffic law some women rights and so more.

1.5 LITERATURE REVIEW & PRIOR ART SEARCH (PAS)
1.5.1 Prior Art Search (PAS)

 Research paper [1]
Patent no: - US 8,626,774 B2
Date: - 23/01/2012
Subject:- LOCATION BASED APPS RANKING FOR MOBILE WIRELESS COMPUTING
AND COMMUNICATING DEVICES
Inventors: - PhaniBhushanAvadhanam()
Xintian LiUS)
Keyword:-location,gps
Description:-
Systems, methods, and apparatuses are disclosed for presenting applications to a user, via a
mobile wireless communication device (user equipment), that are selected and ranked based on
context information describing a location and type of motion of the user equipment, and/or a
time that the ranking request was made, compared to context information describing the
applications.
Apps that could be beneficial, but do not fall Within the user’s purview are often never found.
These approaches also may not take into consideration the personal interests or circumstances of
a user. There is therefore a need in the art for improved systems and method for
ranking apps.
 Research paper 1 [2]

Patent no: - US 6,615,439 B1
Date: - 13/05/2013
Subject:- SMS Message sent from mobile equipment
Inventors: - Jordan SHEINFELD(US)
Keyword:- SMS,Mobile
Description:-
actively preventing the SMS message from being sent in the first manner; and sending, directly
or indirectly, content of the SMS message and metadata associated with the SMS message to the
home network in a second manner, the second manner is not in accordance with the SMS

standard, thereby enabling an SMS center of the home network to send the SMS message to its
destination.

Patent no: -F017112934
Date: -22/01/2015
Subject :-I safe
Inventors: - Dr Sridhar Mandapati(India)
SravyaPamidi(India)
SriharithaAmbati(India)Keyword:-location,gps
Keyword:- apps, android, mobile, safety, Women.
Description:-
This mobile application is very much helpful for any woman. Because when a woman is in
danger position then she simply touch this I Safety mobile app and alert their guardians that the
woman is in danger. By simply touching the app it sends the call for the first added guardian
number and sends the message that she was in danger and sends the location message to the all
saved guardian contacts. Through this mobile app we can alert the people at home that a woman
belonging to their house is safe or not.

Date: -03/05/2015
Subject:-sauver:an android application for women safety
Inventors: - BramarambikaThota(India)
UdayaKanchana Kumar P(India)
Keyword:- Smart Phone, Android, Registered Contacts, GPS location, Database.
Description:-
The usage of smart phones equipped with GPS navigation unit have increased rapidly from 3%
to more than 20% in the past five years. Hence, a smart phone can be used efficiently for
personal safety or various other protection purposes especially for women. This paper presents

Sauver, a personal safety application developed for smart phones of android platform. This app
can be activated by a single click when the user feels she is in danger.
The usage of smart phones equipped with GPS navigation unit have increased rapidly from 3%
to more than 20% in the past five years. Hence, a smart phone can be used efficiently for
personal safety or various other protection purposes especially for women. This paper presents
Sauver, a personal safety application developed for smart phones of android platform. This app
can be activated by a single click when the user feels she is in danger.

Date: -14/04/2016
Subject:-Mobile messaging through android phones
Inventors: - JashandeepSingh(India)
Keyword:- Mobile Messaging Applications, Mobile Messaging Apps, MMA, expressiveness,
usefulness, enjoyment, assortment of services.
Description:-
It also revealed that SMS service is easy to use, useful and the texts received from friends are
able to affect their emotions and feelings. Another study by Pedersen and Nysveen (2002) found
that factors such as easy to use, useful, fun and expressive nature are the main determinants for
using messengers.
Mobile chatting is the most popular services over mobile phone networks. This paper intended to
explore customers’ intention to use Mobile Messaging Applications (MMA) in India. The
current study found that perceived expressiveness, perceived usefulness, perceived enjoyment
and assortment of services to have significant relationship with intention to use MMA. This
indicates that Indian students use mobile messaging to express themselves, to pass the time and
assortment of the services in MMA. Perceived usefulness also plays a significant role in
student’s intention to use MMA.

Project Id: - 57350 SYSTEM ANALYSIS AND DESIGN
CHAPTER 2: SYSTEM ANALYSIS AND DESIGN

2.1 CASE STUDY OF CURRENT SYSTEM
 Currently there are several mobile applications available on the play store for women
safety but all are not working properly and not provide more information.
 User can find help line number and some restaurant number bank number from Google
but not directly call from app and also waste time for find the phone number.
 People are not well knows the laws, traffic rules some women rights and some tips like
beauty tips, Gym tips and so many for study that’s information user can need to purchase
books so its time and money wasting.
2.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

 Currently there are several mobile applications available on the play store for women
safety but all are not working properly and not send location when phone have also not
internet.
 All people not know about the laws, rights of women, traffic rules so some time police
man and some worker are make easily fool to people.
 People are no save all the helpline number so when he/she need helpline number people
want to search helpline number and also dial number to dial pad than call to this number.
 People are not reminding all the various task to in his/her daily life.
 When people are travel alone than his/her relative don’t know the address where he/she is
travel and also not know the vehicle number and type.
2.3 REQUIREMENT OF NEW SYSTEM

In order to overcome the problems and weaknesses of current system we proposed to develop a
new mobile application that provides each and every functionality required for the users.

Advantages of New System are given below:
 Emergency SMS to relative.
 Directly call and SMS from application.
 Get proper Guideline about the law and some other rules.
 Safely travel from one to another place

 Provide reminder for remind task.
2.4 FEASIBILITY STUDY


 While developing the system we carried out following feasibility study.
(1) Technical Feasibility: The system is supposed to be developed using Android. It is
easily available on the play store. Hence all the technologies are Open Source there is no
need to take license.
(2) Economic Feasibility: Hence all the technologies used for developing such application
are open source there is no need to take license version. It will reduce the cost of
application development. Users need to buy a smart phone only in order to use this
application.
(3) Social Feasibility: Hence the application is easily downloaded from Google Play Store
any one can use this application at free of cost.
2.5 DATA FLOW DIAGRAM
Figure 2.1: Context level Data Flow Diagram

Figure 2.2: 1st Level Data Flow Diagram

Figure 2.3: 2ndLevel DFD for Registration & Login

Figure 2.4: 2ndLevel DFD for Laws

Figure 2.5: 2ndLevel DFD for Health

Figure 2.6: 2ndLevel DFD for Helpline

Figure 2.7: 2ndLevel DFD for Education

Figure 2.8: 2ndLevel DFD for Feedback

2.6 OBSERVATION MATRIX

2.6.1 AEIOU Framework
Activity
In the activity we observe that how present system. And define how problems are faced by
peoples because of present system.
Environment
In the Environment we can observe floor plan of present system and identify the scene area. As
well as which environment in our system has possibility of use.
Interaction
In the Interaction we can interact with the affected people and collect information about actually
what problems are faced by people using present system.
Object
In the object we can define the components that are used in our system.
Users
In user we can describe the people that need our system. We can identify who actually needs our
system.
Figure 2.9: AEIOU Summary

2.7 EMPATHIZING CANVAS
Figure 2.10: Empathizing Canvas

2.8 IDEATION CANVAS
Figure 2.11: Ideation Canvas

2.9 PRODUCT DEVELOPMENT CANVAS
Figure 2.12: Product Development Canvas

2.10 BUSINESS MODEL CANVAS (BMC)
Figure 2.13: Product Development Canvas

Project Id: - 57350 Project Management
CHAPTER 3: PROJECT MANAGEMENT

3.1 PROJECT PLANNING & SCHEDULING
3.1.1 Project Development Approach (Process Paradigm) and Justification
Systems Development Life Cycle Method:-
Systems Development, a process consisting of the two major steps of systems analysis and
design. The system development life cycle method is classically thought of as the set of activities
that analysts, designers and users carry out to develop and implement the information system.
The Software development Model used is “Waterfall Model”.
“The waterfall model is a sequential design process, used in software development processes, in
which progress is seen as flowing steadily downwards (like a waterfall) through the phases of
conception, initiation, analysis, design, construction, testing, production/implementation and
maintenance.”
The Waterfall Model was first Process Model to be introduced. It is also referred to as a “linear-
sequential life cycle model”. It is very simple to understand and use. In a waterfall model, each
phase must be completed fully before the next phase can begin. This type of model is basically
used for the project which is small and there are no uncertain requirements. In this model the
testing starts only after the development is complete. In waterfall model phases do not overlap.
Requirement
Design
Implementation
Verification
Maintenance
Figure 3.1: Waterfall Model

Justification:

The most probable phases through which it progresses downwards are
 Definition Study/Analysis: During this phase research is being conducted which
includes brainstorming about the software, what it is going to be and what purpose is it
going to fulfil.
 Basic Design: If the first phase gets successfully completed and a well thought out plan
for the software development has been laid then the next step involves formulating the
basic design of the software on paper.
 Technical Design/Detailed Design: After the basic design gets approved, then a more
elaborated technical design can be planned.
 Construction: In this phase the source code of the programs is written.
 Testing: At this phase, the whole design and its construction is put under a test to check
its functionality. If there are any errors then they will surface at this point of the process.
 Integration: in the phase of Integration, the company puts it in use after the system has
been successfully tested.
 Management and Maintenance: Maintenance and management is needed to ensure that
the system will continue to perform as desired.
Advantages of the Waterfall Model:
 This model is simple and easy to understand and use.

 It is easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
 In this model phases are processed and completed one at a time. Phases do not overlap.
 Waterfall model works well for smaller projects where requirements are very well
understood.

Disadvantages of the Waterfall Model:
 Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-thought out in the concept stage.
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ingoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of
changing.
3.1.2 Project Plan including Milestones, Deliverables, Roles, Responsibilities and

Dependencies
The project plan sets out the resources available to the project, the work breakdown and a
schedule for carrying out the work. The project plan should be regularly revised during the
project. Some parts such as the project schedule will change frequently. The plan of
developing WOW is to fully operate at a high level of efficiency and all the General people,
affected people and helper should understand its advantage. The system main Aim to provide
safety to women and also provide some information of laws and helpline number also
guidance.
Table 3.1: Project Plan
Sr. No. Task Estimated Date
1 Project Selection 17-06-2016 to 26-06-2016
2 Requirement and Specification 27-06-2016 to 22-07-2016
3 Database Design 01-08-2016 to 23-08-2016
4 GUI Design 15-09-2016 to 10-10-2016
5 Coding 16-10-2016 to 25-03-2017
6 Integration and Testing 26-03-2017 to 30-03-2017
7 Maintenance 01-04-2017 to 05-04-2017

Milestones:
Every task or group of tasks should be associated with project milestone. A milestone is
accomplished when one or more work products has been reviewed for quality and has been
approved. Project Milestones include completion of some defines tasks in defined time limits.
The milestones associated with this project are shown below:
 Study Android: First milestone includes study of Android. As the application is going to
be developed using Android (Mobile Application) we need to study about these
technologies.
 Software Requirement Specification: Second milestone of the system is toper form
Software requirement specification. It includes requirement gathering, study of current
system, problems and weakness of current system, functionality required in the system,
Hardware and software requirements etc.
 Designing: Third milestone1 of the system includes designing of Circuit basis need of
our System. And as well as learn about design part of the android.
 Application Development: Fourth milestone of the system includes designing of static
pages of application. It includes all the details of laws and some information.
 Testing and Documentation: Fifth milestone of the system is testing and
documentation. It includes testing of each and every module of the system by preparing
test cases, preparing user manuals for end users and documentation generation.
Deliverables:
Every task that is scheduled should have a defined outcome. For Android application, the
outcome is normally a work product (e.g., the design of a module) or a part of a work product.
Work products are often combined in deliverables. They are delivered at end of some major

phase such as specification, design etc. Deliverables for this project are shown below:
 Project Specification: It includes the requirement analysis and specification of each

module to be developed. It includes description of each module containing what that
module does, how it interacts with another module, what is input to that module and the
outputs from that module.

 Project Design: It includes structural design for each module. Design is used for better
understanding of each modules functionality and interface.
 Developed Product: It is the working product or prototype delivered to users.
 Documentation: It includes some facilities to help the users while using this project.
Roles:
After careful review of software requirements specification, we divide the project in four

different modes: (1) Design Mode (2) Coding Mode (3) Testing Mode and (4) Integration
Mode. Therefore, roles can be defined as Designer, Programmer, Tester & Monitor, and Trouble
shooter. Here we are four members in the project and we play these four roles as per

requirements of project and as per our scheduling.
Responsibilities:
Every task that is scheduled is assigned to a specific team member. Each member’s
responsibility is to develop the assigned module, test it and troubleshooting for that module.
Development Chart
Table 3.2 Development Criteria
ACTIVITY MEMBERS DESCRIPTION
ANALYSIS Member 1-2 Analysis was carried out by all the members
And also reviewed by internal guide.
DESIGN Member 1-2 The designing of the Circuit and the diagram
were done by us by dividing the forms
Internally.
The coding part in the android app was

CODING Member 1-2 completed in group so that works consumes
Less time.

Table 3.3 Project development chart
ID Task Name Start Finish June July Aug. Sep. Oct. March April
1 Project Selection 17-06-2016 26-06-2016
Requirement
And 27-06-2016 22-07-2016
2
Specification
3 Database Design 01-08-2016 23-08-2016

4 GUI Design 15-09-2016 10-10-2016
5 Coding 16-10-2016 25-03-2017
Integration and
6 26-03-2017 30-03-2017
Testing
7 Maintenance 01-04-2017 05-04-2017

Project Id: - 57350 System Requirement Study
CHAPTER 4: SYSTEM REQUIREMENT STUDY

4.1 HARDWARE AND SOFTWARE REQUIREMENTS
4.1.1 Minimum Hardware Requirements
Hardware Specification
 At Mobile Speed:
Table 4.1 Hardware Requirement (Mobile)
Processor speed 2.67 GHz Intel Pentium IV or equivalent

Memory 250 Mb or more
Storage 200Mb of SD card space
 At Development Side
Table 4.2 Hardware Requirement (Developer)
Processor speed 600 MHz

Processor type 250 Mb or more
Memory 4.00 GB or more
Storage 80GB of HDD space
Software Specification
 At Mobile Side
Table 4.3: Software Requirement (Mobile)
Device OS Android 4.2(Jellybean) up to 5.0(Lollipop) or more
 At Development Side
Table 4.4: Software Requirement (Development Side)
O.S Windows 8.1 (64 bit)

Back-end Firebase, JSON, MYSQL

4.2 Technology Used

Android:
Figure 4.1: Android OS[6]
Android is a Linux-base operating system for mobile device such as smart phones and tablet
computer. It is developed by the open Handset Alliance led by Google.
Google maintains an open-source operating system named Android. It's got all the low-level
"stuff" as well as the needed middleware to power and use an electronic device, and it is freely
given away to anyone who wants to grab the code and build the operating system from it. There
is even a full application framework included, so third-party apps can be built and installed, then
made available for the user to run as they like.
The "proper" name for this is the Android Open Source Project, and this is what people mean
when they say things like Android is open and free. Android, in this iteration, is free for anyone
to use as they like.

You might have dabbled with this type of Android if you have used custom ROMs. Many
Third-party developers have taken AOSP and built it as-is for popular phones and tablets. It's
pretty bare-bones, but does have everything you need to power and use a Smartphone.
Application
Android will ship with a set of core applications including an email client, SMS program,
calendar, maps, browser, contacts, and others. All applications are written using the Java
programming language.
Android Runtimes
Android includes a set of core libraries that provides most of the functionality available in the
core libraries of the Java programming language.
Every Android application runs in its own process, with its own instance of the Dalvik virtual
machine. Dalvik has been written so that a device can run multiple VMs efficiently. The Dalvik
VM executes files in the Dalvik Executable (.dex) format which is optimized for minimal
memory footprint. The VM is register-based, and runs classes compiled by a Java language
compiler that have been transformed into the .dex format by the included "dx" tool.
The Davis VM relies on the Linux kernel for underlying functionality such as threading and low-
level memory management.

Figure 4.2: Android Framework [7]
Underlying all application is a set of services and system, including:

 A rich and extensible set of views that can be used to build an application, including list,
grids, text boxes, buttons etc.
 Content providers that enable application to access data from other application such as
contacts), or to share their own data.
 An Activity manager that manages the lifecycle of application and provides a common
navigation back stack.
 A telephony manager that provides access to information about the telephone services on the
devices. Application can use the methods in a class to determine telephony services and states
as well as to access some types of subscriber information.
 An Audio Manager provides access to volume and ringer mode control.
 A Broadcast Receiver that enables your application to receive intents set by other application
using the send Broadcast () method. Essentially, it enables your application to handle events
raised by other application.

Android SDK Versions
8]
Figure 4.3: Android Version (Development) [

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

Features:
New features are expected to be rolled out with each release of Android Studio. The following
features are provided in the current stable version:
 Gradle-based build support.
 Android-specific refactoring and quick fixes.
 Lint tools to catch performance, usability, version compatibility and other problems.
 ProGuard integration and app-signing capabilities.
 Template-based wizards to create common Android designs and components.
 A rich layout editor that allows users to drag-and drop UI components, option to preview
layouts on multiple screen configurations.
 Support for building Android Wear apps
 Built-in support for Google Cloud Platform, enabling integration with Google Cloud
Messaging and App Engine.
Figure 4.5: Firebase [10]
 Server and Database to interact with through API calls.
 Sync data from multiple applications.
 Only write front end code.

 Secure and monitor your data.
 Easy hosting

Features:
 Real-time Database − Firebase supports JSON data and all users connected to it receive
live updates after every change.
 Authentication − you can use anonymous, password or different social authentication.
 Hosting − the apps can be deployed over secured connection to Firebase servers.
JSON
Figure 4.6: JSON (Development) [11]
 JSON or JavaScript Object Notation is an open standard format that uses human-
readable text to transmit data objects consisting of attribute–value pairs.
 It is used primarily to transmit data between a server and web application, as an
alternative to XML.
 Although originally derived from the JavaScript scripting language, JSON is a language-
independent data format.
 Code for parsing and generating JSON data is readily available in a large variety of
programming languages.
 The JSON format was originally specified by Douglas Crock ford. It is currently
described by two competing standards, RFC 7159 andECMA-404.
 The ECMA standard is minimal, describing only the allowed grammar syntax, whereas
the RFC also provides some semantic and security considerations. The official Internet
media type for JSON is application/json.
 The JSON filename extension is.json.

PHP
Figure 4.7: PHP Side [12]
 PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language.
 While PHP originally stood for Personal Home Page, it now stands for PHP: Hypertext
Pre-processor, which is a recursive backroom.
 PHP code can be simply mixed with HTML code, or it can be used in combination with
various templating engines and web frameworks.
 PHP code is usually processed by a PHP interpreter, which is usually implemented as a

web server's native module or a Common Gateway Interface (CGI) executable.
 After the PHP code is interpreted and executed, the web server sends resulting output to
its client, usually in form of a part of the generated web page – for example, PHP code
can generate a web page's HTML code, an image, or some other data.

4.4 Programming Standard
 4.4.1 Which level the java language is belonging to?
Table 4.5 Difference between High, Middle and Low level Language
No High Level Middle Level Low Level

1 High level languages Middle level languages don’t Low level languages
provides almost everything provide all the built-in provides nothing other
that the programmer might functions found in high level than access to the
need to do as already built languages, but provides all machines basic
into the language building blocks that we need to instruction set
produce the result we want
2 Examples: C, C++ Assembler
Java, Python

4.4.2 Java language is a structured language
Table 4.6 Difference between Structure, Object and Non structure Oriented
No Structure oriented Object oriented Non structure

1 In this type of language, large In this type of language, There is no specific
programs are divided into programs are divided into structure for
small programs called objects programming this
functions language
2 Prime focus is on functions Prime focus is on the data that N/A
and procedures that operate on is being operated and not on
data the functions or procedures
3 Data moves freely around the Data is hidden and cannot be N/A
systems from one function to accessed by external functions
another
4 Program structure follows Program structure follows N/A
“Top Down Approach” “Bottom UP Approach”
5 Examples: C++, JAVA and C# (C sharp) BASIC, COBOL,
C, Pascal, ALGOL and FORTRAN
Modula-2

Project Id: - 57350 Implementation
CHAPTER 5: IMPLEMENTATION & TESTING
 WOW will not require any Electric circuit/board

 No extra Instrument/techniques are used
 Require knowledge of basic php.
 No manufacturing/fabrication process
 Source Tool-Android studio.
5.1 Implementation:
Figure 5.1: Splash Activity

Figure 5.2: Login Activity
Figure 5.3: Registration Activity

Figure 5.4: Edit Profile Activity
Figure 5.5: Dashboard

Figure 5.6: Helpline number Activity
Figure 5.7: Helpline Number Detail

Figure 5.8: Call from Helpline Number
Figure 5.9: Travel Safety Activity

Figure 5.10: Health Activity
Figure 5.11: Fitness details Activity

Figure 5.12: Nearby Activity
Figure 5.13: Nearby Hospitals Details

Figure 5.14: Hospital Details
Figure 5.15: Education Activity

Figure 5.16: BCA College Details
Figure 5.17: GYM Activity

Figure 5.18: GYM Tips Details
Figure 5.19: Women Law Activity

Figure 5.20: Details of Women Rights
Figure 5.21: School Activity

Figure 5.22: Details of Gujrati Medium School
Figure 5.23: Kitchen Activity

Figure 5.24: Details of Cateress
Figure 5.25: Pregnancy Guide Activity

Figure 5.26: Tips For Pregnancy
Figure 5.27: English Speech Activity

Figure 5.28: Speech Activity
Figure 5.29: Achievement Activity

Figure 5.30: Details for Post Achievement
Figure 5.31: Reminder Activity

Figure 5.32: Add a Reminder
Figure 5.33: Daily Quotes Activity

Figure 5.34: Details of Daily Quotes
Figure 5.35: News Feed Activity

Figure 5.36: Personal Dairy Activity
Figure 5.37: Add an Important Note

Figure 5.38: Feedback Activity
Figure 5.39: Give Feedback

Figure 5.40: Help

5.2 TESTING
5.2.1 TESTING PLAN
Similar to the project plan, due to confidentiality issues, we cannot provide details test plan to
the development team. We will still add the core components that make up our test plan.
5.2.2 TESTING STRATEGY
A typical screen in JAVA is tested at four levels before it goes for production.
 Level 1 is generally the work to be tested by other developers or other interns (this is
typical first level of testing where focus is not on requirement but end user testing)
Ratio: 0% end user: 100% Technical.
 Level 2 is level where a senior programmer comes into the testing cycle of the screen
that was unit tested by the developer in this phase the onus is to test software for
technical requirements specified.
 Level 3 is where a tester will come into picture. The tester will test the software for both
end user as well as technical point of view.
 Level 4 is where we make the code at Release-Ready. Here screen is tested to the core
and each and every standard must be followed and verified.
This allows us to text a screen at four levels and at the end of four weeks when the screen goes
to production, it is generally bug free because more people have looked at this screen from
different viewpoints.
 UNIT TESTING
Unit testing, also known as component testing refers to tests that verify the functionality of a
specific section of code, usually at the function level. In an object-oriented environment, this is
usually at the class level, and the minimal unit tests include the constructors and destructors.
These types of tests are usually written by developers as they work on code (white-box style),

to ensure that the specific function is working as expected. One function might have multiple
tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the
functionality of a piece of software, but rather is used to assure that the building blocks the
software uses work independently of each other.
Unit testing is a software development process that involves synchronized application of a

broad spectrum of defect prevention and detection strategies in order to reduce software
development risks, time, and costs. It is performed by the software developer or engineer
during the construction phase of the software development lifecycle. Rather than replace
traditional QA focuses, it augments it. Unit testing aims to eliminate construction errors before
code is promoted to QA; this strategy is intended to increase the quality of the resulting
software as well as the efficiency of the overall development and QA process.
Depending on the organization's expectations for software development, unit testing might
include static code analysis, data flow analysis metrics analysis, peer code reviews, code
coverage analysis and other software verification practices.
 INTEGRATION TESTING
Integration testing is any type of software testing that seeks to verify the interfaces between
components against a software design. Software components may be integrated in an iterative
way or all together ("big bang"). Normally the former is considered a better practice since it
allows interface issues to be located more quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction between integrated
components (modules). Progressively larger groups of tested software components
corresponding to elements of the architectural design are integrated and tested until the
software works as a system.
It is basically divided into two types of testing:
1. Top-down integration testing
 Main control module used as a test driver and stubs are substitutes for components

directly subordinate to it.
 Subordinate stubs are replaced one at a time with real components (following the
depth-first or breadth-first approach).
 Tests are conducted as each component is integrated.
 On completion of each set of tests and other stub is replaced with a real component.
 Regression testing may be used to ensure that new errors not introduced.
2. Bottom-up integration testing
 Low level components are combined in clusters that perform a specific software function.
 A driver (control program) is written to coordinate test case input and output.
 The cluster is tested.
 Drivers are removed and clusters are combined moving upward in the program structure.
5.2.3 TESTING METHODS
Testing presents an interesting anomaly for the software engineering activities and attempts to
build software from an abstract concept to tangible product for engineer. Now comes testing. The
engineer creates a series of test case that are initiated to "demolish" the software that has been
build.
 Models of Testing:
Software testing methods are traditionally divided into white- and black-box testing. These
two approaches are used to describe the point of view that a test engineer takes when
designing test cases.

1. White-box testing
 It is also known as clear box testing, glass box testing, transparent box testing and structural
testing.
 It is used to test internal structures or workings of a program, as opposed to the functionality

exposed to the end-user.
 In white-box testing an internal perspective of the system, as well as programming skills, are
used to design test cases.
 The tester chooses inputs to exercise paths through the code and determine the appropriate
outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).
 While white-box testing can be applied at the unit, integration and system levels of the
software testing process, it is usually done at the unit level.
 It can test paths within a unit, paths between units during integration, and between
subsystems during a system–level test.
 Though this method of test design can uncover many errors or problems, it might not detect
unimplemented parts of the specification or missing requirements.
 Techniques used in white-box testing include:
i. API testing (application programming interface) – testing of the application using

public and private APIs
ii. Code coverage – creating tests to satisfy some criteria of code coverage.
iii. Fault injection methods – intentionally introducing faults to gauge the efficacy of
testing strategies
iv. Mutation testing methods
v. Static testing methods
Code coverage tools can evaluate the completeness of a test suite that was created with any
method, including black-box testing. This allows the software team to examine parts of a

system that are rarely tested and ensures that the most important function points have been
tested. Code coverage as a software metric can be reported as a percentage for:
 Function coverage, which reports on functions executed
 Statement coverage, which reports on the number of lines executed to complete the test
100% statement coverage ensures that all code paths, or branches (in terms of control flow) are
executed at least once. This is helpful in ensuring correct functionality, but not sufficient since
the same code may process different inputs correctly or incorrectly.
2. Black-box testing
Figure 5.41 Black-box
 Black-box testing treats the software as a "black box", examining functionality without any
knowledge of internal implementation.
 The testers are only aware of what the software is supposed to do, not how it does it. Black-
box testing methods include: equivalence partitioning, boundary value analysis, all-pairs
testing, state transition tables, decision table testing, fuzz testing, model-based testing,
use case testing, exploratory testing and specification-based testing.
5.2.4 TEST CASES
5.2.4.1 Purpose
Purpose of this application is to reduce the overall overhead in paper work and all the records
are maintained such that the user as well as administrator can easily segment them into desired
properties so it is easy for any novice user to have access to the application. Another purpose is
to make record of papers in database so that it can be referred in future.

5.2.4.2 Required Input & Expected Result
Black Box Testing
Table 5.1 Data entering at Registration
Test Case Title Entering Data during Registration
Purpose of test Data enters successfully or not
Test-data Enrolment no., Username, Name, Department,

E-mail, Password, Confirm Password, Gender,
Image.
Steps  Enter values for all listed above
 Click on the submit button.
 Check the validations.
 Database is checked after submit button whether

the new data are entered or not.
 After complete entering of data and after
pressing submit button, intended page must
open.
 Else an error message is displayed.
Expected Result The Home Page is loaded.
Notes & Questions Que: Which fields are compulsory?

Ans: All fields are compulsory.
Note: User should meet all validations and also
enter valid email address should verify email
verification.

Table 5.2 Login into System
Test Case Title Login to the system

Purpose of test Enabling a user to login to the system
Test-data Username : Admin@gmail.com
Password: *******
Steps  Enter a username and password
 Click on the login button.
 Database is checked to see if the

username/password exists.
 If it exists, the home page opens.
 Else an error message is displayed.

Expected Result The Main Menu page is loaded depending on
the User logged in.
Notes & Questions Que: Who can log into the site?
Ans: Only registered users can log into the
site.
Note: The username field should not exceed
the preset length. Username and password
fields could not be blank.
Table 5.3 Checking Change Password
Test Case Title Changing Password
Purpose of test Data enters successfully or not

Test-data Username, old Password, New Password,
Confirm Password.

Steps  Enter values for all listed above
 Click on the submit button.
 Check the validations.
 Database is checked after submit button whether

the new data are entered or not.
 After complete entering of data and after
pressing submit button, intended page must
open.
Expected Result  Else
The an error message
Changing is displayed.
Password Page is loaded.
Notes & Questions Que: Who can change password?

Ans: Only registered user can change password.
Note: User should meet all validations.

Project Id: - 57350 Reference
REFERENCE
Books:
[1] Java ( E-balaguruswamy)
[2] Composing Mobile Apps: Learn, Explore, Apply using Android
Internet References:
[1] https://docs.google.com/viewer?url=patentimages.storage.googleapis.com/pdfs/US8626
774.pdf
[2] https://www.google.com/patents
[3] http://iosrjournals.org/iosr-jce/papers/Vol17-issue1/Version-1/F017112934.pdf
[4] http://www.ijteee.org/final-print/may2015/Sauver-An-Android-Application-For-
Women-Safety.pdf
[5] http://ijmcr.com
[6] http://googlemix.ru/wp-content/uploads/2011/09/androidHD.jpg
[7] http://learn.jobisite.com/wp-content/uploads/2010/11/android-architecture.png
[8] http://digitalpage.xyz/wp-content/uploads/2016/05/Android-History3-1024x771.png
[9] https://tctechcrunch2011.files.wordpress.com/2017/02/android-studio-logo.png
[10] https://1.bp.blogspot.com/YIfQT6q8ZM4/Vzyq5z1B8HI/AAAAAAAAAAc/UmWSS
MLKtKgtH7CACElUp12zXkrPK5UoACLcB/s1600/image00.png
[11] http://cdn.crunchify.com/wp-content/uploads/2012/10/json-logo.jpg
[12] http://www.xappsoftware.com/wordpress/wp-content/uploads/2014/02/PHP.png

Project Id: - 57350 Appendix
APPENDIX
th
PPR –I (7 Semester)
What Progress you have made in the Project?
We start our work and now we are analysis and gathering all the requirement of different module
of project.
What challenge you have faced?
As started working, we faced little problem in requirement gathering.
What support you need?
We need little support from our college to collecting different data of our module.
Which literature you have referred?
www.androidhive.com
www.vogellatutorial.com
www.androidexample.com
th
PPR –II (7 Semester)
Till now we have done the analysis and designing part. We have gathered all the requirement.
And right now we are almost done with the designing i.e. diagrams. Also 50% database is almost
done.
Yet we haven't faced any major challenge but if in future if we face any then we will let you
know.

We want some general data like, helpline number, women related laws, location of some places
like police station, court, hospitals, etc. so we will be grateful for those people who help us to
collect data. We will like to get support from college as well as from university for getting these
data.
1. Android Programming Tutorials By Marks L. Murphy
2. ANDROID TUTORIALTutorialpoint.com

3. Developer.android.com
4. code learn.org
th
PPR –III (7 Semester)
Till now we have done all the important system dependent diagram that is system requirement
specification. Now we are working on making data dictionary.
we faced little problems in making data flow diagram, Use case diagram and sequence diagram.
We want some general data like, helpline number, women related laws, location of some places
like police station, court, hospitals, etc.
www.androidarsenal.com
www.github.com
th
PPR –IV (7 Semester)
We have done all the diagram and now we are completing data dictionary related to our module,
in which contain all detail also included all the system diagram in the final report. Also Canvas is
ready and made it as requirement of our application.
We faced problem in gathering the location based data which is most important part of our
application.
we need women related laws information about school, hospital, bank, etc.
www.androidexample.com
www.javatutorialpoint.com
www.programminghub.com
th
PPR –I (8 Semester)
in current semester we have started the second module.


in current semester we have study basic of android programming language.in first module, we
have solve the some difficult error.
We will need proper guidance for android programming language. We will also need some
technical support from out professor to install necessary software and android software
development kit. We have studied android programming book for learning Android.
for reference purpose we have use following research paper. Title: SafeStreet: empowering
women against street harassment using a privacy-aware location based application Pub No:
ISBN: 978-1-4503-3163-0
th
PPR –II (8 Semester)
we done how to retrieve data online.
in second module face some issue like user authentication, retrieve online data, etc.
We will need proper guidance for retrieving data successfully. We have studied android
programming websites to learn fetch data.
https://developer.android.com
th
PPR –III (8 Semester)
create database regarding our mobile application and also to complete the connectivity of
designing module with database by using server scripting.
To follow the design pattern and create the mobile application as per architecture is a challenging
task.
For the better understanding of application’s architecture required experience person guidance.

https://github.com/
www.androidarsenal.com
www.androidhive.com
th
PPR –IV (8 Semester)
we have complete most of part of our application and also we are thinking about to implement
new features of our projects.
we have faced many problem in implementing the application front end as well as back end side.
we need an advice from our seniors, Internal guide, external guide and other experts for
programing and implementing attractive features and designing.
https://developer.android.com/training/design-navigation/screen-planning.html
https://www.codeproject.com
https://developer.android.com/samples

BUSINESS MODEL CANVAS (BMC)

1. Key Partners
In this fig. following are the key partners which perform activities to complete our project work.
Figure 1: Key Partners

 Computer Scientist (Coder) to develop code.
 Google is very helpful for this app such as searching the Code, any other new ideas etc.
 Developer make the implementation.

2. Key Activities
Figure 2: Key Activities
 Stable Application there is more than one quite different thing they might mean.
 Expanded Database very large database to store large amount of data.
 Resource Implementation to implement different resources in application.

3. Key Resources
The following key resources are we requiring needed to maintain business model.
Figure 3: Key Resources
 Smart Phone is used for Patients.

 Intellectual to use data directly or indirectly.

4. Value Propositions
For our project we should deliver value to the User. Our user problems helping to solve and their
needs are satisfying. That is:
Figure 4: Value Propositions

 Providing women ability to easily navigate on application.
 Easy and Interactive User-Interface (UI).
 Availability of Important Contact / Laws.
 Announcement and Rewards.

5. Customer Relationships
Figure 5: Customer Relationships

 Self - Service
 Automated service or Non-automated service
 Communities

6. Channels
Figure 6: Channels
 Awareness
 Facebook

7. Customer Segments
In our project following are the most important users:
Figure 7: Customer Segments
 Niche Market
 Diversity
 Internet User
 Advertiser & Marketer

8. Cost Structure
In our project following are the different areas where cost involved during android application
development or hardware and the full structure as shown below is affects cost of product directly
Figure 8: Cost Structure
 Software Development (IT)

 Consulting

9. Revenue Stream
Figure 9: Revenue Stream

 Advertising and Featuring

WOW Report2016

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WOW Report2016

Uploaded by

Copyright:

Available Formats

“World of Women (WOW)”

Mr. Pranav Rangwala

Mahavir Swami College of Engineering & Technology, Surat

Mr. Pranav Rangwala Dr. S.V. Patil Ms Bhavika Patel

(Internal Guide) (Principal) (Head of Department)

Company Name Raksh Infotech

BRIEF OVERVIEW / HIGHLIGHTS

SERVICES & TECHNOLOGY

 Mobile Application Development

This is to certify that the Project-II entitled “WOW” submitted by Kapadia

Date: Head of the department

Table No Table Description Page No

Table 3.1 Project Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 3.2 Development Criteria . . . . . . . . . . . . . . . . . . . . . . 25

Table 3.3 Project development chart . . . . . . . . . . . . . . . . . . . 26

Table 4.1 Hardware Requirement (Mobile) . . . . . . . . . . . . . . 27

Table 4.2 Hardware Requirement (Developer) . . . . . . . . . . . . 27

Table 4.3 Software Requirement (Mobile) . . . . . . . . . . . . . . . 27

Table 4.4 Software Requirement (Developer side) . . . . . . . . . 27

Table 4.5 Difference between High, Middle and Low Level

Table 4.6 Difference between Structure, Object and Non

Table 5.1 Data Entering at Registration. . . . . . . . . . . . . . . . . . 64

Table 5.2 Login into System. . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table 5.3 Checking Change Password . . . . . . . . . . . . . . . . . . 65

Figure No Figure Description Page No

Figure 2.1 Context level Data Flow Diagram . . . . . . . . . . . . . . . 8

Figure 2.2 1st Level Data Flow Diagram . . . . . . . . . . . . . . . . . . 9

Figure 2.3 2nd Level DFD for Registration & Login . . . . . . . . . . . . 10

Figure 2.4 2nd Level DFD for Laws . . . . . . . . . . . . . . . . . . . . . 11

Figure 2.5 2nd Level DFD for Health . . . . . . . . . . . . . . . . . . . . . 12

Figure 2.6 2nd Level DFD for Helpline . . . . . . . . . . . . . . . . . . . . 13

Figure 2.7 2nd Level DFD for Education . . . . . . . . . . . . . . . . . . 14

Figure 2.8 2nd Level DFD for Feedback . . . . . . . . . . . . . . . . . . 15

Figure 2.9 AEIOU Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 2.10 Empathizing Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 2.11 Ideation Canvas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 2.12 Product Development Canvas . . . . . . . . . . . . . . . . . . 19

Figure 2.13 Business Model Canvas (BMC). . . . . . . . . . . . . . . . . 20

Figure 3.1 Waterfall Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 4.1 Android OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 4.2 Android Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 4.3 Android Version (Development) . . . . . . . . . . . . . . . . 31

Figure 4.4 Android Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 4.5 Firebase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Figure 4.7 PHP Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 5.1 Splash Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Figure 5.2 Login Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 5.3 Registration Activity . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 5.4 Edit Profile Activity . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 5.5 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 5.6 Helpline Number Activity . . . . . . . . . . . . . . . . . . . . . 41

Figure 5.7 Helpline Number Detail . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 5.8 Call from Helpline Number . . . . . . . . . . . . . . . . . . . . 42

Figure 5.9 Travel Safety Activity. . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 5.10 Health Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 5.11 Fitness Details Activity. . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 5.12 Nearby Activity . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 5.13 Nearby Hospitals Details . . . . . . . . . . . . . . . . . . . . . . 44

Figure 5.14 Hospital Details . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 5.15 Education Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 5.16 BCA College Details . . . . . . . . . . . . . . . . . . . . . . . . . 46

Figure 5.17 GYM Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Figure 5.18 GYM Tips Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 47