Software Requirements

Specification
for

Toxic Gas Analyzer-TOGA

Version 1.0 approved

Prepared by Vaghela Yash, Mavani Hrishita, Rao Vishwa

LDCE-IT

21 March,2020

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
 Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Change History.............................................................................................................................. ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 2
1.3 Intended Audience and Reading Suggestions .................................................................................. 2
1.4 Product Scope .................................................................................................................................. 2
1.5 References ........................................................................................................................................ 2
1.6 Technology used ............................................................................................................................ 2
2. Overall Description ..................................................................................................................5
2.1 Product Perspective.......................................................................................................................... 5
2.2 Product Functions ............................................................................................................................ 6
2.3 User Classes and Characteristics ..................................................................................................... 6
2.4 Operating Environment .................................................................................................................... 6
2.5 Design and Implementation Constraints .......................................................................................... 6
2.6 User Documentation ........................................................................................................................ 6
2.7 Assumptions and Dependencies ...................................................................................................... 7
3. External Interface Requirements ...........................................................................................8
3.1 User Interfaces ................................................................................................................................. 8
3.2 Hardware Interfaces ......................................................................................................................... 9
3.3 Software Interfaces .......................................................................................................................... 9
3.4 Communications Interfaces ............................................................................................................. 9
4. System Features .....................................................................................................................10
4.1 System Feature 1 ............................................................................................................................ 10
4.2 System Feature 2 ........................................................................................................................... 10
4.3 System Feature 3 …………………………………………………………………………………11
5. Other Nonfunctional Requirements .....................................................................................13
5.1 Performance Requirements ............................................................................................................ 13
5.2 Safety Requirements ...................................................................................................................... 13
5.3 Security Requirements ................................................................................................................... 13
5.4 Software Quality Attributes ........................................................................................................... 14
5.5 Business Rules ............................................................................................................................... 14
6. Other Requirements ............................................................................................................115
Appendix A: Glossary................................................................................................................115
Appendix B: Analysis Models .....................................................................................................16
Appendix C: To Be Determined List ..........................................................................................22

Change History
Date Version File Name Document Format Status
27-Feb-2020 1.0 TOGA_.v1.0.doc Microsoft Word created
5-Mar-2020 1.1 TOGA_Requirements Microsoft Word created
Software Requirements Specification for TOGA Page 1

1. Introduction
1.1 Purpose

Workers in many modern industries (chemical, manufacturing factories etc.) face dangerous
problems including respiratory diseases such as aggravate asthma, inflammation and damaged lung
tissue. High levels of unregulated hazardous gases in such small and medium scale factories can
even lead to death of workers. The aim of this project is to detect the presence and levels of such
gases, so proper precautions can be taken. The main objective of the project is to solve this serious
problem of detecting harmful gases by developing a portable Safety device using Arduino
microcontroller along with gas detection sensors to make sure gas ppms(parts per million) are
within permissible levels to maintain health of factory workers and notify workers on increased gas
levels.

1.2 Document Conventions

• Abbreviation

Sr. No. Abbreviations Description

1 ANDROID Android Studio(2.2.3)
3 PHP Hypertext Pre-processing
4 SDK Software Development Kit
5 API Application Programming Interface
6 GUI Graphical User Interface
7 DB Database
8 MYSQL MY Structured Query Language
9 JDK Java development Kit
10 IOT Internet of Things
11 VCC Power +5V
12 GND Ground
14 IEEE Institute of electrical and electronics engineers
15 SRS Software requirement specifications
16 Open Software for which the code is freely available for use and
Source research
17 GPS Global positioning system
Software Requirements Specification for TOGA Page 2

1.3 Intended Audience and Reading Suggestions

The different types of reader that this document is intended for are developers having knowledge
about android and IOT development, Industry expert having knowledge about various gases and
their safe levels, project managers, marketing staff, users, testers, and documentation writers.
The rest of this SRS contains Overall Description, External Interface Requirements, System
Features, Non Functional Requirements and Other Requirements. Suggested sequence for
reading the document - begin with the overview sections and proceed through the sections that
are most pertinent to each reader type.

1.4 Product Scope

Workers in many modern industries (chemical, manufacturing factories etc) face dangerous
problems including respiratory diseases such as aggravate asthma, inflammation and damaged
lung tissue. High levels of unregulated hazardous gases in such small and medium scale
factories can even lead to death of workers. The Project, titled “TOXIC GAS ANALYZER
(TOGA)” comprise of using Arduino Uno microcontroller, along with different gas sensors of
MQ series, Bluetooth module (HC05), Arduino IDE.The project focuses on detection of
presence of such gases and levels of such gases, so proper precautions can be taken.

