1 Introduction

1.1 Overview

Online Inventory Management system provides efficiently manage the

flow of materials effectively utilize people and equipment, coordinate

internal activities and communicate with customers. If the client who

may not be familiar with the actual software engineering process, this

document contains complete definitions and technical information

regarding the software process, necessary to transform this document

into an actual piece of software and is instead targeted towards non-

software engineering subjects.

It contains all the technical requirements for the software,

including a full list of functional and non-functional requirements. This

documentation is intended to be used by the software developers in

order to create the actual software.

2 Specific Requirements

2.1 External Interface Requirements

2.1.1 User Interfaces

 User interface is one of the tools that used for accessing the

system. Interface in the ZelTags Motor Parts & Accessories has

distinctive uniqueness that the user can easily interact with the

system. The developers began the project with methodological

 research in order to obtain a concise understanding of the

system.

 ZelTags Motor Parts & Accessories has three levels of users. If the

user inputted incorrect information, an error message or the pop-

up message will be displayed to notify the user that the

information inputted is incorrect.

 ZelTags Motor Parts & Accessories has the following environment

of the system:

 Login Page provides the login form that contains a

Username and a Password fields.

 Dashboard Environment displays the Today’s Orders,

User Registration and Products.

 Point of Sales Environment where the user can select

item and contains temporary table of the selected item by

the customer. Also, clickable Checkout button for the

payment of the item to be purchased by the customer.

 Inventory Page contains clickable menu such as

Inventory Report, On Hand Stock, Damages, Sold Items

and Receive Items.

 Reports Environment displays the Sales Report, Stock in

and Returned Items.

  Home page is where the promoting of the products is

present.

2.1.1.1 System’s User Interfaces:

 A Login Form with a username and password to be entered in

order to access different screens based upon to the user.

 Option is on buttons by categories in a screen displaying

information.

 Menu in the screen displaying different buttons to be select.

 There is a screen for displaying information menu regarding what

options the user will select while doing entry for inventory (stock

out, stock in, damages, and returnees.)

1.2.1.2 Interface to Consumer

 The interface to the consumer is the way by which the consumer

provides the product input data and views the pricing result data.

1.2.1.3 Interface to System Administrator

 The interface to the system administrator provides an avenue for

the system administrator to supply Zeltags Motor Parts &

Accessories server management parameters and to view Zeltags

Motor Parts & Accessories server status updates.

2.1.2 Hardware Interfaces

  Network Cable

 UTP (Unshielded Twisted Pair) cable -To connect the

computer to networks.

 Computer Unit

 With a resolution of 1366 x 768 pixels

 With a processor speed of 2.20 GHz.

 With a processor, Intel (R) Pentium(R) CPU B960.

 With a 2.00 GB of RAM

 Router

 Used to forward the data through network

 Printer

 For records or reports printing

 Local Area Network

 For the internet connection

2.1.3 Software Interfaces

 The development of a successful software interface requires more

than creating screens that looks good. The developers worked

together to achieve the goal of creating a user-friendly

environment, intuitive interface which allows the user to accomplish

the task as easy as possible. They used efficient web design

principles to create a valuable web page that provides functionality

which is meaningful to the user and focuses on accomplishing the

 objectives of the system. Through the developer’s knowledge and

understanding the information architecture they were able to

develop a simple but well organized interface.

 Accessible in any windows OS.

2.1.4 Communications Protocols

 The system should be accessed over LAN or WAN. For Clients

to access application server the network should be running

TCP/IP protocol.

2.2 Software Product Features

 Register – The user must register once in order to get access to the

application;after registering, a unique user name and password will be

provided and will allow the logging in of the registered user.

 Log-in – A registered user has to enter his/her unique user

name/passwordcombination in order access the application.

• Manage – An option allowing the user to modify the settings for the

system.

 Easily Import and Export Data - We believe that we should be able

to export all of our data any time we like, and we don't keep our

information in any proprietary format that we can't use or understand.

We can format them into our table format, and upload them. And if we

ever decide to stop we can just export the data.

 Easily Search and Filter Data - One of the primary jobs of our system is

to make it easier to find our stuff, not harder. So all of our views come

with search and filter boxes for each data column. This makes it dirt

simple for someone with very little knowledge of our products to find

things fast.

 Reliable and Accurate Report- The system offers a wide variety of

ways to examine records. We also have an accurate historical record of

all our transactions.

 Transactions - Transactions are at the heart of inventory management

and we make it easy to perform transaction by designing a simple UI for

transaction.

 Data Management - We used to make it easy to manage all of the data

tables now, we don't even have to. New Item ID's, item and moreare

created on the fly - quickly and easily.

 Data Storage – using MySQL as Database, it is more reliable. The server

must always active;all the functions of the system must be available to the

