Software Requirment Specification

For
Web Enabled Dynamic Agricultural
Market Information
Version 1.0

November 12, 2006

Indian Institute of Information Technology and Managment - Kerala

(IIITM-K)

Prepared by Ajay S Ani,Prabu J,Praveen Kumar V, Ranjith K P.

1
Contents
1 Introduction 3
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Overall Description 4
2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Operating Environment . . . . . . . . . . . . . . . . . . . . . 4
2.4 Design and Implementation Constraints . . . . . . . . . . . . . 4
2.5 Assumptions and Dependencies . . . . . . . . . . . . . . . . . 4

3 External Interface Requirements 5

3.1 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 Communications Interfaces . . . . . . . . . . . . . . . . . . . . 5

4 Other Nonfunctional Requirements 5

4.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . 5
4.2 Software Quality Attributes . . . . . . . . . . . . . . . . . . . 5

2
1 Introduction

1.1 Purpose
To develop a system that brings in the power of GIS and database on to
a web browser that helps farmers, traders, administrators, academicians etc
for analyzing the agricultural market information through smart maps.

1.2 Intended Audience

The intended audiences are Academicians, Student developers, Subject ex-
perts etc

1.3 Project Scope

The project intends to empower farmers, extension officers, common people
etc by providing them quick access to prices and quantity of goods available
in different markets. This helps them in generating maximum profit for their
produce. It also helps them in planning for the future season

1.4 References
Academicians
Dr Venkatesh Choppella
Associate Professor
IIITM-K
choppell@iiitmk.ac.in

Mr. T. Radhakrishnan
Chief Technology Officer
IIITM-K
Student Developers
Ajay S Ani
Prabu J
Praveen Kumar
Ranjith KP

3
2 Overall Description

2.1 Product Perspective

Most of the gis based applications run on the client side, also the software
is very costly. This system that we intend to design is based on open source
software such as Mapserver and runs on a browser. Another advantage is
the dynamic nature of the results generated. The information so generated
serves the purpose and need of a whole class of people ranging from farmers
to policy makers

2.2 Product Features

The product will have the functionality to access the market prices of various
commodities from across different markets. The quantity of products avail-
able across different markets will also be monitored. The system will also
be capable of storing previous prices so that the fluctuation in prices can be
monitored and this can also aid in deciding the future farming

2.3 Operating Environment

Operating System : Windows2000/windowsXP professional
Front End : HTML, PHTML, PHP
Backend : PostgreSQL/Postgis
GIS Viewer : Quantum GIS
Development environment : MapServer
Application : GMap

2.4 Design and Implementation Constraints

The design constraints if any will be time

2.5 Assumptions and Dependencies

The accuracy of the presented data will depend on the input provided by
different agencies that will collect the data from different markets

4
3 External Interface Requirements

3.1 User Interfaces

There will be login page where registered users can login and update the
Database table and ordinary users will also go to the website but are required
to login they can click on the link and go straight away to the map from where
they will be getting market information.

3.2 Software Interfaces

The first page that a user sees will be a JSP page. If the user is a Registered
user then he will get a form where he can update market information here
we use MVC architecture, the form data goes to the servlet and from the
servlet it goes to the Bean and the Bean writes the data in to the Postgres
database. This information in the postgres will be displayed in the map by
using the postGIS application. The map file that all users see is coded in
PHP.

3.3 Communications Interfaces

The communication standard that is used is HTTP.

4 Other Nonfunctional Requirements

4.1 Performance Requirements

When viewing the map you will need a Java runtime enabled browser since
the image is loaded as a applet for example if you are using Mozilla firefox
as your browser it has inbuilt java support but when using Internet Explorer
one will not have this support then we have provision of disabling the Java
mode upon which the map will be displayed on the browser.

4.2 Software Quality Attributes

The code is based upon Mapserver documentations and customized and built
so that it will suit our purpose. Since Mapserver belongs to Opensource
community we didn’t violate any rules and authentication requirements and

5
regulations containing security issues that affect the product. All the appli-
cations that we used also Opensource so any one can use it the way he wants
it provided he should be using Windows platform.