Metraipolis › archive › dc_7053c2184fa4

Design by contract — Wikipedia (en)

Source
Wikipedia (en)
Original
https://en.wikipedia.org/wiki/Design_by_contract
License (as archived)
CC-BY-SA-4.0
Archived
2026-10-06T00:56:54.797Z
SHA-256 of the archived text
fe43ff4568f33b4a259a2d721cd10e0e4446dc35e0db6891c6210f79da2f3ec5
Stable URL of this page
https://metraipolis.com/documento/dc_7053c2184fa4

How to cite

Design by contract — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Design_by_contract (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_7053c2184fa4 (Metraipolis archive dc_7053c2184fa4, sha256 fe43ff4568f33b4a259a2d721cd10e0e4446dc35e0db6891c6210f79da2f3ec5)
BibTeX
@misc{dc7053c2184fa4,
  title = {Design by contract — Wikipedia (en)},
  howpublished = {Wikipedia (en)},
  url = {https://en.wikipedia.org/wiki/Design_by_contract},
  note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_7053c2184fa4; sha256 fe43ff4568f33b4a259a2d721cd10e0e4446dc35e0db6891c6210f79da2f3ec5},
  year = {2026}
}

Archived text

Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Design_by_contract. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Design by contract (DbC), also known as contract programming, programming by contract and design-by-contract programming, is an approach for designing software. It prescribes that software designers should define formal, precise and verifiable interface specifications for software components, which extend the ordinary definition of abstract data types with preconditions, postconditions and invariants. These specifications are referred to as "contracts", in accordance with a conceptual metaphor with the conditions and obligations of business contracts. The DbC approach assumes all client components that invoke an operation on a server component will meet the preconditions specified as required for that operation. Where this assumption is considered too risky (as in multi-channel or distributed computing), the inverse approach is taken, meaning that the server component tests that all relevant preconditions hold true (before, or while, processing the client component's request) and replies with a suitable error message if not.

Tema degli esploratori: calcolo e infrastrutture (deposito sistematico; ricerca «distributed computing»).
Fonte: Wikipedia in inglese, voce «Design by contract» — https://en.wikipedia.org/wiki/Design_by_contract
Wikidata Q1200691 (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q1200691
Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Design_by_contract?action=history).
Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza.
Estratto dell'introduzione non modificato nel contenuto; revisione 1374918832, consultata il 2026-10-06T00:14:42.223Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: 10153a3252f662b9c9ce16f92af3f5b444567a6972bd001f3c8fcb3929210183