LOGISTICS AND WAREHOUSE MANAGEMENT SYSTEM

SOFTWARE REQUIREMENT SPECIFICATION DOCUMENT

Page 1 of 10
 TABLE OF CONTENTS

1. INTRODUCTION 3

Introduction: 3

Purpose: 3

Scope: 3

Document Convention: 3

Intended audience: 3

Additional Information: 3

Contact Information/SRS Team Members: 3

References: 4

2 . OVERALL DESCRIPTION 4

Product Perspectives 4

Product Functions 4

User Classes and characteristics: 5

Operating Environment 5
 Hardware Interface: 5
 Software Interface: 6

Design/Implementation Constraints 6

System Functionality 7

Assumptions and Dependencies 10

Page 2 of 10
1. Introduction

Introduction:
We are going to develop the software requirement specifications for the Logistics and
Warehouse Management System (LWMS).

Purpose:
To automate the gasoline pump control system which deals with the dispensing of
gasoline, handling customer payment and monitoring tank levels.

Scope:
The scope of this project is to create and implement the Logistics and Warehouse
Management System (LWMS). The scope of this document is to fully document the
software requirements of the LWMS using the Software Requirement Specifications
format in accordance with IEEE Recommended Practice for Software Requirement
Specifications.
The LWMS implementation date will be determined at an appropriate time.

The LWMS will perform the following functions:

- Interfaces with the mechanical system of the pumps.
- Implements a transaction processing system
- Provides a repository for storing the transaction data.
- Validate and authenticate the customer identification like SSN or Driver’s
license number in case of check payments by the customer.
- Archiving transaction data to the corporate office.
- Retrieve data from the corporate office archives.

The GPCS team developed the design policies from a functional perspective, ensuring
that the state regulatory and safety laws are followed.

Document Convention:
GPCS: Gasoline Pump Control System
SRS: System Requirement Specification

Intended audience:
The customer is Dr. DeLoach.

Additional Information:
The Project Time Line and Quote document and the User problem statement would be
attached to the SRS document.

Contact Information/SRS Team Members:

1. Sudarshan kodwani (lal@ksu.edu)
2. Padmaja Havaldar (pph6666@ksu.edu)
3. Mrunal Dhond (mgd6969@ksu.edu)
4. Nitesh Pai (nitesh@ksu.edu).
Page 3 of 10
References:
1. Requirement Paper (http://www.cis.ksu.edu/~sdeloach/748/homework/case-
study.htm)
2. IEEE Recommended Practice For Software Requirement Specifications
(http://www.cis.ksu.edu/~sdeloach/748/papers/IEEE%20recommended
%20practice%20for%20software%20requirements%20specifications.pdf)
3. Software Project Management: a unified framework.
Walker Royce.  5th edition, 1997.
4. www.raycomm.com

2. Overall Description

Product Perspectives
This document describes the requirement specifications for the implementation of the
gasoline pump control system for handling the dispensing of gasoline, customer payment,
monitoring the tank levels and take care of all the other mechanical process of the pump
station.

The purposes of this document are to serve as:

  A basis of communication between all parties;
  Input to the design team;
  Input to software testing and quality assurance;
  A development manager’s reference;
 A control for the evolution of the system.

Product Functions
The software will automate the process of dispensing gasoline by interfacing with the
mechanical process of the gas station with a single computer. The software will also
process the customer transactions and archive them. Software is supported by the real-
time connectivity between the gas station and the corporate headquarters.

The Following Diagram Fig 1 depicts the various functional interactions of the system.
The System interacts with the Gas Pump Terminal, underground tank level checks,
Customer purchasing gasoline, the customers payment criteria, It handles and archives
the daily transactions, Updating the corporate server with the transactions, the Terminal
operator. The Details of the various interactions will be discussed in the design
document.

Page 4 of 10
Fig 1

User Classes and characteristics:

User classes define the anticipated end users of the Gasoline Pump Control System.
The user classes are differentiated based on the frequency of use, technical expertise and
security or privilege levels.

The following represent the user classes:

 Vehicle users – These users require gasoline for their vehicles.
 Gas station employees (operators, attendants etc.) – These users maintain and
operate the system.
 Corporate Office – Uses the system to archive transaction data.

Operating Environment

 The Gasoline Pump Control System software will be installed at the gas station.
 Hardware Interface:
