skip to main content
10.1145/1127716.1127719acmotherconferencesArticle/Chapter ViewAbstractPublication Pagesacm-seConference Proceedingsconference-collections
Article
Free Access

From C to Java: a case study in portability, efficiency, and maintenance

Published:07 April 2000Publication History

ABSTRACT

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.

References

  1. Belady, L., and Lehman, M. (1972). An Introduction to Growth Dynamics. In W. Freiberger (ed.) Statistical Computer Performance Evaluation. New York: Academic Press.Google ScholarGoogle Scholar
  2. Boehm, B., Clark, C., Horowitz, E., Westland, C., Madachy, R., and Selby, R. (1995). Cost Models for Future Life Cycle Processes: COCOMO 2.0. Annals of Software Engineering, Vol. 1, No. 1, pp. 57--94.Google ScholarGoogle ScholarCross RefCross Ref
  3. Chan, T., Siu Leung, C., Teck, Hua Ho (1996). An Economic Model to Estimate Software Rewriting and Replacement Times. IEEE Transactions on Software Engineering, Vol. 22, No. 8, pp. 580--598. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Corbi, T. A. (1989). Program Understanding: Challenge for the 1990s. IBM Systems Journal, 28, 2, pp. 294--306. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Cross, J. H., Chang, K. H., Hendrix, T. D., Chapman, R. O., and McQuaid, P. M. (1997). Visualization and Measurement of Source Code. CrossTalk Journal of Defense Software Engineering, 10, 12, pp. 16--19.Google ScholarGoogle Scholar
  6. Field, T. (1997) A Good Connection. CIO Magazine, February 1.Google ScholarGoogle Scholar
  7. Gibson, V., and Senn, J. (1989). System Structure and Software Maintenance Performance. Communications of the ACM, Vol. 32, March, pp. 347--358. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. Jorgensen, M. (1995). Experience With the Accuracy of Software Maintenance Task Effort Prediction Models. IEEE Transactions on Software Engineering. Vol. 21, No. 8, pp. 674--681. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. Kafura, D. and Reddy, G. (1987). The Use of Software Complexity Metrics in Software Maintenance. IEEE Transactions on Software Engineering, Vol. 13, No. 3, pp. 335--343. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. Lientz, B. and Swanson, E. (1981). Problems in Application Software Maintenance. Communications of the ACM, Vol. 24, No. 11, pp. 763--769. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Moller, K. and Paulish, D. (1993). An Empirical Investigation of Software Fault Distribution. In Proceedings of CSR '93, Amsterdam: Chapman and Hall.Google ScholarGoogle ScholarCross RefCross Ref
  12. Niessink, F. and van Vliet H. (1998). Two Case Studies in Measuring Software Maintenance Effort. Proceedings of the 1999 International Conference on Software Maintenance, November 16--19, Bethesda, MD. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. Parikh, G. and Zvegnitzov, N. (1993). Tutorial on Software Maintenance. Los Alamitos, CA, IEEE Computer Society Press.Google ScholarGoogle Scholar
  14. Pfleeger, S. (1998). Software Engineering: Theory and Practice. Prentice Hall. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. Pfleeger, S., Fenton, N., and Page, S. (1994). Evaluating Software Engineering Standards. IEEE Computer, Vol. 27, No. 9, (September), pp. 71--79. Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. Singer, J. (1998) Practices of Software Maintenance. Proceedings of the 1999 International Conference on Software Maintenance, November 16--19, Bethesda, MD. Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. Voas, J. (1998). Maintaining Component-Based Systems. IEEE Software, Vol. 14, No. 4, (July/August), pp.22--27. Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. Wilde, N., Matthews, P., and Huitt, R. (1993). Maintaining Object-Oriented Software. IEEE Software, Vol. 10, No. 1, (January), pp. 75--80. Google ScholarGoogle ScholarDigital LibraryDigital Library

Recommendations

Comments

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Sign in
  • Published in

    cover image ACM Other conferences
    ACM-SE 38: Proceedings of the 38th annual on Southeast regional conference
    April 2000
    263 pages
    ISBN:1581132506
    DOI:10.1145/1127716

    Copyright © 2000 ACM

    Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    • Published: 7 April 2000

    Permissions

    Request permissions about this article.

    Request Permissions

    Check for updates

    Qualifiers

    • Article

    Acceptance Rates

    Overall Acceptance Rate178of377submissions,47%
  • Article Metrics

    • Downloads (Last 12 months)10
    • Downloads (Last 6 weeks)2

    Other Metrics

PDF Format

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader