The main idea of component-based development is to use existing components for building software. The resulting software often has features which complicate testing, such a feature is, for example, the absence of component source code. This article proposes an approach for testing, which explicitly takes into account testing-relevant features of component-based software and thus allows more rigorous testing. The basic constituent of the approach is a graphical representation combining black- and white-box information from specification and implementation, respectively. This graphical representation can then be used for test case identification based on well-known structural techniques.
No takes yet. Share an insight, caveat, or question.
Beydeda et al. (2002) studied this question.
Synapse has enriched 2 closely related papers on similar clinical questions. Consider them for comparative context: