Software Requirements Specification (S.R.S.

)
Version 1.0
October 17, 2006

TITLE OF PROJECT: : "A GIS enabled web-interface for Supply

Chain Management used in Commodity Distribution "
Team members:
Ashok Philip Verghese
Deepu R.S.
Shabeerali
Thomas Emmanuel

Team email: milkiway@iiitmk.ac.in

Project blog: http://milki-way.blogspot.com

Table of Contents
1.0 Introduction

1.1 Purpose of this Document

1.2 Scope of the Development Project
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview of Document

2.0 General Description

2.1 User Characteristics

2.2 Product Perspective
2.3 Overview of Functional Requirements
2.4 Overview of Data Requirements
2.5 General Constraints, Assumptions, Dependencies, Guidelines
2.6 User View of Product Use

3.0 Specific Requirements

3.1 External Interface Requirements

3.2 Detailed Description of Functional Requirements
3.3 Performance Requirements
 3.4 Quality Attributes
3.5 Other Requirements

4.0 Acknowledgments

1.0 Introduction

1.1 Purpose of the Document

This document contains the specifications for "A GIS enabled web-interface for Supply chain
management used in Commodity Distribution" project. The specifications will include the
functional requirements and the data requirements, both of which will describe how the
developers will design the product in order to achieve all objectives. This document will serve as
a guide for the client and the developers, allowing for a common document by which to
understand the implementation.

1.2 Scope of the Development Project

"A GIS enabled web-interface for Supply chain management used in Commodity Distribution"
will be a web-based product interface used with the help of GIS and database that helps
commodity manufactures and distributors retrieve information for decision making and deliver
products efficiently and cost-effectively.

1.3 Definitions, Acronyms, and Abbreviations

• GIS - Geographic Information System

• JSP - Java Server Pages
• HTML - Hyper Text Markup Language which can be displayed on any browser..
• JRE - Java Runtime Environment .An environment that runs through most web browsers
and supports more advanced features than HTML.
• Web-based - A program that can be run through a typical internet browser such as
Firefox or Internet Explorer.

1.4 References

Project Documentation Standards for S2S project -

http://www.cs.utexas.edu/users/almstrum/cs373/fa99/doc-stds/

1.5 Overview of Document

The next section (2.0) contains general information on how this program will run. It will
explain most of the program's features and requirements without many implementation details.
Section 3.0 contains the specific requirements and implementation details.
2.0 General Description

2.1 User Characteristics

The primary users of "A GIS enabled web-interface for Supply chain management used in
Commodity Distribution" will be commodity manufactures and distributors. We have taken into
account that the users will probably have limited Internet experience or prior knowledge of GIS.
The keyword for most of the interface will be simplicity. The users will be presented with simple
instructions, without ambiguity. The information will be in an easy to understand format to the
user.

2.2 Product Perspective

The product will be a web-based application running within a web browser. The product will
reside on the server but can be accessed on any machine with internet connection.

2.3 Overview of Functional Requirements

2.3.1 Input

(1) A web based interface for Retailers: .

The retailer will enter an order request which contains the following components: He
can view the status of order information.

Login ID & Password

Quantity of the commodity required
Date

(2) A web based interface for Central suppliers:

Login ID & Password

2.3.2 Output

(1)For Retailers

Order Conformation
Registration Conformation
Order Status

(2)For Suppliers

Geographic location of retailers

Order Information with GIS visualization.
Transaction report on a daily/weekly/monthly basis
Map showing the shortest path

2.3.3 Instructional

There will be an instructional section on how to use this web interface .

 2.4 Overview of Data Requirements

2.4.1 Input

Major data requirement are:-

Maps with spatial data

User information

Product information

Retailer information

Central Distributor

2.4.2 Output

A graphical representation of the area displaying the location of all retailers who
ordered,

Shortest route for product delivery

Delivery report

Query based display with geographical information

Order information status

2.5 General Constraints, Assumptions, Dependencies, Guidelines

• Assumption: Retailers registered will be part of the geographical area covered in the map,
and all commodities will be available at any given time .
• Constraint: The interface must be easily understandable for the retailers.

2.6 User View of Product Use

Upon entering the corresponding URL a web interface will be presented to the user. The home
page will present the user with an option to login. Depending upon who the user is i.e..
(Supplier/Retailer) a corresponding web interface gets displayed. The supplier who will be the
administrator by default could view the daily orders along with a graphical interface. The user
could edit the profile information .

3.0 Specific Requirements

3.1 External Interface Requirements

No External interface requirements.

 3.2 Detailed Description of Functional Requirements

3.2.1 Instructional

The instructional part will serve as a roadmap to the retailers as how to use the web
interface. It will be available as a link in the homepage. The instructions will open up
a separate window, thus running concurrently with the main page.

3.2.2 Data Entry

The Client will enter the commodity information such as name ,quantity as well as
date of delivery. The Supplier will view the ordering information on various
commodities which is query based .Also previous ordering information could be
viewed on request at any time .Any erroneously looking figures will be checked.

3.2.3 Display

This client will be displayed forms to enter requests where as the supplier could view
the detailed list of all retailer requests along with geographical information.

3.3 Performance Requirements

The web interface will handle multiple users.

3.4 Quality Attributes

• The program will be completely functional on Firefox and Microsoft Explorer. It should
work on any platform;
• The program will have a read me file containing the minimum configuration requirement,
and other useful information. The code will be well-documented to make easy
modifications

3.5 Other Requirements

No other requirements are applicable.

4.0 Acknowledgments

Many thanks to DR. Venkatesh Chopella, Mr.T Radhakrishnan