GB/T 25000.51-2016 Systems and software engineering―Systems and software Quality Requirements and Evaluation (SQuaRE)―Part 51:Requirements for quality of Ready to Use Software Product(RUSP) and instructions for testing (English Version)
Systems and software engineering―Systems and software Quality Requirements and Evaluation (SQuaRE)―Part 51:Requirements for quality of Ready to Use Software Product(RUSP) and instructions for testing
Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) -
Part 51: Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing
1 Scope
This Part of GB/T 25000 establishes:
a) Quality requirements for Ready to Use Software Product (RUSP);
b) Requirements for test documentation for the testing of RUSP, including test plan, testing description, and test results;
Note 1: The collection of documents for test is called “test documentation”.
c) Instructions for conformity evaluation of RUSP.
It includes also recommendations for safety or business critical Ready to Use Software Product (RUSP).
This Part 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 Part.
This Part is applicable to Ready to Use Software Product (RUSP).
Note 2: Examples 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 (e.g. real-time operating systems), human resources management software, sales management, smartphone application, freeware and web software such as generators of websites/pages.
Note 3: Open source software is not part of Ready to Use Software Product (RUSP).
The intended users of this Part include:
a) suppliers when:
1) specifying requirements for a Ready to Use Software Product (RUSP);
2) assessing their own software products against the claimed performance;
3) issuing declarations of conformity (ISO/IEC 17050);
4) applying for certificates or marks of conformity (ISO/IEC Guide 23);
b) certification bodies that may wish to establish a certification scheme (international, regional or national) (ISO/IEC Guide 28);
c) testing laboratories which will have to follow the instructions for testing when testing for a certificate or a mark of conformity (ISO/IEC 17025);
d) accreditation bodies for accrediting registration or certification bodies and testing laboratories;
e) potential acquirers who may:
1) compare the requirements for the intended work task with the information in product descriptions of existing software products;
2) look for certified Ready to Use Software Product (RUSP);
3) check if the requirements are otherwise met;
f) end users who may profit from better software products;
g) organizations:
1) establishing management and engineering environments based on the quality requirements and methods of this Part; and
2) managing and improving their quality processes “and personnel”.
h) regulatory authorities who may require or recommend the requirements of this Part for Ready to Use Software Product (RUSP) used in safety or business-critical applications.
Information on how to use this Part is given in Annex B.
2 Conformance
A Ready to Use Software Product (RUSP) conforms to this Part 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) 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 this part 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 referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition (including any amendments) applies.
GB/T 25000.10-2016 Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - Part 10: System and software quality models
4 Terms, definitions and abbreviations
4.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1.1
acquirer
stakeholder that acquires or procures a product or service from a supplier
Note: The acquirer could be one of the following: buyer, customer, owner, purchaser.
[ISO/IEC 12207:2008]
4.1.2
anomaly
any condition that deviates from expectations based on requirements specifications, design documents, standards, etc. or from someone’s perceptions or experiences
[IEEE std 1044-2009]
4.1.3
application administration function
functions performed by users which include installation, configuration, backup, maintenance (patching and upgrading) and uninstallation
4.1.4
conformity evaluation
systematic examination of the extent to which a product, process or service fulfils specified requirements
[ISO/IEC Guide 2: 2004]
4.1.5
conformity evaluation report
document that describes the conduct and results of the evaluation carried out for a Ready to Use Software Product (RUSP)
Note: This was adapted from IEEE std 610.12-1998.
4.1.6
Ready to Use Software Product
RUSP
software product available for any user, at cost or not, and use without the need to conduct development activities
Note 1: Ready to Use Software Product (RUSP) includes:
——the product description (including all cover information, data sheet, website information, etc.);
——the user documentation (necessary to install and use the software), including any configurations of the operating system/s or target computer required to operate the product;
Foreword i
Introduction iv
1 Scope
2 Conformance
3 Normative references
4 Terms, definitions and abbreviations
4.1 Terms and definitions
4.2 Abbreviations
5 Requirements for Ready to Use Software Product (RUSP)
5.1 Requirements for product description
5.2 Requirements for user documentation
5.3 Quality requirements for software
6 Requirements for test documentation
6.1 General requirements
6.2 Requirements for test plan
6.3 Requirements for test description
6.4 Requirements for test results
7 Instructions for conformity evaluation
7.1 General principles
7.2 Conformity evaluation pre-requisites
7.3 Conformity evaluation activities
7.4 Conformity evaluation process
7.5 Conformity evaluation report
7.6 Follow-up conformity evaluation
Annex A (Informative) Guidance for Ready to Use Software Product (RUSP) evaluation in business or safety critical applications
Annex B (Informative) How to use this part
Bibliography
GB/T 25000.51-2016 Systems and software engineering―Systems and software Quality Requirements and Evaluation (SQuaRE)―Part 51:Requirements for quality of Ready to Use Software Product(RUSP) and instructions for testing (English Version)
Standard No.
GB/T 25000.51-2016
Status
valid
Language
English
File Format
PDF
Word Count
14500 words
Price(USD)
140.0
Implemented on
2017-5-1
Delivery
via email in 1 business day
Detail of GB/T 25000.51-2016
Standard No.
GB/T 25000.51-2016
English Name
Systems and software engineering―Systems and software Quality Requirements and Evaluation (SQuaRE)―Part 51:Requirements for quality of Ready to Use Software Product(RUSP) and instructions for testing
Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) -
Part 51: Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing
1 Scope
This Part of GB/T 25000 establishes:
a) Quality requirements for Ready to Use Software Product (RUSP);
b) Requirements for test documentation for the testing of RUSP, including test plan, testing description, and test results;
Note 1: The collection of documents for test is called “test documentation”.
c) Instructions for conformity evaluation of RUSP.
It includes also recommendations for safety or business critical Ready to Use Software Product (RUSP).
This Part 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 Part.
This Part is applicable to Ready to Use Software Product (RUSP).
Note 2: Examples 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 (e.g. real-time operating systems), human resources management software, sales management, smartphone application, freeware and web software such as generators of websites/pages.
Note 3: Open source software is not part of Ready to Use Software Product (RUSP).
The intended users of this Part include:
a) suppliers when:
1) specifying requirements for a Ready to Use Software Product (RUSP);
2) assessing their own software products against the claimed performance;
3) issuing declarations of conformity (ISO/IEC 17050);
4) applying for certificates or marks of conformity (ISO/IEC Guide 23);
b) certification bodies that may wish to establish a certification scheme (international, regional or national) (ISO/IEC Guide 28);
c) testing laboratories which will have to follow the instructions for testing when testing for a certificate or a mark of conformity (ISO/IEC 17025);
d) accreditation bodies for accrediting registration or certification bodies and testing laboratories;
e) potential acquirers who may:
1) compare the requirements for the intended work task with the information in product descriptions of existing software products;
2) look for certified Ready to Use Software Product (RUSP);
3) check if the requirements are otherwise met;
f) end users who may profit from better software products;
g) organizations:
1) establishing management and engineering environments based on the quality requirements and methods of this Part; and
2) managing and improving their quality processes “and personnel”.
h) regulatory authorities who may require or recommend the requirements of this Part for Ready to Use Software Product (RUSP) used in safety or business-critical applications.
Information on how to use this Part is given in Annex B.
2 Conformance
A Ready to Use Software Product (RUSP) conforms to this Part 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) 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 this part 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 referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition (including any amendments) applies.
GB/T 25000.10-2016 Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - Part 10: System and software quality models
4 Terms, definitions and abbreviations
4.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1.1
acquirer
stakeholder that acquires or procures a product or service from a supplier
Note: The acquirer could be one of the following: buyer, customer, owner, purchaser.
[ISO/IEC 12207:2008]
4.1.2
anomaly
any condition that deviates from expectations based on requirements specifications, design documents, standards, etc. or from someone’s perceptions or experiences
[IEEE std 1044-2009]
4.1.3
application administration function
functions performed by users which include installation, configuration, backup, maintenance (patching and upgrading) and uninstallation
4.1.4
conformity evaluation
systematic examination of the extent to which a product, process or service fulfils specified requirements
[ISO/IEC Guide 2: 2004]
4.1.5
conformity evaluation report
document that describes the conduct and results of the evaluation carried out for a Ready to Use Software Product (RUSP)
Note: This was adapted from IEEE std 610.12-1998.
4.1.6
Ready to Use Software Product
RUSP
software product available for any user, at cost or not, and use without the need to conduct development activities
Note 1: Ready to Use Software Product (RUSP) includes:
——the product description (including all cover information, data sheet, website information, etc.);
——the user documentation (necessary to install and use the software), including any configurations of the operating system/s or target computer required to operate the product;
Contents of GB/T 25000.51-2016
Foreword i
Introduction iv
1 Scope
2 Conformance
3 Normative references
4 Terms, definitions and abbreviations
4.1 Terms and definitions
4.2 Abbreviations
5 Requirements for Ready to Use Software Product (RUSP)
5.1 Requirements for product description
5.2 Requirements for user documentation
5.3 Quality requirements for software
6 Requirements for test documentation
6.1 General requirements
6.2 Requirements for test plan
6.3 Requirements for test description
6.4 Requirements for test results
7 Instructions for conformity evaluation
7.1 General principles
7.2 Conformity evaluation pre-requisites
7.3 Conformity evaluation activities
7.4 Conformity evaluation process
7.5 Conformity evaluation report
7.6 Follow-up conformity evaluation
Annex A (Informative) Guidance for Ready to Use Software Product (RUSP) evaluation in business or safety critical applications
Annex B (Informative) How to use this part
Bibliography
