Software Requirements Specification for <Emergency Assistance App>

Page i

Software Requirements
Specification
for

<Emergency Assistance App>

Version 1.0 approved

Prepared by <Sidra Batool-06

Daniya Riaz-24>

<University Of Kotli AJ&K>

<March 21, 2024 >

Software Requirements Specification for < Emergency Assistance App >
Page ii

Table of Contents

Revision History ____________________________________________________________________________________________________ 3

1. Introduction ______________________________________________________________________________________________________ 1
1.1 Purpose_______________________________________________________________________________________________________ 1
1.2 Document Conventions __________________________________________________________________________________________ 1
1.3 Intended Audience and Reading Suggestions __________________________________________________________________________ 1
1.4 Product Scope __________________________________________________________________________________________________ 2
1.5 References ____________________________________________________________________________________________________ 2
2. Overall Description _________________________________________________________________________________________________ 2
2.1 Product Perspective ______________________________________________________________________________________________ 2
2.2 Product Functions _______________________________________________________________________________________________ 3
2.3 Operating Environment __________________________________________________________________________________________ 3
2.3.1 Hardware Requirements: _____________________________________________________________________________________ 3
2.3.2 Software Requirements: ______________________________________________________________________________________ 3
2.4 Design and Implementation Constraints ______________________________________________________________________________ 4
2.5 User Documentation_____________________________________________________________________________________________ 4
2.6 Assumptions and Dependencies ____________________________________________________________________________________ 4
2.6.1 Assumptions: ______________________________________________________________________________________________ 4
2.6.2 Dependencies: _____________________________________________________________________________________________ 5
3. External Interface Requirements _____________________________________________________________________________________ 5
3.1 User Interfaces: _________________________________________________________________________________________________ 5
3.2 Hardware Interfaces: _____________________________________________________________________________________________ 5
3.3 Software Interfaces: _____________________________________________________________________________________________ 6
3.4 Communications Interfaces _______________________________________________________________________________________ 6
4. System Features ___________________________________________________________________________________________________ 6
4.1 Feature 1: Emergency Call Button _________________________________________________________________________________ 6
4.1.1 Purpose: __________________________________________________________________________________________________ 6
4.1.2 Implementation: ____________________________________________________________________________________________ 6
4.2 Feature 2: Location Tracking ______________________________________________________________________________________ 6
4.2.1 Purpose: __________________________________________________________________________________________________ 6
4.2.2 Implementation: ____________________________________________________________________________________________ 7
4.3 Panic Button ___________________________________________________________________________________________________ 7
4.3.1 Purpose: __________________________________________________________________________________________________ 7
4.3.2 Implementation: ____________________________________________________________________________________________ 7
4.4 Customizable Settings ___________________________________________________________________________________________ 7
4.4.1 Purpose: __________________________________________________________________________________________________ 7
4.4.2 Implementation: ____________________________________________________________________________________________ 7
4.5 Accessibility Features ___________________________________________________________________________________________ 7
4.5.1 Purpose: __________________________________________________________________________________________________ 7
4.5.2 Implementation: ____________________________________________________________________________________________ 7
5. Other Nonfunctional Requirements ____________________________________________________________________________________ 8
5.1 Performance Requirements _______________________________________________________________________________________ 8
5.1.1 Response Time: ____________________________________________________________________________________________ 8
5.1.2 Availability: _______________________________________________________________________________________________ 8
5.2 Security ______________________________________________________________________________________________________ 8
5.2.1 Data Security:______________________________________________________________________________________________ 8
5.2.2 Authentication: _____________________________________________________________________________________________ 8
5.3 Usability ______________________________________________________________________________________________________ 8
5.3.1 User Interface: _____________________________________________________________________________________________ 8
5.3.2 Accessibility: ______________________________________________________________________________________________ 8
5.4 Software Quality Attributes _______________________________________________________________________________________ 9
5.5 Feasibility study ________________________________________________________________________________________________ 9
6. Other Requirement _________________________________________________________________________________________________ 9
6.1 Public Awareness Campaign: ______________________________________________________________________________________ 9
Appendix A: Glossary _________________________________________________________________________________________________ 9
Appendix B: Analysis Models ___________________________________________________________________________________________ 9
Revision History
Name Date Reason For Changes Version

