Chapter 5: Software Maintenance - Revision history

Daniel Robbins: /* Maintenance Processes */

2015-08-24T19:22:44Z

‎Maintenance Processes

Daniel Robbins at 19:21, 24 August 2015

2015-08-24T19:21:36Z

Daniel Robbins at 19:21, 24 August 2015

2015-08-24T19:21:01Z

Daniel Robbins: /* Software Maintenance Tools */

2015-08-24T18:53:39Z

‎Software Maintenance Tools

Daniel Robbins: /* Software Maintenance Tools */

2015-08-24T18:52:58Z

‎Software Maintenance Tools

Daniel Robbins: /* Software Maintenance Tools */

2015-08-24T18:51:48Z

‎Software Maintenance Tools

Daniel Robbins: /* Techniques for Maintenance */

2015-08-24T18:51:16Z

‎Techniques for Maintenance

Daniel Robbins: /* Maintenance Process */

2015-08-24T18:47:42Z

‎Maintenance Process

Daniel Robbins: /* Key Issues in Software Maintenance */

2015-08-24T18:44:16Z

‎Key Issues in Software Maintenance

Daniel Robbins: /* Software Maintenance Fundamentals */

2015-08-24T18:39:43Z

‎Software Maintenance Fundamentals

← Older revision		Revision as of 19:22, 24 August 2015
Line 562:		Line 562:
	* software retirement.		* software retirement.

		+	[[File:software-maintenance-process.jpg\|thumb\|400px\|frame\|Figure 5.2: Software Maintenance Process]]
	Other maintenance process models include:		Other maintenance process models include:

@@ Line 43: / Line 43: @@
 activities include software modification, training,
 and operating or interfacing to a help desk.
 The Software Maintenance knowledge area
@@ Line 53: / Line 55: @@
 The breakdown of topics for the Software Maintenance
 KA is shown in Figure 5.1.}}
 == Software Maintenance Fundamentals ==

@@ Line 53: / Line 53: @@
 The breakdown of topics for the Software Maintenance
 KA is shown in Figure 5.1.}}
 == Software Maintenance Fundamentals ==

@@ Line 837: / Line 837: @@
 ISO14764 and ISO15504 and popular maturity
 models like ITIL, CoBIT, CMMI and CM3.
 M. Kajko-Mattsson, “Towards a Business
 Maintenance Model,” IEEE Int’l Conf.

