Requirements specification for

Inventory control system

Project: Information control system
inventory management

April 2019
 Inventory Control Information System
Page 2
System Requirements Specification

Document card

Date Review Author Quality department verified.

Calcina Ticlla Luis Fernando
Del Carpio Berrio Daniel
04/04/2019
Paco Polosi Cesar Edu
Torres Silva Luis

Document validated by the parties on date:

For the community For the university

Professional School of Systems Engineering Catholic University of Santa María

 Inventory Control Information System
Page 3
System Requirements Specification

Content
DOCUMENT PROFILE 2

CONTENT 3

1 INTRODUCTION 5

1.1 Purpose 5

1.2 Scope 5

1.3 Involved personnel 5

1.4 Definitions, acronyms, and abbreviations 6

1.5 References 6

1.6 Resumen 6

2 GENERAL DESCRIPTION 6

2.1 Product perspective 6

2.2 Product functionality 7

2.3 User characteristics 8

2.4 Restrictions 8

2.5 Assumptions and dependencies 8

3 SPECIFIC REQUIREMENTS 8

3.1 Common requirements of interfaces 11

3.1.1 Interfaces of user 11
3.1.2 Interfaces of hardware 11
3.1.3 Interfaces of the software 11
3.1.4 Interfaces of communication 11

3.2 Functional requirements 11

3.2.1 Requirement functional 1 11
3.2.2 Requirement functional 2 11
3.2.3 Requirement functional 3 11
3.2.4 Requirement functional 4 12
3.2.5 Requirement functionality 5 12
3.2.6 Requirement functional 6 12
3.2.7 Requirement functional 7 12
3.2.8 Requirement functional 8 12

3.3 Non-functional requirements 12

 Inventory Control Information System
Page 4
System requirements specification

3.3.1 Usage 12
3.3.2 Failures 12
3.3.3 Availability 12
3.3.4 Update 12
 Inventory Control Information System
Page 5
Especificación de requisitos del sistema

1 Introduction
This document is a Requirements Specification for the control system
inventories. This specification has been structured based on the guidelines provided by the
IEEE standard.

1.1 Purpose
The purpose of this document is to create an information system for the
control and management of inventory for a bookstore, specifying the requirements
functional and non-functional requirements that the system will have for its proper development.

1.2 Alcance
The collected requirements will be sent to the bookstore managers for their
verification of the functionalities that the system will have and also to delve into some
additional requirements that the system will have.

1.3 Involved personnel

Name Calcina Ticlla Luis Fernando
Role Perform technical analysis
Professional Category Ing. Systems
Responsibility Check project quality
Contact information7655791@[Link]

Name Del Carpio Berrios Daniel

Role Give functions to the staff.
Professional Category Ing. Systems
Responsibility Verify project quality
Contact information72638991@[Link]

Name Paco Polosi Cesar Edu

Roll user interviews
Professional Category Ing. Systems
Responsibility Verify project quality
Contact information76440927@[Link]

Name Torres Silva Luis

Role interview with the users
Professional Category Ing. Systems
Responsibility Verify project quality
Contact information74021002@[Link]
 Inventory Control Information System
Page 6
System requirements specification

1.4 Definiciones, acrónimos y abreviaturas

Name Description
e
SICInventory Control Information System
SO Operating System
Functional Requirement
Non-Functional Requirement

1.5 References

Title of the Reference

Document
Standard IEEE IEEE
830 - 1998
Book Systems Analysis and Design Kenneth E. Kendall eighth edition
Analysis of htps://[Link]/i2t/driso/process/proceso_desarrollo_sw/[Link]/procesos-
Requerimientos of development/ra
SWEBOK Knowledge Management Software Engineering Guide

1.6 Resumen
The document consists of 3 parts, the first part consists of the Introduction where it will be given
un pequeño resumen del sistema.

The second part consists of the general description of the system where we will be able to know
the main functions that will be carried out, as well as the characteristics and restrictions that
we will have in the system.

The third part consists of the specific system requirements where the following will be addressed.
functional and non-functional requirements.

2 General description

2.1 Product Perspective

The SICI system will be a product designed for Windows OS, which is the most
used for the users to whom it is addressed.
 Inventory Control Information System
Page 7
System Requirements Specification

2.2 Product functionality

Scheduling
 Inventory Control Information System
Page 8
System Requirements Specification

Gantt charts
 Sistema de información de control de inventarios
Page 9
System Requirements Specification

Use case

Sequence diagram

Class diagram
 Inventory Control Information System
Page 10
System Requirements Specification

Activity diagram
 Inventory Control Information System
Page 11
System requirements specification

State diagram
 Inventory control information system
Page 12
System Requirements Specification

WIREFRAME
 Inventory control information system
Page 13
System requirements specification

Deployment diagram:
 Inventory control information system
Page 14
System requirements specification

Output design (reports):

Inventory control information system
Page 15
System Requirements Specification
 Inventory Control Information System
Page 16
System requirements specification

2.3 User Characteristics

User type Administrator
Training NA
Activities Control and management of the system in general

User type User

Training NA
Activities Management of the data of your products and suppliers.

2.4 Restrictions
The system must be connected to the internet.
The system must be secure for users.
There should not be two users with the same name.
.

2.5 Assumptions and dependencies

It is assumed that the machines where the system will be installed will have Windows OS.
The devices must be connected to the internet at the time of execution.
system.
The devices on which the system will be executed must meet the requirements.
previously indicated to ensure its correct execution