user every time the system is turned on to be able to save and update the

system.
2.3 Software System Attributes

2.3.1 Reliability

 The system exhibit infrequent failures so system is reliable. Also,

the system is being tested before deploying to ensure the

reliability of the system.

 The system provides a password enabled login to the user to

avoid any foreign entity changing the data in the system.

 The system provides the user updates on completion of

requested processes and if the requested processes fail, it should

provide the user the reason for the failure.

2.3.2 Availability

 The system is available with an internet connection.

 Minor updates or changes the system will adopt.

 The system is available if there’s a presence of:

 Internet connection

 The tools being installed and used by the developers in

order for the system to run successfully like XAMMP, Apache

and PHP.
2.3.3 Security

 In order for the system to be secure only authorized users will

be able to access the website by entering the correct login name

and corresponding password.The system valid users are the

Admin and the Cashier.

 The inputted password will be encrypted for the security

purposes.

2.3.4 Maintainability

 Even after deploying the system, the website can be maintained

in present or future. It can upgrade quickly and safely be

performed with a minimum of downtime.

 The product will be built using components that are as

independent as possible to make the system easily modifiable.

 All components of the system will be modular and be as

independent as possible.

 The researcher will be able to update the system with new

updates.

 The system must be stand alone.

2.3.5 Portability

 The systemis portable since it is online it has the ability :

  Ofthe software to be transferred from one machine or

system to another.

 To run into multiple operating systems.

 To update in real time.

2.3.6 Performance

 In every entry in transaction the system provides correct

calculation.

 The system must complete updating the databases, adding,

updating, deletion, and etc.

 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.

 2.4 Database Requirements

2.4.1 Database Requirements Table

Data Attributes Use

Product Input Data  Consumer Users Account This data is used to
 Product Name identify the product and
search for product pricing
data.
Pricing Result Data  Product Name The pricing result data is
 Store Name(s) used to inform the
 Price(s) consumer of competitors
 Price Type (Sale/Regular) and their prices for the
 Price Validation Date(s) consumer-specified
product.

Product Pricing Data  Product Name This data is stored on the

 Store Name(s) ZelTags Motor Parts &
 Price(s) Accessories server and
 Data Source used to generate the
pricing result data.
ZelTags Motor Parts &  Connection Timeout This data is used to
Accessories Server  Product Pricing Data configure the behavior of
Management Parameters Refresh Rate the ZelTags Motor Parts &
Accessories server.

ZelTags Motor Parts & To be specified in design. This data is used to inform
Accessories Server Status the system administrator of
Updates the ZelTags Motor Parts &
Accessories server status.
 2.4.2 Entity Relationship Diagram

 Entity Relationship Diagram Symbols:

SYMBOLS NAME

Entity

Attribute

Primary Key

Relationship

Unique Key

Foreign Key

has
users role

roleName
user_id
roleID
DOB
username
first_name

password
middle_name
cartQTY
email orderID
last_name productID
roleID
date_added
phone user_id
address cartAmount
cartID
gender
cart
 has
total_orderQTY user_id orderID

orders has

date_ordered total_orderAmount
status

invoiceID
has po_sales

invoiceID posID salesID

date_paid
pos_detail totalposQTY
cashier
invoiceID invoiceID orderID
cash
invoiceID
has totalAmount
category

categoryName
categoryID
categoryDesc
brandID brandDesc

has brand
brandName

has
products supplier

productID supplierID
productQty contactNum
productName companyName
productDesc position
categoryID contactFname

date_added email
brandID contactLname

soldQTY address
supplierID
sellingPrice
imageLocation
3 ADDITIONAL MATERIAL

3.1 Definition of Terms:

 Protocol - a protocol is the special set of rules that end points in a

telecommunication connection use when they communicate. Protocols

specify interactions between the communicating entities.

 Interface - a system of interaction or communication between a

computer and another entity such as a printer, another computer,

a network, or a human user.

 TCP/IP - Transmission Control Protocol/Internet Protocol is a set of

rules (protocols) governing communications among all computers on

the Internet.

 LAN - Local Area Network is a network of connected devices that exist

within a specific location.

 WAN - Wide Area Network is a communications network that spans a

large geographic area such as across cities, states, or countries

 OS - Operating System is a software program that enables the computer

hardware to communicate and operate with the computer software.

3.2 Abbreviations

 OS - Operating System
  WAN - Wide Area Network

 LAN - Local Area Network

 TCP/IP - Transmission Control Protocol/Internet Protocol

 MySQL - Structured Query Language.

3.3 References

 Marvel Electronics and Home Entertainment - E-Store Project - Software

Requirements Specification (Version <4.0>)
 https://www.scribd.com/doc/84942401/Software-Requirements-
Specification
 https://www.slideshare.net/senthilasq/srs-documentation