1.5 References
• IEEE Guide for Software Requirements Specifications," in IEEE Std 830-1984 .URL:
https://www.ieee.org/standards/index.html

• ProcessModel:https://www.researchgate.net/publication/299331511_Software_Process_
Models_for_Mobile_Application_Development_A_Review

1.6 TECHNOLOGIES TO BE USED

1.6.1 Arduino

Arduino is an open-source electronics platform based on easy-to-use hardware and

software. Arduino boards are able to read inputs - light on a sensor, a finger on a button, or a
Twitter message - and turn it into an output - activating a motor, turning on an LED,
publishing something online. You can tell your board what to do by sending a set of
instructions to the microcontroller on the board. To do so you use the Arduino programming
language (based on Wiring), and the Arduino Software (IDE), based on Processing.

There are many other microcontrollers and microcontroller platforms available for physical
computing. Parallax Basic Stamp, Netmedia's BX-24, Phidgets, MIT's Handyboard, and
Software Requirements Specification for TOGA Page 3

many others offer similar functionality. All of these tools take the messy details of
microcontroller programming and wrap it up in an easy-to-use package. Arduino also
simplifies the process of working with microcontrollers, but it offers some advantage for
teachers, students, and interested amateurs over other systems:

• Inexpensive - Arduino boards are relatively inexpensive compared to other microcontroller

platforms. The least expensive version of the Arduino module can be assembled by hand,
and even the pre-assembled Arduino modules cost less than $50
• Cross-platform - The Arduino Software (IDE) runs on Windows, Macintosh OSX, and
Linux operating systems. Most microcontroller systems are limited to Windows.
• Simple, clear programming environment - The Arduino Software (IDE) is easy-to-use for
beginners, yet flexible enough for advanced users to take advantage of as well. For teachers,
it's conveniently based on the Processing programming environment, so students learning to
program in that environment will be familiar with how the Arduino IDE works.
• Open source and extensible software - The Arduino software is published as open source
tools, available for extension by experienced programmers. The language can be expanded
through C++ libraries, and people wanting to understand the technical details can make the
leap from Arduino to the AVR C programming language on which it's based. Similarly, you
can add AVR-C code directly into your Arduino programs if you want to.
• Open source and extensible hardware - The plans of the Arduino boards are published under
a Creative Commons license, so experienced circuit designers can make their own version of
the module, extending it and improving it. Even relatively inexperienced users can build
the breadboard version of the module in order to understand how it works and save money.

1.6.2 Android

Android is an open source and Linux-based Operating System for mobile devices such as
smart phones and tablet computers. Android was developed by the Open Handset
Alliance, led by Google, and other companies. Android offers a unified approach to
application development for mobile devices which means developers need only develop
for Android, and their applications should be able to run on different devices powered by
Android.
The first beta version of the Android Software Development Kit (SDK) was released by
Google in 2007 where as the first commercial version, Android 1.0, was released in
September 2008.

Features:

• Beautiful UIAndroid OS basic screen provides a beautiful and intuitive user interface.
• Connectivity GSM/EDGE, IDEN, CDMA, EV-DO, UMTS, Bluetooth, Wi-Fi, LTE,
NFC.
Software Requirements Specification for TOGA Page 4

• Storage SQLite, a lightweight relational database, is used for data storage purposes.
• Media supportH.263, H.264, MPEG-4 SP, AMR, AMR-WB, AAC, HE- AAC, AAC
5.1, MP3, MIDI, OggVorbis, WAV, JPEG,PNG, GIF, and BMP.
• Messaging SMS and MMS
o Web browser based on the open-source Web Kit layout engine, coupled with
Chrome's V8 JavaScript engine supporting HTML5 and CSS3.
• Multi-touch Android has native support for multi-touch which was initially made
available in handsets such as the HTC Hero.
• Multi-tasking User can jump from one task to another and same time various
Applications can run. Simultaneously.
Software Requirements Specification for TOGA Page 5

2. Overall Description

2.1 Product Perspective

The Product “Toxic gas analyzer” will be useful in industries where harmful toxic gases are used.
The currently employed fire detection system have various loopholes also the timely data about
gases present in atmosphere is not kept. Proposed system will be helpful for the workers who are in
constant exposure of such gases. Increased level of such gases may lead to various serious diseases
and causes death in extreme cases.

Arduino
Module

[SYSTEM BLOCK DIAGRAM]

Software Requirements Specification for TOGA Page 6

2.2 Product Functions

