| Kemerer, C.F. and S. Slaughter, "Determinants of Software Maintenance Profiles: An Empirical Investigation", Software Maintenance Research and Practice, Vol. 9, 1997, pp.235-251. |
....3 Obligatory Effort vs. Telon Use Figure 4 Number of Design Defects vs. Telon Use 4. Conclusions Lessons Learned Software managers often find it difficult to plan for maintenance work, and there is little quantitative empirical research devoted to improving their performance. [8]. Through the statistical analysis of one commercial bank s data, we have determined which factors had a real impact on the bank s annual obligatory maintenance effort. While it is interesting to know which factors are important, it is even more valuable for software managers to be able to reduce ....
....the to within the optimal range. Although we only studied 11 projects, this was enough evidence for him, as it confirmed his intuition based on experience with 19 other Telon projects that did not collect detailed data and were not included in the analysis. In addition, Kemerer and Slaughter [8] found in their study that modules generated by a backend case tool that generated Cobol code were significantly less likely to be repaired. There is also evidence that using Telon (compared with traditional Cobol coding) improves development productivity. The ISBSG database shows a median ....
Kemerer, C.F. and S. Slaughter, "Determinants of Software Maintenance Profiles: An Empirical Investigation", Software Maintenance Research and Practice, Vol. 9, 1997, pp.235-251.
No context found.
C.F. Kemerer and S.A. Slaughter. "Determinants of Software Maintenance Profiles: An Empirical Investigation", Software Maintenance: Research and Practice, Volume 9, pages 235-251, 1997.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC