Women Safety App

TECHNICAL REPORT

SUBMITTED BY
Fatima Zahid
(2021-ag-9479)

ADVISED BY
Sir Haris Pervaiz

A TECHNICAL REPORT SUBMITTED IN PARTIAL FULFILLMENT OF

REQUIREMENT FOR THE DEGREE OF
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE
DEPARTMENT OF COMPUTER SCIENCE
FACULTY OF SCIENCES
​ ​ ​
​

UNIVERSITY OF AGRICULTURE FAISALABAD

DECLARATION

I hereby declare that the contents of the report “Women Safety App” is project of my own and
no part has been copied from any published source (except the references). I further declare that
this work has not been submitted for award of any other diploma/degree. The university may
take action if the information provided is found false at any stage. In case of any default the
scholar will be proceeded against as per UAF policy.

_________________
Fatima Zahid​
2021-ag-9479
​ ​ ​
​

CERTIFICATE

To,
The Controller of Examinations,
University of Agriculture,
Faisalabad.

The supervisory committee certify that Fatima Zahid bearing 2021-AG-9479 has successfully
completed his project in partial fulfillment of requirement for the degree of BS Computer
Science under our guidance and supervision.

_____________________________________
Sir Haris Pervaiz
Supervisor

_____________________________________
Mr. Haris Pervaiz
Advisor,
Computer Science
​ ​ ​
​

ACKNOWLEDGEMENT

I thank all who in one way or another contributed to the completion of this report. I am so
grateful to the Department of Computer Science for making it possible for me to study here. My
special and heartily thanks to my advisor, Supervisor Sir Haris Pervaiz who encouraged and
directed me. His/her challenges brought this work towards completion. It is with his/her
supervision that this work came into existence. For any faults, I take full responsibility. I am
thankful to my fellow students whose challenges and productive critics have provided new ideas
for the work. Furthermore, I also thank my family who encouraged me and prayed for me
throughout the time of my research. May the Almighty God richly bless all of you.
​ ​ ​
​

ABSTRACT

Mehr-e-Aman is a women’s safety web and mobile application developed with the mission to
provide fast, accessible, and secure emergency support services for women in Pakistan.
Recognizing the growing concern around gender-based violence and the lack of immediate
resources in critical moments, Mehr-e-Aman was conceptualized to empower women through
technology. This project addresses the problem of unavailability of centralized, easy-to-use, and
real-time safety solutions for women, especially in urban and semi-urban regions. The focus was
to deliver a platform that offers functionalities such as fake calls, live location sharing,
emergency alerts, helpline shortcuts, safe ride booking, self-defense guides, and more —
enabling users to take quick actions when they feel threatened.
The project employed the Agile methodology, enabling iterative development, client feedback,
and modular deployment of features. The application was developed using the MERN stack
(MongoDB, Express.js, React.js, Node.js), Tailwind CSS for responsive styling, Framer Motion
for animations, and integrated APIs for location and alerting services. Testing was carried out
using manual test cases and iterative validation against both functional and non-functional
requirements.
Results from testing revealed that all core modules functioned successfully with positive
feedback during usability testing. The application demonstrated high reliability in delivering
alerts and updates in real-time, with intuitive navigation and UI responsiveness. In conclusion,
Mehr-e-Aman serves as a robust, scalable, and impactful solution aimed at improving women's
safety through a blend of modern web technologies and thoughtful user-centric design.
​ ​ ​
​

Table of Contents

CHAPTER 1 - INTRODUCTION...................................................................................................1
1.1 Background.......................................................................................................................... 1
1.2 Description.........................................................................................................................1
1.3 Problem Statement............................................................................................................ 2
1.4 Scope.................................................................................................................................2
1.5 Objectives.......................................................................................................................... 2
1.6 Feasibility.............................................................................................................................2
1.7 Requirements....................................................................................................................... 3
1.7.1 Functional Requirements............................................................................................ 3
1.7.2 Non- Functional Requirements................................................................................... 3
1.7.3 Hardware Requirements..............................................................................................3
1.7.4 Software Requirements...............................................................................................4
1.8 Stakeholders.........................................................................................................................4
Chapter 2 – MATERIALS & METHODS....................................................................................... 5
2.1 Process Model......................................................................................................................5
2.2 Tools & Technologies.......................................................................................................... 5
2.3 Design................................................................................................................................6
2.3.1 Use Case Diagrams..................................................................................................7
2.3.2 Usage Scenario...................................................................................................... 10
2.3.3 Sequence Diagram:................................................................................................... 12
2.3.4 Class Diagram:..........................................................................................................15
2.3.5 Data Flow Diagram:..................................................................................................16
2.3.6 ER Diagram:............................................................................................................. 19
2.3.7 Database Model:....................................................................................................... 20
2.3.8 Architecture:............................................................................................................. 21
Chapter 3 - RESULTS & DISCUSSION.......................................................................................23
3.1 Testing............................................................................................................................. 23
3.2 Test Cases....................................................................................................................... 23
3.3 Conclusion:........................................................................................................................ 27
Chapter 4 - USER MANUAL........................................................................................................26
References.................................................................................................................................. 28

1
​ ​ ​
​

List of Figures

Figure ‎1.1 Stakeholders​ 4

Figure ‎2.1 Agile Activities​ 5
Figure 2.‎2 Use Case Diagram​ 10
Figure 2.3 Sequence Diagram​ 14
Figure 2.4 Class Diagram​ 15
Figure ‎2.5 Context Diagram 16
Figure ‎2.6 Level 0 DFD​ 17
Figure 2.7 Level 1 DFD​ 18
Figure ‎2.8 Entity Relationship Diagram​ 20
Figure 2.9 Database Model​ 22
Figure ‎2.10 Applications's Architecture​ 24
Figure ‎4.1 Signing in​ 28

2
​ ​ ​
​

List of Tables

Table 2. 1: Add User​ 12

Table 3. 1: User login Test Case​ 27

3
University of Agriculture Faisalabad​ ​ ​
​ ​ Chapter 1 - Introduction

CHAPTER 1 - INTRODUCTION

