Software Requirements Specification

(S.R.S.)

Production Chain Management

System

Project members:

Anurag Joshi
Nitin Singh
Rajesh K.R
Vinay Shukla

Project blog: http://webtech-pg5.blogspot.com

 Table of Contents

1. 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. Over View Of Document

2. 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. 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. Validation Criteria
4.1. Reorganization of successful implementation
4.2. Classes of test conducted to validate

5. Diagram

6. Acknowledgement
1. Introduction

1.1. Purpose of the Document

This document contains the specifications for project "Production Chain Management
System”. 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

"Production Chain Management System " Is a web-based product interface 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

ü 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.
ü Postgre- Database

1.4. References

ü Project Documentation Standards for S2S project -

http://www.cs.utexas.edu/users/almstrum/cs373/fa99/doc-stds/
ü Software Engineering A Practitioner’s Approach by Roger S Pressman

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. General Description

2.1. User Characteristics

The primary users of "Production Chain Management System" will be commodity
manufactures and distributors. We have taken into account that the users will probably
have limited Internet experience. 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

A web based interface for Client.
The Client will enter a production data, which contains the following components:

Ø He can view the status of production data.

Ø Login ID & Password
Ø Quantity of the commodity required
Ø Date
Ø A web based interface for Client:
Ø Login ID & Password
Ø Instructional
Ø There will be an instructional section on how to use this web interface.

2.4. Overview of Data Requirements

Major data requirement are:

Ø Production data
Ø User information
Ø Product information
Ø Client information
Ø Data Upgradation
 2.5. General Constraints, Assumptions, Dependencies, Guidelines
ü Assumption: Client registered and all commodities will be available at any given
time.
ü Constraint: The interface must be easily understandable for the Client.

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. (Client) a corresponding web interface gets displayed. The client who will be the
administrator by default could view the daily production data along. The user could edit
the profile information.

3. 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 client 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 client 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 form to enter the production data.

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. Validation Criteria

4.1. Recognition of successful implementation

Ø Check for storing and retrieving the data
Ø Checking for non existing user name and password
Ø Working on many computers simultaneously

4.2. Classes for test conducted to validate

ü Alpha- Beta test: Here strange combinations of data may be put and checked. A
customer conducts alpha test at the developer’s site. Beta test will conducted at
customer’s site on different system simultaneously.

ü Security test: Checking for security issue with the software. During this many test
player will try to break the security

ü Recovery Test: Here the test will try to fail the software and verifies that the
recovery is done a proper way, the data should be recover

ü Stress test: If the software requires 1gb ram provide it with 512 mb and see how it
works the performance may go down but the system should not crash
5. Diagram

5.1. Automation

Web Enabled
Managing Data Easy to Update Interface

Vendor
User Friendly Management
PCMS
Data Storage
Security problem solved

Speed &Accuracy Extendibility

Time Saving
 5.2. Vendor Management

Owner Steel

Computer
1

Computer Data Computer

3 2

Computer
4
Client Roll

6. Acknowledgments
Many thanks to

ü Dr. Venkatesh Choppella

ü Mr. David Mathews
ü Mr. Praveen Kumar
ü Mr. Sivchand Koripella