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 in.pdf

1、BSI Standards PublicationBS ISO/IEC 25051:2014Software engineering Systems and software QualityRequirements and Evaluation(SQuaRE) Requirementsfor quality of Ready to UseSoftware Product (RUSP) andinstructions for testingBS ISO/IEC 25051:2014 BRITISH STANDARDNational forewordThis British Standard is

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

3、its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 80183 9ICS 35.080Compliance with a British Standard can

4、not confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 28 February 2014.Amendments issued since publicationDate Text affectedBS ISO/IEC 25051:2014Software engineering Systems and software Quality Requirements

5、 and Evaluation (SQuaRE) Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testingIngnierie du logiciel Exigences de qualit et valuation des systmes et du logiciel (SQuaRE) Exigences de qualit pour les progiciels et instructions dessai ISO/IEC 2014INTERNATIONAL ST

6、ANDARDISO/IEC25051Second edition2014-02-15Reference numberISO/IEC 25051:2014(E)BS ISO/IEC 25051:2014ISO/IEC 25051:2014(E)ii ISO/IEC 2014 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utili

7、zed 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 country of the requester.ISO copyright

8、 officeCase postale 56 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyrightiso.orgWeb www.iso.orgPublished in SwitzerlandBS ISO/IEC 25051:2014ISO/IEC 25051:2014(E) ISO/IEC 2014 All rights reserved iiiContents PageForeword ivIntroduction v1 Scope . 12 Conformance . 23 Normativ

9、e references 24 Terms, definitions and abbreviated terms 34.1 Terms and definitions . 34.2 Abbreviated termss . 65 Requirements for Ready to Use Software Product (RUSP) . 65.1 Requirements for product description. 65.2 Requirements for user documentation . 115.3 Quality requirements for software . 1

10、56 Requirements for test documentation .196.1 General Requirements . 196.2 Requirements for the test plan 216.3 Requirements for the testing description . 226.4 Requirements for the test results 237 Instructions for conformity evaluation .247.1 General Principles . 247.2 Conformity evaluation pre-re

11、quisites 247.3 Conformity evaluation activities . 257.4 Conformity evaluation process 257.5 Conformity evaluation report . 257.6 Follow up conformity evaluation .26Annex A (informative) Guidance for Ready to Use Software Product (RUSP) evaluation in business or safety critical applications .27Annex

12、B (informative) How to use ISO/IEC 25051 31Bibliography .32BS ISO/IEC 25051:2014ISO/IEC 25051:2014(E)ForewordISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies tha

13、t 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 and IEC technical committees collaborate in fields of mutual interest. Other interna

14、tional 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/IEC JTC 1.International Standards are drafted in accordance with the rules given in

15、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 national bodies for voting. Publication as an International Standard requires approval by at l

16、east 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 identifying any or all such patent rights.ISO/IEC 25051 was prepared by Joint Technical

17、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 revised. It also incorporates the Technical Corrigendum ISO/IEC 25051:2006/Cor.1:2007.The

18、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 of International Standards, which consists of the following divisions: Quality Management D

19、ivision (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); Extension Division (ISO/IEC 25050: ISO/IEC 25099).iv ISO/IEC 2014 All rights reservedBS ISO/IEC 2

20、5051:2014ISO/IEC 25051:2014(E)IntroductionReady 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 and personal applications.Ready to Use Software Product (RUSP) are packages sold to the acquire

21、r 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 anytime thorough Cloud Computing may be considered as RUSP. The information provided on the cover o

22、f 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 information is given to enable acquirers to evaluate the quality of the Ready to Use Software Product

23、(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 and selected without the opportunity to compare performance among similar products. Suppliers nee

24、d 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 them in providing this confidence.In addition, when users require assurances that business or saf

25、ety 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 specify minimum safety or business critical quality requirements for RUSP; however, informative guidan

26、ce 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 order to conform to ISO/IEC 25010:2011, which replaced ISO/IEC 9126-1:2001 quality model.These items

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

28、 25051:2014Software engineering Systems and software Quality Requirements and Evaluation (SQuaRE) Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing1 ScopeThis International Standard is applicable to Ready to Use Software Product (RUSP).In this Internationa

29、l 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 processors, spreadsheets, database control software, graphics packages, software for technical, scientific or

30、 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 software is not part of Ready to Use Software Product (RUSP).This International Standard establishes:a) Qual

31、ity 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 f

32、or 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 per

33、form 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.The intended users of this International Standard include:a) sup

34、pliers 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 bod

35、ies 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

36、 registration or certification bodies and testing laboratories;INTERNATIONAL STANDARD ISO/IEC 25051:2014(E) ISO/IEC 2014 All rights reserved 1BS ISO/IEC 25051:2014ISO/IEC 25051:2014(E)e) potential acquirers who may:1) compare the requirements for the intended work task with the information in produc

37、t 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 quali

38、ty requirements and methods of this International Standard; and2) managing and improving their quality processes “and personnel”.h) regulatory authorities who may require or recommend the requirements of this International Standard for Ready to Use Software Product (RUSP) used in safety or business-

39、critical applications.2 ConformanceA 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 docu

40、mented 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; and2) the supplier has duly considered the n

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

42、y that they are level 3 subclauses (numbered X.X.X.X). Informative notes complete these clauses and can serve as a guide.3 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, on

43、ly 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 SQuaREISO/IEC 25010, Systems and software

44、engineering Systems and software Quality Requirements and Evaluation (SQuaRE) System and software quality models2 ISO/IEC 2014 All rights reservedBS ISO/IEC 25051:2014ISO/IEC 25051:2014(E)4 Terms, definitions and abbreviated terms4.1 Terms and definitionsFor the purposes of this document, the follow

45、ing terms and definitions apply:4.1.1acquirerstakeholder that acquires or procures a product or service from a supplierNote 1 to entry: The acquirer could be one of the following: buyer, customer, owner, purchaser.SOURCE: ISO/IEC 12207:20084.1.2anomalyany condition that deviates from expectations ba

46、sed on requirements specifications, design documents, standards, etc. or from someones perceptions or experiencesSOURCE: IEEE Std 1044-20094.1.3application administration functionfunctions performed by users which include installation, configuration, application backup, maintenance (patching and upg

47、rading) and uninstallation4.1.4conformity evaluationsystematic examination of the extent to which a product, process or service fulfils specified requirementsSOURCE: ISO/IEC Guide 2:20044.1.5conformity evaluation reportdocument that describes the conduct and results of the evaluation carried out for

48、 a Ready to Use Software Product (RUSP)Note 1 to entry: This was adapted from IEEE Std 610.121990.4.1.6Ready to Use Software Product RUSPsoftware product available for any user, at cost or not, and use without the need to conduct development activitiesNote 1 to entry: Ready to Use Software Product (

49、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 sensible media (disk, CD-ROM, internet downloadable, etc.).Note 2 to entry: Software is mainly composed of programs and data.Note 3 to entry: This definition applies also to product description,