IEEE 14764-2006 en Software Engineering Software Life Cycle Processes Maintenance (IEEE Computer Society)《软件工程 软件生命周期过程 维护》.pdf

《IEEE 14764-2006 en Software Engineering Software Life Cycle Processes Maintenance (IEEE Computer Society)《软件工程 软件生命周期过程 维护》.pdf》由会员分享，可在线阅读，更多相关《IEEE 14764-2006 en Software Engineering Software Life Cycle Processes Maintenance (IEEE Computer Society)《软件工程 软件生命周期过程 维护》.pdf（57页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference numberISO/IEC 14764:2006(E)IEEEStd 14764-2006INTERNATIONAL STANDARD ISO/IEC14764IEEEStd 14764-2006Second edition2006-09-01Software Engineering Software Life Cycle Processes Maintenance Ingnierie du logiciel Processus du cycle de vie du logiciel Maintenance ISO/IEC 14764:2006(E) IEEE Std 1

2、4764-2006 Standard for Software Engineering Software Life Cycle Processes Maintenance Norme pour ingnierie du logiciel Processus de cycle de vie Sponsor Software the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO memb

3、er bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org ii ISO/IEC 14764:2006(E) IEEE Std 1476

4、4-2006 iv IEEE 2006 All rights reservedAbstract: The process for managing and executing software maintenance activities is described. Keywords: life cycle, maintenance, software, software maintenance This ISO/IEEE document is an International Standard and is copyright-protected by ISO and the IEEE.

5、Except as permitted under the applicable laws of the users country, neither this ISO/IEEE standard nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or otherwise, without prior written permission be

6、ing secured. Requests for permission to reproduce should be addressed to either ISO or the IEEE at the addresses below. ISO Copyright Office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Institute of Electrical and Electronics

7、Engineers Standards Association Manager, Standards Intellectual Property 445 Hoes Lane Piscataway, NJ 08854 E-mail: stds.iprieee.org Web: www.ieee.org Copyright 2006 ISO/IEEE. All rights reserved. Published 19 May 2006. Printed in the United States of America. IEEE is a registered trademark in the U

8、.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. ISO/IEC 14764:2006(E) IEEE Std 14764-2006 vi International Standard ISO/IEC 14764:2006(E) International Organization for

9、Standardization/International Electrotechnical Commission Case postale 56 CH-1211 Genve 20 Switzerland IEEE 2006 All rights reservedISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardizati

10、on. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual

11、interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance

12、with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard

13、requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC/IEEE 14764

14、was prepared by Joint Technical Committee ISO/IEC JTC 1, Subcommittee SC 7, (Software and System Engineering). The first edition of ISO/IEC 14764 was prepared by ISO/IEC JTC 1/SC 7. The current edition is the result of merging the original edition with IEEE Std 1219-1998. ISO/IEC JTC 1/SC 7 and the

15、IEEE Computer Society cooperated in this project to merge the two standards. This second edition cancels and replaces the first edition (1999). ISO/IEC 14764:2006(E) IEEE Std 14764-2006 vii IEEE 2006 All rights reserved IEEE Introduction This introduction is not part of ISO/IEC/IEEE 14764:2005(E), S

16、tandard for Software EngineeringSoftware Life Cycle ProcessesMaintenance. This International Standard provides guidance on the Software Maintenance Process. Software Maintenance is a primary process in the life cycle of a software product, as described in ISO/IEC 12207, “Information technology Softw

17、are life cycle processes.” The Maintenance Process contains the activities and tasks of the maintainer. This International Standard is part of the ISO/IEC 12207 family of documents. In this International Standard, ISO/IEC 12207 refers to ISO/IEC 12207:1995 as amended in 2002 and 2004. The only manda

18、tory clauses in this International Standard come from ISO/IEC 12207. The mandatory clauses contain shalls and each shall from ISO/IEC 12207 that is duplicated in this International Standard is boxed. The related ISO/IEC 12207 clause number is listed after the boxed ISO/IEC 12207 shalls. This Interna

19、tional Standard is the result of the harmonization of ISO/IEC 14764 and IEEE Std 1219-1998.1Because maintenance consumes a major share of a software life cycle financial resources, it should be an important project consideration. During operation of the software, problems may be detected that were n

