A Client-Benefits Oriented Taxonomy Of ERP Maintenance
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Case study: lessons learned during a nationwide computer system upgrade
ACM-SE 42 Proceedings of the 42nd annual Southeast regional conference
Comparing Uniform and Flexible Policies for Software Maintenance and Replacement
IEEE Transactions on Software Engineering
Experience Report on the Effect of Software Development Characteristics on Change Distribution
PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
Change profiles of a reused class framework vs. two of its applications
Information and Software Technology
Approximating deployment metrics to predict field defects and plan corrective maintenance activities
ISSRE'09 Proceedings of the 20th IEEE international conference on software reliability engineering
Software quality evaluation through maintenance processes
ECS'10/ECCTD'10/ECCOM'10/ECCS'10 Proceedings of the European conference of systems, and European conference of circuits technology and devices, and European conference of communications, and European conference on Computer science
Empirical testing activities for NeOSS maintenance
APNOMS'07 Proceedings of the 10th Asia-Pacific conference on Network Operations and Management Symposium: managing next generation networks and services
| Hi-index | 0.00 |
Software maintenance costs often total twice the original development cost in the lifetime of application software. Modeling the changes of software maintenance activities might improve software maintenance planning. Current studies model software activities only covering a portion of software lifetimes. This study investigates the changes of maintenance requests during the lifetime of large application software. It discusses the modeling of different software maintenance requests such as: user support, repair and enhancement. We found four distinct stages. User support reaches its peak in the first stage, repair inundates in the second stage. In the third stage, enhancement is the dominant factor. The frequencies of all three different maintenance requests are small in the last stage, when the IS department is looking for new software to replace the existing one.