Issue No. 03 - March (1996 vol. 29)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/2.485902
J.C. McKim , Dept. of Comput. & Inf. Sci., Hartford Graduate Center, CT, USA
"Why can't software be more like hardware?" has been the software engineer's lament for nearly as long as there have been large software systems. In particular, why isn't there a software components industry to rival the existing hardware components industry? Hardware components come with the following attributes: an interface that hides detail that would only confuse or at least distract me; an unambiguous interface specification written in a language I can understand (in the case of the integrated circuit, this may be a fairly complex language, but it's one I expect to learn if I'm going to work with that hardware); a guarantee-the component has been tested and/or validated against its specification. All three items-especially the last one-are notably lacking for software components. Indeed, software tends to come with an antiguarantee, otherwise known as a disclaimer. All of the above points rely on a rigorous specification of the hardware component's interface. In a nutshell, programming by contract is about providing just such specifications for software components (that is, classes), and it provides the best hope of a basis for a true software component industry. The discussion focuses on object oriented software.
economics, object-oriented programming, contracts, formal specification, user interfaces, DP industry, object oriented software, programming by contract, large software systems, software components industry, hardware components industry, interface, unambiguous interface specification, guarantee, software components, disclaimer, rigorous specification, classes, Contracts, Computer industry, Application software
J.C. McKim, "Programming by contract", Computer, vol. 29, no. , pp. 109,110,111, March 1996, doi:10.1109/2.485902