欢迎来到三一文库! | 帮助中心 三一文库31doc.com 一个上传文档投稿赚钱的网站
三一文库
全部分类
  • 研究报告>
  • 工作总结>
  • 合同范本>
  • 心得体会>
  • 工作报告>
  • 党团相关>
  • 幼儿/小学教育>
  • 高等教育>
  • 经济/贸易/财会>
  • 建筑/环境>
  • 金融/证券>
  • 医学/心理学>
  • ImageVerifierCode 换一换
    首页 三一文库 > 资源分类 > PDF文档下载
     

    IEEE-1044-1993-R2002.pdf

    • 资源ID:3771477       资源大小:432.96KB        全文页数:32页
    • 资源格式: PDF        下载积分:6
    快捷下载 游客一键下载
    会员登录下载
    微信登录下载
    三方登录下载: 微信开放平台登录 QQ登录   微博登录  
    二维码
    微信扫一扫登录
    下载资源需要6
    邮箱/手机:
    温馨提示:
    用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)
    支付方式: 支付宝    微信支付   
    验证码:   换一换

    加入VIP免费专享
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    IEEE-1044-1993-R2002.pdf

    The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright Ó 1994 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 1994. Printed in the United States of America. ISBN 1-55937-383-0 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Std 1044-1993 IEEE Standard ClassiÞcation for Software Anomalies Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved December 2, 1993 IEEE Standards Board Abstract: A uniform approach to the classification of anomalies found in software and its documen- tation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classiÞcations and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to deÞne pro- cedural or format requirements for using the classiÞcation scheme. It does identify some classiÞca- tion measures and does not attempt to deÞne all the data supporting the analysis of an anomaly. Keywords: anomaly, category, classification, classification process, supporting data item Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- Print: ISBN 1-55937-708-9, SH94399 PDF: ISBN 0-7381-0406-X, SS94399 IEEE Std 1044-1993(R2002) Reaffirmed September 11, 2002 IEEE Standards documents are developed within the Technical Committees of the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed 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 interest in partici- pating 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, mar- ket, or provide other goods and services related to the scope of the IEEE 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 Þve years for revision or reafÞrmation. When a document is more than Þve years old and has not been reafÞrmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reßect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership afÞliation with IEEE. Suggestions for changes in docu- ments should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to speciÞc applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appro- priate responses. Since IEEE Standards represent a consensus of all concerned inter- ests, 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 com- mittees are not able to provide an instant response to interpretation requests except in those 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 IEEE standards documents may involve the use of patented technology. Their approval by the Institute of Electrical and Electronics Engineers does not mean that using such technology for the purpose of conforming to such standards is authorized by the patent owner. It is the obligation of the user of such technology to obtain all necessary permissions. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- iii Introduction (This introduction is not a part of IEEE Std 1044-1993, IEEE Standard ClassiÞcation for Software Anomalies.) This standard provides a uniform approach to the classiÞcation of anomalies found in software and its documentation. It describes the processing of anomalies discovered during any software life cycle phase, and it provides comprehensive lists of software anomaly classiÞcations and related data items that are helpful to identify and track anomalies. The minimum set of classiÞcations deemed necessary for a complete data set are indicated as mandatory. More detailed classiÞcations are provided for those projects that require more rigor. These lower levels of detail are shown as optional. Application of less than the mandatory set of classiÞcations is not recommended as this may result in insufÞcient detail for meaningful data collection and analysis. Some guidelines on how to apply the standard are provided in 4.1. In addition, annex A provides an example anomaly reporting mechanism that describes how to apply the classiÞcation scheme. The classiÞcation scheme in this standard considers the environment and activity in which the anomaly occurred, the symp- toms of the anomaly, the software or system cause of the anomaly, whether the anomaly is a problem or an enhancement request, where the anomaly originated (by phase and document), the resolution and disposition of the anomaly, the impact of several aspects of the anomaly, and the appropriate corrective action. Collecting the data described in this standard provides valuable information that has many useful applica- tions. Software is usually the most expensive item in computer systems. It is also well documented that the earlier within the software life cycle a problem is discovered, the cheaper it is to Þx. This encourages the use of tools, techniques, and methodologies to Þnd problems sooner. Standard anomaly data is necessary to eval- uate how well these tools, techniques, and methodologies work. This data can also identify when in a projectÕs life cycle most problems are introduced. Distinctions between enhancements and problems in the software help make the decisions as to which anomalies are addressed Þrst, category of funding, etc. Anom- aly data can also assist in the evaluation of reliability and productivity measures. At the time this standard was completed, the ClassiÞcation Standards Working Group had the following membership: Richard Evans, Chair Cynthia Brehmer, Co-chair Jaya Carl, Secretary John B. BowenMyron LipowDavid Simkins Lynn K. BrodersonMary MikhailVijaya Srivastava Linda ClemensPatricia PrattTheodore Sullivan Richard J. GaleDavid SchuckerGreg Ward Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- iv The following persons were on the balloting committee: A. Frank AckermanAnne GeraciGeraldine Neidhart Eleanor AntreassianJean A. GilmoreDennis Nickle Bruce M. BakkenShirley A. Gloss-SolerMichael T. Perkins Jack N. BarnardPaul GrizenkoWilliam E. Perry Boris BeizerL. M. GuntherRon Pfaff H. R. BerlackVirl HaasDonald J. Pfeiffer Barry BoehmPeter J. HarveyJohn N. Postak Kathleen L. BriggsJohn HorchRobert M. Poston Christian BrunelleLaurel V. KaledaJock Rader Fletcher J. BuckleyAdi KasadArthur S. Robinson Elliot J. ChikofskyR. A. KesslerFrances A. Ruhlman Jung K. ChungTom KuriharaMargaret Rumley Francois CoallierLak-Ming LamNorman Schneidewind Stewart CrawfordJohn B. LaneLeonard W. Seagren Patricia W. DaggettRobert A. LaneHarlan K. Seyfer James DobbinsF. C. LimAnthony F. J. Sgarlatti David DotyBen LivsonRobert W. Shillato William P. DuprasDonald LundryJacob Slonim Robert E. DwyerAustin J. MaherWayne Smith Kenneth DymondKartik C. MajumdarTerrence L. Tillmanns Caroline L. EvansDavid M. MarksDavid B. Turner James R. EvansPhilip C. MarriottWilliam Stephen Turner John W. FendrichDarrell MarshRalph Wachter Glenn S. FieldsGlen A. MeldrumDolores R. Wallace Violet FoldesEdward F. MillerJohn P. Walter Kenneth A. FosterCelia H. ModellAndrew H. Weigel Richard FriesGary D. MoorheadBill Wong David GelperinGene T. MorunDennis L. Wood Robert C. Natale When the IEEE Standards Board approved this standard on December 2, 1993, it had the following membership: Wallace S. Read, Chair Donald C. Loughry, Vice Chair Andrew G. Salem, Secretary Gilles A. BarilJim IsaakDon T. Michael* Jos A. Berrios de la PazBen C. JohnsonMarco W. Migliaro Clyde R. CampWalter J. KarplusL. John Rankine Donald C. FleckensteinLorraine C. KevraArthur K. Reilly Jay Forster*E. G. ÒAlÓ KienerRonald H. Reimer David F. FranklinIvor N. KnightGary S. Robinson Ramiro GarciaJoseph L. KoepÞnger*Leonard L. Tripp Donald N. HeirmanD. N. ÒJimÓ LogothetisDonald W. Zipse *Member Emeritus Also included are the following nonvoting IEEE Standards Board liaisons: Satish K. Aggarwal James Beall Richard B. Engelman David E. Soffrin Stanley I. Warshaw Rachel A. Meisel IEEE Standards Project Editor Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- v Contents CLAUSEPAGE 1.Overview 1 1.1 Background 1 1.2 Scope2 2.References2 3.Definitions3 4.Classification standard.4 4.1 Classification process.4 4.2 Standard classification scheme 6 Annex AExample anomaly report 24 Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- IEEE Std 1044-1993IEEE STANDARD CLASSIFICATION vi Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- 1 IEEE Standard ClassiÞcation for Software Anomalies 1. Overview 1.1 Background This standard is based on several deÞnitions, concepts, and processes that need to be understood prior to its use. These are discussed in the following paragraphs. Formal deÞnitions can be found in clause 3. A key term in this standard is anomaly. An anomaly is any condition that departs from the expected. This expectation can come from documentation (requirements speciÞcations, design documents, user documents, standards, etc.) or from someoneÕs perceptions or experiences. An anomaly is not necessarily a problem in the software product; it may be manifesting correct behavior in which case changing the software would be an enhancement. An anomaly may also be caused by something other than the software. For reasons of semantics, use of the word anomaly is preferred over the words error, fault, failure, incident, ßaw, problem, gripe, glitch, defect, or bug throughout this standard because it conveys a more neutral connotation. The methodology of this standard is based on a process (sequence of steps) that pursues a logical progres- sion from the initial recognition of an anomaly to its Þnal disposition. Each step interrelates with and sup- ports the other steps. This process is graphically displayed in Þgure 1, and a complete discussion of the classiÞcation process is in 4.1. This standard does not attempt to enforce any particular anomaly processing procedure other than to identify the basic processes an anomaly goes through. It is expected that users will modify the process based on their organizationÕs procedures. Subclause 4.2 describes the classiÞcation scheme and supporting data items useful for identifying, tracking, and resolving anomalies. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=O'Connor, Maurice Not for Resale, 04/28/2007 20:25:32 MDTNo reproduction or networking permitted without license from IHS -,-,- IEEE Std 1044-1993IEEE STANDARD CLASSIFICATION 2 1.2 Scope This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and Þrmware during any phase of a systemÕs life cycle. This standard deÞnes the minimum requirements for classifying anomalies, as well as providing additional classi- Þcations for projects requiring greater detail. The mandatory classiÞcations are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classiÞcation task, this standard documents the following subjects: a)DeÞnitions of terms not provided in IEEE Std 610.12-1990 1 b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information c)A standard set of categories and classiÞcations, either mandatory or optional d)A list of supporting data items This standard identiÞes those essential (mandatory) categories needed to establish a common deÞnition. The categories provide a common terminology and concepts to communicate among projects, software develop- ment environments, and personnel. It is assumed that all applicable classiÞcations within a mandatory cate- gory shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identiÞed as optional. This standard is n

    注意事项

    本文(IEEE-1044-1993-R2002.pdf)为本站会员(哈尼dd)主动上传,三一文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知三一文库(点击联系客服),我们立即给予删除!

    温馨提示:如果因为网速或其他原因下载失败请重新下载,重复下载不扣分。




    经营许可证编号:宁ICP备18001539号-1

    三一文库
    收起
    展开