Use and Identification of Components in Component-Based Software Development Methods

  • Marko Forsell
  • Veikko Halttunen
  • Jarmo Ahonen
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1844)


New software systems are needed ever more but to keep up with this trend software developers must learn to create quality software more efficiently. One approach is to (re-)use components as building blocks of the new software. Recently there has been more interest to create component-based software development methods to support this. In this article we first set out requirements for reuse-based software development and then evaluate three component-based methods, namely Catalysis, OMT++, and Unified Process. As a conclusion we argue that evaluated methods produce prefabricated components and that component-based means that software developers can change better components to existing systems. Reuse of components to create new software is neglected in these methods.


Software Architecture Service Package Software Reuse Reusable Component Produce Asset 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Bailey, J., Basili, V.: The software-cycle model for re-engineering and reuse. In: Proceedings of the conference on Ada: today’s accomplishments; tomorrow’s expectations, pp. 267–281. ACM, New York (1991)CrossRefGoogle Scholar
  2. 2.
    Basili, V.: Facts and myths affecting software reuse. In: Proceedings of the 16th International Conference on Software Engineering, p. 269 (1994)Google Scholar
  3. 3.
    Basili, V., Caldiera, G., Cantone, G.: A reference architecture for the component factory. ACM Transactions on Software Engineering and Methodology 1(1), 53–80 (1992)CrossRefGoogle Scholar
  4. 4.
    Batory, D., O’Malley, S.: The Design and Implementation of hierarchical software systems with reusable components. ACM Transactions on Software Engineering and Methodology 1(4), 355–398 (1992)CrossRefGoogle Scholar
  5. 5.
    Biggerstaff, T., Richter, C.: Reusability framework, assessment, and directions. IEEE Software, 41–49 (March 1987)Google Scholar
  6. 6.
    Burton, B., Aragon, R., Bailey, S., Koehler, K., Mayes, L.: The reusable software library. IEEE Software, 25–33 (July 1987)Google Scholar
  7. 7.
    Caldiera, G., Basili, V.: Identifying and qualifying reusable software components. IEEE Computer, 61–70 (February 1991)Google Scholar
  8. 8.
    Capretz, L.: A CASE of reusability. Journal of Object-Oriented Programming, 32–37 (June 1998)Google Scholar
  9. 9.
    Davis, J., Morgan, T.: Object-oriented development at Brooklyn Union Gas. IEEE Software, 67–74 (January 1993)Google Scholar
  10. 10.
    Devanbu, P., Brachman, R., Selfridge, P., Ballard, B.: LaSSIE: A knowledge -based software information system. Communications of ACM 34(5), 33–49 (1991)CrossRefGoogle Scholar
  11. 11.
    D’Souza, D., Wills, A.: Objects, Components, and Frameworks with UML: The Catalysis Approach. Addison-Wesley, Reading (1999)Google Scholar
  12. 12.
    Dusink, L., van Katwijk, J.: Reuse dimensions. Software Engineering Notes (August 1995); Proceedings of the Symposium on Software Reusability, Seattle, Washington, April 28-30, pp. 137–149 (1995)Google Scholar
  13. 13.
    Fisher, G.: Cognitive view of reuse and redesign. IEEE Software, 61–72 (July 1987)Google Scholar
  14. 14.
    Henninger, S.: An evolutionary approach to constructing effective software reuse repositories. ACM Transactions on Software Engineering and Methodology 6(2), 111–140 (1997)CrossRefGoogle Scholar
  15. 15.
    Horowitz, E., Munson, J.: An expansive view of reusable software. In: Biggerstaff, T., Perlis, A. (eds.) Software Reusability. Concepts and Models, vol. I, pp. 19–41. ACM Press, New York (1989)Google Scholar
  16. 16.
    Jaaksi, A., Aalto, J.-M., Aalto, A., Vättö, K.: Tried & True Object Development: Industry-Proven Approaches with UML. Cambridge University Press, Cambridge (1999)Google Scholar
  17. 17.
    Jacobson, I., Griss, M., Jonsson, P.: Software Reuse: Architecture, Process and Organization for Business Success. ACM Press, New York (1997)Google Scholar
  18. 18.
    Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley, Reading (1999)Google Scholar
  19. 19.
    Karlson, E.: Software Reuse: A Holistic Approach. John Wiley & Sons Ltd., Chichester (1995)Google Scholar
  20. 20.
    Krueger, C.: Software reuse. ACM Computing Surveys 24(2), 131–183 (1992)CrossRefMathSciNetGoogle Scholar
  21. 21.
    Lanergan, R., Grasso, C.: Software engineering with reusable designs and code. In: Biggerstaff, T., Perlis, A. (eds.) Software Reusability. Applications and Experience, vol. II, pp. 187–195. ACM Press, New York (1989)Google Scholar
  22. 22.
    Lenz, M., Schmid, H., Wolf, P.: Software reuse through building blocks. IEEE Software, 35–42 (July 1987)Google Scholar
  23. 23.
    Lim, W.: Managing Software Reuse. Prentice Hall PTR, Englewood Cliffs (1998)Google Scholar
  24. 24.
    Neighbors, J.: Draco: A method for engineering reusable software systems. In: Biggerstaff, T., Perlis, A. (eds.) Software Reusability. Concepts and Models, vol. I, pp. 295–319. ACM Press, New York (1989)Google Scholar
  25. 25.
    Nierstrasz, O., Meijler, D.: Research directions in software composition. ACMComputing Surveys 27(2), 262–264 (1995)CrossRefGoogle Scholar
  26. 26.
    Ostertag, E., Prieto-Daz, R., Braun, C.: Computing similarity in a reuse library system: An AI-based approach. ACM Transactions on Software Engineering and Methodology 1(3), 205–228 (1992)CrossRefGoogle Scholar
  27. 27.
    Prieto-Daz, R.: Implementing faceted classification for software reuse. Communications of the ACM 34(5), 88–97 (1991)CrossRefGoogle Scholar
  28. 28.
    Prieto-Daz, R., Freeman, P.: Classifying software for reusability. IEEE Software, 6–16 (January 1987)Google Scholar
  29. 29.
    Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., Lorensen, W.: Object-Oriented Modeling and Design. Prentice-Hall, Inc., Englewood Cliffs (1991)Google Scholar
  30. 30.
    Sommerville, I.: Software Engineering, 4th edn. Addison-Wesley, Reading (1992)Google Scholar
  31. 31.
    STARS Conceptual Framework for Reuse Processes (CFPR) Vol. I: Definition, Version 3.0. STARS-VC-A018/001/00 (October 25, 1993), Available at
  32. 32.
    Taivalsaari, A.: A Critical View of Inheritance and Reusability in Object-oriented Programming. Ph.D. Dissertation, Jyväskylä Studies in Computer Science, Economics and Statistics, No. 23. University of Jyväskylä (1993)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2000

Authors and Affiliations

  • Marko Forsell
    • 1
  • Veikko Halttunen
    • 1
  • Jarmo Ahonen
    • 1
  1. 1.Information Technology Research InstituteUniversity of JyväskyläJyväskyläFinland

Personalised recommendations