The terminal have 2 systems one system takes care of the archiving of the daily
transactions; the other system has to show the streaming video.

Page 5 of 10
 So we would need a Pentium system at he minimum and the video system would
require a good quality graphics card. Both systems should have minimum of
32mb RAM memory.
The Corporate Server needs to be a server class machine with at least 256 MB
RAM and Pentium 4 system.
A dedicated link between the corporate sever and the Gas Pump Outlet.

 Software Interface:
The Terminal machines require Windows 9x or better, it needs a MS access 9x or
better to store the daily archives.
The Corporate server should have oracle 8x or better to hold on to all the archives.

User Documentation:
 Manual of the Gasoline Pump Control System.
 Online help and tutorials.

Design/Implementation Constraints

 In the future It is possible that the software design will have to incorporate
changes that could take place in the mechanical domain of the system.
Some of the anticipated changes are given below
- New pumps being purchased
- Change of pumps (sophisticated to normal and vice-versa)
- Incorporation of new safety standards.

 Change in the mode of payment

- Accepting credit cards at the pump terminals
- Real time verification of check payments at the pump terminals
- Customer Account Balance verification.

 Security features at the gas station

- Installation of cameras at each pump terminal.
- Automatic Scan of the Vehicles license number.

Page 6 of 10
System Functionality

The Gas Pump operator is the person who is responsible for the correct and reliable
functioning of the gas pump. Operator is the person who controls the GPCS. Once the
GPCS is started by the Operator the GPCS is in Active and running mode. The Operator

Page 7 of 10
would see the following screen on his workstation. Fig 2. The screen is self explanatory
as to what the functions of the operator would be.

Fig 2.

The Operator can check each tank level, for the two grades of gasoline. When he does the
check, the text boxes will be filled with tank fill percentages. If the Tank goes below 20%
the operator has to ask for the Gasoline tank refill. Online help and tutorial is available to
the operator. Each transaction that happened on a particular day is archived in the local
database. The Operator can Archive the Entire daily transaction history to the central
server by selecting the Archive button. The Operator can view the Customer details by
scanning or entering the Customer Id. The Operator can make a complaint on any
License number and the amount due if the customer absconds without paying the due
amount. The License number would appear once he clicks on the video screen of the
pump where the gas was filled.

When the Operator starts the GPCS system, the Video workstation starts showing the
Operator live streaming video of the different gas pump terminals. This screen is shown
in Fig 3.

Page 8 of 10
Fig 3

We have 3 sophisticated Pumps, viz pump 1-3 and 2 normal pumps pump 4-5.

The sophisticated pump display frame shows the video, the pump status, if green the gas
is being pumped if red pump inactive. When the gas handle is lifted from its holster, a
micro switch sends a signal to this screen and the operator hears a beep. The operator can
view the current gasoline grade, which is dispensed. The operator can view the currents
sale in dollars, which shows the amount in real time. The Operator can also see if the user
selected a preset amount or a preset gasoline quantity. On clicking on the video screen the
operator can see the license number of the vehicle at the terminal,(or the last vehicle that
was there at the terminal). This is useful to the operator to lodge complaints on
absconding customers. The customer needs to come and pay at the kiosk when the sale is
done.

The Normal Pump display frame shows the video, the pump status, if green the gas is
being pumped if red pump inactive. When the gas handle is lifted from its holster, a
micro switch sends a signal to this screen and the operator hears a repeated beeping
sound. The operator has to then turn on the pump terminal for the customer to dispense
the gasoline grade he selected. The operator can view the current gasoline grade, which is
dispensed. The operator can view the currents sale in dollars, which shows the amount in

Page 9 of 10
real time. The operator has a panic button for security and for urgent maintenance
request.

Assumptions and Dependencies

 As soon as the user lifts the pump handle, a signal is automatically sent to the
operator console via the system requesting that the pump be enabled.
 The user has to make the payment at the gas station kiosk where the operator will
be located.
 The system is linked with the corporate office network.
 The system uses licensed third party software products.
 The gas station premises will not be affected by frequent power outages.
 The Gasoline reorder level is set to 20% for each tank.
 Reordering of the tank level signal will be sent to the Gas Tank Refill
Department, once the signal is sent the handling of the Gas Refill is out of the
present system domain.
 At any point of time there is only 2 gasoline grades one in each underground tank.

Page 10 of 10