软件工程.软件非功能尺寸测量的试用标准

[中文适用范围]： 定义了评估中要包含的 NFR 集。a) 范围：1) 由执行非功能性评估的目的决定。2) 定义一组分区。3) 确定哪些非功能性类别和子类别应包含在非功能性规模测量中，以测量软件产品开发和交付的 NFR 规模。4) 可能包含多个应用程序。b) 规模测量类型：1) 开发项目的规模测量包括软件产品开发和交付的所有 NFR。2) 应用程序安装基数的规模测量包括支持已安装应用程序的所有 NFR。授权许可使用仅限于：IEEE 标准委员会 BoG CAG SASB RAC。于 2019 年 10 月 28 日 15:50:29 UTC 从 IEEE Xplore 下载。有限制条件。 ISO/IEC/IEEE 32430:2021(E) IEEE Std 2430-2019 IEEE 软件非功能性规模测量试用标准 59 版权所有 © 2019 IEEE。保留所有权利。3) 评估增强项目包括开发和交付增强项目的所有 NFR。4) 评估维护项目包括选定范围内的所有 NFR。c) 以下提示有助于确定评估范围：1) 审查非功能性评估的目的，以帮助确定评估范围。2) 在确定衡量已安装应用程序群的非功能性规模的范围时，包括维护团队支持的所有非功能性类别，最终通过在每个应用程序的边界内进行分区来区分。 [外文原描述]： This document 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).1 This document also describes the complementarity of functional and non-functional sizes, so that sizing both functional 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, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard 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 will size the NFR based on the definitions they use. This document covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect 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 size 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 standard.