Specification of Requirements according to

the IEEE 830 standard

IEEE Std. 830-1998
22 de octubre de 2008

Resume

This document presents, in Spanish, the Software Requirements Specification (ERS) format
according to the latest version of the IEEE 830 standard. According to IEEE, a good
Requirements Document, despite Unless you strictly follow the organization and format given
in the 830 standard, you must include, in one form or another, all the information presented in
that standard. The IEEE 830 standard is not free of defects or prejudices, and for this reason it
has been rightly criticized by multiple authors and from multiple points of view, even
questioning whether it is really a standard in the usual sense of the term in other engineering.
This document does not intend to pronounce itself in favor or against one or the other: it only
reproduces, with fundamentally educational purposes, how a Requirements Document would
be organized according to the IEEE 830 standard.
´INDEX 2

´Index
1. Introduction 3
1.1. Purpose ................................................................................................. 3
1.2. System Scope ......................................................................................... 3
1.3. Visión General del Documento .......................................................... 4

2. General Description 4
2.1. Perspectiva del Producto ....................................................................... 4
2.2. Funciones del Producto .....................................................................4
2.3. Caracter´ısticas de los Usuarios ............................................................ 5
2.4. Restricciones .......................................................................................... 5
2.5. Suposiciones y Dependencias ............................................................... 5
2.6. Requisitos Futuros .............................................................................6

3. Specific Requirements 6
3.1. Interfaces Externas................................................................................. 7
3.2. Funciones ............................................................................................... 7
3.3. Requisitos de Rendimiento.................................................................... 9
3.4. Restricciones de Diseño ....................................................................... 9
3.5. Atributos del Sistema ........................................................................9

4. Appendices 9
1 INTRODUCTION 3

1. Introduction
This document will present the main requirements specifications that
the system will contain, which has the purpose of managing
information of an urbanization, the general vision of the document is to
better define the use cases that will be had in the project.

1.1. Purpose
The purpose of the document is to adequately transmit the
different use cases that will be taken into consideration when
carrying out the project.

1.2 System Scope

The name that the system will have is (Urbanization Treasury).
The system will be able to manage the information of owners as well as the
payment of different services present in the urbanization.
On the other hand, the benefit of the system is to optimize the
search time of the owners and their payments.

1.3 Document Overview

The system will be made with a different number of objects, as well
as different methods with which the operations will be carried out
where the information will be stored..
2 GENERAL DESCRIPTION 4

2.General Description
The product will mainly be managed by a single person who Will
have control of carrying out all the activities that were
previously defined for the project.

2.1. Product Perspective

The system that will be carried out can be identified by being an
information administrator such as those that are shown in different
stores when paying for their products or in state institutions where
citizen information is kept.

2.2. Product Features

The system will save the information of all the inhabitants of the
urbanization, it will show their information in tables if in different
cases, it will be able to save in the database the information of the
different payments that are made, it will save the information
entered in databases data which is in the cloud.

2.3. User Characteristics

The users of the system do not need extensive knowledge before its use,
only a tutorial of the main functions that it can present.
 2 GENERAL DESCRIPTION 5

2.4. restrictions

The main restrictions that the program has in mind are:

• A limited number of owners.
• The programming language in which it is made is Java.
• It is necessary that you are connected to the internet to be able to use the
database where all the information is stored.
• The main security method is the verification of a password which only the
authorized user will be able to possess.
• The main database of the application is the MongoDB page
• The functionality of the system mainly depends on the menus that will be
displayed with the different options.

2.5. Assumptions and Dependencies

The system will run on devices such as computers, if this changes for
use on mobile devices, a change in the requirements and specifications
will be necessary, in the same way the program uses MongoDB as a
database, when seeing a change in this, it would be necessary to
implement new methods in the system, the program will run on the
windows operating system.

2.6. Future Requirements

In future updates it is expected that the system will be able to show the
amount of payments made by each specific owner or the value that is
missing to pay for the services, in the same way it is expected that the
system can be managed on mobile devices to improve its accessibility.
 3 SPECIFIC REQUIREMENTS 6

3.Specific Requirements

The system has a great diversity of requirements which will be transformed in

the implementation of different functions in the system, therefore each of the
requirements will be presented in detail below in order to facilitate its
implementation in the program in the future. In the same way, each requirement
will be found in its classification depending on how they affect the system and
its functionality.

3.1. External Interfaces

1)The system must present a main menu which has a number of three options to be
able to enter a submenu in each of these options.
2)The submenus will present their options in an orderly manner to be able to implement
their different options, as well as a name with easy to identify the purpose of said options
at the time the user enters.
3)In the options there will be different graphic tools with which to enter the necessary
information, as well as to be able to visualize it depending on the need.

3.2. functions

1)The system must be able to save the administrator's information: name, ID

number and password.

2)The system must verify that the information entered by the administrator is
real, specifically the ID.

3)The system allows a verification of the password to enter the other options.

4)The system will display the menu with the options with which you can observe
the income, modification, elimination of residents as well as the payment, as
well as an option in which you can observe the information saved in the
program.

5)The sub minuses will present us with the options described above with their
distinctive description.

6)The entry of the information of each newborn will be allowed to be able to

save it in databases.
 3 SPECIFIC REQUIREMENTS 7
7)The program will notify you if data is entered incorrectly or if there was a
problem uploading it to the system database.

8)In the delete option, the program allows us to search for each owner by their
identification number and eliminate their information from the database.

9)In the option to modify the system, it allows you to search for the information
of each resident and modify it by using their identification number.

10)These options are repeated with the payment information.

11)The last option of the main menu will allow us to view the information of the
residents as well as their payments in the different services that are given in the
urbanization.

3.3 Performance Requirements

1) The system is designed for only one person who is in charge so that they can use all the
options
.
2) In the system it is planned that an amount of 100 residents be entered with their
respective information.

3) The system will contain three thousand payments in total with their respective
information.

3.4. Design Constraints

1) The program will present simple menus with a minimal amount of

options.

2) The system will contain windows in which you can only enter
specific information with a specific data type.

3) The system will have data tables in which you can view the
information entered by residents such as payments.
 4 APPENDICES 8

3.5. System Attributes

1) The only user who will be able to use the system will have to enter his name and
password to unlock the different options of the program.
2) The program will implement comments when leaving the mouse over to help
understand the user.
3) The program can only be used on devices such as computers or laptops.

4.Appendices
1) The cost of the application is minimal because it is a small program that needs
few equipment.

2) The Java language allows us to perform all the functions that are necessary for
the program to fulfill all its functions.

3) The input format is not available at the moment.