1.1 Background
The alarming increase in gender-based violence and safety concerns for women, especially in
regions like Pakistan, necessitates the development of technological solutions to provide
immediate assistance and assurance. Mehr-e-Aman is a women safety application designed using
the MERN (MongoDB, Express.js, React, Node.js) stack to serve as a digital guardian, offering
tools for emergency alerts, location tracking, safe ride booking, and informative safety guides. In
many cases, women in distress face difficulty reaching out for help due to societal constraints,
limited resources, or lack of awareness. Mehr-e-Aman aims to bridge this gap with accessible
technology that empowers women to report incidents, alert their trusted contacts, and find quick
solutions in threatening situations. This application is particularly relevant in the Pakistani
context where social and cultural norms often limit women’s autonomy. With increasing
smartphone penetration and digital literacy, there is a strong potential for such an app to become
a critical part of everyday safety planning. By leveraging real-time features and an intuitive user
interface, Mehr-e-Aman not only ensures safety but also builds a support network that women
can rely on during emergencies. This background justifies the creation of Mehr-e-Aman as a step
toward safer communities.
1.2 Description
Mehr-e-Aman is a comprehensive safety and emergency response platform aimed at enhancing
personal safety for women in Pakistan. The application offers a range of features including
emergency alert systems, real-time location sharing, incident reporting, self-defense guides, and
access to verified emergency contacts. The core functionality revolves around rapid accessibility
and ease of use during emergencies. Upon launching the app, users can immediately access a
panic button that triggers alerts to emergency contacts along with live location sharing. The app
also includes a "Fake Call" feature to help women navigate dangerous situations discreetly.
The system utilizes MongoDB for storing user and incident data securely, Express.js and Node.js
for backend server operations, and React for building responsive and user-friendly frontend
interfaces. One of the primary goals of Mehr-e-Aman is to reduce response time during
emergencies and enable women to make informed decisions regarding their safety. Potential
pitfalls include challenges in real-time location accuracy, user data privacy, and internet
connectivity. However, these issues are mitigated through offline fallback mechanisms and
encrypted data handling.
Key stakeholders include app users (women), emergency responders, law enforcement agencies,
and NGOs focused on women’s rights. The application is built with scalability in mind, allowing
integration with governmental safety initiatives and additional APIs like Google Maps and SMS
gateways. Implementation will follow an agile methodology to ensure continuous feedback and
improvements. The description outlines how Mehr-e-Aman not only solves existing problems
but also empowers its users through proactive safety management tools.

Women Safety App ​ 1

University of Agriculture Faisalabad​ ​ ​
​ ​ Chapter 1 - Introduction
1.3 Problem Statement
Women in Pakistan often face safety threats ranging from harassment to physical assault in both
public and private spaces. Traditional response mechanisms are slow, uncoordinated, and
inaccessible in times of urgent need. The core problem is the lack of an integrated, real-time, and
user-friendly solution that can provide immediate assistance and assurance during emergencies.
The issue lies not in the absence of technology but in its underutilization for public safety,
particularly for vulnerable groups like women.
Mehr-e-Aman addresses this problem by offering a reliable digital platform that connects users
with emergency contacts, live location sharing, and situational guidance. This project aims to
ensure that help is always a tap away, thereby increasing the sense of security among women and
reducing the response time during critical situations.
1.4 Scope
The scope of Mehr-e-Aman includes the development, deployment, and maintenance of a
MERN-stack based web and mobile application for women’s safety in Pakistan. The application
encompasses emergency alert features, fake calls, live location sharing, safety tips, and access to
helpline numbers. The project also includes a user dashboard for personal information
management and incident history.
Out of scope features include law enforcement API integrations and in-app live video streaming,
which may be considered for future updates. The project targets urban and semi-urban regions of
Pakistan with a plan to expand services based on user feedback. The scope also involves
stakeholder training and awareness programs for effective usage.

1.5 Objectives
To enhance women’s safety and response time during emergencies through a digital platform.
Objectives:
●​ Design and develop an intuitive user interface for web and mobile platforms.
●​ Implement real-time location sharing and emergency alert features.
●​ Provide self-defense tips and educational resources.
●​ Enable users to report incidents and access emergency helplines.
●​ Ensure data security and user privacy through encrypted communication.

1.6 Feasibility

1.6.1 Technical Feasibility – The development team has strong proficiency in MERN stack
technologies, and the platform leverages commonly available APIs and libraries, ensuring
technical feasibility.

1.6.2 Schedule Feasibility – The project is designed to be completed in three main phases over
six months. The schedule includes design, development, testing, and deployment.

Women Safety App ​ 2

University of Agriculture Faisalabad​ ​ ​
​ ​ Chapter 1 - Introduction
1.6.3 Economic Feasibility – The application uses open-source technologies to minimize cost.
Hosting and deployment are optimized using scalable cloud services. Economic feasibility is
validated by a low initial investment.

1.6.4 Cultural Feasibility – Mehr-e-Aman promotes safety without disrupting cultural norms. It
ensures privacy and security, making it culturally acceptable.

1.6.5 Legal/Ethical Feasibility – The application abides by Pakistan’s cyber laws and data
privacy regulations. Ethical considerations like user consent and data transparency are
implemented.

1.6.6 Resource Feasibility – Development tools, human resources, and cloud hosting are already
available or budgeted. No significant resource constraints are anticipated.

1.6.7 Operational Feasibility – The application is designed to function in offline mode for
critical features. It is operable with minimal training, making it viable for widespread use.

1.7 Requirements
1.7.1 Functional Requirements
FR01: User log in
FR01-01 System shall get Username and Password from user
FR01-02 System shall authenticate login credentials
FR01-03 System shall allow access on valid login
FR01-04 System shall show error message on invalid login
FR02: Emergency Alert
FR02-01 System shall provide a panic button
FR02-02 System shall send location to emergency contacts

1.7.2 Non- Functional Requirements

NFR01: System shall be available 24/7
NFR02: System shall respond within 3 seconds
NFR03: System shall ensure encrypted communication
NFR04: System shall have mobile and desktop compatibility

1.7.3 Hardware Requirements

Intel Core i3 or higher

Women Safety App ​ 3

University of Agriculture Faisalabad​ ​ ​
​ ​ Chapter 1 - Introduction
RAM: 4GB minimum
Hard Disk: 40GB or more

1.7.4 Software Requirements

Windows 10 or higher Browser: Google Chrome, Firefox, Edge Node.js: v18 or higher
MongoDB: 6.0+

1.8 Stakeholders
●​ End Users (Women in Pakistan)
●​ Developers
●​ NGOs and Safety Organizations
●​ Law Enforcement Agencies (future scope)
●​ Project Sponsors and Investors

