DEVELOPERS TEAM

BELMM<Project Name>
Supplementary Specification

Version <1.0>
BELMM Version: 1.0
Supplementary Specification Date: 03/02/2019
BELMM-002

Revision History
Date Version Description Author
03/02/2019 1.0 Se redacta los requerimientos funciones y Santiago Soria Luis Felipe
no funcionales del proyecto BELMM.
Benítez Vázquez Eduardo Javier

Confidential <Company Name>, 2024 Page 2

BELMM Version: 1.0
Supplementary Specification Date: 03/02/2019
BELMM-002

Table of Contents
1. Functionality 3
1.1 <Functional Requirement One> 3

2. Usability 3
2.1 <Usability Requirement One> 3

3. Reliability 3
3.1 <Reliability Requirement One> 3

4. Performance 3
4.1 <Performance Requirement One> 3

5. Supportability 3
5.1 <Supportability Requirement One> 3
Supplementary Specification
1. Functionality
[This section describes the functional requirements of the system for those requirements which are
expressed in the natural language style. For many applications, this may constitute the bulk of the SRS
Package and thought should be given to the organization of this section. This section is typically organized
by feature, but alternative organization methods, for example organization by user or organization by
subsystem, may also be appropriate. Functional requirements may include feature sets, capabilities, and
security.
Where application development tools, such as requirements tools, modeling tools, and so on, are employed
to capture the functionality, this section document will refer to the availability of that data, indicating the
location and name of the tool used to capture the data.]

1.1 <Functional Requirement One>

[The requirement description.]

2. Usability
[This section should include all of those requirements that affect usability. Examples follow:
 specify the required training time for a normal users and power users to become productive at
particular operations
 specify measurable task times for typical tasks, or
 specify requirements to conform to common usability standards, for example, IBM’s CUA standards or
Microsoft’s GUI standards]

2.1 <Usability Requirement One>

The requirement description.

3. Reliability
[Requirements for reliability of the system should be specified here. Suggestions are as follows:

Confidential <Company Name>, 2024 Page 3

BELMM Version: 1.0
Supplementary Specification Date: 03/02/2019
BELMM-002

 Availability – specify percentage of time available ( xx.xx%), hours of use, maintenance access,
degraded mode operations, and the like.
 Mean Time Between Failures (MTBF) – this is usually specified in hours but it could also be specified
in terms of days, months or years.
 Mean Time To Repair (MTTR) – how long is the system allowed to be out of operation after it has
failed?
 Accuracy – specify precision (resolution) and accuracy (by some known standard) that is required in
the systems output.
 Maximum bugs or defect rate – usually expressed in terms of bugs/KLOC (thousands of lines of code),
or bugs/function-point.
 Bugs or defect rate – categorized in terms of minor, significant, and critical bugs: the requirement(s)
must define what is meant by a “critical” bug; for example, complete loss of data or complete inability
to use certain parts of the functionality of the system.]

3.1 <Reliability Requirement One>

[The requirement description.]

4. Performance
[The performance characteristics of the system should be outlined in this section. Include specific response
times. Where applicable, reference related Use Cases by name.
 Response time for a transaction(average, maximum)
 Throughput (for example, transactions per second)
 Capacity (for example, the number of customers or transactions the system can accommodate)
 Degradation modes (what is the acceptable mode of operation when the system has been degraded in
some manner)
 Resource use: memory, disk, communications, and so forth]

4.1 <Performance Requirement One>

[The requirement description.]

5. Supportability
[This section indicates any requirements that will enhance the supportability or maintainability of the
system being built, including coding standards, naming conventions, class libraries, maintenance access,
maintenance utilities.]

5.1 <Supportability Requirement One>

[The requirement description.]

Confidential <Company Name>, 2024 Page 4