Table of Contents

INTRODUCTION ..............................
.............................................................
...........................................................
1
1.1
PURPOSE .........................................................
............................................................................
.............................................................. 1
1.2
SCOPE ..............................................................
............................................................................
.............................................................. 1
1.3
DEFINITIONS, ACRONYMS, AND
ABBREVIATIONS ...........................................
............................................................................
1
1.4
REFERENCES ..................................................
............................................................................
.............................................................. 2
1.5
OVERVIEW.......................................................
............................................................................
............................................................. 2
2.
GENERAL DESCRIPTION
.............................................................
.............................................................
......... 2
2.1
SOFTWARE PERSPECTIVE
............................................................................
............................................................................
........ 2
2.2
SOFTWARE FUNCTIONS
............................................................................
............................................................................
........... 2
2.3
ASSUMPTIONS AND DEPENDENCIES
............................................................................
..................................................................... 3
3.
SPECIFIC REQUIREMENTS
.............................................................
.............................................................
..... 4
3.1
EXTERNAL INTERFACE REQUIREMENTS
............................................................................
............................................................. 4
3.1.1
User Interfaces
.............................................................
.............................................................
.................. 4
3.1.2
Hardware Interfaces
.............................................................
.............................................................
......... 4
3.1.3
Software Interfaces
.............................................................
.............................................................
........... 4
3.1.4
Communications Interfaces
.............................................................
............................................................
4
3.2
FUNCTIONAL REQUIREMENTS
............................................................................
............................................................................
.... 4
3.2.1
Customer Registration
.............................................................
.............................................................
...... 5
3.2.2
Product Management
.............................................................
.............................................................
........ 5
3.3
NON-FUNCTIONAL REQUIREMENTS
............................................................................
..................................................................... 5
3.3.1
Performance ........................................
.............................................................
........................................... 5
3.3.2
Reliability ...........................................
.............................................................
............................................ 6
3.3.3
Availability .........................................
.............................................................
............................................ 6
3.3.4
Security ...............................................
.............................................................
........................................... 6
3.3.5
Maintainability ....................................
.............................................................
........................................... 6
3.3.6
Portability ...........................................
.............................................................
........................................... 6
3.4
DESIGN CONSTRAINTS
............................................................................
............................................................................
................. 7
3.5
OTHER REQUIREMENTS
............................................................................
............................................................................
............... 7

Software Requirements
Specification

Table of Contents
INTRODUCTION ..............................
.............................................................
...........................................................
1
1.1
PURPOSE .........................................................
............................................................................
.............................................................. 1
1.2
SCOPE ..............................................................
............................................................................
.............................................................. 1
1.3
DEFINITIONS, ACRONYMS, AND
ABBREVIATIONS ...........................................
............................................................................
1
1.4
REFERENCES ..................................................
............................................................................
.............................................................. 2
1.5
OVERVIEW.......................................................
............................................................................
............................................................. 2
2.
GENERAL DESCRIPTION
.............................................................
.............................................................
......... 2
2.1
SOFTWARE PERSPECTIVE
............................................................................
............................................................................
........ 2
2.2
SOFTWARE FUNCTIONS
............................................................................
............................................................................
........... 2
2.3
ASSUMPTIONS AND DEPENDENCIES
............................................................................
..................................................................... 3
3.
SPECIFIC REQUIREMENTS
.............................................................
.............................................................
..... 4
3.1
EXTERNAL INTERFACE REQUIREMENTS
............................................................................
............................................................. 4
3.1.1
User Interfaces
.............................................................
.............................................................
.................. 4
3.1.2
Hardware Interfaces
.............................................................
.............................................................
......... 4
3.1.3
Software Interfaces
.............................................................
.............................................................
........... 4
3.1.4
Communications Interfaces
.............................................................
............................................................
4
3.2
FUNCTIONAL REQUIREMENTS
............................................................................
............................................................................
.... 4
3.2.1
Customer Registration
.............................................................
.............................................................
...... 5
3.2.2
Product Management
.............................................................
.............................................................
........ 5
3.3
NON-FUNCTIONAL REQUIREMENTS
............................................................................
..................................................................... 5
3.3.1
Performance ........................................
.............................................................
........................................... 5
3.3.2
Reliability ...........................................
.............................................................
............................................ 6
3.3.3
Availability .........................................
.............................................................
............................................ 6
3.3.4
Security ...............................................
.............................................................
........................................... 6
3.3.5
Maintainability ....................................
.............................................................
........................................... 6
3.3.6
Portability ...........................................
.............................................................
........................................... 6
3.4
DESIGN CONSTRAINTS
............................................................................
............................................................................
................. 7
3.5
OTHER REQUIREMENTS
............................................................................
............................................................................
............... 7

SCHOOL OF TECHNOLOGY
BISF
SYSTEM REQUIREMENT SPECIFICATION
HOPEMART INVENTORY SYSTEM
MANAGEMENT
21/08155
NAME : CURTIS KIBANYA
SUPERVISOR : CLIVE ONSOMU

Table of Contents
INTRODUCTION.......................................................................................................................................... 1

1.1PURPOSE.................................................................................................................................................1

