Software Eng Practical

Software Requirements Specification
for
Retail Management System
Prepared by
Mainak Ghosh (91/MCA/170003)
Sudipta Sen (91/MCA/170006)
Joybrata Pal (91/MCA/170007)

Table of Contents
1. Introduction 2
1.1 Purpose1
1.2 Product Scope 1
2. Overall Description 3-4
2.1 Product Perspective 3
2.2 Product Functions 3-4
2.3 User Classes and Characteristics 4
2.4 Assumptions and Dependencies 4
3. Other Nonfunctional Requirements 5-6
3.1 Performance Requirements 5
3.2 Software Quality Attributes 5-6
1
1. Introduction
1.1 Purpose:
Retail is the sale of goods and services from people or organizations to the end-user.
Retailers are part of the supply chain of this system. They purchase goods in enormous
quantities and sell them to the consumer.
Retail software is used by all small, medium and large enterprises. The main
purposes of using a software is to regulate pricing, calculate taxes, inventory
management and manage POS, billing and payroll.
1.2 Product Scope:
Retail Inventory Management helps to manage different aspects of the retailer’s

supply chain. CRM(Customer Relationship Management) to retain customers and
maintain specific details about customers such as customer’s name, address, what they
purchase recently and what items they purchase regularly etc. Retail accounting for
inventory control, transaction monitoring and pricing. Order Management to keep track
of orders being made. Retail billing management to optimize store performance and
increase productivity
Retail software works wonders for our business. Here are the benefits of having
retail management software installed for your business:
1. Generating reports is easy. The best advantage in the retail billing software is
that you can view the whole history of your business transactions in a single
report itself.
2. Automation is a great experience. Your data is updated from time to time. In this
process, you are reminded of out of stock items and even given information
about the stock of items that aren’t selling and also provide information about
expired products.
3. Decision making gets easier. We can do better planning with all the information
that you get from the inventory/items data that you have.
4. Customer relationship gets better. It will help to retain customers.
2
2. Overall Description
2.1 Product Perspective:
There are two ways to manage business.

Previously we used to manage information entirely "old school" by using pens
and paper.It's still possible to operate a business without a computer, but it would have
to be a very small business and the need of physically counting it periodically at regular
intervals, and then reconciling again with the figures shown on the record after
accounted for incoming orders and outgoing sales makes it more harder and error
prone.
Another way to do that is by computerizing your inventory system. You can use
the computer just to speed record keeping or go to a full-blown, real-time inventory
system, depending on your needs, but either way, you'll benefit from having it
computerized.
2.2 Product Functions:
❏ Automated Reordering and In-Stock Information
Computerized inventory informs employees and customers within seconds

whether an item is in stock. Because the inventory is synced with sales, there is a
running tally of what is in stock and what isn't. This helps flag reordering needs and
provides better service to customers. As inventory drops below a specific threshold,
new orders are placed with vendors and tracked to let customers know when the new
products will arrive.
❏ Accounting
Financial statements are more easily generated with shared data between
inventory and bookkeeping.
3
❏ Forecasting and Planning
Inventory management software does more than track where inventory is located
and when to reorder it. A data collection system is used to create needed forecasting
and strategic planning reports. Business owners review trends regarding which
products do well in certain months or during specific cyclical seasons. Business owners
use this data to plan for growth and order inventory intelligently to best utilize cash flow
resources.
2.3 User Classes and Characteristics:

There are basically three types of users in our system:
1) Accountant: This user is responsible for billing of the item purchased by any
customer and check bills of the items purchased for business.
2) Stock Manager: This user is responsible for inserting newly purchased items into
the database and removing items manually from database if needed.
Store Manager: This user is the super user of the system. This user has total access to
the system.
2.4 Assumptions and Dependencies:

1) Customer, supplier, staff and store manager are the external entity for retail
management business.
2) There will be a staff who will help customers to find the right product and
generate the bill and take the payment from customers and also helps the new
customer in registration.
3) We will have only one supplier who will supply our required products for the
business.
4) Manager will supervise all business related work.
5) A monthly report is generated automatically which will help the manager in
decision making for business growth.
6) We assume that the expenses in these business are - cost of products for
business and monthly wages to staff.
7) Whenever the quantity of a particular item will be below the threshold level, it will
automatically generate report for manager.
4
3. Other Nonfunctional Requirements
erformance Requirements
3.1 P
❏ The system must not lag, because the workers using it don‟t have down-time to
wait for it to complete an action.
❏ The system must complete updating the databases, adding new vendors and
payments relating to customer or vendor successfully every time the user
requests such a process.
❏ All the functions of the system must be available to the user every time the
system is turned on.
❏ The calculations performed by the system must comply according to the norms
set by the user and should not vary unless explicitly changed by the user.
3.2 Software Quality Attributes
3.2.1 Usability
❏ The system must be easy to use by both managers and billing counter stuff such
that they do not need to read an extensive amount of manuals.
❏ The system must be quickly accessible by both managers and billing counter
stuff.
❏ The system must be intuitive and simple in the way it displays all relevant data
and relationships.
❏ The menus of the system must be easily navigable by users with buttons that are
easy to understand.
3.2.2 Reliability
❏ The System must give accurate inventory status to the user continuously. Any
inaccuracies are taken care of by the regular confirming of the actual levels with
the levels displayed in the system.
5
❏ The System must successfully add any customer, product and supplier given by
the user and provide estimations and inventory status in relevance with the newly
updated entities.
❏ The system must provide a password enabled login to the user to avoid any
foreign entity changing the data in the system.
❏ The system should provide the user updates on completion of requested
processes and if the requested processes fail, it should provide the user the
reason for the failure.
❏ The system should not update the data in any database for any failed processes.
3.3.3 Supportability
❏ The software is designed such that it works even on systems having the
minimum configuration.
❏ The system is adaptable even if additional plugins or modules are added at a
later point.
❏ The data can be exported to the manager so as to make the system more
portable.

Software Eng Practical

Uploaded by

Copyright:

Available Formats

Software Eng Practical

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Eng Practical

Uploaded by

Copyright:

Available Formats

Software Requirements Specification

Retail Management System

Mainak Ghosh​ (91/MCA/170003)

Sudipta Sen ​(91/MCA/170006)

Joybrata Pal ​(91/MCA/170007)

1.2 Product Scope 1

2. Overall Description 3-4

2.1 Product Perspective​ 3

2.2 Product Functions ​3-4

2.3​ ​User Classes and Characteristics​ ​4

2.4​ ​Assumptions and Dependencies​ ​4

3. Other Nonfunctional Requirements​ ​5-6

3.1 Performance Requirements 5

3.2 Software Quality Attributes 5-6

1.2 Product Scope​:

Retail Inventory Management helps to manage different aspects of the retailer’s

There are two ways to manage business.

2.2​ Product Functions:

❏ Automated Reordering and In-Stock Information

Computerized inventory informs employees and customers within seconds

2.3​ User Classes and Characteristics:

2.4​ Assumptions and Dependencies:

3.2​ Software Quality Attributes

You might also like

Mainak Ghosh (91/MCA/170003)

Sudipta Sen (91/MCA/170006)

Joybrata Pal (91/MCA/170007)

2.1 Product Perspective 3

2.2 Product Functions 3-4

2.3 User Classes and Characteristics 4

2.4 Assumptions and Dependencies 4

3. Other Nonfunctional Requirements 5-6

1.2 Product Scope:

2.2 Product Functions:

2.3 User Classes and Characteristics:

2.4 Assumptions and Dependencies:

3.2 Software Quality Attributes