A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Status
- Inactive-Reserved Standard
- PAR Approval
- 2017-03-23
- Superseded by
- 32430-2024
- Board Approval
- 2019-06-13
- History
-
- Published:
- 2019-10-16
- Inactivated Date:
- 2023-03-30
Working Group Details
- Society
- IEEE Computer Society
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Working Group
-
NSM-WG - Standard for Nonfunctional Sizing Measurements Working Group
- IEEE Program Manager
- Christy Bahn
Contact Christy Bahn - Working Group Chair
- Talmon Ben-Cnaan
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
No Active Projects
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
32430-2021
IEEE/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements
A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard. Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.
32430-2024
IEEE Approved Draft Software engineering - Software Non-Functional Sizing Measurement
The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method SNAP (Software Non-functional Assessment Process) and provides guideline and examples of how to use the size measurements in software projects.
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
No Superseded Standards
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards