The Use of Software Complexity Metrics in Software Maintenance
IEEE Transactions on Software Engineering
System structure and software maintenance performance
Communications of the ACM
Program understanding: challenge for the 1990's
IBM Systems Journal
An Economic Model to Estimate Software Rewriting and Replacement Times
IEEE Transactions on Software Engineering
Software engineering: theory and practice
Software engineering: theory and practice
Problems in application software maintenance
Communications of the ACM
Maintaining Object-Oriented Software
IEEE Software
Maintaining Component-Based Systems
IEEE Software
Experience With the Accuracy of Software Maintenance Task Effort Prediction Models
IEEE Transactions on Software Engineering
Practices of Software Maintenance
ICSM '98 Proceedings of the International Conference on Software Maintenance
Two Case Studies in Measuring Software Maintenance Effort
ICSM '98 Proceedings of the International Conference on Software Maintenance
| Hi-index | 0.00 |
The "write once, run anywhere" model for Java-based systems holds great promise for reducing the cost associated with maintaining software systems that must run on multiple hardware platforms and multiple operating systems. The GRASP research project at Auburn University has recently completed a port of its software engineering tool, also called GRASP, from its original implementation in C to Java. This effort has provided an excellent opportunity for the authors to empirically observe the effects on portability, efficiency, and maintainability that such a transformation could have. This case study in reengineering and maintenance suggests that Java has not yet matured to the point that all its potential and promises can be fulfilled. However, as it matures and becomes more stable, Java offers the opportunity to significantly reduce the cost and effort of maintaining multiple host software systems.