EMERGENCY APP ANALYSIS DOC

CHAPTER 5

ANALYSIS DOCUMENT

5.1 Software Requirement Specification (SRS)

Software Requirement Specification (SRS) on Emergency App provide detail view of

android based application. This project eases the process of contacting neary emergency
centres to through a simple and easy to use User Interface.

5.1.1 Introduction
5.1.1.1 Purpose
The Emergency App helps the user identify nearby emergency centres given their current
location. It is an android based application implemented to eliminate the process of searching
for nearby emergency centres on the phone or calling generic centre numbers. The
application was designed with the perspective of reducing the stress related with handling
emergency situations.

5.1.1.2 Scope
The system allows the users to search for nearby emergency centres usually within a range of
2-8kms from the user. The user can contact these emergency centres through the call feature
or they can find the shortest route to these emergency centres using the Map button.
The application also provides a “Panic Mode” which is activated when the users cell signal is
less than 30%. The purpose of this mode is to contact the users safe contacts and let them
know of the last known location of the user.

5.1.1.3 Definitions, acronyms & abbreviations

GUI: Graphical User Interface
Firebase: an API that synchronizes application data across iOS, Android, and Web devices,
and stores it on Firebase's cloud. The product assists software developers in building real-
time, collaborative applications.
Firestore: Cloud Firestore is a NoSQL document database that lets you easily store, sync,
and query data for your mobile and web apps - at global scale.

MVJPT 5
EMERGENCY APP ANALYSIS DOC

Places SDK: The Places SDK for Android allows you to build location-aware apps that
respond contextually to the local businesses and other places near the device.

5.1.1.4 References
https://firebase.google.com/docs/auth/android/phone-auth?authuser=0
https://developer.android.com/guide/topics/ui/layout/recyclerview
https://developers.google.com/places/web-service/intro
https://stackoverflow.com/questions/19805880/get-signal-strength-in-android
https://developer.android.com/reference/android/app/ListActivity.html

5.1.1.5 Overview
The Emergency App helps the user identify nearby emergency centres given their current
location, find all centres within a certain radius, contact centres, find map routes to
emergency centres, panic mode that is auto activated when cell signal is low.

5.1.2 Overall description

The Emergency App system allows the users to search for nearby emergency centres usually
within a range of 2-8kms from the user. The user can contact these emergency centres
through the call feature or they can find the shortest route to these emergency centres using
the Map button.
The application also provides a “Panic Mode” which is activated when the users cell signal is
less than 30%. The purpose of this mode is to contact the users safe contacts and let them
know of the last known location of the user.

5.1.2.1 Product perspective

The application is provided with user friendly interface and works efficiently. It provides
simple database rather than complex ones for high requirements and it provides good and
easy graphical user interface as well as experienced users.

5.1.2.1.1 System interfaces

The Emergency Application system has one actor which is the user.

MVJPT 6
EMERGENCY APP ANALYSIS DOC

5.1.2.1.2 User interfaces:-

1. User interface for login.
2. User interface for user to verify their safety contacts
3. User interface for user to register.
4. User interface for a quick view of the emergency centres.
5. User interface to adjust application settings.
6. User interface for searching all emergency centres based on distance.
7. User interface for Panic mode
8. User interface user management

5.1.2.1.3 Hardware interfaces

The System must run over the internet, all the hardware shall require to connect internet will
be hardware interface for the system.

5.1.2.1.4 Software interfaces

The database being used is Firebase Firestore to store all the registered users and their
verified safety phone numbers. The user location tracking is achieved through the usage of
the phones GPS system, which aids in the process of locating nearby Emergency centres
using the Google Places API.

5.1.2.1.5 Communications interfaces

The system requires SMS and a stable Internet connection on the mobile phone.

5.1.2.1.6 Memory constraints

It requires 20.7MB of memory for storage and 1GB of RAM to run the application

5.1.2.2 User characteristics

Customer need to have minimum mobile knowledge to operate application and to setup their
safety contacts.

5.1.3 Specific Requirements

5.1.3.1 External interface requirements

MVJPT 7
EMERGENCY APP ANALYSIS DOC

