An approach to increasing software component reusability in Ada

  • Hyoseob Kim
  • Cornelia Boldyreff
Software Development Methods
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1088)


The phenomenal growth in the costs of producing software over the last three decades has forced the computing industry to look for alternative strategies to that implied by the waterfall model of computer system development. One frequently observed solution is that of reusing the code from previously designed systems in the construction of new ones; this technique is known as software reuse. Ada language was developed as a tool to address the above problems and is believed to have many useful language features such as package and generics to produce reusable software. But programming in Ada does not guarantee the production of highly reusable software. Therefore guidelines for users are needed to maximise the benefits from using Ada. In this paper, Ada code reuse guidelines are proposed, and as an attempt to prove the usefulness of them, reuse metrics are used.


Ada Code Reuse Guidelines Reuse Metrics 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Roger S. Pressman. Software Engineering: A Practitioner's Approach. McGraw-Hill, Inc., third edition, 1992.Google Scholar
  2. [2]
    J. A. Siegel et al. National software capacity: Near-term study. Technical Report CMU/SEI-90-TR-12, Carnegie Mellon University/Software Engineering Institute, May 1990.Google Scholar
  3. [3]
    Ada Joint Program Office. A strategy for a software initiative. Technical report, Department of Defense, 1985.Google Scholar
  4. [4]
    Joseph Eugene Hollingsworth. Software Component Design-for-Reuse: A Language-Independent Discipline Applied to Ada. PhD thesis, Department of Computer and Information Science, The Ohio State University, 1992.Google Scholar
  5. [5]
    M. V. Wilkes, D. J. Wheeler, and S. Gill. Programming for the Digital Computer. Addison-Wesley, 1953.Google Scholar
  6. [6]
    M. D. McIlroy. Mass produced software components. In P. Naur, B. Randell, and J. N. Buxton, editors, Proceedings of NATO Conference on Software Engineering, pages 88–98, New York, 1969. Petrocelli/Charter.Google Scholar
  7. [7]
    Edward Stewart Garnett. Software Reclamation: Upgrading Code for Reusability. PhD thesis, Lancaster University, September 1990.Google Scholar
  8. [8]
    Ted Biggerstaff. Software Reusability, Concepts and Models, volume I, page xv. ACM Press, 1989.Google Scholar
  9. [9]
    James W. Hooper and Rowena O. Chester. Software Reuse Guidelines and Methods. Plenum Press, 1991.Google Scholar
  10. [10]
    John Nissen and Peter Wallis, editors. Portability and style in Ada. The Ada Companion Series. Cambridge University Press, 1984.Google Scholar
  11. [11]
    R. J. St. Dennis. Reusable Ada software guidelines. In Proceedings of the Twentieth Hawaii International Conference on System Sciences, pages 513–520, January 1987.Google Scholar
  12. [12]
    The Ada-Europe Software Reuse Working Group. Ada reusability guidelines. In R. J. Gautier and P. J. L. Wallis, editors, Software Reuse with Ada, pages 99–173. Peter Peregrinus Ltd., 1990.Google Scholar
  13. [13]
    IBM Systems Integration Division. STARS reusability guidelines. Technical report, Electronic Systems Division, Air Force Systems Command, USAF, Hanscomb AFB, Massachusetts, April 1990. Contract No. F19628-88-D-0032, Task IR40: Repository Integration, Delivered as part of: CDRL Sequence No. 1550.Google Scholar
  14. [14]
    M. Ramachandran. An Investigation into Tool Support for the Development of Reusable Software. PhD thesis, Lancaster University, 1992.Google Scholar
  15. [15]
    Software Productivity Consortium Services Corporation. Ada 95 Quality and Style: Guidelines for Professional Programmers. Draft Baseline Version, SPC-94093-CMC. Software Productivity Consortium Corporation, February 1995.Google Scholar
  16. [16]
    E. B. Swanson. The dimensions of maintenance. In Proceedings of the Second International Conference on Software Engineering, pages 492–497. IEEE, October 1976.Google Scholar
  17. [17]
    Norman E. Fenton. Software Metrics: A rigorous approach. Chapman & Hall, second edition, 1991.Google Scholar
  18. [18]
    Victor R. Basili, Gianluigi Caldiera, and H. Dieter Rombach. The goal question metric approach. Institute for Advanced Computer Studies, Department of Computer Science, University of Maryland at College Park, U.S.A. and FB Informatik, Universität Kaiserslautern, Germany.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1996

Authors and Affiliations

  • Hyoseob Kim
    • 1
  • Cornelia Boldyreff
    • 1
  1. 1.Centre for Software Maintenance Department of Computer ScienceUniversity of DurhamDurhamUK

Personalised recommendations