Figure 1.1: Stakeholders

Women Safety App ​ 4

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods

Chapter 2 – MATERIALS & METHODS

2.1 Process Model

For the development of the Mehr-e-Aman – Women Safety Web Application, the Agile process
model was adopted. Agile methodology is a form of Rapid Application Development and is ideal
for iterative and incremental software development. It divides the entire development lifecycle
into small, manageable sprints or iterations, which allow for adaptive planning, evolutionary
development, early delivery, and continuous improvement.​
​
In the context of Mehr-e-Aman, Agile allowed for frequent feedback from stakeholders
(students, instructors, and potential end-users), ensuring that features like emergency alerts, live
tracking, safe zone indicators, and community help were refined iteratively based on real-time
needs. The iterative approach also enabled us to respond swiftly to change requests, fix emerging
issues early, and deploy working modules faster.​
​
Each sprint focused on completing key components of the system such as user registration and
authentication, alert management, location sharing, dashboard design, and profile management.
Agile ceremonies including daily stand-ups and sprint reviews ensured regular monitoring and
timely adaptation.

Figure 2.1: Agile Activities

2.2 Tools & Technologies​

• React.js – For building the responsive frontend user interface.
• Tailwind CSS – For rapidly styling and customizing components.
• Node.js – As the runtime environment for executing JavaScript on the server.
• Express.js – A backend framework used to build RESTful APIs.
• MongoDB – A NoSQL database used to store user information and emergency reports.
• JWT (JSON Web Tokens) – Used for secure user authentication.
• Vite – For efficient frontend development and bundling.
• Axios – To handle HTTP requests between frontend and backend.
• Framer Motion – For adding animations to the interface.
• Heroicness & React Icons – For icons used across the application.
• VS Code – The primary code editor used for development.
• Git & GitHub – For version control and team collaboration.
• Postman – For API testing and validation.
• Render & MongoDB Atlas – For deploying frontend and database services.

Women Safety App ​ 5

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
2.3 Design
Use Case Diagram
A use case is a functional requirement that users expect from the system. It describes how
external actors interact with the system to achieve a specific goal. A Use Case Diagram visually
represents these interactions, showing relationships between the system and its environment
(actors) through defined system functionalities (use cases).
Use cases should be appropriately sized—each covering a complete and useful system task. Very
small (e.g., Enter Password) or overly broad (e.g., Manage All Features) use cases are avoided.
For the Mehr-e-Aman Women Safety App, the system provides various safety features
accessible from a central point after user authentication.

1.1 Components of the Use Case Diagram

Actors
Actors are external entities (usually users or other systems) that interact with the system. In this
project:
●​ User: The person using the app for safety and emergency assistance.
Use Cases
These are the specific functions the user can perform:
●​ Sign Up: Allows a new user to register on the app.
●​ View Home Page: Main screen after login; provides access to core features.
●​ Make Fake Call: Simulates a fake incoming call to help the user exit unsafe situations.
●​ Send Current Location: Sends the user’s real-time location to selected emergency
contacts.
●​ Save Emergency Contacts: Enables the user to save and manage trusted contact
numbers.
●​ Call Emergency Number (1122): Instantly connects the user to emergency services.
Associations
Solid lines represent interactions between the user and each use case. These indicate direct usage
of system features.
System Boundary
The system boundary defines what is inside (the system’s functionalities) and what is outside
(external actors). In this case, all use cases are encapsulated within the Mehr-e-Aman System
boundary.
Relationships Between Use Cases
●​ <<include>> Relationship:
●​ The View Home Page use case includes the functionality of:
▪​ Make Fake Call

▪​ Send Current Location

▪​ Save Emergency Contacts
▪​Call Emergency Number
●​ These are embedded functionalities accessible from the home page.

1.2 Use Case Diagram – Mehr-e-Aman

Women Safety App ​ 6

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
Here is the textual layout of the diagram. A proper UML diagram can be created based on this
structure using tools such as Lucidchart, Draw.io, or StarUML.

+-------------------------------------------+
| Mehr-e-Aman System |
| |
| ○ Sign Up |
| ○ View Home Page |
| ├── <<include>> Make Fake Call |
| ├── <<include>> Send Location |
| ├── <<include>> Save Contacts |
| └── <<include>> Call 1122 |
+-------------------------------------------+
↑
[User]

2.3.1 Use Case Diagrams

A use case is a functionality that users need from the system. A use case diagram depicts the
relationship among the actors and use cases. Each use case should ideally represent a complete
and meaningful functionality. The size of a use case should be moderate — neither too granular
(e.g., “Enter Password”) nor too broad (e.g., “Manage Entire System”).

For the Mehr-e-Aman women safety application, the main actor is the User, and the system
provides functionalities such as signing up, making fake calls, sending current location,
saving emergency contacts, and calling emergency services (e.g., 1122). These are
moderate-sized, meaningful use cases representing distinct actions a user performs.

The components in a use case diagram include:

Actors:
Actors represent external entities that interact with the system. In Mehr-e-Aman, the primary
actor is the User, who initiates all system actions. The actor is represented as a stick figure with
the label User beneath it.

Use Cases:

Use cases define the functional behavior of the system. In this application, the following use
cases have been identified:
●​ Sign Up
●​ View Home Page

Women Safety App ​ 7

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
●​ Make Fake Call
●​ Send Current Location
●​ Save Emergency Contacts
●​ Call Emergency Number (1122)
●​
Associations:

Solid lines connect actors to the use cases they interact with. These lines represent associations
that show direct communication between the user and a specific functionality.

System boundary:

The system boundary is depicted as a rectangle enclosing all the use cases and labeled as
Mehr-e-Aman System. The actor remains outside this boundary, indicating they are external to
the system.
Relationship between Use cases:
i)​ Include:

Include Relationship (<<include>>):​

The View Home Page use case includes other use cases such as Make Fake Call, Send
Current Location, Save Emergency Contacts, and Call Emergency Number. These
functionalities cannot be accessed without first reaching the home page. Hence, they are
modeled using the <<include>> relationship.

Uses:
Below is a textual representation of the use case diagram. A visual diagram should be created in
UML modeling tools like Lucid chart, Draw.io, or StarUML using this structure.
+--------------------------------------------+
+--------------------------------------------+
| Mehr-e-Aman System |
| |
| ○ Sign Up |
| ○ View Home Page |
| ├──<<include>> Make Fake Call |
| ├──<<include>> Send Location |
| ├──<<include>> Save Contacts |
| └──<<include>> Call 1122 |
+--------------------------------------+
↑
[User]