21/03/2023 1.0
Software Requirements Specification for < Emergency Assistance App >
Page 1

1. Introduction
1.1 Purpose
The purpose of the Software Requirements Specification (SRS) for the Emergency Assistance App is
to outline the functional and non-functional requirements necessary for the development of a
comprehensive mobile application designed to provide immediate support and resources during
emergency situations. This document serves as a guide for the development team, stakeholders, and
other parties involved in the design, implementation, and testing of the app. By clearly defining the
scope, features, constraints, and dependencies of the Emergency Assistance App, the SRS ensures a
common understanding among all stakeholders and facilitates the development process by providing
a roadmap for the creation of a reliable, user-friendly, and effective emergency response tool.

1.2 Document Conventions

The document follows a structured approach in presenting the software requirements, with each
section and functional requirement being clearly numbered for easy reference. Functional
requirements are highlighted in bold text to distinguish them from other content. Technical terms and
acronyms are italicized upon first use to ensure clarity and understanding. References to external
sources or related documents, if necessary, are cited using standard citation formats. Additionally,
any supplementary notes or comments are provided either within the text in italics or as separate
sections, clearly marked for differentiation. This consistent formatting and organization aid in
enhancing the readability and comprehension of the software requirements specification (SRS)
document.

1.3 Intended Audience and Reading Suggestions

The Software Requirements Specification (SRS) for an "Emergency Assistance App" targets a diverse
audience including project managers, software developers, quality assurance testers, designers,
system administrators, emergency response professionals, and end users. It should be written in clear
language, detailing functional and non-functional requirements.
Software Requirements Specification for < Emergency Assistance App >
Page 2

1.4 Product Scope

The Software Requirements Specification (SRS) for the Emergency Assistance App encompasses the
development of a comprehensive mobile application focused on ensuring user safety and providing
timely emergency response services. The app will include features tailored to woman safety, such as
panic buttons for immediate alerting, discreet distress signals, and evidence collection functionalities.
Additionally, it will facilitate ambulance services by enabling users to request medical assistance with
detailed emergency information for swift dispatch. Integrated fire detection technology will detect
fire outbreaks and notify both users and emergency services promptly. Location tracking capabilities
utilizing GPS will ensure precise identification of user coordinates during emergencies, enhancing
response efficiency. The app will prioritize user privacy and data security.

1.5 References

• https://firebase.google.com/docs/auth/android/phone-auth?authuser=0
• https://stackoverflow.com/questions/19805880/get-signal-strength-in-android
• https://ieeexplore.ieee.org/document/8723988
• https://jestec.taylors.edu.my/Speccial%20Issue%20ICITE2021/Special%20issue%20ICITE21_04.pdf

2. Overall Description
2.1 Product Perspective

The Emergency Assistance App aims to provide users with a comprehensive and efficient platform
for accessing emergency services swiftly and seamlessly during critical situations. With a userfriendly
interface, the app will allow individuals to quickly alert emergency contacts, including family
members and relevant authorities, with precise location information. The app will prioritize
accessibility, reliability, and user privacy to ensure that individuals feel confident and supported in
times of distress, ultimately contributing to safer and more connected communities.
Software Requirements Specification for < Emergency Assistance App >
Page 3

2.2 Product Functions

The Emergency Assistance app is designed to provide users with immediate access to vital emergency
services and support in times of crisis. Its primary function includes enabling users to quickly alert
emergency services such as police, fire, or medical assistance with the tap of a button. The app utilizes
GPS technology to pinpoint the user's location and share it with emergency responders, ensuring a
swift and accurate response. Additionally, it offers features such as storing emergency contacts, and
personal details that can aid first responders in providing appropriate care. The app also includes a
panic button for situations where discreet assistance is needed, sending alerts to trusted contacts or
local authorities discreetly. Overall, the Emergency Assistance app aims to enhance user safety and
peace of mind during emergencies by facilitating efficient communication and coordination with
emergency services.