The main function of the product is to detect harmful gases and send readings to mobile application.
thus, user can monitor current gas levels and can also maintain logs. Also, user can ask for
emergency help through triple click of power button in case of emergency. They can view
temperature details as well.

2.3 User Classes and Characteristics

Workers:
The product mainly focuses on anticipation of industry workers. They must have basic knowledge
about using smartphone.

Factory Manager:
Monitors the gas level in factory to take appropriate actions.

Technical Team:
They are responsible for maintenance and installation of Product.

2.4 Operating Environment

Mobile application is internet based so to update data mobile will need internet. However to
update data in application mobile with Bluetooth support is needed.

The Hardware module can work in environment with less humidity and module should be
away from dust outlet.

2.5 Design and Implementation Constraints

• Challenges in implementation of product is that due to portability need Arduino nano is to
be used in integrating all sensors .
• Data should be available in case of no internet also , therefore it is challenging to fetch data
from Bluetooth module.

2.6 User Documentation

The product will include a user manual. The user manual will include product overview, complete
configuration of the required software and hardware, technical details and contact information
which will include email address of the product manager.
Software Requirements Specification for TOGA Page 7

2.7 Assumptions and Dependencies

Proper working of this app is dependent on the internet connectivity of the users’ mobile
Assumptions and dependencies:
• It is assumed that the user has basic knowledge of the system .
• It is assumed that the data entered by the user while registering is true.
• It is assumed that user have knowledge about installation of system
• It is assumed that user have basic knowledge about using smartphone.
Software Requirements Specification for TOGA Page 8

3. External Interface Requirements

3.1 User Interfaces

3.1.1 User Login Interface

• User can login using email-id and password

• On submitting ,the screen will be redirected to home screen
• User must be alerted with error message on inputting false data .
• Login interface must be smooth.

3.1.2 Registration Interface

• User can get registered by using details specified.

• On submitting ,the screen will be redirected to home screen
• User must be alerted with error message on inputting data in incorrect format
• Mandatory fields must be visible differently.

3.1.3 View Readings Interface

• User can view gas levels with time stamp.

• It also shows current location on screen.
• It must have a button to save readings.
• It should lead to view historical data screen.

3.1.4 View Gas level Interface

• This interface will have list of gas

• On selecting a gas it will open a dialog which will show minimum and maximum gas
range.

3.1.5 Temperature view Interface

• User can view humidity levels

Software Requirements Specification for TOGA Page 9

• User can view temperature

• User can view heat levels

3.2 Hardware Interfaces

• MQ-2 for Sensing Methane

• Power button triple click support for calling
• MQ-7 for Sensing Carbon-monoxide
• MQ-135 for Sensing Sulphur-dioxide
• MQ-136 for Sensing Hydrogen Sulphide
• MQ-137 for Sensing Carbon-dioxide
• DHT11 for Sensing Temperature and Humidity
• HC05 Bluetooth Module
• Arduino MEGA
• Jumper wires

3.3 Software Interfaces

• OS: windows xp or above
• Bluetooth service
• IDE: Android studio, Arduino, dream viewer
• Tools: Adobe Illustrator, Xampp, phpMyAdmin
• Technology: Android, java, php, json
• Browser: Google chrome
• Database : MySQL
• Platform: Android SDK Framework
• Emulator : SDK version2.2 or higher

3.4 Communications Interfaces

• Communication between web server and database is done using http protocol
• Arduino uses Bluetooth to communicate with application
• Internet connection is used to load data into database.
Software Requirements Specification for TOGA Page 10

4. System Features
Following are various features of our system.

4.1 System Feature 1

Current Gas Readings and Historical Data

4.1.1 Description and Priority

4.1.1.1 User can view current gas readings and also save the gas readings which can
be viewed later along with timestamp and location

4.1.2 Stimulus/Response Sequences

User: request for reading
System: fetch data from data base
System: display data
User: save response
User: request for historical data
System: display historical data

4.1.3 Functional Requirements

4.1.3.1 User must be able to see current gas levels

4.1.3.2 User must be able to save current gas level

4.1.3.3 User must be able to save gas levels with time stamp and location

4.1.3.4 User must be able to view minimum and maximum gas level range

4.1.3.5 User must be able to see past readings.

4.2 System Feature 2

Emergency call and buzz alarm on high gas levels

4.2.1 Description and Priority

4.2.1.1 User can call emergency number in case of fire or increase In gas levels also
system will alert user by alarm and notification

4.2.2 Stimulus/Response Sequences

User: dial emergency number by triple clicking on power button
System: checking if gas levels are high
System: connects call on high levels
System: buzz alarm
Software Requirements Specification for TOGA Page 11

