|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Karine Arnout, Bertrand Meyer, "Uncovering Hidden Contracts: The .NET Example," Computer, vol. 36, no. 11, pp. 48-55, November, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MC.2003.1244535, author = {Karine Arnout and Bertrand Meyer}, title = {Uncovering Hidden Contracts: The .NET Example}, journal ={Computer}, volume = {36}, number = {11}, issn = {0018-9162}, year = {2003}, pages = {48-55}, doi = {http://doi.ieeecomputersociety.org/10.1109/MC.2003.1244535}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - Computer TI - Uncovering Hidden Contracts: The .NET Example IS - 11 SN - 0018-9162 SP48 EP55 EPD - 48-55 A1 - Karine Arnout, A1 - Bertrand Meyer, PY - 2003 VL - 36 JA - Computer ER - | |||
Software contracts take the form of routine preconditions, postconditions, and class invariants written into the program itself. The design by contract methodology uses such contracts for building each software element, an approach that is particularly appropriate for developing safety-critical software and reusable libraries. This methodology is a key design element of some existing libraries, especially the Eiffel software development environment, which incorporates contract mechanisms in the programming language itself.
Because the authors see the contract metaphor as inherent to quality software development, they undertook the work reported here as a sanity check to determinewhether they see contracts everywhere simply because their development environment makes using them natural or whether contracts are intrinsically present, even when other designers don't express or even perceive them.

