{"id":398771,"date":"2024-10-20T04:38:32","date_gmt":"2024-10-20T04:38:32","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/ieee-2430-2019-2\/"},"modified":"2024-10-26T08:26:16","modified_gmt":"2024-10-26T08:26:16","slug":"ieee-2430-2019-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/ieee\/ieee-2430-2019-2\/","title":{"rendered":"IEEE 2430-2019"},"content":{"rendered":"
New IEEE Standard – Active. 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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
1<\/td>\n | IEEE Std 2430\u2122-2019 Front cover <\/td>\n<\/tr>\n | ||||||
2<\/td>\n | Title page <\/td>\n<\/tr>\n | ||||||
4<\/td>\n | Important Notices and Disclaimers Concerning IEEE Standards Documents <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | Participants <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | Contents <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1.\u2002Overview 1.1\u2002Scope 1.2\u2002Purpose <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1.3\u2002Word usage 2.\u2002Normative references <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3.\u2002Definitions, acronyms, and abbreviations 3.1\u2002Definitions <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3.2\u2002Abbreviations <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.\u2002Introductory Information 4.1\u2002Non-Functional Software Size Measurement (NFSSM) introduction <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.2\u2002Software-intensive system and software product 4.3\u2002Software domains 4.4\u2002The relations between non-functional requirements (NFR) definition and functional user requirements (FUR) <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 4.5\u2002Key features of the NFSSM <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 4.6\u2002Future evolution of NFR <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4.7\u2002Objectives and benefits <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.\u2002Non-functional size: Categories and sub-categories 5.1\u2002Category 1: Data operations <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.2\u2002Category 2: Interface design <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.3\u2002Category 3: Technical environment <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 5.4\u2002Category 4: Architecture <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 5.5\u2002Sizing code data <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 6.\u2002The sizing process <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 6.1\u2002The timing of the non-functional sizing 6.2\u2002Non-functional sizing and FSM <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 6.3\u2002Steps to determine the non-functional size <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 6.4\u2002Calculating the Non-functional size <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 7.\u2002Complementarity of the functional and the non-functional sizes <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 7.1\u2002Requirements involving functional and non-functional requirements <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 8.\u2002Use of non-functional software sizing 8.1\u2002Functional size and non-functional size 8.2\u2002Project management <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 8.3\u2002Performance management <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Annex\u00a0A (informative) NFSSM strengths <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Annex\u00a0B (informative) Bibliography <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Back cover <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements<\/b><\/p>\n |