ii)​ Extend:

Women Safety App ​ 8

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
A use case extends another use case to do more than the latter. It extends the functionality of one
use case to further level. is displayed in the diagram editor as a dashed line with an open
arrowhead pointing from the extension use case to the base use case. The arrow is labeled with
the keyword «extend».

Use Case Diagram:

Women Safety App ​ 9

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods

Figure 2.2 Use Case Diagram

2.3.2 Usage Scenario

Use Case Title Trigger SOS Alert

Abbreviated Title
Use Case Id 1
Requirement Id 3
Description:
This use case allows a user to send an SOS alert with location to predefined emergency contacts.
Pre Conditions: 1. User must be logged in
2. Emergency contacts must be added
Task Sequence Exceptions
1.​ User presses the SOS button
2.​ System fetches user’s current location
3.​ System sends SMS and push notification with location to contacts
4.​ System logs the event in database

Post Conditions: SOS alert sent to contacts with location

Unresolved issues:
Authority: Registered User
Modification history: 1.0
Author: Mehr-e-Aman Team
Description: Initial scenario draft

▪​ Use Case Title: Add User

▪​ Use Case Id: UC-01

▪​ Requirement Id: FR-03

▪​ Description: This use case is about adding a new user to the existing system with the
privileges defined at the time of user account creation.
▪​ Pre Conditions:
1.​ All must-required information about the new user should be available.
2.​ Database should be available in online mode.

▪​ Task Sequence & Exceptions

Task Sequence Exceptions

Women Safety App ​ 10

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
1.​ Administrator opts to Add a new user account.
2.​ System asks for necessary information.

3.​ Administrator provides all the required information and opts to

complete the operation.
4.​ There is a problem in the data provided; some data needs to be
corrected.
5.​ System after confirmation adds the new account
6.​ System sends the account creation email to the administrator’s email
id and user’s email address.

▪​ Post Conditions
●​ A new user account is successfully created.
●​ Unresolved Issues: None
●​ Authority: Administrator
●​ Modification History: 1.0
●​ Author: Mehr-e-Aman Group
▪​ Description

▪​ Initial version documented as part of usage scenarios for the Mehr-e-Aman project.

Table 2. 1: Add User

Use Case Title Login User

Use Case Id UC-02
Requirement Id FR-01
Description: This use case allows registered users to authenticate and access their profile/dashboard.
Pre Conditions: User mustbe registered in the system.
Internet connection must be available.
Task Sequence Exceptions
1.​ User enters login credentials. Invalid email or
password entered.
2.​ System verifies credentials. Account blocked
or not activated.
3.​ If valid, user is redirected to their dashboard
4.​ A session token is created for maintaining authentication

Post Conditions:
•​ User is logged in and granted access to the dashboard.
Unresolved issues: None
Authority: Registered User

Women Safety App ​ 11

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
Modification history: 1.0
Author: Mehr-e-Aman Group
Description: Part of system authentication functionality.

2.3.3 Sequence Diagram:

. To register the user and to authenticate the user
This process includes making a new account in the app then start to sign in the app.
•Actors Involved: User, Mobile Application, Authentication Server, Database.
•Steps:
1.User launches the app and clicks on the button for sign up.
2.It is worth noting that Mobile App captures the user details which include name, email and
password and forwards them to the Authentication Server.
3.After checking the details, Authentication Server saves them in the Database.
4.The server side of the executed database returns a message with either success or failure
messages.
5.Upon receiving an authentication response message, Authentication Server sends a response
message to the Mobile App that registration is either successful or unsuccessful.
6.Mobile App directs the user to a success message or the user is asked to edit his or her details.

2. Emergency Alert System

•Actors Involved: User of the application, Any smart phone with application installed in it, GPS
module of the particular mobile, User’s contact list in the phone, If any, service number of any
emergency service.
•Steps:
1.User activates the emergency button on the application interface.
2.Emergency function of Mobile App is activated and it asks the GPS Location from the GPS
Module.
3.GPS Module communicates to the Mobile App the current location, in terms of latitude and
longitude.
4.Mobile App’s Emergency Message formatting features the incident details (including location)
and transmits it to the Contacts List in form of an SMS, email or push notification.
5.In the case it applies, Mobile App notifies the Emergency Services or the police with the
notification containing location information.
6.If it is an alert, Contacts and/or Emergency Services get the message and take appropriate
action.

3. Safety Check-In
Let the user organize regularly updated safety check-ins with family or friends.
•Actors Involved: User, Mobile App, Contact list, Stopwatch.
•Steps:
1.User chooses a time interval of their activity check-ins (e.g. 30 mins).
2.Mobile App sets the time ticking for the check-in to begin.
3.Whenever the timer buzzes, the Mobile App will send the message “Are you safe?”
notification to the User.

Women Safety App ​ 12

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
4.Hence, the user responds by pressing a button either positively or negatively (for example, ‘Yes
I’m Safe”).
5.Mobile App informs the Trusted Contacts that the particular user is safe.
6.And if the User does not respond, the Mobile App sends a notification to Trusted Contacts or
Emergency services.
4. SOS Button
These are an SOS button that immediately sends alerts to close contacts or services to the user’s
current location.
•Actors Involved: The roles available for the application includes User, Mobile App, GPS
Module, Contacts List, Emergency Services.
•Steps:
1.User enters the SOS mode by pressing the SOS button on the mobile application interface.
2.Mobile App then notifies the Contacts List and the Emergency Services (with the location).
3.Mobile App cause the GPS Module to output real time location information to the GPS
Module.
4.Emergency Services and/or Contacts are the receiver of this alert along with the user’s current
location demanding an urgent response.

Sequence Diagram Example for the Emergency Alert System:

1.Mobile App → Contacts List: Need help now sent along with location.
2.Mobile App → Emergency Services: Send emergency message with your location (if it is safe
to do so).
3.Contacts List → User: Phone call, SMS, or mobile App notification received.
4.Emergency Services → User: Offer a hand (if possible).

Women Safety App ​ 13

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods

Figure 2.3 Sequence Diagram

