IEEE 2430-2019

IEEE 2430-2019 IEEE Approved Draft Standard for Software Nonfunctional Sizing Measurement

standard by IEEE, 09/11/2019

More details

Download

PDF AVAILABLE FORMATS IMMEDIATE DOWNLOAD
$42.68

$97.00

(price reduced by 56 %)

Full Description

Scope

The standard specifies the set of definitions, rules and steps for applying a nonfunctional size measurement method (based on SNAP - Software Nonfunctional Assessment Process

Purpose

Having both functional size and non-functional size provides a complete picture of software product development.The functional size is quantifiable and represents a good measure of the functional project/application size.Providing a quantifiable measure for the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends

Abstract

New IEEE Standard - Active.This standard defines a method for the sizing of nonfunctional software requirements. It complements ISO/IEC 20926:2009 which defines a method for the sizing of functional user requirements. The standard includes non-functional categories for data operations, interface design, technical environment, and architecture software. It includes steps to determine and calculate the non-functional size. It explains how to handle requirements involving both functional and non-functional requirements. It 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 non-functional size should correspond to the total size necessary to produce the software. This standard also describes the complementarity of the functional and the non-functional size, so that sizing both the functional and the non functional requirements do not overlap. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.

Contact us