IEEE Std 1044.1-1995 IEEE Standard Classification for Software Anomalies.pdf
《IEEE Std 1044.1-1995 IEEE Standard Classification for Software Anomalies.pdf》由会员分享,可在线阅读,更多相关《IEEE Std 1044.1-1995 IEEE Standard Classification for Software Anomalies.pdf(59页珍藏版)》请在三一文库上搜索。
1、The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright 1996 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 1996. Printed in the United States of America. ISBN 1-55937-697-X IEEE Std 1044.
2、1-1995 IEEE Guide to Classification for Software Anomalies Sponsor Software Engineering Committee of the IEEE Power Engineering Society Approved December 12, 1995 IEEE Standards Board Approved 1 August, 1996 American National Standards Institute Abstract: This guide provides supporting information t
3、o assist users applying the IEEE Std 1044- 1993, IEEE Standard Classification for Software Anomalies, to decide whether to conform com- pletely to or just extract ideas from IEEE Std 1044.1. This guide will enable users of IEEE Std 1044- 1993 to implement and customize IEEE Std 1044-1993 for their o
4、rganization in an effective and ef- ficient manner. Keywords: anomaly, category, classification, software, supporting data item IEEE Standards documents are developed within the Technical Committees of the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Board. Members
5、of the committees serve vol- untarily and without compensation. They are not necessarily members of the Institute. The standards devel- oped within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an
6、 interest in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE
7、Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revi
8、sion or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest editio
9、n of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of member- ship affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretat
10、ions: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a
11、consensus of all concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason IEEE and the members of its technical committees are not able to provide an instant response to interpretation requests except in those
12、 cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photocopy portions of any individual standar
13、d for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Cus- tomer Service, 222 Rosewood Driv
14、e, Danvers, MA 01923 USA; (508) 750-8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copy- right Clearance Center. Note: Attention is called to the possibility that implementation of this standard may require use of subj
15、ect matter covered by patent rights. By publication of this stan- dard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying all patents for which a license may be required by an IEEE standard o
16、r for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. iii Introduction (This introduction is not a part of IEEE Std 1044.1-1995, IEEE Guide to Classification for Software Anomalies.) On most projects, some formality in reporting anomalies all
17、ows you to record the facts and impressions about an anomaly when it is encountered so that it can be understood by someone at a later date. Typically, information about what happened, how it happened, and the environment in which it happened are put into the anomaly reports. IEEE Std 1044-1993 call
18、s this information “supporting data items.” Armed with this information, the anomaly can be reproduced, a fix can be applied, and the new program can be verified not to have the same anomaly symptoms. Many anomaly tracking information systems of this type are well documented, have been used successf
19、ully for years, and are thought of as good anomaly tracking systems. However, when an organization begins to mature, the universal software quality question is asked: “How best can we get rid of the bugs in our products or prevent them from happening?” To effectively answer this question, you need m
20、ore information about the anomalies that have been found in the software. Knowing the date, submitter, software version, and module an anomaly was reported against usually does not point in the direction of problem areas. The information that will facilitate the discovery of “common errors made,” “m
21、ost effective activity to find anomalies,” “the place where anomalies were first introduced,” and other telling facts about your development process comes from classification analysis of each anomaly reported. This is where application of the IEEE Std 1044-1993 classification scheme will prove inval
22、uable. Implementing IEEE Std 1044-1993 can lead to better project management decisions, increased depth of data analysis, and improved software development processes. The consistent historical data allows trend analysis through several releases of the same project, several projects, and/or organizat
23、ions. This historical consistency of data makes it possible to measure the effects of any process changes you implement from release to release, project to project, or organization to organization. Additionally, using a database and change control procedure reduces the labor of tracking changes, ana
24、lyzing data, and providing an audit trail. This guide provides the alternatives and methods for getting the most out of IEEE Std 1044-1993. Many benefits of using IEEE Std 1044-1993 could be obtained by using any classification scheme. However, the big advantage of IEEE Std 1044-1993 is the effort s
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE Std 1044.1-1995 Standard Classification for Software Anomalies 1044.1 1995
链接地址:https://www.31doc.com/p-3659135.html