BS ISO IEC 25051-2014 Software engineering Systems and software Quality Requirements and Evaluation (SQuaRE) Requirements for quality of Ready to Use Software Product (RUS.pdf

1、BSI Standards Publication BS ISO/IEC 25051:2014 Software engineering Systems and software Quality Requirements and Evaluation (SQuaRE) Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testingBS ISO/IEC 25051:2014 BRITISH STANDARD National foreword This British St

2、andard is the UK implementation of ISO/IEC 25051:2014. It supersedes BS ISO/IEC 25051:2006 which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained

3、on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2014. Published by BSI Standards Limited 2014 ISBN 978 0 580 80183 9 ICS 35.080 Compliance with a

4、 British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 28 February 2014. Amendments issued since publication Date Text affectedBS ISO/IEC 25051:2014 Software engineering Systems and so

5、ftware Quality Requirements and Evaluation (SQuaRE) Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing Ingnierie du logiciel Exigences de qualit et valuation des systmes et du logiciel (SQuaRE) Exigences de qualit pour les progiciels et instructions dessai

6、ISO/IEC 2014 INTERNATIONAL STANDARD ISO/IEC 25051 Second edition 2014-02-15 Reference number ISO/IEC 25051:2014(E)BS ISO/IEC 25051:2014ISO/IEC 25051:2014(E)ii ISO/IEC 2014 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014 All rights reserved. Unless otherwise specified, no part of this p

7、ublication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the c

8、ountry of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in SwitzerlandBS ISO/IEC 25051:2014ISO/IEC 25051:2014(E) ISO/IEC 2014 All rights reserved iii Contents Page Foreword iv Intro

9、duction v 1 Scope . 1 2 Conformance . 2 3 Normative references 2 4 T erms, definitions and abbr e viat ed t erms 3 4.1 Terms and definitions . 3 4.2 Abbreviated termss . 6 5 Requirements for Ready to Use Software Product (RUSP) . 6 5.1 Requirements for product description. 6 5.2 Requirements for use

10、r documentation .11 5.3 Quality requirements for software .15 6 Requirements for test documentation .19 6.1 General Requirements .19 6.2 Requirements for the test plan 21 6.3 Requirements for the testing description .22 6.4 Requirements for the test results 23 7 Instructions for conformity evaluatio

11、n .24 7.1 General Principles .24 7.2 Conformity evaluation pre-requisites 24 7.3 Conformity evaluation activities .25 7.4 Conformity evaluation process 25 7.5 Conformity evaluation report .25 7.6 Follow up conformity evaluation .26 Annex A (informative) Guidanc e for R ead y t o Use S oftw ar e Pr o

12、duct (R USP) e v aluation in business or safety critical applications .27 Annex B (informative) How to use ISO/IEC 25051 31 Bibliogr aph y .32BS ISO/IEC 25051:2014ISO/IEC 25051:2014(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commi

13、ssion) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO

14、 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO

15、/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to nationa

16、l bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for

17、identifying any or all such patent rights. ISO/IEC 25051 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. This second edition cancels and replaces the first edition (ISO/IEC 25051:2006), which has been technically r

18、evised. It also incorporates the Technical Corrigendum ISO/IEC 25051:2006/Cor.1:2007. The main changes are as follows: English and French titles corrected; modification of RUSP definition, scope and examples; harmonization with the current SQuaRE series. ISO/IEC 25051 is a part of the SQuaRE series

19、of International Standards, which consists of the following divisions: Quality Management Division (ISO/IEC 2500n); Quality Model Division (ISO/IEC 2501n); Quality Measurement Division (ISO/IEC 2502n); Quality Requirements Division (ISO/IEC 2503n); Quality Evaluation Division (ISO/IEC 2504n); Extens

20、ion Division (ISO/IEC 25050: ISO/IEC 25099).iv ISO/IEC 2014 All rights reservedBS ISO/IEC 25051:2014ISO/IEC 25051:2014(E) Introduction Ready to Use Software Product (RUSP) are used in an increasingly wide variety of application areas and their correct operation is often vital for business, safety an

21、d personal applications. Ready to Use Software Product (RUSP) are packages sold to the acquirer who had no influence on its features and other qualities. Typically the software is sold pre-wrapped or downloaded via web store with its user documentation. A software product, which a user can use anyti

22、me thorough Cloud Computing may be considered as RUSP. The information provided on the cover of the package or the supplier website is often the only means whereby the manufacturer or marketing organization can communicate with the acquirer and user. It is therefore important that essential informat

23、ion is given to enable acquirers to evaluate the quality of the Ready to Use Software Product (RUSP) for their needs. Selecting high quality Ready to Use Software Product (RUSP) is of prime importance, because Ready to Use Software Product (RUSP) may have to be operational in various environments an

24、d selected without the opportunity to compare performance among similar products. Suppliers need a way to ensure confidence in services given by the Ready to Use Software Product (RUSP) to the users. Some suppliers may choose a conformity evaluation group for evaluation or certification to assist th

25、em in providing this confidence. In addition, when users require assurances that business or safety critical risks are involved, those assurances may need to be addressed by the user using techniques chosen by the user after the purchase. It is not the intent of this International Standard to specif

26、y minimum safety or business critical quality requirements for RUSP; however, informative guidance is given. (See Annex A.) ISO/IEC 25051:2006 was developed based on ISO/IEC 9126-1:2001 and replaced ISO/IEC 12119:1994. This second edition of ISO/IEC 25051 is a revision of ISO/IEC 25051:2006, in orde

27、r to conform to ISO/IEC 25010:2011, which replaced ISO/IEC 9126-1:2001 quality model. These items are the major points for revising this International Standard, which provides a set of requirements for Ready to Use Software Product (RUSP) and requirements for testing a Ready to Use Software Product

28、(RUSP) against its requirements. ISO/IEC 2014 All rights reserved vBS ISO/IEC 25051:2014BS ISO/IEC 25051:2014Software 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 Th

29、is 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 1 Examples of Ready to Use Software Product (RUSP) include but are not limited to text process

30、ors, 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. NOTE 2 Open source softw

31、are 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, a

32、nd 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 Stan

33、dard 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 out

34、side the scope of this International Standard. The intended users of this International Standard 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 con

35、formity (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

36、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; INTERNATIONAL ST ANDARD ISO/IEC 25051:2014(E) ISO/IEC 2014 All rights reserved 1BS ISO/IEC 25051:2014ISO/IEC 25051:20

37、14(E) 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 pr

38、ofit from better software products; g) organizations: 1) establishing management and engineering environments based on the quality requirements and methods of this International Standard; and 2) managing and improving their quality processes “and personnel”. h) regulatory authorities who may require

39、 or recommend the requirements of this International Standard for Ready to Use Software Product (RUSP) used in safety or business-critical applications. 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)

40、 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

41、 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

42、. 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 do

43、cuments, 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

44、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 models2 ISO/IEC 2014 All rights reservedBS ISO/IEC

45、25051:2014ISO/IEC 25051:2014(E) 4 T erms, d efinitions and abbr e viat ed t erms 4.1 T erms and definiti ons 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 1 to entry: The ac

46、quirer could be one of the following: buyer, customer, owner, purchaser. SOURCE: ISO/IEC 12207:2008 4.1.2 anomaly any condition that deviates from expectations based on requirements specifications, design documents, standards, etc. or from someones perceptions or experiences SOURCE: IEEE Std 1044-20

47、09 4.1.3 application administration function functions performed by users which include installation, configuration, application backup, maintenance (patching and upgrading) and uninstallation 4.1.4 conformity evaluation systematic examination of the extent to which a product, process or service ful

48、fils specified requirements SOURCE: 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 1 to entry: This was adapted from IEEE Std 610.121990. 4.1.6 Ready to Use Software

49、 Product RUSP software product available for any user, at cost or not, and use without the need to conduct development activities Note 1 to entry: 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, the software contained on a computer