1.2SCOPE......................................................................................................................................................1

1.3 DEFINITIONS, ACRONYMS, AND

ABBREVIATIONS............................................................................................................................................2

1.4REFERENCES.............................................................................................................................................2

1.5OVERVIEW...............................................................................................................................................2

2. GENERAL DESCRIPTION ......................................................................................................................... 3

2.1SOFTWARE
PERSPECTIVE.................................................................................................................................................3

2.2 SOFTWARE
FUNCTIONS ....................................................................................................................................................
.................3 2.3 ASSUMPTIONS AND
DEPENDENCIES ...............................................................................................................................................
.......................4

3. SPECIFIC
REQUIREMENTS .............................................................................................................................................
........................ 4

3.1 EXTERNAL INTERFACE

REQUIREMENTS .............................................................................................................................................
.........................4
 3.1.1 User
Interfaces .......................................................................................................................................................
.............. 4

3.1.2 Hardware
Interfaces .......................................................................................................................................................
.............. 4

3.1.3 Software
Interfaces .......................................................................................................................................................
.............. 4

3.1.4 Communications
Interfaces .......................................................................................................................................................
.............. 5

3.2 FUNCTIONAL
REQUIREMENTS .............................................................................................................................................
.........................5

3.2.1 Customer
Registration ....................................................................................................................................................
................. 5

3.2.2 Product
Management ..................................................................................................................................................
................... 5

3.3 NON-FUNCTIONAL
REQUIREMENTS .............................................................................................................................................
.........................6

3.3.1
Performance ..................................................................................................................................................
................... 6

3.3.2
Reliability .......................................................................................................................................................
.............. 6

3.3.3
Availability ......................................................................................................................................................
............... 7

3.3.4
Security ..........................................................................................................................................................
........... 7
 3.3.5
Maintainability ...............................................................................................................................................
...................... 7

3.3.6
Portability .......................................................................................................................................................
.............. 7

3.4 DESIGN
CONSTRAINTS ................................................................................................................................................
......................7

3.5 OTHER REQUIREMENTS .........................................................................................................................8

1. Introduction
The inventory management system has become an important factor in the
modern business field.
This system should help businessmen to streamline administrative tasks and
provide real-time access to the data.
Building this system in a standalone application interface will further help the
ease of accessibility through the provided portal.
The study findings enable the definition of the project problem statement, its
objectives, scopes, and advantages of the inventory management system.

1.1 Purpose
The purpose of this document is to present a detailed description of the
Inventory Management System of Hopemart Supermarket.
It will explain the software's purpose and features, the software, the
interfaces of the software, what the software will do, the constraints under
which it must, operate, and how the software will react to external stimuli.
This document is intended for both the end users and the developers of the
software.

1.2 Scope
This document covers the requirements for the Inventory Management
System.
This software will provide a graphical environment in which the users of the
system will be able to perform various operations that are associated with
storing, marinating, updating, and retrieving Product information.
The purpose of this is to guide developers in selecting a design that will be
able to accommodate the full-scale application.
This system will capture information about customer’s personal details
products and quantities. Storing updating and retrieving in a fast and accurate
way.

1.3 Definitions, Acronyms, and Abbreviations

The Inventory Management System has to handle records for the number of
products and maintenance was difficult.
Though it used an information system, it was totally manual. Hence there is a
need to upgrade the system with a computer-based information system.
1.4 References
An Integrated Approach to Software Engineering Approach - Pankaj Jalote
Software Engineering A Practitioner’s Approach - Roger S Pressman

1.5 Overview
The purpose of this document is to present a detailed description of the
Inventory Management System.
It will explain the software's purpose and features, the software, the interface of
the software, what the software will do, the constraints under which it must
operate, and how the software will react to external stimuli.
This document is intended for both the end users and the developers of the
software.

2. General Description
2.1 Software Perspective
The product Inventory Management system is an independent product and does
not depend on any other product or system.
The product will automate various tasks associated with handling product details
and better organize the stored information and optimum performance, thus
helping the businesses to ensure the smooth working of these processes.
2.2 Software Functions
Our system has two types of accessing modes;

i)Administrator:
IMS is managed by the Administrator.
The administrator has to update and monitor the registered product details, add
a new product, provide product numbers for all products, assign each product
quantity and GST etc., Administrator can update his profile and also give help to
the customers.

ii) Customer:
Customers can purchase the products and make payments accordingly.
All his data will be saved into the database by the administrator to keep a record
of the sold products.

2.3 Assumptions and Dependencies

• We assume that the Office personnel do all the data entry based and the
correct values obtained from forms and registers.
• We assume that the computers that will use the software will be part of the
proper platform to run it.
• Users with administrator access should be careful in deleting or modifying any
information knowingly or unknowingly which will lead to inconsistency of the
database.
• The end users of this software are assumed to have a basic level of computer
knowledge i.e. point and click.
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
• GUI along with meaningful Frames and buttons
• Reports are generated as per the requirement

3.1.2 Hardware Interfaces Hardware Environment

Hardware environment Dual-core 2nd generation
System configuration RAM 8GB
Operating system Windows 10

