IEEE 2430-2019 pdf free

IEEE 2430-2019 pdf free.IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements.
1.3 Word usage
The word shall indicates mandatory requirements strictly to be followed in order to conform to the standard
and from which no deviation is permitted (shall equals is required to).2’3
The word should indicates that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required (should equals is recommended that).
The word mar is used to indicate a course of action permissible within the limits of the standard (may equals is permitted to).
The word can is used for statements of possibility and capability, whether material, physical. or causal (can equals is able to).
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this document is explained). For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies.
ISO/IEC 14143-1:2007, Information Technology—Software measurement—Functional size measurement.4’
ISO/IEC 20926:2009, Software and systems engineering—Software rneasuremcnt—IFPUG functional size measurement method 2009.
ISO/IEC 25010:2011, Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—System and software quality models.
ISO/IEC TR 14143-5:2004 Information technology—Soflware rneasurcmcnt—-Functional size measurement—Part 5: Determination of functional domains for use with functional size measurement.
ISO/IEC/IEEE 24765:2017, Systems and software engineering—Vocabulary.
3. Definitions, acronyms, and abbreviations
3.1 Definitions
For the purposes of this document, the following terms and definitions apply. For terms not defined in this clause, consult ISO/IEC/IEEE 24765:2017 or the IEEE Siandwds Dictionary Online.
adaptive maintenance: Modification of a software product, performed after delivery, to keep a software product usable in a changed or changing environment.
NOTE I – Adaptive maincnancc provides enhancements necessary to accommodate changcs in the environment in which a software product must operate. These changes are those that must be made to keep pace with the changing environment. For example. the operating system niightbe upgraded, and some changes may be made to accommodate the new operating system.’
NoTE 2— From ISO/IEC 14764:2006 ed 2.0. Copyright © 2006 IEC Geneva, Switzerland. www.icc.ch. [Btj.°
application: A cohesive collection of automated procedures and data supporting a business objective:
it consists of one or more components, modules, or subsystems. Examples: accounts payable, accounts receivable, payroll, procurement, shop production, assembly line control, air search radar, target tracking. weapons firing, flight line scheduling, and passenger reservations.
NOTE -From ISO/1EC 20926:2009 ed 2.0. Copyright 2009 IEC Geneva. Switzerland. www.iec.ch.
boundary (application boundary): A conceptual interface between the software under study and its users. The boundary (also referred to as application boundary) defines what is external to the application: it indicates the border between the software being measured and the user: it acts as a “membrane” through which data processed by transactions pass into and out of the application: it is dependent on the user’s external business view of the application: it is independent of non-functional and/or implementation considerations. The boundary is identical when assessing the functional size and the non-functional size.IEEE 2430 pdf download.