Women Safety App ​ 14

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
2.3.4 Class Diagram:
This paper also makes use of a class diagram to illustrate the main stakeholders in the Women
Safety App and how they are interconnected to offer the App’s services. Thus, the most
important class of the design is the User class containing mandatory fields including User ID,
User’s name and surname, email, phone number, geographical location of the User. This class
includes several methods; register () which deals with the registration of the user in the app,
login () to authenticate the user within the app, and update Profile () to alter some of the details
of the user’s profile within the app.

Another associated class is the Emergency Contact, which includes the listing of contacts of the
user in case of an emergency. These are contact ID, user ID, name, phone Number, relationship –
this allows the system to allow for the registration of more than one emergency contact per user.
There are methods, including add Contact () and remove Contact () which enable the user to add
and delete their rescue contacts on the app easily.

The SOS Alert class is also part of the class diagram Inheritance dependencies above As
mentioned earlier. It has the ability to save details about alert raised by a user in emergency
situation; having fields like alert ID, time stamp, location, status etc. Functions like trigger Alert
() and send Alert () can directly call an emergency alert to configured individuals or even
emergency services, to guarantee action.

Location tracking is performed by the Location History class, wherein the user’s movement is
recorded using elements such as location ID, latitude, longitude and time stamp. For tracking the
current position of the user, the method called track Location () is used while for storing the data
of the location, the store Location () method is used.

The Safety Tip class provides safety tips to the users, its fields include tip ID, tip Title,
description and category. With this class, users are able to learn safety tips either by their location
or by their interest. A few of the feature is view Tip (), that offers users powerful and timely
security information or get Tips By Category ().

This is especially important in an object-oriented approach and as the app grows and gets revised
the logical organization created by the class diagram helps. By adopting this structure, the app is
well positioned in managing large volumes of data, provide adequate data security and last but
not least, be easy to use to satisfy its intended users.

Women Safety App ​ 15

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods

Figure 2.4 Class Diagram

2.3.5 Data Flow Diagram:

Here is the Data Flow Diagram (DFD) section for your project documentation Mehr-e-Aman,
following the proper format and structure:
Data Flow Diagram (DFD)
This section presents the DFD models that illustrate how data flows within the Mehr-e-Aman
Women Safety App. The diagrams highlight the interactions between external entities, system
processes, and data stores in a visual format that enhances understanding of the system's
functionality and structure.
Purpose of the DFD
The main objective of the Data Flow Diagram is to graphically represent the flow of data in the
Mehr-e-Aman application. It shows how information is input, processed, and output across
various modules, enabling clear communication among developers, stakeholders, and users. The
DFD starts from a general overview (Context Diagram) and breaks down into detailed levels
(Level 1 and Level 2) for clarity and in-depth analysis.

Context Diagram (Level 0)

The Context Diagram is the top-level DFD that represents the entire Mehr-e-Aman system as a
single process. It shows the interaction between external entities and the system. The external
entities for this system include:
●​ User (women using the app)
●​ Emergency Contacts

Women Safety App ​ 16

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
●​ Admin
●​ External Services (SMS, GPS)
Data Flows:
●​ User submits registration data
●​ User triggers emergency alert
●​ System sends alert with location to Emergency Contacts
●​ Admin manages user and incident data

Figure 2.5 Level 0 DFD

​ ​ ​
Level 1:

Level 1 DFD
The Level 1 diagram breaks down the main process into sub-processes and data stores. The
major processes include:
1.​ Register/Login User
2.​ Manage Profile
3.​ Trigger Emergency Alert
4.​ View Safety Tips
5.​ View Nearby Helplines
6.​ Admin Incident Management
Data Stores:
●​ User Data
●​ Alert History
●​ Safety Resources
●​ Incident Reports
Data Flows:
●​ Registration details flow from User to User Data
●​ Location and Alert Data flow from User to Alert History
●​ Admin accesses Incident Reports from storage
●​ Safety Resources are accessed by Users

Women Safety App ​ 17

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods

Figure 2.6 Level 1 DFD

Level 1 DFD
The Level 1 diagram breaks down the main process into sub-processes and data stores. The
major processes include:
1.​ Register/Login User
2.​ Manage Profile
3.​ Trigger Emergency Alert
4.​ View Safety Tips
5.​ View Nearby Helplines
6.​ Admin Incident Management
Data Stores:
●​ User Data
●​ Alert History
●​ Safety Resources
●​ Incident Reports
Data Flows:
●​ Registration details flow from User to User Data
●​ Location and Alert Data flow from User to Alert History
●​ Admin accesses Incident Reports from storage
●​ Safety Resources are accessed by Users

Women Safety App ​ 18

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
2.3.6 ER Diagram:
The Entity-Relationship (ER) Diagram illustrates the logical structure of the database for the
Mehr-e-Aman Women Safety App. It defines the entities involved in the system, their attributes,
and the relationships among them. This diagram helps database designers and developers
understand the data model, its integrity constraints, and how the entities interact.
Purpose of the ER Diagram
The ER diagram is essential for designing a normalized and efficient relational database. It
enables clarity in the design phase and serves as a blueprint for implementing the actual database
schema in the back end of the Mehr-e-Aman system.

There is also Alert in the app as an entity for storing data related to the alerts, including Alert ID,
Timestamp, Location, and Alert Type. These alerts are associated with the Location object also
tracking the user’s current coordinates, latitude, longitude and time in milliseconds. Incidents for
tracking purposes can also be reported through the Incident entity which has properties such as
the Incident, Description, the time of occurrence, Timestamp and Status; the Incident is related to
the User and can be related an optional Police Station entity. It comprises Station ID, Station
Name, Phone Number, Address, and Location; elements that may help in the management of
responses to disasters.

Notifications posted to applications are Logged in a Notifications entity, including fields such as
Notification ID, message, timestamp and Is Read Notification filed that indicates if the message
was read by the User. As it can be noted from the above standings, multiple notifications are
possible for each user. These relations make the whole data constituency cover all possible
scenarios, a user may have many contacts, alerts, locations, and incidents; an alert is associated
with a concrete location; and incidents can be linked to the relevant police station for further
actions.

Having a structured organization promotes database management and contributes much to the
potency of emergency responses and the security of users in using the app.

Women Safety App ​ 19

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods

Figure 2.7 Entity Relationship Diagram

2.3.7 Database Model:

