IEEE 829-2008 en Standard for Software and System Test Documentation (IEEE Computer Society)《软件和系统试验文件》.pdf
《IEEE 829-2008 en Standard for Software and System Test Documentation (IEEE Computer Society)《软件和系统试验文件》.pdf》由会员分享,可在线阅读,更多相关《IEEE 829-2008 en Standard for Software and System Test Documentation (IEEE Computer Society)《软件和系统试验文件》.pdf(132页珍藏版)》请在麦多课文档分享上搜索。
1、IEEE Std 829-2008(Revision ofIEEE Std 829-1998)IEEE Standard for Software andSystem Test DocumentationIEEE3 Park AvenueNew York, NY 10016-5997, USA18 July 2008IEEE Computer SocietySponsored by theSoftware +1 978 750 8400. Permission to photocopy portions of any individual standard for educational cl
2、assroom use can also be obtained through the Copyright Clearance Center.iv Copyright 2008 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std 829-2008, IEEE Standard for Software and System Test Documentation. Software and software-based systems testing is a technical d
3、iscipline of systems engineering. The purpose of software and software-based systems testing is to help the development organization build quality into the software and system during the life cycle processes and to validate that the quality was achieved. The test process determines whether the produ
4、cts of a given life cycle activity conform to the requirements of that activity, and whether the product satisfies its intended use and user needs. This determination can include inspection, demonstration, analysis, and testing of software and software-based system products. Test activities are perf
5、ormed in parallel with software and system development, not just at the conclusion of the development effort. The test activities provide objective data and conclusions about software and system quality. This feedback can include anomaly identification, performance measurement, and identification of
6、 potential quality improvements for expected operating conditions across the full spectrum of the software-based systems and their interfaces. Early feedback allows the development organization to modify the products in a timely fashion and thereby reduce overall project and schedule impacts. Withou
7、t a proactive approach, anomalies and associated changes are typically delayed to later in the schedule, resulting in greater costs and schedule delays. This revision of the standard makes significant changes from the prior version. The following is a summary of the changes: Changed focus from being
8、 document-focused to being process-focused in keeping with IEEE/EIA Std 12207.0TM-1996awhile retaining information on test documentation. Added the concept of an integrity level to assist organizations in determining a recommended minimum set of testing tasks and concurrent selection of test documen
9、tation needed to support the tasks. Identified minimum recommended tasks for the sample integrity level scheme. Added an activity for choosing appropriate documents and contents. Added a Master Test Plan (MTP) for documenting the actual management of the total test effort. Added a Level Interim Test
10、 Status Report to be issued during the test execution activity. Added a Master Test Report for when there are multiple Level Test Reports that need consolidation. The Master Test Report may also summarize the results of the tasks identified in the Master Test Plan. Identified sample metrics in Annex
11、 E. Added the concept of independence in Annex F. The following key concepts are emphasized in this standard: Integrity levels. Defines four integrity levels (ranging from high integrity to low integrity) to describe the importance of the software and the software-based system to the user. aIEEE pub
12、lications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854, USA (http:/standards/ieee.org/). v Copyright 2008 IEEE. All rights reserved. Recommended minimum testing tasks for each integrity level. Defines the recommended minimum testing ta
13、sks required for each of the four integrity levels. Includes a table of optional testing tasks for tailoring the test effort to meet project needs and application specific characteristics. Intensity and rigor applied to testing tasks. Introduces the notion that the intensity and rigor applied to the
14、 testing tasks vary according to the integrity level. Higher integrity levels require the application of greater intensity and rigor to the testing tasks. Intensity includes greater scope of testing across all normal and abnormal system operating conditions. Rigor includes more formal techniques and
15、 recording procedures. Detailed criteria for testing tasks. Defines specific criteria for each testing task, including recommended minimum criteria for correctness, consistency, completeness, accuracy, readability, and testability. The testing task descriptions include a list of the required task in
16、puts and outputs. Systems viewpoint. Includes recommended minimum testing tasks to respond to system issues. Selection of test documentation. Both the types of test documentation and the content topics within each documentation type need to be selected based on the testing tasks associated with the
17、identified integrity level. Compliance with International and IEEE Standards. Defines the test processes to be compliant with life cycle process standards such as ISO/IEC 12207:1995,bIEEE Std 1074TM-2006 and IEEE/EIA Std 12207.0-1996 as well as the entire family of IEEE software and systems engineer
18、ing standards. This standard supports the full software life cycle processes, including acquisition, supply, development, operation, and maintenance. The standard is compatible with all life cycle models; however, not all life cycle models use all of the life cycle processes described in this standa
19、rd. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or ref
20、erring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available
21、for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities
22、 and private users, the IEEE does not waive any rights in copyright to this document. bISO/IEC publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Varemb, CH-1211, Genve 20, Switzerland/Suisse (http:/www.iso.ch/). ISO/IEC publications are also available in the Unit
23、ed States from Global Engineering Documents, 15 Inverness Way East, Englewood, Colorado 80112, USA (http:/ Electronic copies are available in the United States from the American National Standards Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http:/www.ansi.org/). vi Copyright
24、2008 IEEE. All rights reserved. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE docume
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE8292008ENSTANDARDFORSOFTWAREANDSYSTEMTESTDOCUMENTATIONIEEECOMPUTERSOCIETY 软件 系统 试验 文件 PDF

链接地址:http://www.mydoc123.com/p-1248951.html