Software Maintenance Knowledge Area

Once in operation, anomalies are uncovered, operating environments change, and new user requirements surface. The maintenance phase of the lifecycle commences upon delivery but maintenance activities occur much earlier. The software maintenance knowledge area is divided into six sub-areas.

The first one presents the domain's basic concepts, definitions, the main activities and problems of software maintenance.

The second sub-area describes the maintenance process, based on IEEE Std 1219 and ISO/IEC 14764.

The third sub-area regroups key issues related to software maintenance. The topics covered are technical, management, cost and estimation, and measurement issues.

Techniques for maintenance constitute the fourth sub-area. Those techniques include program comprehension, re-engineering, reverse engineering, and impact analysis.

The above summary was adapted from the Introduction to the IEEE Computer Society's SWEBOK Guide. For more information on the Software Requirements Knowledge Area, read Chapter 6 of the SWEBOK Guide.

Standards

Standard:

Title:

Abstract:

IEEE Std 1219™-1998

 

IEEE Standard for Software Maintenance

The process for managing and executing software maintenance activities is described.

IEEE Std 1061™-1998

 

IEEE Standard for a Software Quality Metrics Methodology

A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product software quality metrics is defined. The methodology spans the entire software life cycle.

IEEE Std 14143.1™-2000

 

IEEE Adoption of ISO/IEC 14143-1:1998 Information Technology—Software Measurement—Functional Size Measurement— Part 1: Definition of Concepts

This part [volume] of ISO/IEC 14143 defines the fundamental concepts of Functional Size Measurement (FSM) and describes the general principles for applying an FSM Method. This part of ISO/IEC 14143 does NOT provide detailed rules on how to:

  • Measure Functional Size of software using a particular method;

  • Use the results obtained from a particular method;

  • Select a particular method.

This part of ISO/IEC 14143 is applicable when determining if a method for sizing software is an FSM Method. It does not prevent the development of various methods, but rather provides a basis for assessing whether a particular method conforms to FSM. Implementation notes that relate to the IEEE interpretation of ISO/IEC 14143-1:1998 are provided.

About IEEE standard numbers.