ISO IEC 25051 2014 pdf – Software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing.
1 Scope This International Standard is applicable to Ready to Use Software Product (RUSP). In this International Standard, the term“RUSP” is used as an adjective and stands for“Ready to Use Software Product”. NOTE 1Examples of Ready to Use Software Product (RUSP) include but are not limited to text processors, spreadsheets, database control software, graphics packages, software for technical, scientific or real-time embedded functions, human resources management software, sales management, smartphone application, freeware and web software such as generators of websites/pages. NOTE2 Open source software is not part of Ready to Use Software Product (RUSP). This International Standard establishes: a) Quality requirements for Ready to Use Software Product (RUSP); . b) Requirements for test documentation for the testing of Ready to Use Software Product (RUSP]), including test plan, test description, and test results; NOTE The collection of documents for test is called “test documentation”. c) Instructions for conformity evaluation of Ready to Use Software Product (RUSP]. It includes also recommendations for safety or business critical Ready to Use Software Product (RUSP]. This International Standard deals only with providing the user with confidence that the Ready to Use Software Product (RUSP] will perform as offered and delivered. It does not deal with the production realization (including activities and intermediate products, e.g. specifications). The quality system of a supplier is outside the scope of this International Standard.
2 Conformance A Ready to Use Software Product (RUSP) conforms to this International Standard if: a it has the properties specified in Clause 5; b) it has been tested by producing test documentation that meets the requirements of Clause 6; c anomalies found during testing are documented and resolved prior to product release. Anomalies against advertised performance claims must be fixed or the performance claim must be removed. Known anomalies may be considered acceptable if: 1) i the anomaly is not a violation of a performance claim; and 2] the supplier has duly considered the nature and the impact of the anomaly on the potential acquirer and deemed it negligible, and has preserved the documentation of the anomalies for future improvement. Clause 7 and Annex A are optional. NOTE To facilitate the conformity evaluation, requirements of the present standard are drafted in a way that they are level 3 subclauses (numbered X.X.X.X). Informative notes complete these clauses and can serve as a guide. . 3 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 25000, Systems and software engineering一Systems and software Quality Requirements and Evaluation (SQuaRE) – – Guide to SQuaRE ISO/IEC 25010, Systems and software engineering- Systems and software Quality Requirements and Evaluation (SQuaRE) – – System and software quality models
4.1.10 pass/fail criteria decision rules used to determine whether a software item or a software feature passes or fails a test [SOURCE: IEEE Std 829.12-1998] 4.1.11 product description docuiment stating properties of software, with the main purpose of helping potential acquirers in the evaluation of the suitability for themselves of the software before purchasing it 4.1.12 product identification software product name, version, variant, and date information 4.1.13 requirements document document containing any combination of requirements or regulations to be met by a Ready to Use Software Product (RUSP) Note 1 to entry: These documents may be technical reports, standards, requirements list [or model requirements specification) for a kind of user, or a statute or regulation imposed by a governing or regulatory body. 4.1.14 software function implementation of an algorithm in the software with which the end user or the software can perform part or all of a work task Note 1 to entry: A function does not need to be callable by the end user (e.g. automatic backup or saving of data).