Abstract
A software maintenance size can be used to predict maintenance effort or maintenance time. However, the traditional maintenance size metric only relies on line of source code (LOC), which hardly is suitable for object-oriented software. This research proposed four new maintenance size metrics based on number of classes, number of methods, average number of methods per class, and weighted methods per class. An automated report generation system in HDD industry (ARGS_PMS) was used as a case study to measure the performance of each proposed metric. We found that, for enhanced software maintenance tasks, maintenance size based on an average number of methods per class (MS-MC) gave the best performance in predicting maintenance time. For a refactoring maintenance task, maintenance size based on line of code (MS-LOC), weighted methods per class (MS-WMC) and average methods per class (MS-MC) were the best, better and good estimators for predicting maintenance time, respectively. On average, the maintenance size based on weighted methods per class gave the best performance.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