Overview
The database model of Mehr-e-Aman is designed to store, organize, and manage all the essential
data related to user safety services. This includes user information, emergency contacts, alerts,
incident reports, safety tips, and administrative controls. The database is structured to ensure
normalization, minimize redundancy, and maintain referential integrity between tables.
Purpose
The database model provides the logical structure that underpins the system's data management.
It supports CRUD operations (Create, Read, Update, Delete), ensures data consistency, and
facilitates secure access to information for both users and administrators.
Database Type
●​ Relational Database Management System (RDBMS)
●​ Technology Used: MongoDB (NoSQL structure supported if required), or
MySQL/PostgreSQL if relational
●​ Implementation: Managed via Mongoose ORM (for MongoDB) in Node.js backend.

Women Safety App ​ 20

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
Alerts are managed through the Alert table where Alert ID, User ID, Timestamp, Latitude,
Longitude and Alert Type are stored. An alert is associated with specific user location identified
with the Location table of Location, User ID, Latitude, Longitude, and Timestamp. For the sake
of mobile application, users can also report an incident in the application as seen in the Incident
table that has attributes like, Incident ID, User ID, Description, Timestamp and Status. Every
occurrence can be linked with a police station from the Police Station table which contains
fields: Station ID, Station Name, Phone Number, Address, Latitude, Longitude.
In the Notification table, User Notifications sent to the users are recorded under Notification ID,
User ID, Message, Timestamp, and Is Read to show if they have been viewed or not.
Relationships between these tables are well-defined: Multiple contacts, alerts, locations and
incidents can be used by a user though many of the alerts can be used for one location. incidents
can be associated with one police station while users can get many notifications.
Because of this, the chosen relational database model allows for orderly storage, retrieval, and
management of data in order to sustain the app’s functionality for emergency response and
security purposes for its users.

Figure 2.8 Database Model

​

2.3.8 Architecture:
System Architecture: 3-Tier Architecture
Overview:

Women Safety App ​ 21

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
The Mehr-e-Aman – Women Safety Application is designed using a 3-tier architecture to ensure
modular development, scalable deployment, and secure separation of concerns. This architecture
splits the system into three independent layers: Presentation Tier, Application Tier, and Data Tier.
This approach was chosen for its flexibility in managing complex software systems, supporting
independent scaling, development, and maintenance of components, and ensuring a clear
separation of responsibilities. It enables parallel development and future scalability of the
application with ease.
8.1 Presentation Tier (Client Side)
The presentation layer is responsible for interacting with the end users. In the Mehr-e-Aman
application, this tier is built using modern frontend technologies that ensure responsive design,
accessibility, and dynamic interaction.
Technologies Used:
●​ React.js (Frontend Framework)
●​ Tailwind CSS (Styling)
●​ Framer Motion (Animation)
●​ Axios (HTTP Requests)
●​ React Router DOM (Routing)
●​ Heroicons / React Icons (Visual Elements)
Role:
●​ Display UI for login, registration, emergency alerts, safety tips, and profile.
●​ Receive input from the user and pass it to the backend via API calls.
●​ Show real-time feedback from the server including success/failure messages.
●​ Load maps, safety indicators, and alert status dynamically.
8.2 Application Tier (Business Logic)
The application tier is the core engine of the system where all the main functionality and logic
reside. It handles data processing, validation, request routing, and communication between the
presentation and data tiers.
Technologies Used:
●​ Node.js (Runtime Environment)
●​ Express.js (Backend Web Framework)
●​ JSON Web Token (JWT) for Authentication
●​ Mongoose (MongoDB ORM)
Role:
●​ Handles user authentication and authorization.
●​ Manages logic for emergency alerts, incident reporting, and data validation.
●​ Controls business rules such as when to trigger a safety notification or fetch stored
records.
●​ Serves as a middleware layer to ensure secure and efficient communication between
frontend and database.
8.3 Data Tier (Database Layer)
The data tier stores all persistent data and is responsible for managing information that powers
the Mehr-e-Aman application. This includes user records, emergency contacts, alerts, tips, and
incident reports.
Technologies Used:
●​ MongoDB (NoSQL Database)
●​ Cloud-based MongoDB Atlas (for deployment)

Women Safety App ​ 22

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 2- Materials & Methods
●​ Mongoose (Object Modeling)
Role:
●​ Stores user credentials, profile data, safety records, and alert logs.
●​ Ensures data integrity and allows for scalable data management.
●​ Provides robust querying capabilities to support real-time features (e.g., alert retrieval,
user location updates).
●​ Implements security features such as encrypted password storage and access control.
8.4 Architectural Benefits
●​ Modular Development: Teams can independently update frontend, backend, or database
without affecting the other tiers.
●​ Scalability: Each tier can be scaled independently depending on load requirements.
●​ Security: Sensitive business logic and data access are isolated from the client tier.
●​ Maintainability: Easier to debug, extend, or upgrade one component without refactoring
the entire application.
●​ Deployment Flexibility: Can deploy frontend and backend on separate cloud instances for
optimized performance.
8.5 Deployment Overview
●​ Frontend: Deployed using Netlify or Vercel
●​ Backend API: Hosted on Node.js server via Heroku or Render
●​ Database: MongoDB Atlas (Cloud-hosted)
Diagram (optional for document visualization):
Presentation Layer (React.js)​
↓​
Application Layer (Node.js + Express.js)​
↓​
Data Layer (MongoDB)

Figure 2.9 Application Architecture

Women Safety App ​ 23

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 3- Results & Discussion

Chapter 3 - RESULTS & DISCUSSION

