Software Requirements

Specification
for

“STOCK KEEPER FOR A SHOP”

Version 1.0 approved

Team:

ANJALI KUMARI 19BCE0092

SOURABH AGARWAL 19BCE2581

VINUKONDA SAI VAMSEEDHAR RAJU-

19BCE2120

Instructor: MANJULA R
Course: SOFTWARE ENGINEERING
Lab Section: L11+L12
Date:20/02/2022
Software Requirements Specification for Stock Management System Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
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
1.5 References ........................................................................................................................................ 1
2. Overall Description ..................................................................................................................1
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics...................................................................................................... 2
2.4 Operating Environment .................................................................................................................... 3
2.5 Design and Implementation Constraints .......................................................................................... 3
3. External Interface Requirements ...........................................................................................3
3.1 Hardware Interfaces ......................................................................................................................... 3
3.2 Software Interfaces .......................................................................................................................... 3
4. System Features .......................................................................................................................4
4.1 System Feature 1 .............................................................................................................................. 4
4.1.1 Description and Priority ..................................................................................................... 4
4.1.2 Stimulus/Response Sequences ............................................................................................ 4
4.1.3 Functional Requirements ................................................................................................... 4
5. Other Nonfunctional Requirements .......................................................................................5
5.1 Safety Requirements ........................................................................................................................ 5
5.2 Security Requirements ..................................................................................................................... 5
5.3 Business Rules ................................................................................................................................. 5
6. Project Planning and Scheduling ...........................................................................................8

Project Use Case Diagram… .................................................................................. 7

Project Timeline (Gantt chart)… ............................................................................ 9
Work Breakdown Structure ………………………………………………10………8
“STOCK KEEPER FOR A SHOP”

1. Introduction
1.1 Purpose
This document lists the requirement specifications for “STOCK KEEPER FOR A SHOP”. The
document is subject the change as the project progresses. The given version of the document is
the initial one. Further changes of the project will be recorded to the document.

1.2 Document Conventions

This document is created in Microsoft Word 2016 edition. The topics are written in Bold and in
Times New Roman font of size 14. The content following the topic is written in Arial Italic with font
size of 11. The key points and the topic are written in bold and the rest of the content is in normal
text format of Arial Italic. Also, the core hardware requirements are in bold to grab immediate
attention.

1.3 Intended Audience and Reading Suggestions

The intended audience for the project is small businesses and medium size enterprises suitable for
use in small villages, town. This application is also intended to target street vendors and small
shop holders. It has a simple Graphical user interfaces and is really easy to interact with. A person
with a minimal technical Knowledge about computers and programming can easily operate the
software.

1.4 Product Scope

The main objective of the process is to fully digitalize the stock keeping process of the shop. Along
with making the process fully digital, we intend to include some other features to the application so
that it helps the shopkeeper to maximize the profits.
In general, our objective is to include the following features on our application:
• Keep a record of stock in the shop
• Calculate profit or loss
• Notify the shop owner when any item has crossed its expiry date.
• Aware the shop owner if an item is being rapidly sold so that the owner can order more.
• Aware the owner if any item is going to be finished in the shop • keep record of the employee in
the shop
• Provide yearly review such as which item was sold more in which month.

1.5 References
[1] R. Elmasri & S. B. Navathe, Fundamentals of Database Systems, Addison Wesley, 7th Edition,
2015.
[2] Thomas Connolly, Carolyn Begg, Database Systems: A ‖ Practical Approach to Design,
Implementation and Management‖,6th Edition,2012.
[3]. Moskowitz,Robert, ”Using Your Computer for Inventory Control", Accvision Retrieved August
17, 2010.
[4] Lockard, Robert (29 November 2010) "3 Advantages of Using Inventory Management.
“STOCK KEEPER FOR A SHOP”

[5] ”Inventory Management Organism” by A Rohini, Wubshetasamnew Woldeyohannshiluf and

Teshometeklemicheal Walelignayimelo.