20、ot detected during validation and acceptance. Therefore, a maintenance effort is needed to cope with these problems. This maintenance effort also covers software improvements needed to meet new or modified user requirements. Software maintenance is commonly needed when upgrading system components, s

21、uch as operating systems and databases, as well as when modifications are made to external software and systems interfaces. Software maintenance may be a significant portion of life cycle costs. Software maintainers use a number of specific tools, methods, and techniques. This International Standard

22、 does not specify how to implement or perform the activities and tasks in the Software Maintenance Process since these are dependent upon the formal agreement and organizational requirements. Maintenance is required on all types of software, whatever the technology, technique, or tool used to create

23、 it. Clause 1 provides the scope of this International Standard. Clause 2 provides conformance information. Clause 3 provides normative references. Clause 4 provides terms and definitions. Clause 5 provides the application of this International Standard. Clause 6 provides the details of the Maintena

24、nce Process. Clause 7 provides execution considerations for the Maintenance Process. Clause 8 provides the software maintenance strategy. Annex A provides a cross reference between clauses in this International Standard and ISO/IEC 12207. Annex B provides a list of abbreviations used in this Interna

25、tional Standard. Annex C provides a bibliography. Notice to users Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/ standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpreta

26、tions Current interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/ index.html.Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard

27、, 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 or patent applications for which a license may be required to implement an IEEE standard or for conducting inquiries into the legal

28、 validity or scope of those patents that are brought to its attention. 1IEEE publications are available from the Institute of Electrical and Electronics Engineers, Inc., 445 Hoes Lane, Piscataway, NJ 08854, USA (http:/standards.ieee.org/). ISO/IEC 14764:2006(E) IEEE Std 14764-2006 viii IEEE 2006 All

29、 rights reservedParticipants At the time this standard was completed, the Software Maintenance Working Group had the following membership: Paul Croll, Chair Thomas Pigoski, Editor James W. Moore, Liaison to ISO/IEC JTC 1/SC 7 The following members of the individual balloting committee voted on this

30、standard. Balloters may have voted for approval, disapproval, or abstention. Edward Bartlett Bakul Banerjee Juris Borzovs Curtis Browne Bruce Bullock Joseph Butchko Keith Chow Antonio M. Cicu Todd Cooper Paul Croll Geoffrey Darnton Guru Dutt Dhingra Einar Dragstedt Clint Early Christof Ebert John Fe

31、ndrich Gregg Giesler John Garth Glynn Lewis Gray Michael Grimley Victoria Hailey John Horch Peeya Iwagoshi William Junk Joerg Kampmann Piotr Karocki Ron Kenett J. Dennis Lawrence Carol Long James Moore Jeremy Moore Richard Moore Rajesh Moorkath Gerald Radack Annette Reilly Garry Roedler Terence Rout

32、 James Ruggieri James Sanders Robert J. Schaaf David Schultz Carl Singer Mike Smith Mitchell Smith Luca Spotorno Thomas Starai Richard Thayer Scott Valcourt John Walz Oren Yuen Janusz Zalewski Li Zhang Geraldine ZimmermanWhen the IEEE-SA Standards Board approved this standard on 30 March 2006, it ha

33、d the following membership: Steve M. Mills, Chair Richard H. Hulett, Vice Chair Don Wright, Past Chair Judith Gorman, Secretary Mark D. Bowman Dennis B. Brophy Joseph Bruder Richard Cox Bob Davis Julian Forster* Joanna N. Guenin Mark S. Halpin Raymond Hapeman William B. Hopf Lowell G. Johnson Herman

34、 Koch Joseph L. Koepfinger* David J. Law Daleep C. Mohla Paul Nikolich T. W. Olsen Glenn Parsons Ronald C. Petersen Gary S. Robinson Frank Stone Malcolm V. Thaden Richard L. Townsend Joe D. Watson Howard L. Wolfman *Member Emeritus Also included are the following non-voting IEEE-SA Standards Board l

35、iaisons: Satish K. Aggarwal, NRC Representative Richard DeBlasio, DOE Representative Alan H. Cookson, NIST Representative Mike Fisher IEEE Standards Project Editor CONTENTS 1 Overview.1 1.1 Scope .1 1.2 Purpose 1 1.3 Field of application 1 1.4 Limitations.2 1.5 Conformance2 2 Normative references 2