3 Specific Requirements
Functional Requirements

Identification of RF01
requirement:
Name of the Validate the user.
Requirement:
Characteristics: Users must identify themselves with their email address and
 Inventory control information system
Page 17
System Requirements Specification

password
Description of The system can be consulted by any user depending on the
requirement: module in which it is found and its level of accessibility.
Priority of the requirement:
High

Identification of the RF02

requirement:
Name of the Provide information about the Box.
Requirement:
Characteristics: Money input and return depending on the situation.
Description of The system will allow us to enter certain amounts of money that
requirement: it will represent the real money that the seller has.
Priority of the requirement:
High

Identification of RF03
requirement:
Name of the Enter Distributors.
Requirement:
Features: Entry of data from the distributors.
Description of the The data of the distributors that the company has will be entered.
requirement: such as: name, phone, address, email. As well as the
deletion and updating of data.
Priority of the requirement:
High

Identification of RF04
requirement:
Name of the Enter products
Requirement:
Characteristics: Ingreso de datos de los productos.
Description of entry of data for purchased products such as the description,
requirement: categoría, marca, precio de costo, stock actual y límite de stock.
Priority of the requirement:
High

Identification of the RF05

requirement:
Name of the Alert the user
Requirement:
Characteristics: Minimum stock alert.
Description of the system will send an alert message when the stock of a product
requirement: reached the minimum.
Priority of the requirement:
High

Identification of RF06
requirement:
Name of the To sell
Requirement:
Characteristics: The system will allow the sale of products and will increase the money.
stored in the box.
 Inventory control information system
Page 18
System requirements specification

Description of Allows the user to record the sales and earnings made by each
requirement: purchase of the products.
Priority of the requirement:
High

Identification of the RF07

requirement:
Name of the Generate Reports.
Requirement:
Characteristics: The system will allow us to generate reports that inform us about products.
best sellers in a given time.
Description of Allows the user to request reports of their products.
requirement:
Priority of the requirement:
High

Identification of the RF08

requirement:
Name of Buy
Requirement:
Characteristics: It allows to deduct money from the cash register when making payment for a purchase.
of products to their distributors.
Description of It will allow the user to access the cash register and be able to deduct the money from the
requirement: payment to the distributors.
Priority of the requirement:
High

Non-Functional Requirements.

Identification of the RNF01

requirement:
Name of the Use.
Requirement:
Characteristics: Easy to use for the user.
Description of Its use is not difficult to learn as it contains a guide detailing the
requirement: system steps.
Priority of the requirement:
High

Identification of RNF02
requirement:
Name of the Faults.
Requirement:
Characteristics: It will have a very low failure rate.
Description of The failure rate of the system must not be greater than 0.5% of
requirement: total operating time.
Priority of the requirement:
High

Identification of RNF03
requirement:
Name of the Disponibilidad.
 Inventory Control Information System
Page 19
System Requirements Specification

Requirement:
Characteristics: The system must be available 99.99% of the time to the user.
Description of The system must be fully available so that the user does not
requirement: I have difficulties every time I try to log in.
Priority of the requirement:
High

Identification of RNF04
requirement:
Name of Update.
Requirement:
Characteristics: The system will be constantly updated.
Description of The data that the system manages will be updated each time the
requirement: users modify the information.
Priority of the requirement:
High

3.1 Common interface requirements

.
3.1.1 User interfaces

The interface with users will consist of an advantage where they will be able to enter their
data and log into the system, where they will be able to access their respective products in their
inventory, the box and the ability to update the product information and also of the
users.

3.1.2 Hardware interfaces

It will be essential to have equipment in good condition that meets the requirements already.
established.

3.1.3 Software interfaces

Operating System: Windows 7 or higher.

3.1.4 Communication interfaces

The teams where the system will be installed must communicate with each other, and
update with each modification of information.

3.2 Functional requirements

3.2.1 Functional requirement 1

Validate the user: Users must identify themselves with their email.
email and password
 Inventory control information system
Page 20
System Requirements Specification

The system can be accessed by any user depending on

of the module in which you are and its level of accessibility.

3.2.2 Functional requirement 2

Report cash data: Income and money return depending

of the situation.

The system will allow us to enter certain amounts of money that

It will represent the real money that the seller has.
3.2.3 Functional requirement 3

Enter Distributors: The distributor data will be entered

that the company has: name, phone, address, email. As well as
also the deletion and update of the data.

3.2.4 Functional requirement 4

Enter products: input of the data of the acquired products

como la descripción, categoría, marca, precio de costo, stock actual y límite
in stock.

3.2.5 Functional requirement 5

Alert the user: the system will send an alert message when the
the stock of a product has reached the minimum.

3.2.6 Functional requirement 6

Seller:Allows the user to record the sales and profits made by

each purchase of the products.

3.2.7 Functional Requirement 7

Reports: The system will allow us to generate reports that inform us about
best-selling products in a given time.

3.2.8 Functional requirement 8

Buying: It will allow the user to access the cash register and be able to deduct the money.
from the payment to the distributors.

3.3 Non-functional requirements

3.3.1 Use
 Inventory control information system
Page 21
System requirements specification

Its use is not difficult to learn as it contains a detailed guide.

steps of the system.

3.3.2 Failures

The failure rate of the system shall not be greater than 0.5% of
total operation time.

3.3.3 Availability

The system must be fully available so that the user does not...
I have difficulties every time I try to log in.

3.3.4 Update

The data that the system controls will be updated every time the
users modify the information.