This chapter presents the evaluation of the system’s performance based on the functional and
non-functional requirements defined in Chapter 1. It includes the results from software testing
activities, mainly focusing on the test cases that were designed to validate and verify the correct
behavior of the Mehr-e-Aman application.
3.1 Testing
Testing is a crucial phase in software development, aiming to ensure that the developed
application behaves according to the requirements. In Mehr-e-Aman, multiple testing strategies
were applied including unit testing, integration testing, and user acceptance testing.
The key objectives of testing were:
●​ To verify that the system meets the functional requirements (e.g., emergency alert system,
location tracking, SOS button).
●​ To validate the non-functional requirements such as usability, responsiveness,
performance, and security.
●​ To identify and resolve any bugs or inconsistencies before deployment.
Test cases were written according to the best practices, such as simplicity, coverage, clarity, and
relevance to end-user needs.
3.2 Test Cases
Below is a table showing representative test cases from the project:
Test Actual
Description Input Data Expected Result Status
Case ID Result
TC01 User Registration
Name, Email, Phone,
Password
Successful registration Passed ✅
TC02
User Login with
valid credentials
Email, Password Dashboard accessed Passed ✅
TC03
SOS Alert Button
Functionality
Tap SOS
Location and alert sent to
authorities
Passed ✅
TC04 Profile Data Fetch
User ID (via JWT
token)
Display user profile info Passed ✅
TC05
Invalid Login
Attempt
Wrong credentials Show error message Passed ✅
TC06
View Saved
Incidents
Click "Saved" tab
Display all saved
incidents
Passed ✅
TC07
Responsive Design
Check
Resize
browser/device
screen
Components adjust
layout accordingly
Passed ✅
TC08 JWT Token Expiry Use expired token
Redirect to login /
unauthorized access error
Passed ✅
TC09
Contact Form
Submission
Filled contact form
Success message
displayed
Passed ✅
Women Safety App ​ 23
University of Agriculture Faisalabad.​ ​ ​
​ Chapter 3- Results & Discussion
Test Actual
Description Input Data Expected Result Status
Case ID Result
TC10
Forgot Password
Flow
Enter email for
recovery
Recovery email sent Passed ✅
3.3 Discussion
The results of the above test cases confirm that the system is performing as intended. All core
functional features including user registration, login, SOS activation, profile viewing, and
incident management are working successfully without errors.

●​
●​
🔒
The application also satisfied all non-functional requirements:

⚡ Security: JWT authentication was implemented for secure session handling.

Performance: API response times were optimized to maintain a responsive user

●​ 📱experience.
Responsiveness: Tailwind CSS ensured a fluid and adaptive layout for mobile, tablet,

●​ 🎨and desktop views.

Usability: UI/UX principles were followed, resulting in a clean, user-friendly
interface.
No major bugs were found during testing and user acceptance feedback was positive, confirming
that the app meets both the technical and end-user expectations.

Detailed Test Cases:

Test Case ID: TC001

Test Title: Verify user registration with valid data
Test Priority: High
Requirement Reference: 1.1 - User Registration Module
Test Summary: To verify that the user is able to register successfully using valid inputs.
Test Execution Date: 2025-05-22
Pre-conditions: User is on the registration page.
Dependencies: None
Test Steps:
1.​ Open the registration form.
2.​ Enter full name, email, phone, address, and password.
3.​ Click on the "Register" button.
Test Data:
●​ Name: Ayesha Khan
●​ Email: ayesha@example.com
●​ Phone: 03001234567
●​ Address: Karachi, Pakistan
●​ Password:Mehr@123​
Expected Result: User should be registered and redirected to login page with a success
message.​
Post-condition: New user entry should be created in the database.​

Women Safety App ​ 24

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 3- Results & Discussion
Actual Result: User successfully registered and redirected to login page.​
Status: Pass
Notes: None

Test Case ID: TC002

Test Title: Verify login with valid credentials
Test Priority: High
Requirement Reference: 1.2 - Login Module
Test Summary: Ensure user can login using correct email and password.
Test Execution Date: 2025-05-22
Pre-conditions: User is registered.
Dependencies: TC001
Test Steps:
1.​ Navigate to login page.
2.​ Enter registered email and password.
3.​ Click on the "Login" button.
Test Data:
●​ Email: ayesha@example.com
●​ Password: Mehr@123
Expected Result: User should be redirected to the dashboard.​
Post-condition: User session should start and JWT token generated.
Test Case ID: TC003
Test Title: Verify SOS alert sends location and alert
Test Priority: High​
Requirement Reference: 2.1 - SOS Alert System​
Test Summary: To check whether clicking SOS button sends location to contacts.​
Test Execution Date: 2025-05-23​
Pre-conditions: User is logged in and has active location services.​
Dependencies: TC002
Test Steps:
1.​ Log into the app.
2.​ Click on "SOS" button from dashboard
3.​ Confirm permission for location.
Test Data: GPS enabled, registered contact​
Expected Result: Location and SOS alert sent to contacts with timestamp.​
Post-condition: Alert entry saved in backend and visible in incident history.​
Actual Result: Alert successfully sent with timestamp
Test Case ID: TC004​
Test Title: Verify profile data fetch using JWT​
Test Priority: Medium​
Requirement Reference: 1.4 - Profile Management​
Test Summary: To verify user data is fetched using secure JWT token.​
Test Execution Date: 2025-05-23​
Pre-conditions: User must be logged in with valid token.​
Dependencies: TC002
Women Safety App ​ 25
University of Agriculture Faisalabad.​ ​ ​
​ Chapter 3- Results & Discussion
Test Steps:
1.​ Navigate to Profile page.
2.​ JWT token should be auto included in header.
3.​ Verify the response contains user data.​
Test Data: Token from login session​
Expected Result: User profile displays correct name, email, phone, address.​
Post-condition: Data should be rendered from backend securely.
Test Case ID: TC005​
Test Title: Verify location sharing via Live Location feature​
Test Priority: Medium​
Requirement Reference: 2.2 - Live Location Module​
Test Summary: To ensure the user can share real-time location.​
Test Execution Date: 2025-05-24​
Pre-conditions: GPS enabled and user logged in.​
Dependencies: TC002
Test Steps:
1.​ Log in and go to "Quick Actions".
2.​ Tap "Share Live Location".
3.​ Allow GPS access.​
Test Data: Real-time coordinates​
Expected Result: Contact receives location URL.​
Post-condition: Live feed session created temporarily.

Test Case: User Login:

Well-designed test cases are essential for achieving comprehensive coverage. They should be
simple, reusable, and based on actual user requirements. Below is a sample test case for verifying
the login functionality of the Mehr-e-Aman application.

Table 3. 1: User login Test Case

Test Case ID: TC-1

Test Case Title: To verify the Login functionality of the application
Test Case Priority: High
Requirement: User Login
Test Description: This test will verify the user login process.

Test Date: 05/25/2025

Pre-Conditions: 1. Run the application.
2. Click Sign in button.

Dependencies: Internet Availability

Women Safety App ​ 26

