lOMoARcPSD|39716354

SRS Warehouse Management System

Transportation Planning (Rajiv Gandhi Proudyogiki Vishwavidyalaya)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)
 lOMoARcPSD|39716354

Software Requirements
Specification

For

Ware House Management

System

Version 1.0 approved

Department of Software Engineering, MUST

<10/01/2019>

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

Table of Contents
Table of Contents ..........................................................................................................................
Revision History ........................................................................... Error! Bookmark not defined.
1. Introduction ..............................................................................................................................1
1.1 Purpose ..............................................................................................................................................1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions ...................................................................................1
1.4 Product Scope ....................................................................................................................................1
2. Overall Description ..................................................................................................................2
2.1 Product Perspective ..........................................................................................................................2
2.2 Product Functions .............................................................................................................................2
2.3 User Classes and Characteristics ......................................................................................................2
2.4 Operating Environment ....................................................................................................................2
2.5 Design and Implementation Constraints ..........................................................................................2
2.6 User Documentation ........................................................................................................................3
2.7 Assumptions and Dependencies ...................................................................................................... 3
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ..................................................................................................................................3
3.2 Hardware Interfaces ..........................................................................................................................3
3.3 Software Interfaces ...........................................................................................................................4
3.4 Communications Interfaces ..............................................................................................................4
4. System Features .......................................................................................................................4
4.1 System Feature 1 ...............................................................................................................................4
5. Other Nonfunctional Requirements .......................................................................................6
5.1 Performance Requirements .............................................................................................................. 6
5.2 Safety Requirements ........................................................................................................................ 6
5.3 Security Requirements ..................................................................................................................... 6
5.4 Software Quality Attributes ............................................................................................................. 7
5.5 Business Rules ................................................................................................................................. 7
Appendix A: Glossary....................................................................................................................7
1. Introduction `

1.1 Purpose

The “Ware House Management System” aims to reduce the paper work,financial expenses and
provides the real time performance to the user in a more manageable way. This is the version 1.0 of
the requirement development phase and is the initial released.

1.2 Document Conventions

• Times New Roman font style is selected throughout the document

• Chapter headings sized is fixed to 18
• Normal and sub-headings are set to 14. • Text sized is fixed to 12
• Paper size is set to A4.
• All headings are in Bold.

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

1.3 Intended Audience and Reading Suggestions

This SRS will lead the development team‘s members specially:

• Designer
• Tester
• End user
• Project Manager to implement the customer’s need that lead the project to be successful. This SRS is
organized according to the IEEE’s format. Moreover this will be a legal contract between the client and
development organization.

1.4 Product Scope

The WHMS is responsible for maintaining registered items , their quantities and alarming the
manager and admin at lower stock. Moreover it will be able to have a good check and balance in the
all branches associated with this system. This system will be a great deal for the owner and his/her
customers and worker to perform their jobs in a very efficient way. This will be applicable to the all
stores having daily life’s needed items, Thus it is a generic system.

2. Overall Description

2.1 Product Perspective

This project is originally designed by our organizations (MUST). The client has never use any
automatic system for all his franchises ,before this his accountant manually performed paper work
for each transection and we replace this with our WHMS to use resources efficiently. This system
will also communicate with the HBL to keep the record of each transection and offers the customers
to pay online through their credit card etc.

2.2 Product Functions

The system will be able to:

• Allow admin to add and remove customer, manager, dealer, and supplier, generate report, view stock,
and to check in and out transections.
• Alarms the manager and admin on low stock of the items.
• Generate auto bills through barcode reader.
• Offers regular customers to have specific discounts.
• Keep track of in and out items.
• Allows customers to pay bills through their credit card.

2.3 User Classes and Characteristics

The following users will interact with WHMS and their main goals are as follows

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

• Admin: add and remove customer, manager, dealer, and supplier, generate report, view
stock, and to check in and out transections.
• Customer: The system will allow the customers to added as a permanent/regular or normal,
pay via cash or credit.
• Ware House Manager: Report to the admin on admin’s demand manually and report
regularly to the admin on each month.
 Sales Manager
 External payment modules: HBL will interact with WHMS to keep track of in and out
transections

2.4 Operating Environment

This is a web base system and will be operated on any online resource that supports internet.
The minimum operating requirements are:
• Dual core processor of 1.0 GHz minimum.
• 256MBytes of RAM.
• Rom of 520 MB to 1 GB
2.5 Design and Implementation Constraints

The proposed system is subject to general constraints of schedule, scope and cost that are Common to
every software system. However, following additional constraints are associated with the WHMS

2.5.1 Implementation Constraint

• This System should be running in an Windows operating system on any browser.

• The front end of system’s mobile application will be developed using Asp.Net, HTML,CSS and
C#. The system will use SQLServer database which is open source.
• All implementation will be completed within N months.
2.5.2 Design Constraints
• The system will have a relational data base.
• It will employ an object oriented approach.
• The project team will communicate with the client and evaluate the module by user before moving to the
next module.
• Only the organization’s defined process will be used while developing

2.6 User Documentation

• User manual for system information.

• Training for end user

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

2.7 Assumptions and Dependencies

All the requirements all well defined and the developer will not make any assumption. If the
developers is not clear on any requirement he must be have to clear it by the requirement engineer
before implementing it.

3. External Interface Requirements

3.1 User Interfaces

The design of interfaces should be such that the system users can use system with very ease. System
navigation should be made simple and consistent. All the interfaces should follow the Usability Principles

3.2 Hardware Interfaces

3.2.1 Barcode Reader:

This will be used to detect the item and generate the price associated with it.

3.2.2 Credit Card Swipe Machine:

This machine will allow user to pay via their credit card.

3.3 Software Interfaces

3.3.1 Operating System

This is the commonly used OS run on the PCs, this system will be able to run on all version of windows.

3.3.2 HBL’s System

This system will also be able interact with the HBL’s system for payment via credit card. All
the communication to WHMS requires high speed connectivity of internet.

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

3.4 Communications Interfaces

A notification will be displayed on each action in a corresponding interface. In case of low stock
WHMS will send the notification to the admin and manager. The manager will notify to the admin
by using admin’s private address e.g., email.There will be a complete communication mechanism
between the users of this system and all communication will be encrypted specifically for banking
transections .

4. System Features

4.1 Admin’s Features

It will include the following features :

4.1.1 Stimulus/Response Sequences

For the admin and any other user to perform any action he must have a valid login that
provided by this system. After Successfully login each user will perform his
corresponding functions.

4.1.2 Functional Requirements

• Provide list of product sale on the last day of month

• List is provided from every store
• Capable of handling large inventory
• Capable of in and out transections
• Manage stock in and out list
• Show billing details
• System should give notification of low stock

4.1.3 Admin Module (Data management system)

The system allows admin to perform the following task.

• Add Products
• In & Out Transactions
• Add Supplier
• Add Dealer
• View Supplier/Dealer
• View Transactions
• Monthly Report
• View Stocks
• Billing of In/Out Transactions

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

4.1.4 Sales Manager Module (Counter system):

The system allows Sales Manager to perform the following task.

• In & Out Transactions

• View Stocks
• Payment assurance
• Check for discount
• Issue bills
• Reads Barcode for price detection
4.1.5 Warehouse Manager Module (warehouse management system)

The system allows Warehouse Manager to perform the following task.

• In & Out Transactions

• View Supplier/Dealer
• View Transactions
• Monthly Report
• View Stocks

4.1.6 Payment module (billing system)

• Communication with banks

• Transaction
• Generate bills

4.1.7 Customer module (customer management system)

• Add customer
• Register as verified/permanent
• Check customer
• Keep track of purchase
• Send data

5. Other Non-functional Requirements

5.1 Performance Requirements

WHMS is a real time web based system. The system shall be able to response the user initiated actions
in a real time environment. The change of view state of an action should not take longer than 5 second.

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

5.2 Safety Requirements

The system must be able to secure the data of all the branches ,in case of any un-conditional
environment like fire, earth quake etc. there should be a backup and disaster in order to get back the
system’s data.

5.3 Security Requirements

The WHMS will be available only to the authorized users. It should be only interact with the HBL’s system
as an external.
5.4 Software Quality Attributes

5.4.1 Usability

WHMS must be very easy to use. Infrequent user must be able to use this system with a little bit training or
by reading helping manual.

5.4.2 Portability

WHMS will be able to use all versions of the windows operating system.

5.4.3 Reliability

There should be no space for error, if user make some mistake then there a catch and throw to handle
the errors. It should be able to continue to perform all others actions if one modules affected.

5.4.4 Interoperability

WHMS will be able to interact HBL’s system for payment modules. WHMS maintain all the payment
transactions via interacting with HBL’s system.

5.4.5 Flexibility

WHMS will be able to add new franchise if admin wishes to open a new branch in a city. WHMS will
also be responsible to maintain the newly opened franchise.

5.4.6 Maintainability

WHMS will be easy to install, implement and maintainable. If some bugs arises then it should be easily
recoverable.

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

5.5 Business Rules

The discount to the customer will depends upon the regular customers and on the purchasing cost of the
items available in the system.

Appendix A

The given below is the system diagram of the Ware House Management System

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)

 lOMoARcPSD|39716354

Downloaded by Likhil Chandra (likhilchandra6@gmail.com)