2. Overall Description
2.1 Product Perspective
Stock keeper for shop system is the digitalized version of the traditional manual stock entry and
management using pen and paper. Existing manual system requires tedious work and takes a lot
of time to record and organize the inventory. Apart from that, the physical record is a subject to a
lot of depreciation and danger and can get easily damaged by a lot of physical factors. Moreover,
they are not easily accessible. The new digitalized system aims to overcome the above-mentioned
drawbacks of the existing system. It will allow its user to digitally perform and store all the
information and data and make the data easily accessible. Furthermore, it will reduce the workload
of the employees of the shop and it makes the business more efficient. The system also allows the
customers to check the availability of a specific item that they want, its price, its availability and the
expiry date and any discounts (if available). Administrator can modify, remove existing stocks, and
also add new items to the store. Furthermore, administrator can see customer requests, trading
items, and decide whether to accept and reject them. The product is solely meant to provide a
convenient platform to the customer as well as the store owner to perform shopping in small shops.
However, in the process personal information of the user including name, contact, and nationality,
date of birth, address, profession and payment details may be asked.

2.2 Product Functions

The functionality of the app is mentioned below:

1. Stock Management: If you want to add a newly registered/bought item, just click the ‘Add
Stock’ tab and enter the necessary information about the item to be added into the inventory. You
can also check the information about the items (the Cost Price, Selling Price, etc ) added to the
inventory by using the ‘Search’ tab and also can check the expiry date of the product using the
‘Check Expiry’ tab.

2. Trending: Items One of the most useful and best feature of our software, ‘the trending products’
allows the user to find the information about the most sold and the least sold items in the shop. It
can be found out by clicking the ‘trending’ tab.

3. Billing: The billing can be done after a purchase of series of items by a customer in which the
user has to enter the credentials of the customer and list the items he/she have bought and their
quantities. The software will automatically create a bill and calculate the total amount.

2.2 User Classes and Characteristics

The intended users of this app will be people in the domain of small proprietary businesses or even
businessmen with inventory tracking needs. The average user is expected to use this app in a daily
manner. Users of the system should be able to retrieve stock information and the availability of any
product in the shop or the inventory and also change the metadata about the items whenever
necessary. The system will support two types of user privileges, Customer, and Employee.
“STOCK KEEPER FOR A SHOP”

Customers will have access to customer functions, and the employees will have access to both
customer and other administrative functions. The customer should be able to do the following
functions:
• View the products available
• Check the price
• Check the trending items
• Send an enquiry

2.3 Operating Environment

1. Operating System:
The Stock keeper for shop system is a GUI based application which will successfully operate on
the below mentioned Operating System:
1. Windows 7 with server pack 2 (or)
2. Windows 8.1 or higher (or)
3. Linux / MacOS

The hardware platform includes:

1. Processor: Intel Core Duo 2.0 GHz or more.
2. RAM: 1 GB or more.
3. Hard-disk: 50GB or more.
4. Monitor: 15” CRT, or LCD monitor.

2.4 Design and Implementation Constraints

We often see that the track of stocks is often kept manually or sometimes not kept in the smaller
shops with not such a skilled employee. So, looking at the scenario we have decided to create a
stock keeping software that can run on very low specifications and would be suitable for a smaller
shop and can be run very easily and virtually by anyone. It will help the shops to get insights on
their inventory and help for their betterment. We also plan to make the software as simple as
possible and will be implemented as a suitable graphical user-end interface which can be used to
navigate around the application very easily.

3. External Interface Requirements

3.1 Hardware Interfaces
• Processor: Intel Core Duo 2.0 GHz or more
• RAM: 1 GB or More
• Hard-disk: 50GB or more
• Monitor: 15” CRT, or LCD monitor
• Keyboard: Normal or Multimedia
• Mouse: Compatible mouse

3.2 Software Interfaces

1. Operating System:
“STOCK KEEPER FOR A SHOP”

 Windows 7 with server pack 2.

 Windows 8.1 or higher.
 Linux / MacOS.

