Measuring and Communicating Component Reliability

  • John D. McGregor
  • Judith A. Stafford
  • Il-Hyung Cho
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3026)


Much of the research on component-based software engineering assumes that each component has a single service. This simplifies analyses but it is a significant departure from actual components. This paper reports on an investigation of the feasibility of using design constructs as a means of treating several methods as a single unit. We introduce the CoRe Method for measuring and communicating component reliability based on grouping services according to the various roles a component can fulfill. Grouping the services of a component into a few sets satisfies the goal of simplicity while still providing the designer with a more realistic and useful model of component reliability. The CoRe method is described and results of a preliminary experiment in its use are reported.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Selic, B., Rumbaugh, J.: Using UML for Modeling Complex Real-Time Systems, Rational Corp. (1998)Google Scholar
  2. 2.
    Allen, R., Garlan, D.: A Formal Basis for Architectural Connection. ACM Transactions on Software Engineering and Methodology (1997)Google Scholar
  3. 3.
    Cho, I., McGregor, J.D.: Component Specification and Testing Interoperation of Components. In: IASTED 3rd International Conference on Software Engineering and Applications (October 1999)Google Scholar
  4. 4.
    Szyperski, C.: Component Software: Beyond Object-Oriented Programming. Addison-Wesley, Boston (1998)Google Scholar
  5. 5.
    Musa, J.: Software Reliability Engineering. McGraw-Hill, New York (1998)Google Scholar
  6. 6.
    Trivedi, K.S.: Probability and Statistics with Reliability, Queuing and Computer Sciene Applications, 2nd edn. Wiley Interscience, New York (2002)Google Scholar
  7. 7.
    Stafford, J.A., Wallnau, K.C.: Is third party certification really necessary? In: Proceedings of the Fourth ICSE Workshop on Component-Based Software Engineering, Toronto, CA, May 2001, pp. 13–19 (2001)Google Scholar
  8. 8.
    Stafford, J.A., Wolf, A.L.: Annotating Components to Support Component-Based Static Analyses of Software Systems. In: Proceedings of the Grace Hopper Celebration of Women in Computing 2000, Hyannis, Massachusetts (September 2000)Google Scholar
  9. 9.
    Reussner, R.H., Poernomo, I.H., Schmidt, H.W.: Reasoning on Software Architectures with Contractually Specified Components. In: Cechich, A., Piattini, M., Vallecillo, A. (eds.) Component-Based Software Quality. LNCS, vol. 2693, pp. 287–325. Springer, Heidelberg (2003) (to appear)CrossRefGoogle Scholar
  10. 10.
    Hamlet, D., Mason, D., Woit, D.: Theory of Software Reliability Based on Components. In: Proceedings of the 23rd International Conference on Software Engineering (ICSE 2002), Toronto, Canada, May 2001, IEEE Computer Society Press, Los Alamitos (2001)Google Scholar
  11. 11.
    Yacoub, S., Cukic, B., Ammar, H.: Scenario-Based Reliability Analysis of Component- Based Software. In: Proceedings of Tenth International Symposium on Software Reliability Engineering (ISSRE 1999), Boca Raton, Florida, November 1999, pp. 22–31 (1999)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • John D. McGregor
    • 1
  • Judith A. Stafford
    • 1
  • Il-Hyung Cho
    • 1
  1. 1.Clemson University , Tufts University 

Personalised recommendations