4.2.3 Functional Requirements

4.1.3.1 User must be able to see current gas levels

4.1.3.2 User must be able to save current gas level

4.1.3.3 User must be able to save gas levels with time stamp and location

4.1.3.4 User must be able to view minimum and maximum gas level range

4.1.3.5 User must be able to see past readings.

4.3 System Feature 2

Display temperature details

4.3.1 Description and Priority

4.3.1.1 User can view current temperature , humidity and heat levels

4.3.2 Stimulus/Response Sequences

User: request for temperature reading
System: fetch data from data base
System: display data

4.3.3 Functional Requirements

4.3.3.1 User must be able to see current temperature.

4.3.3.2 User must be able to see current humidity levels.

4.3.3.3 User must be able to see current heat levels.

Software Requirements Specification for TOGA Page 12

• USE CASE
Software Requirements Specification for TOGA Page 13

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The performance of the Application can be determined by it response time , time to

complete the given task and reliability of output data.

The performance requirements of Toxic gas Analyzer are the following:

• Data about gas readings should be updated within 1 second.

• Application should update temperature within a second.
• Arduino should give precise result about readings.
• Application should give alert within 2 seconds of suspicious gas levels.
• Location of user should be sent even in low internet.
• Module should be portable.
• The database shall be able to accommodate a minimum of 1,000 records of Users.
• The software shall support use of multiple users at a time.
• Module should be easy to install.
• Also, it should be made sure that app will not hindrance to the user Input.

5.2 Safety Requirements

• Read the smoke detector’s manual before installing for proper set-up.
• Install smoke detectors on the ceiling. If you must mount the smoke detector on the wall, it
should be placed less than 12 inches away from the ceiling.
• Don’t install on windows or sliding doors as the winds and air may not pick up the heat of
smoke or fire.
• Don’t install In humid or moist areas including the bathroom.
• Don’t install In areas that easily collect dust and dirt including unfinished attics.
• Don’t install Near ceiling fans or air vents.
• Test the smoke detector monthly.
• Keep the smoke detector clean.
• Replace batteries annually.

5.3 Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification below.

• Keep specific log or history data sets.

• Children below age of 14 should not be allowed to use application
• Controlled access to data
• User are not allowed to modify gas readings manually.
Software Requirements Specification for TOGA Page 14

5.4 Software Quality Attributes

• Portable
• Adaptable
• Reliable
• Interoperable
• Provides good response time
• High performance
• Easy to use

5.5 Business Rules

The Product is intended for industrial use only. Number of Detection and alarm units depends on
size of industry.
Software Requirements Specification for TOGA Page 15

6. Other Requirements
For information regarding functional requirements, refer to section 4: System Features. Each feature
has its requirements listed alongside the feature information. Special requirements for each system
feature are also mention in section 4. There are no additional Functional requirements.

Appendix A: Glossary

Sr. No. Abbreviations Description

1 ANDROID Android Studio(2.2.3)
2 ARDUINO Arduino Ide(1.8.3)
3 PHP Hypertext Pre-processing
4 SDK Software Development Kit
5 API Application Programming Interface
6 GUI Graphical User Interface
7 DB Database
8 MYSQL MY Structured Query Language
9 JDK Java development Kit
10 IOT Internet of Things
11 VCC Power +5V
12 GND Ground
14 IEEE Institute of electrical and electronics engineers
15 SRS Software requirement specifications
16 Open Software for which the code is freely available
Source for use and research

17 GPS Global positioning system

Software Requirements Specification for TOGA Page 16

Appendix B: Analysis Models

• Data flow diagram

• Context Level Diagram (TOGA)

[DFD – 0 level ]
Software Requirements Specification for TOGA Page 17

• 1st LEVEL DFD DIAGRAM (TOGA)

[DFD – 1 level ]
Software Requirements Specification for TOGA Page 18

• 2nd LEVEL DFD DIAGRAM (TOGA)

[DFD – 2 level ]
Software Requirements Specification for TOGA Page 19

• Activity diagram
Software Requirements Specification for TOGA Page 20

• class diagram
Software Requirements Specification for TOGA Page 21

• state-transition diagrams

• Entity-relationship diagrams
Software Requirements Specification for TOGA Page 22

Appendix C: To Be Determined List

https://developer.android.com/index.html
www.tutorialspoint.com www.javatpoint.com
http://www.androidhive.info https://www.circuito.io
https://www.arduino.cc
https://www.sciencedirect.com/topics/engineering/toxic-gas

https://www.ehs.uci.edu/programs/labres/ToxicGP.pdf