University of Agriculture Faisalabad.​ ​ ​
​ Chapter 3- Results & Discussion
Test Steps: 1.Enter Valid username and password and click Login​
2. Click Sign Out
3.Without entering username click sign in​
4. Without entering password click sign in
5. Enter wrong password or username and click sign in
Test Data Email id and password of user
Expected Results: 1. System should open home page.
2. Login page should be displayed.
2. An error message should be shown to enter username
3. An error message should be shown to enter password
4. Error message should be shown to enter correct password and user id
Actual Results: As above
Post Conditions: System shows Dashboard page of signed in user. In case of unauthorized sign in
attempt system shows the message “Invalid username/password”.
Status: (Pass/Fail) Pass
Other Comments: None

3.3 Conclusion:

The Mehr-e-Aman application has been thoroughly tested across its core modules including user
registration, login, emergency alerts, location sharing, and contact management. All test cases
developed during the software lifecycle were executed with a focus on both functional and
non-functional requirements. Overall, the application achieved a 100% pass rate in critical
functional areas such as user authentication, emergency SOS triggers, and contact
communication.​
​
The interface of Mehr-e-Aman was evaluated for responsiveness, user friendliness, and
consistency. It is intuitive, features modern UI components, and supports mobile and desktop
browsers alike. Animations and transitions are used to enhance the user experience without
impacting performance. The accessibility features include large text buttons, clean layout, and
support for screen readers.​
​
From a non-functional perspective, the app met expectations in performance, scalability, and
security. Data confidentiality is maintained using secure APIs and the system is designed to be
resilient in low network conditions. Through JWT authentication and encrypted communications,
the application provides a robust foundation for handling sensitive safety data.​
​
In conclusion, Mehr-e-Aman successfully delivers a reliable, responsive, and easy-to-use
platform for women’s safety with minimal usability barriers. It fulfills its core mission while
maintaining strong security and accessibility standards.

Women Safety App ​ 27

University of Agriculture Faisalabad.​ ​ ​
​ ​ Chapter 4- User Manual

Chapter 4 - USER MANUAL

Introduction:​
This User Manual provides a brief overview of each user interface screen, explaining the purpose
and functionality of buttons, links, and input fields to help users understand how to interact with
the Mehr-e-Aman Women Safety App effectively.
1.​ Home Page
Screenshot: (Insert image of Home Page UI here)
Description:
●​ Logo: Displays Mehr-e-Aman brand identity.
●​ Navigation Bar: Contains links to Home, Features, Help, Profile, etc.
●​ Emergency Button (Red Circle): Triggers immediate alert to emergency contacts.
●​ Quick Access Tiles:
o​ Fake Call: Simulates a phone call to provide an excuse or distraction.
o​ Live Location: Starts real-time GPS sharing.
o​ Safe Ride: Redirects to safe ride booking options.
o​ Tips: Opens self-defense guides.
2.​ Registration Page
Screenshot: (Insert image of Registration Page here)
Description:
●​ Full Name Field: Input for user’s real name.
●​ Email Field: Required for account creation and alerts.
●​ Phone Field: Used for identity and alert triggers.
●​ Password Field: Creates login password.
●​ Register Button: Validates and submits data.
●​ Link to Login: Redirects to login page for existing users.
3.​ Login Page
Screenshot: (Insert image of Login Page here)
Description:
●​ Email Input: Accepts registered email.
●​ Password Input: For secure login.
●​ Forgot Password Link: Navigates to recovery page.
●​ Login Button: Authenticates user credentials.
●​ Sign Up Link: Goes to Registration page.
4.​ Emergency Alert
Screenshot: (Insert image of Alert UI here)
Description:
●​ Red Alert Button: Instantly sends SMS/location to emergency contacts.
●​ Status Message: Shows confirmation of alert delivery.
●​ Map: Displays user’s current location.
5.​ Fake Call Interface
Screenshot: (Insert image of Fake Call UI here)

Women Safety App ​ 26

University of Agriculture Faisalabad.​ ​ ​
​ ​ Chapter 4- User Manual
Description:
●​ Call Timer: Countdown before the call rings.
●​ Cancel Button: Stops the fake call trigger.
●​ Set Voice: Optionally select male/female voice or ringtone.
6.​ Live Location Tracking
Screenshot: (Insert image of Live Location screen here)
Description:
●​ Share Location Button: Starts live location broadcast.
●​ Stop Button: Ends location sharing.
●​ Map Interface: Shows user’s movement and address.
7.​ Safe Zone
Screenshot: (Insert image of Safe Zone UI here)
Description:
●​ Add Safe Zone: Users can mark areas considered safe (e.g., home, workplace).
●​ Radius Selector: Adjusts safe zone area.
●​ Notification Toggle: Enables entry/exit notifications.
8.​ Profile Management
Screenshot: (Insert image of Profile Page here)
Description:
●​ Profile Picture: Shows placeholder image (e.g., scenic banner).
●​ Fields: Name, Email, Phone, Address – view or edit user data.
●​ Save Changes Button: Updates profile in the database.
9.​ Safety Tips
Screenshot: (Insert image of Safety Tips screen here)
Description:
●​ Card List: Presents actionable advice on handling emergencies.
●​ Icons: Illustrates each tip visually.
●​ Scroll: Vertical scroll to view multiple tips.
10.​Help / Support Page
Screenshot: (Insert image of Help page here)
Description:
●​ FAQs: Covers most common queries.
●​ Contact Form: Submit issues or feedback.
●​ Email Display: support@mehreaman.pk
11.​Footer Section
Screenshot: (Insert image of Footer here)
Description:
●​ Quick Links: Navigation shortcuts.
●​ Social Icons: Facebook, Twitter, Instagram – opens Mehr-e-Aman pages.
●​ Copyright: Legal disclaimer.

Women Safety App ​ 27

University of Agriculture Faisalabad.​ ​ ​
​ ​ Chapter 4- User Manual

Figure 3.1 Signing in

Women Safety App ​ 28

Women Safety App ​ 27
 References

1.​ Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach. 8th ed.,

McGraw-Hill Education.
2.​ Sommerville, I. (2016). Software Engineering. 10th ed., Pearson Education.
3.​ Microsoft. (2024). Introduction to 3-tier architecture. Retrieved from
https://learn.microsoft.com/4
4.​ Mozilla Developer Network (MDN). (2024). JavaScript Documentation. Retrieved
from https://developer.mozilla.org/
5.​ Bootstrap. (2023). The most popular HTML, CSS, and JS library in the world

Women Safety App ​ 28