《ISO-14764-2006.pdf》由会员分享，可在线阅读，更多相关《ISO-14764-2006.pdf（56页珍藏版）》请在三一文库上搜索。
1、 Reference number ISO/IEC 14764:2006(E) IEEE Std 14764-2006 INTERNATIONAL STANDARD ISO/IEC 14764 IEEE Std 14764-2006 Second edition 2006-09-01 Software Engineering Software Life Cycle Processes Maintenance Ingnierie du logiciel Processus du cycle de vie du logiciel Maintenance ISO/IEC 14764:2006(E)
2、IEEE Std 14764-2006 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In dow
3、nloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in th
4、e General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address
5、 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 14764-2006 Standard for Software Engineering Software Life Cycle Processes Maintenance Norme pour ingnierie du logiciel Processus
6、 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. -,-,- ISO/IEC 14764:2006(E) IEEE Std 14764-2006 vi International Standard ISO/IEC 14764:2006(E) In
7、ternational Organization for Standardization/International Electrotechnical Commission Case postale 56 CH-1211 Genve 20 Switzerland IEEE 2006 All rights reserved ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized syst
8、em for worldwide 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 co
9、llaborate in fields 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 Stand
10、ards are drafted 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. Publicatio
11、n as an International 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 pat
12、ent rights. ISO/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-19
13、98. ISO/IEC JTC 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). ISO/IEC 14764:2006(E) IEEE Std 14764-2006 vii IEEE 2006 All rights reserved IEEE Introduction This introduction is not part o
14、f ISO/IEC/IEEE 14764:2005(E), Standard 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
15、, “Information technology Software 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 i
16、n 2002 and 2004. The only mandatory 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
17、/IEC 12207 shalls. This International Standard is the result of the harmonization of ISO/IEC 14764 and IEEE Std 1219-1998.1 Because maintenance consumes a major share of a software life cycle financial resources, it should be an important project consideration. During operation of the software, prob
18、lems may be detected that were not 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 whe
19、n upgrading system components, such 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 techniq
20、ues. This International Standard 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, t
21、echnique, or tool used to create 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 prov
22、ides the details of the Maintenance 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 ab
23、breviations used in this International 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
24、 errata periodically. Interpretations 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
25、. 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 or patent applications for which a license may be required to implement an IEEE standard or for co
26、nducting inquiries into the legal validity or scope of those patents that are brought to its attention. 1 IEEE 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
27、 Std 14764-2006 viii IEEE 2006 All rights reserved Participants 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
28、 balloting committee voted on this 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
29、 Clint Early Christof Ebert John Fendrich 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 Annett
30、e Reilly Garry Roedler Terence Rout 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 Zimmerman When the IEEE-SA Standards Board approved t
31、his standard on 30 March 2006, it had 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 Will
32、iam B. Hopf Lowell G. Johnson Herman 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
33、non-voting IEEE-SA Standards Board liaisons: 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 application1 1.4 Limitations.2 1.5 Con
34、formance2 2 Normative references 2 3 Definitions and terms3 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
35、.5 Outputs.8 5.2 Problem and Modification 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 .
36、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 .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 consideration
37、s.24 6.1 Introduction24 6.2 Types of maintenance25 6.3 Arrangements for maintenance25 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
38、27 6.8 Maintainability.28 6.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
39、 .32 7.2.2 Defining the process32 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 plan33 7.3.3 Maintenance plan topics 34 7.4 Resource analysis 37 7.4.1 Personnel resources38 7.4.2 Envir
40、onment 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 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
41、reserved -,-,- Copyright 2006 IEEE. 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 Intern
42、ational 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. The scope of this International Standard includes maintena
43、nce 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 executing software maintenance activities. Use of this stan
44、dard 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 of maintenance for software while under development, as we
45、ll 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 framework within which generic and specific software maintena
46、nce 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 of technology (tools, techniques, and methods) to software
47、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 maintenance, and provides maintenance planning requirement
48、s. 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 software and additionally for those respo
49、nsible 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 management 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 foll