AniTrax

Software Requirements Specification

Team 50 Phase 3
Bandaru Praveen Kumar
Lade Pratik
Manivasagam Niranjan
Rajendhran Krishna Anandh
Soundra Rajan Shiyamsundar
Thurvas Jeyakumar Sabharinath Babu

Table of Contents
1.Introduction............................................................................................................................................. 4
2.General Description................................................................................................................................ 4
2.1.Purpose............................................................................................................................................ 4
2.2.Product Functions............................................................................................................................4
2.3.User Characteristics.........................................................................................................................4
2.3.1.Village Administrators............................................................................................................. 5
2.3.2.Forest Officials........................................................................................................................ 5
2.3.3.Biologists/ Animal Enthusiasts................................................................................................ 5
2.4.Assumptions and Limitations..........................................................................................................5
2.4.1.Assumptions............................................................................................................................ 5
2.4.2.Limitations...............................................................................................................................5
3.Software Architecture............................................................................................................................. 6
3.1.Level 0.............................................................................................................................................6
3.2.Level 1.............................................................................................................................................6
3.2.1.Modules................................................................................................................................... 7
GPS Transmitter with Sonar Assembly........................................................................................7
Base Station Data Processor........................................................................................................ 7
Distributed Data Center............................................................................................................... 7
Interface....................................................................................................................................... 7
Web Server...................................................................................................................................7
3.3.Level 2........................................................................................................................................ 8
3.3.1.Level 2 GPS Transmitter and Sonar Assembly.............................................................. 8
Actuator........................................................................................................................................8
Mini Sonar................................................................................................................................... 8
Shape Estimator........................................................................................................................... 9
GPS Locator.................................................................................................................................9
Data Accumulator........................................................................................................................ 9
3.3.2.Level 2 Base Station Data Processor .............................................................................9
Data Center.................................................................................................................................. 9
Analytics Module.......................................................................................................................10
Data Distribution Tagger ...........................................................................................................10
3.3.3.Level 2 Web Server Module.........................................................................................10
Customization Module:..............................................................................................................10
Map View Renderer:.................................................................................................................. 11
Graphs/Tables/Charts generator:................................................................................................ 11
Animal Information Renderer:...................................................................................................11
3.4.Data Storage.................................................................................................................................. 11
4.Cross Reference Listing........................................................................................................................ 12
5.Functional Requirements...................................................................................................................... 13
5.1.Use Cases...................................................................................................................................... 13
5.1.1.Use case: The Village administrator...................................................................................... 13
5.1.2.Use case: The Biologists........................................................................................................13
5.1.3.Use case: The Forest Official.................................................................................................14
5.1.4.Use case: Data Center and Analytics Module........................................................................14
5.1.5.Use case: GPS device and the sonar assembly...................................................................... 14

2
5.2.Component Description.................................................................................................................14
5.2.1.GPS device activation and transmission................................................................................14
5.2.2.Sonar Activation and information collection.........................................................................14
5.2.3.Shape Estimator..................................................................................................................... 15
5.2.4.Data Logging......................................................................................................................... 15
5.2.5.Data Analysis ........................................................................................................................ 15
5.2.6.User Interface.........................................................................................................................15
5.2.7.View Manager............................................................................................................................ 15
6.Non-functional Requirements............................................................................................................... 16
6.1.Security and Permissions...............................................................................................................16
6.2.Scalability and Recovery...............................................................................................................16
6.3.Configurablilty.............................................................................................................................. 16
6.4.Flexibility...................................................................................................................................... 16
7. AniTrax Change Request Form ...........................................................................................................17
8.User Interface........................................................................................................................................ 19
8.1.Customization screen.................................................................................................................... 19
8.2.Global Map view........................................................................................................................... 20
8.3.Graph View....................................................................................................................................21
8.4.Mobile Application........................................................................................................................22
9.Integration Thread................................................................................................................................. 22

