ISO IEC IEEE 14764-2022 pdf free download – Software engineering — Software life cycle processes — Maintenance.
1.4 Limitations
This document describes the framework of the maintenance process but does not specify the details ofhow to implement or perform the activities and tasks included in the process.
ln this document, there are a number of lists. None of these is presumed to be exhaustive. They areintended as examples.
2Normative references
The following documents are referred to in the text in such a way that some or all of their contentconstitutes requirements of this document.For dated references, only the edition cited applies.Forundated references, the latest edition of the referenced document(including any amendments) applies.ISO/1EC/IEEE 12207,Systems and Software engineering —Software life cycle processes
3Terms, definitions and abbreviated terms
3.1Terms and definitions
For the purposes of this document, the terms and definitions in lSO/IEC/IEEE 12207 and the followingapply.
ISO,IEC and IEEE maintain terminology databases for use in standardization at the following addresses:—ISO online browsing platform: available at https:.//www.iso.org/obp
—IEC Electropedia: available at https:// www.electropedia.org/
—IEEE Standards Dictionary Online: available at https://dictionary.ieee.org3.1.1
adaptive maintenance
modification of a software product, performed after delivery, to keep a software product usable in achanged or changing environment
Note 1 to entry: Adaptive maintenance provides enhancements (3.1.7) necessary to accommodate changesin the environment in which a software product operates. These changes help keep pace with the changingenvironment, e.g. an upgrade to the operating system results in changes in the applications.
3.1.2
additive maintenance
modification of a software product performed after delivery to add functionality or features to enhancethe usage of the product
Note 1 to entry: Additive maintenance may be excluded from the definition of maintenance in the context ofdependability that addresses recovery of a system to previous operational, functional and performance level, e.g.definition, monitor or measurement of availability, recoverability, or MTBF(mean time between failure).
Note 2 to entry: “Additive maintenance” type is distinguished from “perfective maintenance”(3.1.9) type andrecognized as a different maintenance type to be able to:
provide additional new functions or features to improve software usability, performance, maintainability3.1.6), or other software attributes for the future;
add functionality or features with relatively large additions or changes on software for improving softwareattributes after delivery with identified opportunitiesto negotiate any of additions or changes on maintenancestrategy, methods,resources, agreements, or service levels between suppliers and acquirers.
Note 3 to entry: Additions or enhancements(3.1.7) can be handled through the maintenance process, while largerchanges can involve a neww development effort.
3.1.3
correction
<software> change that addresses and implements problem resolutions to recover gaps and to makesoftware operational enough to meet defined operational requirements
Note 1 to entry: In this document, the term “correction” is mainly used as a maintenance type and to classifymodification requests (MR][3.1.8)-
3.1.4
corrective maintenance
modification of a software product performed after delivery to correct discovered problemsNote 1 to entry: The modification repairs the software product to satisfy defined system requirements.3.1.5
emergency maintenance
unscheduled modification performed to temporarily keep a system operational, pending correctivemaintenance (3.1.4)
Note 1 to entry:Emergency maintenance may be performed to make a software system partially operational. Itmay include various modifications to the software or its parameters in order to limit operations, functionalities,inputs, outputs, interfaces, usability, etc.
Note 2 to entry: Emergency maintenance can be regarded as a corrective maintenance type.3.1.6
maintainability
degree of effectiveness and efficiency with which a product or system can be modified
Note 1 to entry: Modifications can include corrections (3.1.3), improvements or adaptation of the software tochanges in environment, and in requirements and functional specifications. Modifications include those carriedout by specialized support staff, and those carried out by business or operational staff, or end users.
Note 2 to entry: Maintainability includes installation of updates and upgrades.
Note 3 to entry:Maintainability can be interpreted as either an inherent capability of the product or system tofacilitate maintenance activities, or the quality in use experienced by the maintainers for the goal of maintainingthe product or system.
[SOURCE:ISO/IEC 25010:2011，4.2.7，modified —”by the intended maintainers” at the end of thedefinition has been removed.]
3.1.7
enhancement
software change that addresses and implements a new requirement
Note 1 to entry: There are three types of software enhancements: adaptive,perfective and additive.Anenhancement is not a software correction (3.1.3].ISO IEC IEEE 14764 pdf download.