Inventory System

Submitted by: Submitted by

Views: 991

Words: 4085

Pages: 17

Category: Literature

Date Submitted: 03/01/2013 10:37 PM

Report This Essay

CHAPTER 3

3.1 Software Requirement Specification Document

1. Introduction

1.1 Goals and objectives

This Software Requirement Specification (SRS) provides the detailed requirements for the (Casa Milan Hardware Distributors) Sales and Inventory System. This document is intended to be used primarily by the software designers during the design phase, but will also be used extensively during the testing phase.

The (Hardware Distributors) Sales and Inventory System will integrate and organize the existing sales and inventory systems of the company.

1.2 Statement of scope

This section contains a general description of the software functionality followed by detailed requirements that will be traced throughout the project.

Before gaining access to the (Casa Milan Hardware Distributors) Sales and Inventory System, the intended users will be required to enter their username and password. There should be three (3) users who will have the privilege to access the system. Hence, the proponents categorized the users depending on their job classifications.

The system has a log-in and log-out form. In logging-in to the system, the administrator can access the whole system by recording, updating, saving reports, adding, editing, and deleting personnel, printing reports, invoice reports and recoveries.

The Sales Clerk can access the sales part in the system. In addition, the sales clerk also responsible in issuing invoices, updating and generating sales reports.

The Inventory Clerk is responsible in monitoring the number of incoming and outgoing of products. In addition, the Inventory Clerk also responsible in adding, updating and saving products. Thus, monitoring and generating daily, weekly, monthly, annually tally of inventory reports.

The following table groups user requirements into various categories. Each requirement is assigned a priority to indicate whether it must be implemented (High) or may be left out (Low). Low priority...