List of Figures
1. Level 0 Diagram....................................................................................................................................6
2.Level 1 Diagram.....................................................................................................................................6
3.Level 2 GPS Assembly Diagram.............................................................................................................8
4.Level 2 Base station Data processor Diagram.......................................................................................9
5.Level 2 Web server Diagram................................................................................................................10
6. Class diagram showing the data collected..........................................................................................11
7.Use Case diagram of the system..........................................................................................................13
8.Sensor Configuration Screenshot.........................................................................................................19
9.Global Map view Screenshot................................................................................................................20
10.Graph View Screenshot.......................................................................................................................21
11.Mobile application Screenshot............................................................................................................22
12. System Components Diagram............................................................................................................23

1.Introduction
The purpose of this Software requirement document of is to provide complete overview of
different components in the AniTrax system, its interfaces, systems goals, major capabilities and its
end users. It gives detailed description of the functional and non-functional requirements of the system.
It defines the constraints under which the system operates.
AniTrax System will integrate with the Google Maps API and provide tracking information of
an animal. This system will have the capability to send SMS notifications to certain end user groups
depending on the location of the animal. It will also analyze historical location data that is collected and
present information to the user based on his requirement. This system is designed to be accessed from
mobile devices as well as computers.

2.General Description
2.1.Purpose
The motive behind the AniTrax System is to provide information about animals so as to
improve the co-existence between animals and humans and also to unveil several mysteries
surrounding animal life-cycles. The existing systems provide only the current location information of
the animal. The aim of AniTrax System is to integrate all the relevant information about animals and
provide customized information according to the end users need. We believe that this information,
would help biologists and wild life enthusiasts to take conservation efforts in the right direction.
Anitrax sends out warnings to people living in villages near forests during potential animal
intrusion. We believe that logging the location data and mining information from this data could help
biologists uncover several of the mysteries pertaining to its life cycle.

2.2.Product Functions
Some of the features of AniTrax system :
An alerting system for common people living near forests.
A sonar and a shape estimator unit that when activated gives the herd count.
All of the location and herd count information of the animals are stored in data centers. A data
analysis unit is capable of extracting information from the this data center and present it to the
user on demand basis.
The application will be accessible from Web Browser and will also contain a mobile
application. The application will also provide alerts via SMS to warn people living near forest
of possible intrusion.

2.3.User Characteristics
This application will be mainly used by
Village Administrators
Forest Officials
Biologists / Animal Enthusiasts

5
2.3.1.Village Administrators
A Village Administrators will be generally concerned about animal intrusion. They will be accessing
the system via the mobile application. They will be able to decide which animals are dangerous for
their landscape and setup localized warning schemes. For example herbivorous animals are not deemed
as invaders in residential locations of a village but when the same animal invades a farmland it is
capable of crop damage.
2.3.2.Forest Officials
A Forest official is generally more concerned about animal poaching and intrusion than animal
migration details. He will be alerted when there is a decrease in number of animals in the herd or
whenever there is an animal intrusion.
2.3.3.Biologists/ Animal Enthusiasts
A Biologist or animal enthusiast use the historical data collected by the system for research to
understand the life cycle of an animal under a give environment. The applications data can be used to
track migration information, environmental effects and aging effects on an animal.

2.4.Assumptions and Limitations

2.4.1.Assumptions

The users of this application have basic knowledge about computers and mobile devices
The application is compatible with all browsers and mobile devices
The user will have uninterrupted Internet connectivity regardless of the device used
The data centers will be scaled on a regular basis.
When a new sensor is placed on an animal the general information about the animal is
updated in the database by the user.
The system contains the information about the end users to be alerted on an emergency
and is updated regularly.
The sensor cannot be removed easily or does not fall off easily.

2.4.2.Limitations