36、3 Definitions and terms 3 4 Application of this International Standard.4 4.1 Maintenance Process4 4.2 Organization of this International Standard .5 5 Maintenance Processes5 5.1 Process Implementation.6 5.1.1 Inputs .6 5.1.2 Tasks7 5.1.3 Controls8 5.1.4 Support.8 5.1.5 Outputs.8 5.2 Problem and Modi

37、fication Analysis 9 5.2.1 Inputs .9 5.2.2 Tasks9 5.2.3 Controls12 5.2.4 Support.12 5.2.5 Outputs.12 5.3 Modification Implementation 13 5.3.1 Inputs .13 5.3.2 Tasks13 5.3.3 Controls14 5.3.4 Support.14 5.3.5 Outputs.15 5.4 Maintenance Review/Acceptance15 5.4.1 Inputs .15 5.4.2 Tasks15 5.4.3 Controls16

38、 5.4.4 Support.16 5.4.5 Outputs.17 5.5 Migration .17 5.5.1 Inputs .17 5.5.2 Tasks17 5.5.3 Controls20 5.5.4 Support.20 5.5.5 Outputs.21 5.6 Software retirement21 5.6.1 Inputs .21 5.6.2 Tasks22 5.6.3 Controls24 5.6.4 Support.24 5.6.5 Outputs.24 6 Execution considerations.24 6.1 Introduction24 6.2 Type

39、s of maintenance 25 6.3 Arrangements for maintenance 25 ISO/IEC 14764:2006(E) IEEE Std 14764-2006 ix IEEE 2006 All rights reserved 6.4 Tools for maintenance .26 6.5 Software maintenance measurement .27 6.6 Documentation of process .27 6.7 Early involvement in development 27 6.8 Maintainability.28 6.

40、8.1 Maintainability and the development process28 6.8.2 Maintainability and specific activities in the development process.29 6.9 Software transition.30 6.10 Documentation.31 7 Software maintenance strategy31 7.1 Introduction .31 7.2 The maintenance concept 32 7.2.1 Scope .32 7.2.2 Defining the proc

41、ess 32 7.2.3 Designation of who will provide maintenance.32 7.2.4 Estimate of maintenance costs.33 7.3 Maintenance planning33 7.3.1 Introduction33 7.3.2 The maintenance plan 33 7.3.3 Maintenance plan topics 34 7.4 Resource analysis 37 7.4.1 Personnel resources38 7.4.2 Environment resources 38 7.4.3

42、Financial resources 38 Annex A (informative) Cross-reference between ISO/IEC/IEEE 14764 and ISO/IEC 12207 and ISO/IEC 12207 Amd 139 Annex B (informative) Abbreviations.42 Annex C (informative) Bibliography.43 ISO/IEC 14764:2006(E) IEEE Std 14764-2006 x IEEE 2006 All rights reservedCopyright 2006 IEE

43、E. All rights reserved 1 Standard for Software Engineering Software Life Cycle Processes Maintenance 1 Overview This International Standard describes in greater detail management of the Maintenance Process described in ISO/IEC 12207, including Amendments. This International Standard also establishes

44、 definitions for the various types of maintenance. This International Standard provides guidance that applies to planning, execution and control, review and evaluation, and closure of the Maintenance Process. The scope of this International Standard includes maintenance for multiple software product

45、s with the same maintenance resources. “Maintenance” in this International Standard means software maintenance unless otherwise stated. 1.1 Scope This standard describes an iterative process for managing and executing software maintenance activities. Use of this standard is not restricted by size, c

46、omplexity, criticality, or application of the software product. This standard uses a process model to discuss and depict each phase of software maintenance. The criteria established apply to both the planning of maintenance for software while under development, as well as the planning and execution

47、of software maintenance activities for existing software products. Ideally, maintenance planning should begin during the stage of planning for software development. This International Standard provides the framework within which generic and specific software maintenance plans may be executed, evalua

48、ted, and tailored to the maintenance scope and magnitude of given software products. This International Standard provides the framework, precise terminology, and processes to allow the consistent application of technology (tools, techniques, and methods) to software maintenance. This International S

49、tandard provides guidance for the maintenance of software. The basis for the Maintenance Process and its activities comes from the definitions of ISO/IEC 12207. It defines the activities and tasks of software maintenance, and provides maintenance planning requirements. It does not address the operation of software and the operational functions, e.g., backup, recovery, system administration, which are normally performed by those who operate the software. This International Standard is written primarily for maintainers of s