Software Requirements Specifications For the Try n Save Incorporated ERP System

Chelsea Raymond July 10 2011

1

Table of Contents
1.0 Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations 1.4 References 1.5 Overview Overall Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics 2.4 Constraints 2.5 Assumptions and Dependencies Specific Requirements 3.1 External Interface Requirements 3.1.1 User Interfaces 3.1.2 Hardware Interfaces 3.1.3 Software Interfaces 3.1.4 Communications Interfaces 3.2 Classes/Objects 3.3 Design Constraints 3.4 Performance Requirements 3.5 Software System Attributes

3 3 3 3 3

2.0

4 4 5 5 6

3.0

6 6 7 7 7 8 8 8

1.
1.1

Introduction
Purpose
The purpose of this Software Requirements Specification is to provide a complete description of all functions and specifications of the ERP system for Try n Save Incorporated. The expected audience of this document is the software developers as well as the management of TSI and any employees using the software program.

1.2

Scope
The Try n' Save Enterprise Resource Planning system is designed to run on the local computers and registers in all local stores and warehouses and to allow each store to maintain inventory and submit automatic restock orders. The data will be accessible at TSI's headquarters to be analyzed by management.

1.3

Definitions, Acronyms and Abbreviations

TSI: Try n Save Incorporated ERP: enterprise resource planning POS: point of sale SO: store order TO: Transfer order RO: Resupply order LOC: lines of code

1.4

References
IEEE Std. 830 - 1998 IEEE Recommended Practice for Software Requirements Specifications

1.5

Overview of Document
The following section of the document, section 2, provides an overall description of the functionality of the software. It describes the requirements and is used as a context for the technical requirements located in the following section. The next section, section 3, describes in technical terms the functionality of the product and is intended for developers.

2.

Overall Description

2.1Product Perspective
Our product will be used primarily to maintain the inventory of all Try 'n Save stores and to automatically determine and execute inventory restock orders. Our product will also have the ability to generate data reports for Headquarters and will allow datamining features for sales analysis.

This figure shows the system and its interactions with all other components.

2.2Product Functions
2.2.1 Inventory Management
Upon logging on the the program an employee should be able to: enter individual items item id item quantity minimum amount to be stocked at all times delete items no longer being sold change item details 4

item quantity minimum amount of item to be stocked

2.2.2 Automatic Store Order

Upon recieveing a POS signal from local registers the program will: determine, based on the current amount of a specific item in stock: The item count is above the minimum required amount result: do not send SO to warehouse, update count in inventory The item count is below minimum required amount result: submit SO to regional warehouse.

2.2.3 Automatic Restock/Transfer Ordering

Upon receiving an SO from local stores the program on location at a regional warehouse will first reply with an acknowledgment and then: determine, based on the current amount of a specific item in stock: The item count is above the minimum required amount result: fulfill request to local store, and ship order to specific store. The item count is below minimum required amount result: Warehouse inventory system checks for another regional warehouse with a surplus of the specific item(above a 90 day stock). If available, submit a TO to peer regional warehouse and then fulfill request, and ship item to local store. If NOT available, submit a RO to item supplier, fulfill request and ship to local store.

2.2.3 Headquarter Database

Management located at TSI headquarters will be able to use the system in order to: maintain a corporate-wide view of sales and inventory systems of all local stores and regional warehouses. Generate monthly and quarterly management reports summarizing sales by store, sales by region, total sales, inventory by store, inventory by region and total inventory utilize data-mining feature to analyze trends in the data by region, time-of-year, holiday, and pet demographics for which parameters can be set by management.

2.3

User Characteristics

Employees using the software at both the local stores and regional warehouses should be able to maintain and organize inventory for their stores and warehouses. These employees should be trained in the program and very comfortable with and knowledgeable of local computers. At the headquarter level, skilled and trained analysts should be consulting data in order to fully utilize all data available in order to take best advantage of the features.

2.4Constraints
The product must run on a Windows operating system that is free of any viruses or fatal errors. The system must be able to create backup files of all inventory data to ensure. System must allow Java. 5

3.
3.1

Specific Requirements
External Interface Requirements 3.1.1.User Interfaces
3.1.1.1 Keyboard An English language keyboard must be available and will be used to input all inventory data. 3.1.1.2 Mouse A Standard two-button mouse must be connected and working in order to navigate the program and input and view data. 3.1.1.3 Monitor The monitor will be used to display all information provided by the program and should be of good quality.

3.1.2Hardware Interfaces
Windows 7, XP, Vista, 2000 Java supported 3.1.3

Software Interfaces
The system will not call upon any other software.

3.1.4

Communications Interfaces
Communications between local store registers and computers, warehouse computers and printers, and headquarter databases will be done over local telephone lines and wireless internet at the choice of TSI management and based on local availability. All communication will be done over standard communication protocols.

3.2 Classes/Objects 3.2.1 ORDER Class

The purpose of the Order class is to manage the submission of a store order from the POS all the way until the item is ready for shipment. 6

3.2.2 RESTOCK Class

The purpose of the Restock class is to correctly decide whether the item being restocked comes from a regional warehouse, a peer regional warehouse or a supplier.

3.3 Design Constraints

The system will be designed completely in Java and will only be able to run on Windows platforms.

3.4 Performance Requirements

The system at the warehouses must submit an acknowledgment back to the local store in under one minutes time, 90% of the time. The Windows operating system and all computers must be in good and working order at all times.

3.5 Software System Attributes

The system must be reliable, secure and maintained at all times.