2. Software/Modules:

 Anaconda.
 Python IDE.
 PyQT python module.
 DB Browser for SQlite2.

4. System Features
4.1 System Feature
4.1.1 Description and Priority
The system has the following features: -
 Login/Registration: Allows users to access their own personal interface. It
has high priority of 8 as it contains personal information like contact details.

 Product Catalogue: Contains all of the available items of the system. It has
highest priority of 10 as without it there would lose the main aim of this
application.

 Product Basket: Contains all the items that the customer wishes to purchase.
It has a relatively high priority with 7.

 Profit/Loss Generator: Allows traders to keep a record of their turnover being

generated for the products that are sold via application. This would attain the
rank of relatively high priority of 7 as the maintaining of the record can also
be done manually. The record done via the application make it efficient for
usage by the trader.

 Bio-Data/Personal Details: Has the information about the merchant in case

of inquiry and also about the customer info so as to send promotional or
marketing ads. It has a low priority of 3 as the program can function without it
just as well.

4.1.2 Stimulus/Response Sequences

 Search for a particular item, displays a detail list of all items with that id or name.
 When logging in the user inputs details and the system verifies the detail with the one
present in the database to take the user to the product catalogue.
 When customer adds item to basket, the system will include the new item in its
database for when the customer is about to checkout.
“STOCK KEEPER FOR A SHOP”

 When the traders select turnover section all the profits margins product wise must
appear and those that have be sold off.
 When the traders enter history section, a list of products that they have sold before
are displayed.

4.1.3 Functional Requirements

 REQ-1: Authentication, validation, authorization of a user with respect to his/her role
when he/she enters their credentials while logging into the system.
 REQ-2: Administrative functions, which allows the admin to access all information in
the system including user info, product details, etc.
 REQ-3: Audit tracking, allows the trader as well as admin to keep track of all sales
done through the system, to note any suspicious activities.
 REQ-4: Amount adjustments, payment confirmation to verify as well as ensure a safe
transaction by verifying password and correct payment details. Facilitation of the
returns and cancellations and safe guarding the payment details.
 REQ-5: Enabling the trader to remove stock off the shelf and modify the prices
according to the demand and consumption and also increase the products or
introduce new items to the catalogue.
 REQ-6: Detailed summary of the purchase receipt to be forwarded to the customer.

5. Other Nonfunctional Requirements

5.1 Safety Requirements
 Password trials for logging attempt should be not more than 5 consecutive unsuccessful
trials within a span of 5 hours (the time limit can be modified by the admin).
 Complete security and invisibility of the payment details of the customer except from the
admin to avoid compromise of data or leave no room to any form of data attacks.
High/Military grade like level encryption features may or may not be required nevertheless
basic hash function is incorporated.

5.2 Security Requirements

 User and trader account details heavily secured by proper storage.
 Prevention of other monitoring apps when logging in for safety of credentials.

5.3 Business Rules

 Admin being the head has the full and complete legal authority over the distribution of sales
and enrollment of new traders or customers subject to certain rules.
 Traders have rules related to the customer service and products and their sales. They have
complete autonomy with respect to the sales, restocking or withdrawal of products with
conditions.
 Customers have the freedom and authority to choose cancel or claim a refund post
verification if it is a genuine claim and accordingly settle.
“STOCK KEEPER FOR A SHOP”

 Final rules are set by the Government heading the state or state head/ruler/judge who take a
call or approve the method of operation by assenting to the operation in the form of granting
economic licenses.
“STOCK KEEPER FOR A SHOP”

6.

6.1 USE CASE DIAGRAM:

“STOCK KEEPER FOR A SHOP”
“STOCK KEEPER FOR A SHOP”

6.2
Project Planning and scheduling:

Timeline of project

6.3 Gantt chart format:

“STOCK KEEPER FOR A SHOP”

6.4 Work Breakdown Structure: