Software engineering — Software life cycle processes — Maintenance
Introduction: This document provides guidance on the software maintenance process. Maintenance is a technical process in the life cycle of a software product, as described in ISO/IEC/IEEE 12207. The maintenance process contains the activities and tasks of the maintenance organization. This document is the result of the harmonization of ISO/IEC 14764 and IEEE Std 1219, and the update for ISO/IEC/IEEE 12207:2017. 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, problems may be detected that were not detected during verification, 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, such as operating systems and databases, as well as when changes are made to external software and systems’ interfaces. Software maintenance is typically a significant portion of life cycle costs, even when a part of the system under maintenance includes COTS software. Software maintenance organizations uses a number of specific tools, methods, and techniques. This document 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. Maintenanc
Scope: 1.1 Overview This document provides guidance for the maintenance of software, based on the maintenance process and its activities and tasks defined in ISO/IEC/IEEE 12207:2017, 6.4.13. Moreover, this document describes the maintenance process in greater detail and establishes definitions for the various types of maintenance. This includes maintenance for multiple software products with the same maintenance resources. “Maintenance” in this document means software maintenance unless otherwise stated. The document 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. However, it does include the related disposal process defined in ISO/IEC/IEEE 12207:2017, 6.4.14. This document is written primarily for managers, maintenance organizations, quality managers, users and acquirers of systems containing software. Many of the activities and tasks discussed in this document apply equally to maintenance services, as well as to maintained software products. For example, in a COTS intensive system, maintenance services are performed to sustain the product in operations. While the scope of this document is software maintenance, hardware and hardware costs are important considerations for maintenance. 1.2 Purpose This document provides guidance on the maintenance process. It identifies how the maintenance process can be invoked during acquisition and operation. This document 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. 1.3 Field of application This document is intended to provide guidance for the planning for and maintenance of software products or services, whether performed internally or externally to an organization. It is not intended to apply to the operation of the software. This document is intended to provide guidance for two-party situations and can be equally applied where the two parties are from the same organization. This document is intended to also be used by a single party as self-imposed tasks (ISO/IE