IEEE standard for software maintenance.pdf
《IEEE standard for software maintenance.pdf》由会员分享,可在线阅读,更多相关《IEEE standard for software maintenance.pdf(54页珍藏版)》请在三一文库上搜索。
1、 IEEE Std 1219-1998 (Revision of IEEE Std 1219-1992) IEEE Std 1219-1998 IEEE Standard for Software Maintenance IEEE Computer Society Sponsored by the Software Engineering Standards Committee 21 October 1998SH94568 Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS
2、under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 02:50:11 MDTNo reproduction or networking permitted without license from IHS -,-,- The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright
3、 1998 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 1998. Printed in the United States of America. ISBN 0-7381-0336-5 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written p
4、ermission of the publisher. IEEE Std 1219-1998 (Revision of IEEE Std 1219-1992) IEEE Standard for Software Maintenance Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 25 June 1998 IEEE-SA Standards Board Abstract: The process for managing and executing software
5、 maintenance activities is described. Keywords: life cycle, maintenance, software, software maintenance Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 02:50:11 MDTN
6、o reproduction or networking permitted without license from IHS -,-,- IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinat- ing Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without comp
7、ensation. 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 inter- est in participating in the development of the s
8、tandard. 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 Standard. Furthermore, the viewpoint expressed at the
9、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 sub- jected to review at least every ve years for revision or reafrmation. When a document is more than ve y
10、ears old and has not been reafrmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reect 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 Standard
11、s are welcome from any interested party, regardless of membership afliation with IEEE. Suggestions for changes in documents 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 po
12、rtions of standards as they relate to specic 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 rep- resent a consensus of all concerned interests, it is important to ensure th
13、at any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously
14、 received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photocopy portions of any individual standard for internal or personal use is g
15、ranted 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, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8
16、400. Permission to photocopy portions of any individual standard for educational class- room use can also be obtained through the Copyright Clearance Center. Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights.
17、By publication of this standard, 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 patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal v
18、alidity or scope of those patents that are brought to its attention. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 02:50:11 MDTNo reproduction or networking permit
19、ted without license from IHS -,-,- Copyright 1998 IEEE. All rights reserved. iii Introduction (This introduction is not a part of IEEE Std 1219-1998, IEEE Standard for Software Maintenance.) This standard describes the process for managing and executing software maintenance activities. Clause 2 list
20、s references to other standards useful in applying this standard. Clause 3 provides a set of denitions and acronyms that are either not found in other standards, or have been modied for use with this standard. Clause 4 contains required information pertaining to the software maintenance process. In
21、order to be in compliance with this standard, Clause 4 must be adhered to. Annex A, Maintenance guidelines, contains additional information that is not required for compliance. Top- ics in this annex include: the source of maintenance forms discussed in the standard, validation and verica- tion (V i
22、.e., software quality assurance (SQA), software conguration management (SCM), and verication and validation (V b)Analysis; c)Design; d)Implementation; e)Regression/system testing; f)Acceptance testing; and g)Delivery. These phases are graphically depicted in Table 2. Software maintenance factors in
23、Table 3 are the entities qualied by the associated metrics/measures identied for each phase. 4.1 Problem/modication identication, classication, and prioritization In this phase, software modications are identied, classied, and assigned an initial priority ranking. Each modication request (MR) shall
24、be evaluated to determine its classication and handling priority. Classica- tion shall be identied from the following maintenance types: a)Corrective; b)Adaptive; c)Perfective; and d)Emergency. Metrics/measures and associated factors identied for this phase should be collected and reviewed at appro-
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE standard for software maintenance
链接地址:https://www.31doc.com/p-3770595.html