Purchase the full subscription package now and enjoy a 40% discount, along with free updates for future editions.
AS ISO/IEC 25051:2019
$177.61
Software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing
The objective of this Standard is to establish quality requirements for Ready to Use Software Product (RUSP); requirements for test documentation for the testing of RUSP, including test plan, test description, and test results; and instructions for conformity evaluation of RUSP.
Table of contents
Header
About this publication
Preface
Foreword
Introduction
1 Scope
2 Conformance
3 Normative references
4 Terms, definitions and abbreviated terms
4.1 Terms and definitions
4.2 Abbreviated termss
5 Requirements for Ready to Use Software Product (RUSP)
5.1 Requirements for product description
5.1.1 Availability
5.1.1.1
5.1.2 Contents
5.1.2.1
5.1.2.2
5.1.2.3
5.1.2.4
5.1.3 Identification and indications
5.1.3.1
5.1.3.2
5.1.3.3
5.1.3.4
5.1.3.5
5.1.3.6
5.1.3.7
5.1.4 Mapping
5.1.4.1
5.1.5 Product quality – Functional suitability
5.1.5.1
5.1.5.2
5.1.5.3
5.1.5.4
5.1.5.5
5.1.5.6
5.1.6 Product quality – Performance efficiency
5.1.6.1
5.1.6.2
5.1.6.3
5.1.7 Product quality – Compatibility
5.1.7.1
5.1.7.2
5.1.7.3
5.1.8 Product quality – Usability
5.1.8.1
5.1.8.2
5.1.8.3
5.1.8.4
5.1.8.5
5.1.8.6
5.1.9 Product quality – Reliability
5.1.9.1
5.1.9.2
5.1.9.3
5.1.10 Product quality – Security
5.1.10.1
5.1.11 Product quality – Maintainability
5.1.11.1
5.1.11.2
5.1.11.3
5.1.12 Product Quality – Portability
5.1.12.1
5.1.12.2
5.1.12.3
5.1.13 Quality in use – Effectiveness
5.1.13.1
5.1.13.2
5.1.14 Quality in use – Efficiency
5.1.14.1
5.1.14.2
5.1.14.3
5.1.15 Quality in use – Satisfaction
5.1.15.1
5.1.15.2
5.1.16 Freedom from risk
5.1.16.1
5.1.16.2
5.1.17 Context coverage
5.1.17.1
5.1.17.2
5.2 Requirements for user documentation
5.2.1 Availability
5.2.1.1
5.2.2 Contents
5.2.2.1
5.2.3 Identification and indications
5.2.3.1
5.2.3.2
5.2.3.3
5.2.3.4
5.2.4 Completeness
5.2.4.1
5.2.4.2
5.2.4.3
5.2.4.4
5.2.4.5
5.2.4.6
5.2.4.7
5.2.4.8
5.2.5 Correctness
5.2.5.1
5.2.5.2
5.2.6 Consistency
5.2.6.1
5.2.7 Understandability
5.2.7.1
5.2.7.2
5.2.8 Product quality – Functional suitability
5.2.8.1
5.2.9 Product quality – Compatibility
5.2.9.1
5.2.9.2
5.2.9.3
5.2.10 Product quality – Usability/Learnability
5.2.10.1
5.2.11 Product quality – Usability/Operability
5.2.11.1
5.2.11.2
5.2.11.3
5.2.12 Product quality – Reliability
5.2.12.1
5.2.13 Product quality – Security
5.2.13.1
5.2.14 Product quality – Maintainability
5.2.14.1
5.2.15 Quality in use – Effectiveness
5.2.15.1
5.2.16 Quality in use – Efficiency
5.2.16.1
5.2.17 Quality in use – Satisfaction
5.2.17.1
5.2.17.2
5.2.18 Quality in use – Freedom from risk
5.2.18.1
5.2.19 Quality in use – Context coverage
5.2.19.1
5.3 Quality requirements for software
5.3.1 Product quality – Functional suitability
5.3.1.1
5.3.1.2
5.3.1.3
5.3.1.4
5.3.1.5
5.3.2 Product quality – Performance efficiency
5.3.2.1
5.3.3 Product quality – Compatibility
5.3.3.1
5.3.3.2
5.3.3.3
5.3.3.4
5.3.3.5
5.3.3.6
5.3.4 Product quality – Usability
5.3.4.1
5.3.4.2
5.3.4.3
5.3.4.4
5.3.4.5
5.3.4.6
5.3.4.7
5.3.4.8
5.3.4.9
5.3.4.10
5.3.5 Product quality – Reliability
5.3.5.1
5.3.5.2
5.3.5.3
5.3.5.4
5.3.5.5
5.3.6 Product quality – Security
5.3.6.1
5.3.6.2
5.3.6.3
5.3.6.4
5.3.6.5
5.3.7 Product quality – Maintainability
5.3.7.1
5.3.7.2
5.3.7.3
5.3.8 Product quality – Portability
5.3.8.1
5.3.8.2
5.3.8.3
5.3.9 Quality in use – Effectiveness
5.3.9.1
5.3.9.2
5.3.10 Quality in use – Efficiency
5.3.10.1
5.3.10.2
5.3.11 Quality in use – Satisfaction
5.3.11.1
5.3.11.2
5.3.12 Quality in use – Freedom from risk
5.3.12.1
5.3.12.2
5.3.12.3
5.3.13 Quality in use – Context coverage
5.3.13.1
5.3.13.2
6 Requirements for test documentation
6.1 General Requirements
6.1.1 Purpose
6.1.1.1
6.1.2 Consistency
6.1.2.1
6.1.2.2
6.1.3 Requirements for content
6.1.3.1
6.1.3.2
6.1.3.3
6.1.3.4
6.1.4 Approach
6.1.4.1
6.1.4.2
6.1.4.3
6.1.4.4
6.1.4.5
6.1.4.6
6.1.4.7
6.1.4.8
6.1.4.9
6.1.4.10
6.1.4.11
6.1.4.12
6.1.4.13
6.1.4.14
6.2 Requirements for the test plan
6.2.1 Pass/fail criteria
6.2.1.1
6.2.2 Software Test environment
6.2.2.1
6.2.3 Schedule
6.2.3.1
6.2.4 Risk
6.2.4.1
6.2.5 Human Resource
6.2.5.1
6.2.6 Tool and equipment resource
6.2.6.1
6.2.6.2
6.2.7 Communication
6.2.7.1
6.3 Requirements for the testing description
6.3.1 Test case description
6.3.1.1
6.3.1.2
6.3.2 Test procedures
6.3.2.1
6.3.2.2
6.3.2.3
6.4 Requirements for the test results
6.4.1 Execution report
6.4.1.1
6.4.1.2
6.4.1.3
6.4.2 Anomaly report
6.4.2.1
6.4.2.2
6.4.2.3
6.4.2.4
6.4.2.5
6.4.2.6
6.4.3 Assessment of the test results
6.4.3.1
7 Instructions for conformity evaluation
7.1 General Principles
7.2 Conformity evaluation pre-requisites
7.2.1 Presence of Ready to Use Software Product (RUSP) items
7.2.2 Presence of system elements
7.3 Conformity evaluation activities
7.3.1 Product description conformity evaluation
7.3.2 User documentation conformity evaluation
7.3.3 Software conformity evaluation
7.4 Conformity evaluation process
7.5 Conformity evaluation report
7.6 Follow up conformity evaluation
Annex A
A.1 General
A.2 Fault Detection and Accommodation including software redundancy
A.3 Retry Fault Recovery
A.4 n-Version Programming
A.5 Recovery Block Programming
A.6 Model Following
A.7 Wrappers
A.8 Techniques to be considered to establish Ready to Use Software Product (RUSP) quality features
