BS ISO IEC 30130-2016 Software engineering Capabilities of software testing tools《软件工程 软件测试工具的能力》.pdf

1、BSI Standards Publication BS ISO/IEC 30130:2016 Software engineering Capabilities of software testing toolsBS ISO/IEC 30130:2016 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 30130:2016. The UK participation in its preparation was entrusted to Technical

2、 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 its correct application. The Brit

3、ish Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 86509 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 Policy and Strategy Committee on 31 Jan

4、uary 2016. Amendments/corrigenda issued since publication Date Text affectedBS ISO/IEC 30130:2016 Software engineering Capabilities of software testing tools Ingnierie du logiciel Capacits des outils dessai de logiciel INTERNATIONAL STANDARD ISO/IEC 30130 Reference number ISO/IEC 30130:2016(E) First

5、 edition 2016-02-01 ISO/IEC 2016 BS ISO/IEC 30130:2016ii ISO/IEC 2016 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any mea

6、ns, 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 office Ch. de Blandonnet 8 CP 401 CH-

7、1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 30130:2016(E)BS ISO/IEC 30130:2016ISO/IEC 30130:2016(E)Foreword v Introduction vi 1 Scope . 1 2 Normative references 1 3 T erms and definitions . 1 4 Object model for software testing to

8、ols 2 4.1 Overview of the object model 2 4.2 Test target 3 4.3 Dynamic test execution entity . 3 4.4 Code analysis entity 4 4.5 Test management entity . 4 5 Category of test entity . 5 5.1 Overview 5 5.2 Categories of dynamic test execution entities 5 5.2.1 Input for dynamic test execution . 5 5.2.2

9、 Dynamic test execution 5 5.2.3 Test data repository 5 5.2.4 Test environment 6 5.3 Categories of code analysis entities 6 5.3.1 Input for code analysis 6 5.3.2 Code analysis . 6 5.4 Categories of test management entities 6 5.4.1 Test plan 6 5.4.2 Test asset 6 5.4.3 Quality record report . 6 5.4.4 T

10、est completion report . 6 5.4.5 Verification and validation report . 6 5.4.6 Test status report 6 6 Characteristics of software testing tools . 6 6.1 Overview 6 6.2 Quality characteristics 7 6.3 Granularity . 8 6.4 Other aspects of characteristics . 9 7 Capabilities of software testing tools 9 7.1 O

11、verview 9 7.2 Dynamic test execution 9 7.2.1 Input for dynamic test execution . 9 7.2.2 Dynamic Test Execution .10 7.2.3 Test data repository .11 7.2.4 Test Environment .12 7.3 Code analysis .13 7.3.1 Input for code analysis .13 7.3.2 Code analysis 13 7.4 Test management .14 7.4.1 Test plan .14 7.4.

12、2 Test asset .14 7.4.3 Quality record report 14 7.4.4 Test completion report 15 7.4.5 Verification and validation report 15 7.4.6 Test status report .15 7.5 Summary of capabilities with characteristics .16 ISO/IEC 2016 All rights reserved iii Contents PageBS ISO/IEC 30130:2016ISO/IEC 30130:2016(E)An

13、nex A (informative) Capabilities mapping to test process .19 Annex B (informative) Overview of the approach for this International Standard 25 Bibliography .27 iv ISO/IEC 2016 All rights reservedBS ISO/IEC 30130:2016ISO/IEC 30130:2016(E) Foreword ISO (the International Organization for Standardizati

14、on) and IEC (the International Electrotechnical Commission) 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 d

15、eal with particular fields of technical activity. ISO 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

16、IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document shoul

17、d be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). 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

18、 for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for t

19、he convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL:

20、Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 7, Software and systems engineering. ISO/IEC 2016 All rights reserved vBS ISO/IEC 30130:2016ISO/IEC 30130:2016(E) Introduction This International Standard defines the framewo

21、rk to which capabilities of software testing tools are allocated in order to identify the capabilities of products being used by any project for software testing. To develop high-quality software with reasonable time and budget, the use of software testing tools is required. The increase in the size

22、 and complexity of software is complemented by an increase in the difficulty and complexity of software testing. This created a larger demand for the support of tools in order to test software effectively and efficiently. Testing tools are highly diverse due to their contexts of use. Testing itself

23、varies by objective, such as functional testing or nonfunctional testing, and granularity, such as unit testing or system testing. Testing tool vendors vary by providing tools with a different function or combination of functions. And despite vendor provided explanations for the type of testing supp

24、ort functions, there is little common understanding of these functions. In this environment, it is difficult to utilize a testing tool that is suitable for a project without common understanding of tool functions, proper acquisition of the needed tools, and efficient training. The framework defined

25、by this International Standard consists of objectives of testing, granularity of software to be tested and capabilities. In Clause 4, an object model for software testing tools as basis for the framework is defined. In Clause 5, three of the categories in that software testing model (Dynamic Test Ex

26、ecution, Code Analysis, and Test Management) are specified. In Clause 6, quality characteristics, granularity, and other aspects of characteristics are defined and in Clause 7, tool capabilities are mapped onto those categories and characteristics.vi ISO/IEC 2016 All rights reservedBS ISO/IEC 30130:

27、2016Software engineering Capabilities of software testing tools 1 Scope This International Standard defines the framework to which capabilities of software testing tools are allocated in order to identify the capabilities of products being used by any project for software testing. Software testing p

