BS ISO IEC 25040 pdf download

admin
BS ISO IEC 25040 pdf download

BS ISO IEC 25040 pdf download.Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Evaluation process
1 Scope
This International Standard contains requirements and recommendations for the evaluation of software product quality and clarifies the general concepts. It provides a process description for evaluating software product quality and states the requirements for the application of this process. The evaluation process can be used for different purposes and approaches. The process can be used for the evaluation of the quality of pre- developed software, commercial-off-the-shelf software or custom software and can be used during or after the development process. This International Standard establishes the relationship of the evaluation reference model to the SQuaRE documents as well as shows how each SQuaRE document should be used during the activities of the evaluation process. It is intended for those responsible for software product evaluation and is appropriate for developers, acquirers and independent evaluators of software products. These three different approaches are detailed in ISO/IEC 14598-3, ISO/IEC 14598-4, and ISO/IEC 14598-5. It is not intended for evaluation of other aspects of software products (such as functional requirements, process requirements, business requirements, etc.).
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply. 4.1 acquirer individual or organization that acquires or procures a system, software product or software service from a supplier NOTE Adapted from ISO/IEC 12207:2008.4.2 analysis model algorithm or calculation combining one or more base and/or derived measures with associated decision criteria 4.3 attribute inherent property or characteristic of an entity that can be distinguished quantitatively or qualitatively by human or automated means NOTE 1 Adapted from ISO/IEC 15939:2007. NOTE 2 ISO 9000 distinguishes two types of attributes: a permanent characteristic existing inherently in something; and an assigned characteristic of a product, process or system (e.g. the price of a product, the owner of a product). The assigned characteristic is not an inherent quality characteristic of that product, process or system. 4.4 attribute for quality measure attribute that relates to software product itself, to the use of the software product or to its development process NOTE Attributes for quality measure are used in order to obtain quality measure elements. 4.5 base measure measure defined in terms of an attribute and the method for quantifying it NOTE 1 A base measure is functionally independent of other measures. NOTE 2 Adapted from the International Vocabulary of Basic and General Terms in Metrology, 1993. [ISO/IEC 15939:2007] 4.6 commercial-off-the-shelf software product software product defined by a market-driven need, commercially available, and whose fitness for use has been demonstrated by a broad spectrum of commercial users 4.7 context of use users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used [ISO 9241-11:1998]4.8 custom software software product developed for a specific application from a user requirements specification 4.9 data collection of values assigned to base measures, derived measures and/or indicators [ISO/IEC 15939:2007] 4.10 decision criteria thresholds, targets, or patterns used to determine the need for action or further investigation, or to describe the level of confidence in a given result. [ISO/IEC 15939:2007]4.11 derived measure measure that is defined as a function of two or more values of base measures [ISO/IEC 15939:2007] NOTE 1 Adapted from the International Vocabulary of Basic and General Terms in Metrology, 1993. NOTE 2 A transformation of a base measure using a mathematical function can also be considered as a derived measure. 4.12 developer individual or organization that performs development activities (including requirements analysis, design, testing through acceptance) during the software life-cycle process NOTE Adapted from the definition in ISO/IEC 12207:2008. 4.13 division of standards division forms a family of standards serving complementary purposes 4.14 end user individual person who ultimately benefits from the outcomes of the system NOTE The end user can be a regular operator of the software product or a casual user such as a member of the public. 4.15 entity object that is to be characterized by measuring its attributes EXAMPLE An object can be a process, product, project, or resource. [ISO/IEC 15939:2007] 4.16 evaluation systematic determination of the extent to which an entity meets its specified criteria [ISO/IEC 12207:2008]