Biologists require information from multiple sites. Integrating the data is a major hurdle.
The system cannot be put into use until there is a proper backup system deployed with
disaster recovery servers at several locations.
The sensors placed on the animals must be able to work without failure or contain a
recovery system.
The network connectivity for between the sensors and the receiver inside water is not
reliable.
The system uses an artificial intelligence based shape estimator which requires proper
training. So it is possible that during the training phase(initial phase) the system may
fail.

3.Software Architecture
This section will cover the Software Architecture over view using Data Flow Diagrams, at
increasing levels of functionality. This provides a basic level information of the architecture.

3.1.Level 0
Level 0 depicts data flow at context level, which shows the basic interaction between AniTrax
system and the User.
Animal alert warning

User

Customization/Configuration

AniTrax System

Animal Tracking information

Image 1: Level 0 Diagram

3.2.Level 1
AniTrax system in the previous level is exploded in to sub systems and data flow between these
sub-systems are shown in this is level. The first level break down includes modules 1. GPS transmitter,
2. Base station data processor, 3. Distributed data center, 4. Web interface, 5. Web server. These
modules processes the data coming into them and out puts the processed data, which in turn contributes
in rendering animal tracking information.

Image 2: Level 1 Diagram

7
3.2.1.Modules
GPS Transmitter with Sonar Assembly
GPS transmitter is attached to the animal, which periodically gets activated by an actuator.
The actuation intervals are configured remotely by the user. The actuator initially activates a
sonar unit that works with a shape estimator and gives an estimate of the herd size. Using global
positioning satellite network the GPS transmitter transmits location of the animal and the size of
the herd to a base station.
Base Station Data Processor

Raw data about the animal location received form GPS transmitter is logged in a data center.
The data center then communicates with a data analysis unit that uses data mining algorithms to
extract information that might be useful for the user and stores it back in the data center. It logs
all these data in structured fashion and periodically feeds the data in to a distributed data center.
Distributed Data Center

Distributed Data Center consists of data storage systems distributed geographically, this module
stores data about different animals received from various transmitters and replicates this data on
some of the data storage systems, in order to provide faster, fault tolerant and high availability
of animal tracking information for the geographically distributer users.
Interface

Web Interface provides the user necessary GUI for customizing the Animal tracking
Information he/she wish to receive, and also acts as a channel to initialize requests for any
particular tracking information. Web Interface sends this customization information(transmitter
and sonar) and user requests to the web server following HTTP protocol, which subsequently
receives Animal tracking information and displays in a graphical user interface to the end user.
It should be noted that the GUI provides a plethora for the user to view and analyze the data
that he requires. Further privacy is provided by using views and permissions for each user type.
For example, a village administrator need not have access to the logged information in the data
center. The only thing that he is concerned about is the possibility of an intrusion.Thus he will
only be able to view that information. There is also a mobile interface that receives warnings
when an animal comes in close proximity to a village.
Web Server
Web server module is primarily responsible for storing the users configuration, processing the
received data requests, and querying the distributed data center for the animal tracking
information. According to the users configuration, web server does all the necessary
computation required on the data received from the distributed data center and sends it to the
web interface. Web server also caches frequently requested information in its local database for
a faster processing of requests.

3.3.Level 2
Data flow diagrams in level 2 would be exploding each and every module in level 1 to their respective
sub modules. We now explain the level 2 diagram for each explained in level 1.
3.3.1.Level 2 GPS Transmitter and Sonar Assembly

Image 3:Level 2 GPS Assembly Diagram

Actuator

The actuator is responsible for activating the transmitter periodically. The schedule for
activation is set remotely by the user. The actuator sends the signal to the mini sonar and
another to the GPS device.
Mini Sonar

The sonar, when activated, sends a high frequency sound signal which gets reflected by the
objects around. The sonar then reads the reflected sound wave. The data extracted from this
signal is compared with the data stored in the shape estimator to determine the herd size.

9
Shape Estimator