2.3 Operating Environment

The operating environment for an Emergency Assistance app as outlined in a Software Requirements
Specification (SRS) involves specific hardware and software requirements to ensure its functionality
and performance. Here are the key components of the operating environment:

2.3.1 Hardware Requirements:

• Smartphones and Tablets.
• GPS Capability
• Sufficient Storage

2.3.2 Software Requirements:

• Operating System Compatibility: Android
• Location Services: Access to location services APIs for GPS functionality, enabling the app to
retrieve and share the user's precise location.
• Push Notification Services: Integration with push notification services (e.g., Firebase Cloud
Messaging for Android) to send real-time alerts and updates to users.
Software Requirements Specification for < Emergency Assistance App >
Page 4

• Telecommunications APIs: Integration with telecommunications APIs for making emergency

calls (e.g., dialing 911 or local emergency numbers), sending SMS messages, and establishing
data connections when required.
• Backend Infrastructure: A secure backend system hosted on reliable servers with databases for
storing user data securely. This includes sensitive information like emergency contacts, and user
preferences.

2.4 Design and Implementation Constraints

Design and implementation constraints for the emergency assistance app include technical limitations,
resource constraints (such as budget and time), legal and regulatory requirements and security
considerations.

2.5 User Documentation

The user documentation for the Emergency Assistance app in the Software Requirements
Specification (SRS) encompasses comprehensive guides and resources to help users understand and
utilize the app's features effectively. This documentation includes step-by-step instructions on how to
download and install the app on their mobile devices, create and manage their user profiles, set up
emergency contacts and use the emergency assistance features such as making emergency calls,
sending alerts, and sharing their location with first responders. It also provides troubleshooting tips
and contact information for customer support, ensuring users can access assistance and guidance
whenever needed while using the app in emergency situations.

2.6 Assumptions and Dependencies

2.6.1 Assumptions:
• Users will possess smartphones or tablets with compatible operating systems (e.g., iOS, Android)
and GPS capabilities to enable accurate location tracking.
Software Requirements Specification for < Emergency Assistance App >
Page 5

• Users will provide accurate and up-to-date personal information, emergency contacts, and medical
details within the app to facilitate effective emergency response.
• The app will be used in environments where emergency services (e.g., police, fire department,
medical responders) are accessible and responsive to emergency alerts and calls.

2.6.2 Dependencies:
• Third-party APIs: The app may rely on third-party APIs such as Twilio for emergency call
functionalities, Firebase for push notifications, and Google Maps API for location services.
• Backend infrastructure: The app depends on a secure backend infrastructure (servers, databases)
for storing user data securely, managing authentication, and facilitating communication between
the app and emergency services.
• Availability of emergency services: The app's effectiveness relies on the availability and
responsiveness of local emergency services, including police, fire department, and medical
responders, to handle emergency alerts and calls initiated through the app.

3. External Interface Requirements

3.1 User Interfaces:

• The user interface should be user-friendly, with intuitive navigation and clear instructions for
accessing emergency features.
• Include a prominent emergency button on the main screen for quick access to emergency services.
• Display the user's location on a map interface and provide directions to nearby emergency services
or safe locations.

3.2 Hardware Interfaces:

• The app should utilize the device's GPS functionality to accurately track the user's location during
emergencies.
• Ensure compatibility with a wide range of mobile devices, including smartphones and tablets
running popular operating system (Android).
Software Requirements Specification for < Emergency Assistance App >
Page 6

3.3 Software Interfaces:

• APIs for seamless integration with emergency services such as ambulance dispatch systems and
police departments.
• Database connectivity for storing and retrieving user information securely.
• Encryption protocols for protecting sensitive data during transmission

3.4 Communications Interfaces

• Enable voice calls to emergency services directly from within the app, utilizing the device's
telephony capabilities.
• Utilize push notifications to deliver alerts and updates to users during emergency situations.
• Offer the option for users to send emergency SMS messages to designated contacts or emergency
services if internet connectivity is limited.