3.1.3 Software Interfaces

Front end java
Back end MySQL 5.1.36

When invalid inputs are given to the modules then the error messages will be
popped up in order to inform the user that the input provided is not taken by the
database.
When incomplete information is provided by the user and the user tries to
submit the form in order to store the details in the database the system will pop
up a message box asking the user to enter all the details required.

3.1.4 Communications Interfaces

 The machine will have to be part of the college Local area Network to access the
central database.

3.2 Functional Requirements

Inventory Management System involves the following functions:

3.2.1 Customer Registration:

- IMS provides customer registration and status information to the administrator
to view their status.
- IMS provides automatic customer register number generation based on a
randomization algorithm. - IMS provides to customers to purchase products and
enlist them in their profile.

3.2.2 Product Management:

- Easily track product information (sold and available).
- Quickly produce reports for single or multiple sold products.

3.3 Non-Functional Requirements

3.3.1 Performance
Easy tracking of records and updating can be done.
All the requirements relating to the performance characteristics of the system
are specified in the section below.
There are two types of requirements:
A. Static Requirements
These requirements do not impose any constraints on the execution
characteristics of the system.
They are:
1) Number of Terminals
The software makes use of an underlying database that will reside in the same
system, while the front end will be available to the administrative computer.
2) Number of Users
The number of users can be administrator only, but this software can be
extended to applications for almost all staff members of the organization.

B. Dynamic Requirements
These specify constraints on the execution characteristics of the system.
They typically include response time and throughput of the system.
Since these factors are not applicable to the proposed software, it will suffice if
the response time is high and the transactions are carried out precisely and
quickly.

3.3.2 Reliability
The software will not be able to connect to the database in the event of the
server being down due to a hardware or software failure.

3.3.3 Availability
The software will be available only to the administrator of the organization and
the product as well as customer details will be recorded by him.
He can add customers, update and delete them as well as add new products and
manage them.

3.3.4 Security
The security requirements deal with the primary security.
The software should be handled only by the administrator and authorized users.
Only the administrator has the right to create new accounts and generate
inventory.
Only authorized users can access the system with the username and password of
the administrator.

3.3.5 Maintainability
Backups for the database are available.

3.3.6 Portability
The Software is a web-based application and is built in JAVA and SQL so it is
platform-independent and independent of the operating system.

3.4 Design Constraints

This software provides security.
The login form prevents the system from being misused by unauthorized users.
Only an authorized operator will be granted rights to modify as per requirements.
This software is also reliable and fault-tolerant.
The system developed is designed to handle invalid inputs.
Since reliability is a major area of concern the system has a backup to avoid data
loss.
The user should know the programming language very well that is used to
develop software.

3.5 Other Requirements Database

All the data will be stored in a relational database.
Software Requirements
Specification

Table of Contents
INTRODUCTION ..............................
.............................................................
...........................................................
1
1.1
PURPOSE .........................................................
............................................................................
.............................................................. 1
1.2
SCOPE ..............................................................
............................................................................
.............................................................. 1
1.3
DEFINITIONS, ACRONYMS, AND
ABBREVIATIONS ...........................................
............................................................................
1
1.4
REFERENCES ..................................................
............................................................................
.............................................................. 2
1.5
OVERVIEW.......................................................
............................................................................
............................................................. 2
2.
GENERAL DESCRIPTION
.............................................................
.............................................................
......... 2
2.1
SOFTWARE PERSPECTIVE
............................................................................
............................................................................
........ 2
2.2
SOFTWARE FUNCTIONS
............................................................................
............................................................................
........... 2
2.3
ASSUMPTIONS AND DEPENDENCIES
............................................................................
..................................................................... 3
3.
SPECIFIC REQUIREMENTS
.............................................................
.............................................................
..... 4
3.1
EXTERNAL INTERFACE REQUIREMENTS
............................................................................
............................................................. 4
3.1.1
User Interfaces
.............................................................
.............................................................
.................. 4
3.1.2
Hardware Interfaces
.............................................................
.............................................................
......... 4
3.1.3
Software Interfaces
.............................................................
.............................................................
........... 4
3.1.4
Communications Interfaces
.............................................................
............................................................
4
3.2
FUNCTIONAL REQUIREMENTS
............................................................................
............................................................................
.... 4
3.2.1
Customer Registration
.............................................................
.............................................................
...... 5
3.2.2
Product Management
.............................................................
.............................................................
........ 5
3.3
NON-FUNCTIONAL REQUIREMENTS
............................................................................
..................................................................... 5
3.3.1
Performance ........................................
.............................................................
........................................... 5
3.3.2
Reliability ...........................................
.............................................................
............................................ 6
3.3.3
Availability .........................................
.............................................................
............................................ 6
3.3.4
Security ...............................................
.............................................................
........................................... 6
3.3.5
Maintainability ....................................
.............................................................
........................................... 6
3.3.6
Portability ...........................................
.............................................................
........................................... 6
3.4
DESIGN CONSTRAINTS
............................................................................
............................................................................
................. 7
3.5
OTHER REQUIREMENTS
............................................................................
............................................................................
...............