The shape estimator is an element that communicates with the sonar assembly. It contains
learning algorithm to improve the estimate of the animal shape. The shape estimator has initial
shape of the animal that is fed in by the user at the time of installation. As time passes, the
learning algorithm perfects its notion of the animal. Initial false positives are to be ignored.
GPS Locator

The GPS locator when activated communicates with GPS satellites to find the current coordinates of the animal.
Data Accumulator

The Data accumulator module communicates with the sonar assembly and the GPS device. It
combines the information obtained from both devices using a filler in between and then sends
this data to the transmitter.
3.3.2.Level 2 Base Station Data Processor

Data from
the
transmitter

ra
tured
c
u
r
t
s
Un

1. Data Center

2.Analytics Module

Structured information

Animal
Tracking
Information

Local
Data Center in
Region 1

a
w dat

3.
Data Distribution Tagger

Local
Data Center in
Region 2

Local
Data Center in
Region 3

Image 4: Level 2 Base station Data processor Diagram

Data Center

The data center is just a universal sink that stores all of the data that is transmitted to it from the
GPS and sonar assembly. The data center is periodically scaled because it houses several
terabytes of data. It also has a data recovery and a periodic data backup feature.

10
Analytics Module

The data analytics module contains several data mining algorithms that extract the information
that is stored in the data center. It then returns this data back to the data center and stores it.
Data Distribution Tagger

Using the location data from the data center, the data distribution tagger identifies the region in
which this data will be useful. It then identifies the closest local data center to which this data
has to be sent and send it there for storage and utilization.
Since the distributed data center is a single entity we do not have to draw a level two diagram for it.
3.3.3.Level 2 Web Server Module

Image 5: Level 2 Web server Diagram

Customization Module:

User will be able to configure/customize the data he/she wishes to receive by entering data
through key board, mouse or touch screen. The data will be like name of the animal, scientific
name, Animal family based on taxonomy (mammal, reptile, avian etc.), Herbivore or Carnivore,

11
weather a warning required for a particular animal when in close proximity to a human habitat?
Customization module will also manage the activation schedules for the transmitter. The user
can retrieve and configure this information as well.
Map View Renderer:

Map view displays the locations of all the animals in a particular region. This will be the default
view for the user. User will also be able to save the map in an image format which might be
helpful for future reference.
Graphs/Tables/Charts generator:

This Graphs/Tables/Charts generator module is responsible for generating graphs, tables or

charts instantly upon users input parameters, which he is attempting to measure.
Animal Information Renderer:

Animal Information Renderer provides all the necessary information required by the Map View
Renderer and Graphs/Tables/Charts generator modules.
We do not expand the Interface module because it is a simple web page or a mobile application that
communicates with the web server module using HTTP requests and displays the data to the user.

Image 6: Class diagram showing the data collected

3.4.Data Storage
Large corpus of data is stored in Distributed data center as a replicated file system and web servers
local data base consists of relational tables. A sample view of these tables is shown below:
Data flow across various modules will be in xml format, here is a sample xml snippet containing

12
animal tracking information.
<Animal> Elephant
<Class> Mammal </Class>
<Animal Location>
..
<X-Coordinate> 3.4391e^4 </X-Coordinate>
<Y-Coordinate> 7.3322e^5 </Y-Coordinate>
<Acquisition Time> Sat Jul 23 02:16:57 2013 </ Acquisition Time>
..
..
</Animal Location>
</Animal>

4.Cross Reference Listing

Software Requirement System Specification
Reference
Reference

Function

4.2.1

3.1.1

GPS device activation and transmission

4.2.2

3.1.1,6.1

Sonar Activation and information collection

4.2.3

3.1.2,6.1

Shape Estimation using contours

4.2.4

3.2.1

Data Logging in the Distributed data centers

4.2.5

3.2.1, 3.2.2

Data analysis and pattern matching

4.2.6

6.3

User Interface

4.2.7

6.3

View Management and User Authentication

13

