BS ISO IEC IEEE 29119-2-2013 Software and systems engineering Software testing Test processes《软件和系统工程 软件测试 试验过程》.pdf

1、BSI Standards Publication BS ISO/IEC/IEEE 29119-2:2013 Software and systems engineering Software testing Part 2: Test processesBS ISO/IEC/IEEE 29119-2:2013 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC/IEEE 29119-2:2013. The UK participation in its prep

2、aration was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for

3、 its correct application. The British Standards Institution 2013. Published by BSI Standards Limited 2013 ISBN 978 0 580 73288 1 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Polic

4、y and Strategy Committee on 30 September 2013. Amendments issued since publication Date Text affectedBS ISO/IEC/IEEE 29119-2:2013Reference number ISO/IEC/IEEE 29119-2:2013(E) ISO/IEC 2013 IEEE 2013INTERNATIONAL STANDARD ISO/IEC/ IEEE 29119-2 First edition 2013-09-01 Software and systems engineering

5、Software testing Part 2: Test processes Ingnierie du logiciel et des systmes Essais du logiciel Partie 2: Processus des essais BS ISO/IEC/IEEE 29119-2:2013 ISO/IEC/IEEE 29119-2:2013(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2013 IEEE 2013 All rights reserved. Unless otherwise specified, no part of thi

6、s publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ISO, IEC or IEEE at the respective address below. ISO copyright office IEC Central Office Institute of Electrical and Electronic

7、s Engineers, Inc. Case postale 56 3, rue de Varemb 3 Park Avenue, New York CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA Tel. + 41 22 749 01 11 Switzerland E-mail stds.iprieee.org Fax + 41 22 749 09 47 E-mail inmailiec.ch Web www.ieee.org E-mail copyrightiso.org Web www.iec.ch Web www.iso.o

8、rg Published in Switzerland ii ISO/IEC 2013 All rights reserved IEEE 2013 All rights reservedBS ISO/IEC/IEEE 29119-2:2013 ISO/IEC/IEEE 29119-2:2013(E) ISO/IEC 2013 All rights reserved IEEE 2013 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Scope . . 1 2 Conformance . 1 2.1 Inte

9、nded Usage 1 2.1.1 Full Conformance 1 2.1.2 Tailored Conformance 1 3 Normative References . 2 4 Terms and Definitions . 2 5 Multi-Layer Test Process Model 10 6 Organizational Test Process 11 6.1 Introduction 11 6.2 Organizational Test Process 12 6.2.1 Overview . 12 6.2.2 Purpose . . 13 6.2.3 Outcome

10、s . 13 6.2.4 Activities and tasks . 13 6.2.5 Information items . . 14 7 Test Management Processes . 15 7.1 Introduction 15 7.2 Test Planning Process . . 16 7.2.1 Overview . 16 7.2.2 Purpose . . 17 7.2.3 Outcomes . 17 7.2.4 Activities and tasks . 17 7.2.5 Information items . . 21 7.3 Test Monitoring

11、and Control Process . 21 7.3.1 Overview . 21 7.3.2 Purpose . . 22 7.3.3 Outcomes . 22 7.3.4 Activities and tasks . 23 7.3.5 Information Items . . 24 7.4 Test Completion Process . 25 7.4.1 Overview . 25 7.4.2 Purpose . . 25 7.4.3 Outcomes . 25 7.4.4 Activities and tasks . 26 7.4.5 Information Items .

12、 . 27 8 Dynamic Test Processes 27 8.1 Introduction 27 8.2 Test Design & Implementation Process 29 8.2.1 Overview . 29 8.2.2 Purpose . . 30 8.2.3 Outcomes . 30 8.2.4 Activities and tasks . 31 8.2.5 Information Items . . 33 8.3 Test Environment Set-Up & Maintenance Process 34 8.3.1 Overview . 34 BS IS

13、O/IEC/IEEE 29119-2:2013 ISO/IEC/IEEE 29119-2:2013(E) iv ISO/IEC 2013 All rights reserved IEEE 2013 All rights reserved8.3.2 Purpose .34 8.3.3 Outcomes .34 8.3.4 Activities and tasks .34 8.3.5 Information Items .35 8.4 Test Execution Process 36 8.4.1 Overview .36 8.4.2 Purpose .36 8.4.3 Outcomes .36

14、8.4.4 Activities and tasks .37 8.4.5 Information Items .37 8.5 Test Incident Reporting Process 38 8.5.1 Overview .38 8.5.2 Purpose .38 8.5.3 Outcomes .38 8.5.4 Activities and tasks .39 8.5.5 Information Items .39 Annex A (informative) Partial Example Test Design Process .40 Annex B (normative) ISO/I

15、EC/IEEE 29119-2 and ISO/IEC 12207:2008 Process Alignment .42 B.1 Overview .42 B.2 ISO/IEC 12207:2008 to ISO/IEC/IEEE 29119-2 Mapping .42 Annex C (informative) ISO/IEC/IEEE 29119-2 and ISO/IEC 15288:2008 process alignment 53 Annex D (informative) ISO/IEC/IEEE 29119-2 and ISO/IEC 17025:2005 process al

16、ignment 54 Annex E (informative) ISO/IEC/IEEE 29119-2 and ISO/IEC 25051:2006 process alignment .55 Annex F (informative) ISO/IEC/IEEE 29119-2 and BS 7925-2:1998 process alignment 56 Annex G (informative) ISO/IEC/IEEE 29119-2 and IEEE Std 1008-2008 process alignment 57 Bibliography 59 BS ISO/IEC/IEEE

17、 29119-2:2013 ISO/IEC/IEEE 29119-2:2013(E) ISO/IEC 2013 All rights reserved IEEE 2013 All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bod

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

19、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/IEC JTC 1. IEEE Standards documents are developed within the IEEE Societies

20、and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and i

21、nterests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or ver

22、ify the accuracy of any of the information contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted by the joint te

23、chnical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is called to the possibility that implementation of this standard may require the use of subject matter covered

24、 by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a license may be required, for conducting inquirie

25、s into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agreements are reasonable or non-d

26、iscriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards Association. ISO/IEC/IEEE 29119-2

27、 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software & Systems Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development Organization coopera

28、tion agreement between ISO and IEEE. ISO/IEC 29119 consists of the following standards, under the general title Software and systems engineering Software testing: Part 1: Concepts and definitions Part 2: Test processes Part 3: Test documentation Part 4: Test techniques BS ISO/IEC/IEEE 29119-2:2013 I

29、SO/IEC/IEEE 29119-2:2013(E) vi ISO/IEC 2013 All rights reserved IEEE 2013 All rights reservedIntroduction The purpose of the ISO/IEC/IEEE series of software testing standards is to define a generic process model for software testing that can be used by any organization when performing any form of so

30、ftware testing. It comprises test process descriptions that define the software testing processes at the organizational level, test management level and dynamic test levels. Supporting informative diagrams describing the processes are also provided. ISO/IEC/IEEE 29119 supports dynamic testing, funct

31、ional and non-functional testing, manual and automated testing, and scripted and unscripted testing. The processes defined in this series of international standards can be used in conjunction with any software development lifecycle model. Each process is defined using the generic process template th

32、at is provided in ISO/IEC TR 24774:2010 Guidelines for Process Description, and covers the purpose, outcomes, activities, tasks and information items of each test process. Testing is a key approach to risk mitigation in software development. This part of ISO/IEC/IEEE 29119 follows a risk-based appro

33、ach to testing. Risk-based testing is a best-practice approach to strategizing and managing testing, as it allows testing to be prioritized and focused on the most important features and quality attributes. The concepts and vocabulary that support this series of international standards are defined i

34、n ISO/IEC/IEEE 29119-1 Concepts and definitions. Templates and examples of test documentation that are produced during the testing process are defined in ISO/IEC/IEEE 29119-3 Test documentation. Software test design techniques that can be used during testing are defined in ISO/IEC/IEEE 29119-4 Test

35、techniques. This series of international standards aims to provide those responsible for software testing with the information required to manage and perform software testing in any organization. BS ISO/IEC/IEEE 29119-2:2013 INTERNATIONAL STANDARD ISO/IEC/IEEE 29119-2:2013(E) ISO/IEC 2013 All rights

36、 reserved IEEE 2013 All rights reserved 1Software and systems engineering Software testing Part 2: Test processes 1 Scope This part of ISO/IEC/IEEE 29119 specifies test processes that can be used to govern, manage and implement software testing for any organization, project or smaller testing activi

37、ty. It comprises generic test process descriptions that define the software testing processes. Supporting informative diagrams describing the processes are also provided. This part of ISO/IEC/IEEE 29119 is applicable to testing in all software development lifecycle models. This part of ISO/IEC/IEEE

38、29119 is intended for, but not limited to, testers, test managers, developers and project managers, particularly those responsible for governing, managing and implementing software testing. 2 Conformance 2.1 Intended usage The requirements in this part of ISO/IEC/IEEE 29119 are contained in Clauses

39、6 to 8. This part of ISO/IEC/IEEE 29119 provides requirements for a number of test processes suitable for use during the complete software lifecycle. It is recognized that particular projects or organizations may not need to use all of the processes defined by this part of ISO/IEC/IEEE 29119. Theref

40、ore, implementation of this part of ISO/IEC/IEEE 29119 typically involves selecting a set of processes suitable for the organization or project. There are two ways that an organization can claim to conform to the provisions of this part of ISO/IEC/IEEE 29119. The organization shall assert whether it

41、 is claiming full or tailored conformance to this part of ISO/IEC/IEEE 29119: 2.1.1 Full conformance Full conformance is achieved by demonstrating that all of the requirements (i.e. shall statements) of the full set of processes defined in this part of ISO/IEC/IEEE 29119 have been satisfied. 2.1.2 T

42、ailored conformance When this part of ISO/IEC/IEEE 29119 is used as a basis for establishing a set of processes that do not qualify for full conformance, the subset of processes for which tailored conformance is claimed, is recorded. Tailored conformance is achieved by demonstrating that all of the

43、requirements (i.e. shall statements) for the recorded subset of processes have been satisfied. Where tailoring occurs, justification shall be provided (either directly or by reference), whenever a process defined in Clauses 6, 7 and 8 of this part of ISO/IEC/IEEE 29119 is not followed. All tailoring

44、 decisions shall be recorded with their rationale, including the consideration of any applicable risks. Tailoring decisions shall be agreed by the relevant stakeholders. EXAMPLE Where organizations follow information item management processes in standards such as ISO 15489 (Information and documenta

45、tion - Records management) or ISO 9001 (Quality management systems - Requirements) or BS ISO/IEC/IEEE 29119-2:2013 ISO/IEC/IEEE 29119-2:2013(E) 2 ISO/IEC 2013 All rights reserved IEEE 2013 All rights reserveduse similar internal organizational processes, they can decide to use those processes in pla

46、ce of the information item management tasks defined in this part of ISO/IEC/IEEE 29119. 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. Fo

47、r undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC/IEEE 29119-1, Software and systems engineering Software testing Part 1: Concepts and definitions ISO/IEC/IEEE 29119-3, Software and systems engineering Software testing Part 3: Test docume

48、ntation ISO/IEC/IEEE 29119-4, Software and systems engineering Software testing Part 4: Test techniques 1ISO/IEC 12207:2008, Systems and software engineering Software life cycle processes Other standards useful for the implementation and interpretation of this document are listed in the Bibliography

49、. 4 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 24765 and the following apply. NOTE Use of the terminology in this part of ISO/IEC/IEEE 29119 is for ease of reference and is not mandatory for conformance with this part of ISO/IEC/IEEE 29119. The following terms and definitions are provided to assist with the understanding and readability of this part of ISO/IEC/IEEE 29119. Only terms critical to the understanding of this part of