scope:

This document defines a method for measuring the non-functional size of the software. It complements ISO/IEC 20926:2009, which defines a method for measuring the functional size of the software.

This document also describes the complementarity of functional and non-functional sizes, so that sizing both the functional and non-functional requirements for software do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects.

In general, there are many types of non-functional requirements. Moreover, non-functional requirements and its classification evolve over time as the technology advances. This document does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users size the NFR based on the definitions they use.

This document covers a subset of non-functional requirements. It is expected that, with time, the state of the art can improve and that potential future versions of this document can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspects that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional sizes would then correspond to the total size necessary to bring the software into existence.

Calculating the effort and duration of the implementation of the NFR is outside the scope of this document.

Purpose

The purpose of this document is to define a method for measuring the non-functional size of the software.