5.Functional Requirements
5.1.Use Cases
In this section we use a simple use case diagram to explain the functional requirements of the system.
We identify the following major actors in the system:

The Village Administrator

The Biologist

Forest official

A GPS device and Sonar Assembly

A data center and analysis unit

Image 7: Use Case diagram of the system

5.1.1.Use case: The Village administrator

The village administrator is capable of deciding which of the animals pose a danger to his
people and is able to set up warnings for those animals alone.

He has access to only the mobile application.

5.1.2.Use case: The Biologists

The biologists are able to view the Graph and Map views of the data that is collected by the
system based on his need.

The biologists also have the authority to configure the sonar and GPS unit's activation times.

14
5.1.3.Use case: The Forest Official

The forest official gets information about possible animal intrusion in nearby villages so that he
can act accordingly.

He also gets updates about any significant drop in the herd size which could possibly indicate
poaching.

5.1.4.Use case: Data Center and Analytics Module

Logs all of the data from the GPS device.

Communicates with the analysis component to detect interesting patterns that may satisfy a user
need.

Capable of receiving requests from users and sending the required information to the user.

5.1.5.Use case: GPS device and the sonar assembly

This device when activated, communicates with the satellite and retrieves the current location of
the animal and the herd size.

The GPS device is configurable by the forest official and the biologist.

The data collected is then transmitted to the data center for classification and storage.

5.2.Component Description
We now look at the key components of the system and the role that each component plays towards
achieving the overall objective of the system.
5.2.1.GPS device activation and transmission
Input: Interval for the next immediate transmission from the base station controller will
periodically be sent.
Output:An acknowledgment message with the current location information.
The GPS device upon receiving this request will activate and obtain the location information. It
will also communicate with the sonar module and send an activation message. It will receive the
herd information and append it to the location information and transmit it to the base station.
5.2.2.Sonar Activation and information collection
Input: The activation message from the GPS device.
Output: The estimate of the herd count.
The Sonar will then communicate with the Shape Estimator module. After gathering the herd
count, it sends the information to the GPS device for transmission.

15
5.2.3.Shape Estimator
Input: Message from the sonar device.
Output: The closest matching shape contours and the number of matching objects.
The shape estimator will communicate with the sonar to give the shape information required to
detect nearby animals. And take a count. The shape of the animal is learned by the module
using artificial intelligence.
5.2.4.Data Logging
Input: The location data that is transmitted from the GPS device.
The Data logging module is just a storage device that stores the location data of all the animals.
It is a vital component because, it forms the knowledge base for the data analysis component
with which it communicates .
5.2.5.Data Analysis
Input: Location data that is logged.
Output: Useful patterns and information that satisfies user need.
Upon the user request, this component, communicates with the data log, queries it and extracts
the required information. This component has several mining algorithms that are used to extract
useful information from the location information and present it to the user based on need.
5.2.6.User Interface
Input: The User need.
Output: Data presented as maps or graphs according to the users need.
The user interface serves as the bridge between the user and the AniTrax system. It mainly
interacts with the data analysis subsystem and the View Manager component. It simply
transfers the user's request to the data analysis module or the user credentials to the view
manager.
5.2.7.View Manager
Input: The user credentials.
Output: User permissions
The user logs into the system using his password. The view manager identifies the type of user
and delivers functionalities pertaining to that particular type of user. For example the data
analytics part of the system is only needed by the biologist. So the option is unavailable to a

16
village administrator.

6.Non-functional Requirements
6.1.Security and Permissions

The system achieves this requirement by having a login for each user.

The view manager differentiates between the different user types.

Once the system identifies the user type it grants access to certain functionalities to the user
while denying the remaining functionalities. For example, the village administrator cannot
access the logged data in the data centers because modifying it could cause adverse effects.

6.2.Scalability and Recovery

The data centers of the system are constantly monitored and scaled.

Periodically the system initiates a back up process that takes all of the important information
that has been collected so far and stores it while flushing the unwanted archived data that has no
or little significance.