@@ Line 820: / Line 820: @@
 software measurement tools.
 {{EndSection|title=References|body=
 {{reference

@@ Line 798: / Line 798: @@
 == Software Maintenance Tools ==
+{{RightSection|{{referenceLink|number=1|parts=c6s4}} {{referenceLink|number=2|parts=c14}}}}
 This topic encompasses tools that are particularly
 important in software maintenance where existing

@@ Line 725: / Line 725: @@
 === Program Comprehension ===
+{{RightSection|{{referenceLink|number=2|parts=c6, c14s5}}}}
 Programmers spend considerable time reading and
 understanding programs in order to implement
@@ Line 734: / Line 734: @@
 === Reengineering ===
+{{RightSection|{{referenceLink|number=2|parts=c7}}}}
 Reengineering is defined as the examination and
 alteration of software to reconstitute it in a new
@@ Line 747: / Line 747: @@
 === Reverse Engineering ===
+{{RightSection|{{referenceLink|number=1|parts=c6s2}} {{referenceLink|number=2|parts=c7, c14s5}}}}
 Reverse engineering is the process of analyzing
 software to identify the software’s components
@@ Line 766: / Line 766: @@
 === Migration ===
+{{RightSection|{{referenceLink|number=1|parts=c5s5}}}}
 During software’s life, it may have to be modified
 to run in different environments. In order to
@@ Line 786: / Line 786: @@
 === Retirement ===
+{{RightSection|{{referenceLink|number=1|parts=c5s6}}}}
 Once software has reached the end of its useful
 life, it must be retired. An analysis should

@@ Line 546: / Line 546: @@
 === Maintenance Processes ===
+{{RightSection|{{referenceLink|number=1|parts=c5}} {{referenceLink|number=2|parts=c5}} {{referenceLink|number=1|parts=s5.5}}}}
 Maintenance processes provide needed activities
 and detailed inputs/outputs to those activities as
@@ Line 579: / Line 579: @@
 === Maintenance Activities ===
+{{RightSection|{{referenceLink|number=1|parts=c5, c6s8.2, c7s3.3}}}}
 The maintenance process contains the activities
 and tasks necessary to modify an existing software
@@ Line 598: / Line 598: @@
 ==== Unique Activities ====
+{{RightSection|{{referenceLink|number=1|parts=c3s10, c6s9, c7s2, c7s3}} {{referenceLink|number=2|parts=c6, c7}}}}
 There are a number of processes, activities, and
 practices that are unique to software maintenance:
@@ Line 610: / Line 610: @@
 ==== Supporting Activities ====
+{{RightSection|{{referenceLink|number=1|parts=c4s1, c5, c6s7}} {{referenceLink|number=2|parts=c9}}}}
 Maintainers may also perform support activities,
 such as documentation, software configuration
@@ Line 619: / Line 619: @@
 ==== Maintenance Planning Activities ====
+{{RightSection|{{referenceLink|number=1|parts=c7s3}}}}
 An important activity for software maintenance is
 planning, and maintainers must address the issues
@@ Line 674: / Line 674: @@
 ==== Software Configuration Management ====
+{{RightSection|{{referenceLink|number=1|parts=c5s1.2.3}} {{referenceLink|number=2|parts=c11}}}}
 IEEE 14764 describes software configuration
 management as a critical element of the maintenance
@@ Line 703: / Line 703: @@
 ==== Software Quality ====
+{{RightSection|{{referenceLink|number=1|parts=c6s5, c6s7, c6s8}} {{referenceLink|number=2|parts=c12s5.3}}}}
 It is not sufficient to simply hope that increased
 quality will result from the maintenance of software.

@@ Line 245: / Line 245: @@
 ==== Limited Understanding ====
+{{RightSection|{{referenceLink|number=2|parts=c6}}}}
 Limited understanding refers to how quickly a
 software engineer can understand where to make
@@ Line 264: / Line 264: @@
 ==== Testing ====
+{{RightSection|{{referenceLink|number=1|parts=c6s2.2.2}} {{referenceLink|number=2|parts=c9}}}}
 The cost of repeating full testing on a major
 piece of software is significant in terms of time
@@ Line 287: / Line 287: @@
 ==== Impact Analysis ====
+{{RightSection|{{referenceLink|number=1|parts=c5s2.5}} {{referenceLink|number=2|parts=c13s3}}}}
 Impact analysis describes how to conduct, costeffectively,
 a complete analysis of the impact of
@@ Line 325: / Line 325: @@
 ==== Maintainability ====
+{{RightSection|{{referenceLink|number=1|parts=c6s8}} {{referenceLink|number=2|parts=c12s5.5}}}}
 IEEE 14764 [1*, c3s4] defines maintainability
 as the capability of the software product to be
@@ Line 355: / Line 355: @@
 ==== Alignment with Organizational Objectives ====
+{{RightSection|{{referenceLink|number=2|parts=c4}}}}
 Organizational objectives describe how to demonstrate
 the return on investment of software maintenance
@@ Line 373: / Line 373: @@
 ==== Staffing ====
+{{RightSection|{{referenceLink|number=1|parts=c4s5, c10s4}}}}
 Staffing refers to how to attract and keep software
 maintenance staff. Maintenance is not often
@@ Line 382: / Line 382: @@
 ==== Process ====
+{{RightSection|{{referenceLink|number=1|parts=c5}} {{referenceLink|number=2|parts=c5}}}}
 The software life cycle process is a set of activities,
 methods, practices, and transformations that people
@@ Line 396: / Line 396: @@
 ==== Organizational Aspects of Maintenance ====
+{{RightSection|{{referenceLink|number=1|parts=c7s2.3}} {{referenceLink|number=2|parts=c10}}}}
 Organizational aspects describe how to identify
 which organization and/or function will be
@@ Line 425: / Line 425: @@
 ==== Outsourcing ====
+{{RightSection|{{referenceLink|number=3}}}}
 Outsourcing and offshoring software maintenance
 has become a major industry. Organizations
@@ Line 454: / Line 454: @@
 ==== Cost Estimation ====
+{{RightSection|{{referenceLink|number=2|parts=c7s2.4}}}}
 Section 2.1.3 describes how impact analysis identifies
 all systems and software products affected
@@ Line 470: / Line 470: @@
 ==== Parametric Models ====
+{{RightSection|{{referenceLink|number=2|parts=c12s5.6}}}}
 Parametric cost modeling (mathematical models)
 has been applied to software maintenance. Of significance
@@ Line 479: / Line 479: @@
 ==== Experience ====
+{{RightSection|{{referenceLink|number=2|parts=c12s5.5}}}}
 Experience, in the form of expert judgment,
 is often used to estimate maintenance effort.
@@ Line 491: / Line 491: @@
 === Software Maintenance Measurement ===
+{{RightSection|{{referenceLink|number=1|parts=c6s5}} {{referenceLink|number=2|parts=c12}}}}
 Entities related to software maintenance, whose
 attributes can be subjected to measurement,
@@ Line 512: / Line 512: @@
 ==== Specific Measures ====
+{{RightSection|{{referenceLink|number=2|parts=c12}}}}
 The maintainer must determine which measures
 are appropriate for a specific organization based

@@ Line 65: / Line 65: @@
 === Definitions and Terminology ===
+{{RightSection|{{referenceLink|number=1|parts=c3}} {{referenceLink|number=2|parts=c1s2, c2s2}}}}
 The purpose of software maintenance is defined
 in the international standard for software maintenance:
@@ Line 82: / Line 82: @@
 === Nature of Maintenance ===
+{{RightSection|{{referenceLink|number=2|parts=c1s3}}}}
 Software maintenance sustains the software product
 throughout its life cycle (from development
@@ Line 118: / Line 118: @@
 === Need for Maintenance ===
+{{RightSection|{{referenceLink|number=2|parts=c1s5}}}}
 Maintenance is needed to ensure that the software
 continues to satisfy user requirements. Maintenance
@@ Line 145: / Line 145: @@
 === Majority of Maintenance Costs ===
+{{RightSection|{{referenceLink|number=2|parts=c4s3, c5s5.2}}}}
 Maintenance consumes a major share of the financial
 resources in a software life cycle. A common
@@ Line 184: / Line 184: @@
 === Categories of Maintenance ===
+{{RightSection|{{referenceLink|number=1|parts=c3, c6s2}} {{referenceLink|number=2|parts=c3s3.1}}}}
 Three categories (types) of maintenance have
 been defined: corrective, adaptive, and perfective