1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58Maintenance ICS 35.080Software Engineering Software life cycle processes BRITISH STANDARDBS ISO/IEC
2、 14764:2006BS ISO/IEC 14764:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2006 BSI 2006ISBN 0 580 46596 9Amendments issued since publicationAmd. No. Date CommentsThis publication does not purport to include all the necessary
3、provisions of a contract. Users are responsible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations. National forewordThis British Standard was published by BSI. It is the UK implementation of ISO/IEC 14764:2006. It supersedes BS ISO/IEC 14764
4、:1999 which is withdrawn.The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering.A list of organizations represented on IST/15 can be obtained on request to its secretary.Reference numberISO/IEC 14764:2006(E)IEEEStd 14764-2006INTERNATIONA
5、L 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 BS ISO/IEC 14764:2006ii Standard for Software Engineering Software Life Cycle Processes Maintenance
6、Norme pour ingnierie du logiciel Processus de cycle de vie Sponsor Software +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. BS ISO/IEC 14764:2006vi International Standard ISO/IEC 1
7、4764:2006(E) International Organization for Standardization/International Electrotechnical Commission Case postale 56 CH-1211 Genve 20 Switzerland ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwid
8、e standardization. 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 fi
9、elds of mutual 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
10、 in accordance 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 Internat
11、ional Standard 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/
12、IEC/IEEE 14764 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
13、1/SC 7 and the IEEE Computer Society cooperated in this project to merge the two standards. This second edition cancels and replaces the first edition (1999). BS ISO/IEC 14764:2006viiIEEE Introduction This introduction is not part of ISO/IEC/IEEE 14764:2005(E), Standard for Software EngineeringSoftw
14、are 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 Software life cycle processes.” The Mainte
15、nance 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 mandatory clauses in this International St
16、andard 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 International Standard is the result of the
17、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 not detected during validation and acc
18、eptance. 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, such as operating systems and database
19、s, 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 does not specify how to implement or
20、 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 it. Clause 1 provides the scope of t
21、his 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 Maintenance Process. Clause 7 provides execut
22、ion 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 International Standard. Annex C provides a b
23、ibliography. 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. Interpretations Current interpretations can be
24、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, no position is taken with respect t
25、o 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 validity or scope of those patents t
26、hat 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/). BS ISO/IEC 14764:2006viii Participants At the time this standard was completed, the Software Main
27、tenance 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 standard. Balloters may have voted for approval, disapproval, or abstention. Edward Bar
28、tlett 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 Fendrich Gregg Giesler John Garth Glynn Lewis Gray Michael Grimley Victoria Hailey John H
29、orch 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 James Ruggieri James Sanders Robert J. Schaaf David Schultz Carl Singer Mike Smith Mit
30、chell 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 had the following membership: Steve M. Mills, Chair Richard H. Hulett, Vice Chair Don Wri
31、ght, 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 Koch Joseph L. Koepfinger* David J. Law Daleep C. Mohla Paul Nikolich T. W. Olsen Glen
32、n 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 liaisons: Satish K. Aggarwal, NRC Representative Richard DeBlasio, DOE Representative Al
33、an H. Cookson, NIST Representative Mike Fisher IEEE Standards Project Editor BS ISO/IEC 14764:2006CONTENTS 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 3 Definitions and terms 3 4 Application of this International Stan
34、dard.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 Modification Analysis 9 5.2.1 Inputs .9 5.2.2 Tasks9 5.2.3 Controls12
35、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 5.4.4 Support.16 5.4.5 Outputs.17 5.5 Migration .17 5.5.1 Inputs
36、.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 Types of maintenance 25 6.3 Arrangements for maintenance 25 ixBS ISO/I
37、EC 14764:20066.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.8.1 Maintainability and the development process28 6.8.2 Maintainability and specific activities in the development pro
38、cess.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 process 32 7.2.3 Designation of who will provide maintenance.32 7.2.4 Estimate of maintenance costs.33 7.3 Maintenance pla
39、nning33 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 Financial resources 38 Annex A (informative) Cross-reference between ISO/IEC/IEEE 14764 and ISO/IEC 12207 and ISO/IEC
40、12207 Amd 139 Annex B (informative) Abbreviations.42 Annex C (informative) Bibliography.43 x BS ISO/IEC 14764:20061 Standard for Software Engineering Software Life Cycle Processes Maintenance 1 Overview This International Standard describes in greater detail management of the Maintenance Process des
41、cribed in ISO/IEC 12207, including Amendments. This International Standard also establishes 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.
42、The scope of this International Standard includes maintenance for multiple software products 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 e
43、xecuting software maintenance activities. Use of this standard is not restricted by size, complexity, 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
44、of maintenance for software while under development, as well as the planning and execution 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 fra
45、mework within which generic and specific software maintenance plans may be executed, evaluated, 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 o
46、f technology (tools, techniques, and methods) to software maintenance. This International Standard 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
47、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 fo
48、r maintainers of software and additionally for those responsible for development and quality assurance. It may also be used by acquirers and users of systems containing software who may provide inputs to the maintenance plan. 1.2 Purpose This International Standard provides guidance on the managemen
49、t of (or how to perform) the Maintenance Process. It identifies how the Maintenance Process can be invoked during acquisition and operation. This lnternational Standard also emphasizes the following in the Maintenance Process: the maintainability of software products; the need for maintenance service models; and the need for a maintenance strategy and plan. 1.3 Field of application This International Standard is intended to provide guidance for the planning for and maintenance of software products or services, whether performed internally or externally