6.3.Configurablilty

The system is completely configurable.

The certain user groups have the authority to configure every tracker individually.

The user can also configure the contour that has been built in the shape estimator using learning
algorithms.

The user can also decide on which of the animals cause a threat, and the extent of the threat.

6.4.Flexibility

The system offers high order of flexibility for the user's need.

The same pattern of data can be rendered to the user in different format upon the user request.

For example some of the options available to the users are bar graphs, line graphs, tables,etc.

17

7. AniTrax Change Request Form

Request Information (This section must be filled by the client)
Request Number
Version
Date of request (mm/dd/yyyy)
Initiator
Change Type

___ New requirement

___ Change requirement

___ Other

Reason

___ Defect
___ Performance

___ Customer Request

___ Other

Priority

___ High

___ Medium

___ Low

Category

___ UI

___ Anitrax

___ Sensor
Configurati
on

Description

Signatures

Technical Evaluation (Attach related documents)

Received by

Date received(mm/dd/yyyy)

Assigned to

Date Assigned(mm/dd/yyyy)

Documents Affected

Section

Page

Reference

Requirements specification
System design specification

Time & Cost Estimates

Stages
Analysis/Design
Coding/Testing
Acceptance

Estimate Time

Estimate Cost

Date completed
(mm/dd/yyyy)

18
Project Impact Analysis

___ Yes ___ No

Total hours

___ Budget

___ Resources

___ Schedule

___ Risks

Total Cost USD

Approvals
Status
Signatures

___ Approved

___ Denied
Dates (mm/dd/yyyy)

___ Pending

19

8.User Interface
The Interface module is the most important component in the AniTrax system. The amount of options
that the user interface gives and the configurablity that is offered is superior to any current system
available in the market. This section presents mock ups of the Graphical user interface that is provided
by the system. This will in turn be a pointer to the functionality and options available in the system.

8.1.Customization screen

Image 8: Sensor Configuration Screenshot

Whenever there is a new device that is deployed, the system recognizes it and forces the user to
configure the device, so that it can categorize the animal type in its data center and also set the
activation schedule for the sonar and the GPS device. The user enters information about the type of
animal the device is attached to. He can also decide the interval between the device activation on an
hourly basis. This option will allow the user to prolong the battery life of the device.

20

8.2.Global Map view

Image 9: Global Map view Screenshot

This is the global map view of the system. It shows all of the animals that are tagged with the
system in any particular device. On the left pane is a list of areas that are accessible. Each option gets
the data from a local distributed data center. The blue marker shows a new device that has been
installed. Clicking on this marker takes the user to the configuration screen explained before.

21

8.3.Graph View

Image 10: Graph View Screenshot

This view uses the historical location information that is logged in data centers and displays this
data according to the users information need. In this particular example the user requests a path trace of
all the carnivores that are tagged with the device. There are several other options available to the user to
enable him to study the characteristics of animals.

22

8.4.Mobile Application

Elephant

Image 11: Mobile application Screenshot

(a) Analysis (b)Villager warning

There is also a mobile application that comes with the system. The app's main functionality is to
give out warnings to the village administrator about possible intrusions and to give analysis results on
the fly to biologists based on their need.

9.Integration Thread
The integration thread shows all the components that are essential for the system to function. The
AniTrax system gathers location information using a tracking device attached onto the animal. This
information is sent to a Central Data center for storage. A data analysis module extracts information
based on the user need and sends it to the user interface which in our case is a web application or a
mobile application.The user interface has internal modules that help in rendering the data as the user
needs. For example as a bar graph or a pie chart etc. In order for the system to be tested all of these
components made operational. There are several other features to the system which can later be
implemented to enhance the capabilities of the system after these basic systems have been deployed

23
and tested.

The System

Tracking Device
(GPS)

Animal

User Interface

Data Center

Data Analytics

Image 12: System Components Diagram

User