28、rocesses are identified in ISO/IEC/IEEE 29119-2 and software verification processes are identified in ISO/IEC 12207. This International Standard is fully harmonized with these existing standards in terms of software testing processes. This International Standard focuses on the following areas that t

29、he existing ISO/IEC standards do not deal with the following: categorization of software test entities and software testing tools (Clauses 4 and 5); characterization of each software testing tool category (Clauses 5 and 6); mapping of software testing tool capabilities and characteristics (Clauses 6

30、 and 7). 2 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. For undated references, the latest edition of the referenced document (including

31、any amendments) applies. ISO/IEC 25010, Systems and software engineering Systems and software Quality Requirements and Evaluation (SQuaRE) System and software quality models 3 T erms a nd definiti ons For the purposes of this document, the following terms and definitions apply. 3.1 quality record re

32、port report which is generated through dynamic test execution and code analysis to record test results and other output Note 1 to entry: Including Test Result, Static Code Analysis Report, Test Incident Report, and Metrics. 3.2 test target version specific version of test target which is used for on

33、e-time execution of Dynamic Test Execution or Code Analysis 3.3 testing tool specific or generic tool which is used for test execution and test management such as test results recording, test results display, test results interpretation, generation of test data, generation of test procedure, generat

34、ion of test scripts, test modelling, etc. 3.4 package namespace for the grouped elements INTERNATIONAL ST ANDARD ISO/IEC 30130:2016(E) ISO/IEC 2016 All rights reserved 1BS ISO/IEC 30130:2016ISO/IEC 30130:2016(E) 4 Object model for software testing tools 4.1 Overview of the object model A software te

35、sting tool is described by its input, process, output and environment. To define software testing tools, the object model for software testing is identified. The object model for software testing tools consists of the following elements: a) test process, which represents processes of dynamic test; b

36、) code analysis process, which represents processes of code analysis; c) test entity, which represents entities that appear in the process; d) test tool, which supports inputs, processes, outputs and test entity. Test Process comprises multiple subprocesses. Each process has input and output. These

37、input and output are basically test entities. Test processes are specified in detail by ISO/IEC/IEEE 29119-2. Code Analysis Process comprises multiple sub processes. Each process has input and output. These input and output are basically test entities. Test Entity comprises multiple entities. The en

38、tity is referred to as Dynamic Test Execution Entity that is required or created in Dynamic Test Process. The entity is referred to as Code Analysis Entity that is required or created in Code Analysis Process. A test entity represents a single performance of a test, in which the target of the test i

39、s tested in various respects. Testing has two modes of execution. Dynamic Test Execution involves actual execution of the code and Code Analysis involves examination of the source code of the target. The testing tools take test entities as input and produce test entities. By producing test entities,

40、 testing tools effectively support the testing process. The object model diagrams, Figures 1 to 5, are described using UML 2 (ISO/IEC 19505-2). Test Process includes Dynamic Test Process and Test Management Process. Code Analysis Process includes Code Analysis Process and Code Analysis Management Pr

41、ocess. Test Entity includes Test Management Entity, Dynamic Test Execution Entity and Code Analysis Entity, and Test Target. Test Tool includes Test Execution Tool and Test Management Tool.2 ISO/IEC 2016 All rights reservedBS ISO/IEC 30130:2016ISO/IEC 30130:2016(E) Figure 1 Object model of software

42、testing Test Process and Test Tool have indirect relationships which are described in Annex A. 4.2 Test target Test Target is a set of source code and executable code of software that is in development. It has a hierarchical structure, and any part of the structure or the whole structure is tested.

43、Test Target Version is a specific version of the software. Figure 2 Object model of the package “Test Target” 4.3 Dynamic test execution entity Dynamic Test Execution Entity is prepared to identify necessary entities which are used in one-time dynamic test execution. Test Data, Test Target Version,

44、Test Result, and Expected Result are identified in this package. In one-time dynamic test execution, Test Environment is used. Test Target Version which is used in one-time dynamic test execution is extracted from an appropriate granularity and version of Test Target. Test Data which is used in one-

45、time dynamic test execution is designed for Test Case which is derived from Specification and is stored on Test Data Collections in Test Data Repository. Specification, Test Case, and Test Target are referred to as input for Dynamic Test Execution. ISO/IEC 2016 All rights reserved 3BS ISO/IEC 30130:

46、2016ISO/IEC 30130:2016(E) Test Data Repository has Test Data which is used by all Dynamic Test Execution and is classified by Objective and Technique. Figure 3 Object model of the package “Dynamic Test Execution Entity” 4.4 Code analysis entity Code Analysis Entity is prepared to identify necessary

47、entities which are used in one-time code analysis. Test Target Version and Code Analysis Result are identified in this package. Test Target Version which is used in one-time code analysis is extracted from an appropriate granularity and version of Test Target. Test Target and Check List which are us

48、ed in Code Analysis are referred to as Input for Code Analysis. Check List usually does not depend on Specification. Figure 4 Object model of the package “Code Analysis Entity” 4.5 Test management entity Test Management Entity is prepared to identify necessary packages and entities which are used to

49、 manage the entire test processes. Test Plan, Test Asset, Quality Record Report, Test Completion Report ,Verification and Validation Report,and Test Status Report are identified in this package.4 ISO/IEC 2016 All rights reservedBS ISO/IEC 30130:2016ISO/IEC 30130:2016(E) Dynamic Test Execution Documentation and Static Code Analysis Report are referred to as Quality Record Report. Dynamic Test Execution Documentation is composed by Metric, Test Result, and Test Incident Report. Static