Issue No. 11 - November (2004 vol. 30)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TSE.2004.80
Murali Sitaraman , IEEE Computer Society
Bruce W. Weide , IEEE
Two kinds of interface contract violations can occur in component-based software: A client component can fail to satisfy a requirement of a component it is using, or a component implementation can fail to fulfill its obligations to the client. The traditional approach to detecting and reporting such violations is to embed assertion checks into component source code, with compile-time control over whether they are enabled. This works well for the original component developers, but it fails to meet the needs of component clients who do not have access to source code for such components. A wrapper-based approach, in which contract checking is not hard-coded into the underlying component but is "layered” on top of it, offers several relative advantages. It is practical and effective for C++ classes. Checking code can be distributed in binary form along with the underlying component, it can be installed or removed without requiring recompilation of either the underlying component or the client code, it can be selectively enabled or disabled by the component client on a per-component basis, and it does not require the client to have access to any special tools (which might have been used by the component developer) to support wrapper installation and control. Experimental evidence indicates that wrappers in C++ impose modest additional overhead compared to inlining assertion checks.
Assertion checkers, binary components, design by contract, preconditions, postconditions, class invariants, coding techniques, debugging aids, specification.
S. H. Edwards, J. Hollingsworth, M. Sitaraman and B. W. Weide, "Contract-Checking Wrappers for C++ Classes," in IEEE Transactions on Software Engineering, vol. 30, no. , pp. 794-810, 2004.