Software engineering — Trial use standard for software non-functional sizing measurements (ISO/IEC/IEEE 32430:2021)
This standard defines a method for the sizing of non-functional software requirements. It complements ISO/ IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR).1This standard also describes the complementarity of functional and non-functional sizes, so that sizing bothfunctional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size,together with functional size, should be used for measuring the performance of software projects, settingbenchmarks, and estimating the cost and duration of software projects.In general, there are many types of non-functional software requirements. Moreover, non-functional aspectsevolve over time and may include additional aspects in the as technology advances. This standard does notintend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standardfor the definition of NFR. It is assumed that users will size the NFR based on the definitions they use.This standard covers a subset of non-functional types. It is expected that, with time, the state of the art canimprove and that potential future versions of this standard can define an extended coverage. The ultimategoal is a version that, together with ISO/ IEC 20926:2009, covers every aspect that may be required of anyprospective piece of software, including aspects such as process and project directives that are hard orimpossible to trace to the software' s algorithm or data. The combination of functional and non-functional sizewould 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 standard.
View in