5.1.3.1.1 User interfaces

1. User interface for login.
2. User interface for user to verify their safety contacts
3. User interface for user to register.
4. User interface for a quick view of the emergency centres.
5. User interface to adjust application settings.
6. User interface for searching all emergency centres based on distance.
7. User interface for Panic mode
8. User interface user management

5.1.3.1.2 Communication interfaces

CI-1: The security of a user must be consistent through the use of passwords.
CI-2: The application will get current user location through GPS.
CI-3: The Panic mode messages are sent through SMS

5.1.3.2 Performance requirements

The system requires a minimal system capable of sending SMS and getting current user
location.

5.1.3.3 Software system attributes

5.1.3.3.1 Reliability
The system provides storage of all user information on Firestore which allows for updation of
the user data on setup on new devices.

5.1.3.3.2 Availability
The system is available at all times, meaning the user can access it using a mobile, only
restricted by the down time of the server on which the application runs. It means 24 X 7
availability.

5.1.3.3.3 Security
● Firebase is used instead of message to confirm the registration of users
● HTTPS is used for secure communication between app and the server

MVJPT 8
EMERGENCY APP ANALYSIS DOC

● To avoid fake emergency centres, the Google Places API is used to find all verified
centres.

5.1.3.3.4 Maintainability
A commercial database is used for maintaining the database and the application API takes
care of the site.

5.1.3.3.5. Portability:-
The application provides support to run all Android devices.

5.2 UML DIAGRAM

5.2.1 DATA FLOW DIAGRAM

Level 0

Fig 5.2.1.1

Level 1

Fig 5.2.1.2

Fig 5.2.1.3
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. A DFD is often used as a preliminary
step to create an overview of the system without going into great detail, which can later be
elaborated. DFDs can also be used for the visualization of data processing (structured
design).

A DFD shows what kind of information will be input to and output from the system, how the
data will advance through the system, and where the data will be stored. It does not show

MVJPT 9
EMERGENCY APP ANALYSIS DOC

information about process timing or whether processes will operate in sequence or in parallel,
unlike a traditional structured flowchart which focuses on control flow, or a UML activity
workflow diagram, which presents both control and data, flows as a unified model

FLOW CHART

Fig 5.2.1.4
A flowchart is a type of diagram that represents an algorithm, workflow or process, showing
the steps as boxes of various kinds, and their order by connecting them with arrows.
Flowcharts are used in analyzing, designing, documenting or managing a process or program
in various fields. Flowcharts are used in designing and documenting simple processes or
programs. Like other types of diagrams, they help visualize what is going on and thereby help
understand a process, and perhaps also find flaws, bottlenecks, and other less-obvious
features within it.

ENTITY RELATIONSHIP DIAGRAM

Fig 5.2.1.5
An Entity–Relationship Model (ER model for short) describes interrelated things of interest
in a specific domain of knowledge. A basic ER model is composed of entity types (which
classify the things of interest) and specifies relationships that can exist between instances of
those entity types. In software engineering, an ER model is commonly formed to represent

MVJPT 10
EMERGENCY APP ANALYSIS DOC

things that a business needs to remember in order to perform business processes.

Consequently, the ER model becomes an abstract data model, that defines a data or
information structure which can be implemented in a database, typically a relational database.

Entity–relationship modeling was developed for database design by Peter Chen and published
in a 1976 paper.

CLASS DIAGRAM

Fig 5.2.5
Class diagram in the Unified Modeling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.

The class diagram is the main building block of object-oriented modelling. It is used for
general conceptual modelling of the systematic of the application, and for detailed modelling
translating the models into programming code. Class diagrams can also be used for data
modeling.[1]The classes in a class diagram represent both the main elements, interactions in
the application, and the classes to be programmed.

USECASE DIAGRAM

Fig 5.2.6
A use case diagram at its simplest is a representation of a user's interaction with the system
that shows the relationship between the user and the different use cases in which the user is
involved. A use case diagram can identify the different types of users of a system and the
different use cases and will often be accompanied by other types of diagrams as well.

MVJPT 11