BS-7925-2-1998.pdf
《BS-7925-2-1998.pdf》由会员分享,可在线阅读,更多相关《BS-7925-2-1998.pdf(58页珍藏版)》请在三一文库上搜索。
1、| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BRITISH STANDARD BS 7925-2:1998 ICS 35.080
2、 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW Software testing Part 2: Software component testing Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 12:43:07 GMT+00:00 2006, Uncontrolled Copy, (c) BSI This British Standard, having been pre
3、pared under the direction of the DISC Board, was published under the authority of the Standards Board and comes into effect on 15 August 1998 BSI 1998 The following BSI references relate to the work on this standard: Committee reference IST/15 Draft for Public Comment 97/644971 DC ISBN 0 580 29556 7
4、 BS 7925-2:1998 Amendments issued since publication Amd. No.DateText affected Committees responsible for this British Standard The preparation of this British Standard was entrusted to Technical Committee IST/15, Software engineering, upon which the following bodies were represented: British Compute
5、r Society Defence Research Agency Institution of Electrical Engineers Lloyds Register of Shipping Ministry of Defence National Computing Centre Ltd. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 12:43:07 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 7925-2:199
6、8 BSI 1998i Contents Page Committees responsibleInside front cover Forewordiii Introduction1 1Scope1 2Normative reference1 3Definitions2 4Process2 5Test case design techniques3 6Test measurement techniques6 Annex A (informative) Process guidelines10 Annex B (informative) Guidelines for testing techn
7、iques and test measurement17 Annex C (informative) Test technique effectiveness48 BibliographyInside back cover Figure 1 Generic component test process2 Figure A.1 Document hierarchy10 Figure A.2 Example of component test strategy12 Figure A.3 Example of project component test plan14 Figure A.4 Exam
8、ple of component test plan14 Figure A.5 Example of test specification15 Figure A.6 Example of component test report16 Figure B.1 Input exam mark17 Figure B.2 Input coursework mark18 Figure B.3 Equivalence partitions and boundaries for total mark18 Figure B.4 Input exam mark23 Figure B.5 Input course
9、work mark23 Figure B.6 Boundary values23 Figure B.7 Equivalence partitions and boundaries24 Figure B.8 State transition diagram26 Figure B.9 STD for manage_display_changes27 Figure B.10 Cause-effect graph30 Figure B.11 Control flow graph for binsearch35 Figure C.1 Partial ordering of structural test
10、 coverage criteria49 Table B.1 Input exam mark19 Table B.2 Input coursework mark19 Table B.3 Invalid inputs20 Table B.4 Valid outputs20 Table B.5 Invalid outputs20 Table B.6 Minimized test case suite22 Table B.7 Input exam mark23 Table B.8 Input coursework mark23 Table B.9 Valid outputs24 Table B.10
11、 Additional test cases25 Table B.11 Additional test cases25 Table B.12 Possible transitions27 Table B.13 manage_display_changes component28 Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 12:43:07 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 7925-2:1998 ii BSI
12、1998 Page Table B.14 Notation for state tables28 Table B.15 State table for the manage_display_changes component28 Table B.16 State table29 Table B.17 Test cases29 Table B.18 Decision table30 Table B.19 Test cases30 Table B.20 Test cases31 Table B.21 Test cases to cover mutations32 Table B.22 Test c
13、ases35 Table B.23 Occurrence of variables and their categories36 Table B.24 du-pairs and their type37 Table B.25 All-c-uses38 Table B.26 All-c-uses38 Table B.27 Test inputs39 Table B.28 Alternative test inputs39 Table B.29 Test inputs40 Table B.30 Test cases40 Table B.31 Test cases40 Table B.32 Test
14、 cases40 Table B.33 Overall set of test cases41 Table B.34 Test cases41 Table B.35 Initial test case set44 Table B.36 LCSAJs44 Table B.37 Additional tests45 Table B.38 New test sets45 Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 12:43:07 GMT+00:00 2006, Uncon
15、trolled Copy, (c) BSI BS 7925-2:1998 BSI 1998iii Foreword This part of BS 7925 was prepared by Technical Committee IST/15. It was developed by a working party of the British Computer Society Specialist Interest Group in Software Testing (BCS SIGIST). A British Standard does not purport to include al
16、l the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i to
17、iv, pages 1 to 50, an inside back cover and a back cover. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 12:43:07 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ivblank Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 12:43:07 G
18、MT+00:00 2006, Uncontrolled Copy, (c) BSI BSI 19981 BS 7925-2:1998 Introduction This standard specifies a process for the testing of software components and techniques for the design and measurement of that testing. It enables users to improve the quality of their software testing and thus the quali
19、ty of their software products. The standard can be used in the context of both the Inspection and testing provisions of BS EN ISO 9001 and the Software coding and testing provisions of BS ISO/IEC 12207. An important attribute of this standard is that it contains objective provisions which make it po
20、ssible to determine whether or not it has been followed in a particular case. The standard includes the concept of measuring testing as well as assessment of whether the testing meets defined targets. As there are many challenges in software testing, the standard is deliberately limited in scope to
21、cover only the lowest level of independently testable software. Because the interpretation of, and name for, this lowest level is imprecise, the term component has been chosen rather than other common terms such as unit, module, or program to avoid confusion with them (see BS 7925-1). 1 Scope This B
22、ritish Standard specifies a process for the testing of software components and techniques for the design and measurement of that testing. This standard is fully applicable to the testing of components written in procedural languages. The functional test case design techniques and test measurement te
23、chniques specified are applicable to all languages. The structural test case design techniques and test measurement techniques specified may not be applicable to non-procedural languages. This standard prescribes the generation of test cases using only valid input data values, i.e. values for which
24、the behaviour of the component under test is defined by its specification. NOTEGood practice in component testing would also include test cases that use invalid input data values as a means of testing the adequacy of the components specification. Formalization of such error guessing is excluded from
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- BS 7925 1998
链接地址:https://www.31doc.com/p-3736253.html