Quantitative method to determine software maintenance life cycle

The planning of software maintenance is a major problem that information systems managers are facing in many organizations. The problem stems from two basic root causes: the competing demands (services, repairs, improvements, etc.) for the same limited maintenance resources and the uncertainty associated with these demands. Managers lack reliable tools that could enable them to handle the uncertainty and thereby proactively plan the maintenance to better respond to user requests. This study provides a quantitative method to estimate the uncertainty and to help managers forecast the demands of maintenance. Since the accuracy of maintenance request forecast depends on predictable regimes of demands, the method first hypothesizes a non-stationary, life-cycle model for the basic regimes of different types of maintenance requests. Each regime features a probabilistic dominance of certain types of requests in the overall distribution of demands. The method then includes ways to characterize the distributions of different types of requests, monitor their evolution, and determine the shifting of regimes on which the managers base their planning decisions. This study performs a laboratory experiment to validate the quantitative method that determines the software maintenance life cycle. The findings confirm the hypothesis and substantiate the appropriateness of the quantitative method proposed.

[1]  Chris F. Kemerer,et al.  Now the learning curve affects CASE tool adoption , 1992, IEEE Software.

[2]  David S. Hinley,et al.  Software evolution management: a process-oriented perspective , 1996, Inf. Softw. Technol..

[3]  Chris F. Kemerer,et al.  Determinants of software maintenance profiles: an empirical investigation , 1997 .

[4]  Mark John Taylor,et al.  Knowledge for software maintenance , 1997, J. Inf. Technol..

[5]  David Gefen,et al.  The non-homogeneous maintenance periods: a case study of software modifications , 1996, 1996 Proceedings of International Conference on Software Maintenance.

[6]  Hans van Vliet,et al.  Software maintenance from a service perspective , 2000 .

[7]  Ned Chapin Software maintenance life cycle , 1988, Proceedings. Conference on Software Maintenance, 1988..

[8]  Paolo Donzelli,et al.  Tailoring the software maintenance process to better support complex systems evolution projects , 2003, J. Softw. Maintenance Res. Pract..

[9]  Peter Middleton,et al.  Maintenance management: From product to process , 1995, J. Softw. Maintenance Res. Pract..

[10]  J. S. Collofello,et al.  A task-based approach to improving the software maintenance process , 1992, Proceedings Conference on Software Maintenance 1992.

[11]  Hans van Vliet,et al.  Software maintenance from a service perspective , 2000, J. Softw. Maintenance Res. Pract..

[12]  B. Silverman,et al.  Nonparametric regression and generalized linear models , 1994 .

[13]  E. Burton Swanson,et al.  Characteristics of application software maintenance , 1978, CACM.

[14]  Kenneth L. Kraemer,et al.  Evolution and organizational information systems: an assessment of Nolan's stage model , 1984, CACM.

[15]  Chris F. Kemerer,et al.  Determinants of software maintenance profiles: an empirical investigation , 1997, J. Softw. Maintenance Res. Pract..

[16]  Mari Georges MACS: Maintenance assistance capability for software , 1992, J. Softw. Maintenance Res. Pract..

[17]  H.-J. Kung,et al.  Software Maintenance Life Cycle Model , 1998, Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272).

[18]  Alain Abran,et al.  Analysis of maintenance work categories through measurement , 1991, Proceedings. Conference on Software Maintenance 1991.

[19]  R. L. Glass Editor's corner: Software maintenance is a solution - Not a problem , 1989, J. Syst. Softw..