4. System Features
4.1 Feature 1: Emergency Call Button
4.1.1 Purpose:
Imagine you're in a scary situation and need help fast. The emergency call button is like having a
direct line to emergency services at your fingertips.

4.1.2 Implementation:
We'll make sure the button is big and obvious on the screen. When you tap it, it immediately dials the
emergency number for your area, whether it's 911 or another local number.

4.2 Feature 2: Location Tracking

4.2.1 Purpose:
If you're lost or in trouble and can't explain where you are, the app can do it for you. It's like having
a map that updates in real-time to show exactly where you are.
Software Requirements Specification for < Emergency Assistance App >
Page 7

4.2.2 Implementation:
We'll use GPS technology in your phone to track your movements. This way, when you need help,
responders can find you quickly and accurately.

4.3 Panic Button

4.3.1 Purpose:
Sometimes, you just need to let everyone know you're in trouble ASAP. The panic button is like
sounding an alarm that brings help running.

4.3.2 Implementation:
We'll add a big red button to the app. pressing it sends an alert to emergency services and your
contacts, letting them know you're in an urgent situation.

4.4 Customizable Settings

4.4.1 Purpose:
Everyone's needs are different. With customizable settings, you can tailor the app to work just the
way you want it to.

4.4.2 Implementation:
You can adjust settings like emergency contacts and privacy controls to suit your preferences and
situation.

4.5 Accessibility Features

4.5.1 Purpose:
The app is designed to be inclusive and easy to use for everyone, including those with disabilities or
special needs.

4.5.2 Implementation:
We've included features like text-to-speech, voice commands, high-contrast interfaces, and adjustable
font sizes to make sure everyone can use the app effectively during emergencies.
Software Requirements Specification for < Emergency Assistance App >
Page 8

5. Other Nonfunctional Requirements

5.1 Performance Requirements
Here are some other non-functional requirements for an Emergency Assistance App:
5.1.1 Response Time:
The app should be responsive and function smoothly even under heavy load or in situations with weak
network connectivity. There should be clear timeframes defined for critical actions like sending alerts
or connecting to emergency services.
5.1.2 Availability:
The app should be highly available, meaning users can access it and use its features whenever they
need it during an emergency. This might involve setting a target uptime percentage.

5.2 Security
5.2.1 Data Security:
The app should implement strong security measures to protect user data, including personal
information, location data, and any communication history within the app. This might involve
encryption of data both at rest and in transit.
5.2.2 Authentication:
The app should have a secure authentication mechanism to prevent unauthorized access. This could
involve multi-factor authentication for critical actions.

5.3 Usability
5.3.1 User Interface:
The app's interface should be intuitive and user-friendly, especially during stressful emergency
situations. This means clear icons, easy navigation, and minimal steps to activate emergency
features.
5.3.2 Accessibility:
The app should be accessible to users with disabilities, following accessibility guidelines for font size,
color contrast, and screen reader compatibility.
Software Requirements Specification for < Emergency Assistance App >
Page 9

5.4 Software Quality Attributes

• Reliability: High availability to minimize downtime during emergencies.

• Security: Strong data confidentiality, integrity, and authentication to protect user privacy.
• Usability: Easy to use interface with clear navigation for quick action in critical situations.
• Performance: Responsive operation even under heavy load or weak network conditions.

5.5 Feasibility study

The feasibility study for an "Emergency Assistance App" looks at whether the app can work on
different devices and networks (technical feasibility), if it's worth the money to develop and maintain
(economic feasibility), if it follows the law and protects data (legal feasibility), if it's easy to use and
can grow if needed (operational feasibility), and if it can be finished on time (scheduling feasibility).
This helps decide if the app is a good idea and can be made successfully to meet user needs and
market demands.

6. Other Requirement
6.1 Public Awareness Campaign:

 Develop a program to educate the community about the app's features and benefits.

Appendix A: Glossary

SRS Software Requirements Specification

GPS Global Positioning System

Appendix B: Analysis Models

None at this time.