Design by Contract
E347705
Design by Contract is a software development methodology that treats software components as parties to a formal agreement, specifying precise obligations, benefits, and invariants to improve correctness and reliability.
All labels observed (3)
| Label | Occurrences |
|---|---|
| Design by Contract canonical | 12 |
| C# code contracts | 1 |
| DbC | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T3304325 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Design by Contract Context triple: [Bertrand Meyer, knownFor, Design by Contract]
-
A.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
-
B.
Hoare logic
Hoare logic is a formal system in computer science used to reason rigorously about the correctness of computer programs using logical assertions about program states.
-
C.
Clean Architecture
Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
-
D.
Liskov Substitution Principle
The Liskov Substitution Principle is an object-oriented design rule stating that objects of a superclass should be replaceable with objects of a subclass without altering the correctness of a program.
-
E.
Domain-Driven Design: Tackling Complexity in the Heart of Software
"Domain-Driven Design: Tackling Complexity in the Heart of Software" is a seminal software engineering book by Eric Evans that introduces the domain-driven design approach for managing complexity in large, business-focused software systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Design by Contract Target entity description: Design by Contract is a software development methodology that treats software components as parties to a formal agreement, specifying precise obligations, benefits, and invariants to improve correctness and reliability.
-
A.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
-
B.
Hoare logic
Hoare logic is a formal system in computer science used to reason rigorously about the correctness of computer programs using logical assertions about program states.
-
C.
Clean Architecture
Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
-
D.
Liskov Substitution Principle
The Liskov Substitution Principle is an object-oriented design rule stating that objects of a superclass should be replaceable with objects of a subclass without altering the correctness of a program.
-
E.
Domain-Driven Design: Tackling Complexity in the Heart of Software
"Domain-Driven Design: Tackling Complexity in the Heart of Software" is a seminal software engineering book by Eric Evans that introduces the domain-driven design approach for managing complexity in large, business-focused software systems.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
formal specification approach
ⓘ
software correctness technique ⓘ software development methodology ⓘ |
| aimsTo |
improve software correctness
ⓘ
improve software reliability ⓘ reduce software defects ⓘ |
| alsoKnownAs |
Design by Contract
ⓘ
surface form:
DbC
contract programming ⓘ programming by contract ⓘ |
| appliesTo |
classes
ⓘ
interfaces ⓘ methods ⓘ software components ⓘ |
| associatedWithLanguage | Eiffel ⓘ |
| basedOnConcept | formal agreement between software components ⓘ |
| canBe |
checked at runtime
ⓘ
used for static analysis ⓘ |
| defines |
benefits of software components
ⓘ
invariants of software components ⓘ obligations of software components ⓘ |
| emphasizes |
clear responsibilities of components
ⓘ
documented assumptions ⓘ documented guarantees ⓘ precise specification of behavior ⓘ |
| helpsWith |
clearer interface specifications
ⓘ
early detection of bugs ⓘ improved documentation of code behavior ⓘ |
| influenced |
.NET Code Contracts
ⓘ
Java Modeling Language ⓘ Spec# ⓘ design-by-contract libraries in multiple languages ⓘ |
| inspiredBy | legal contracts ⓘ |
| introducedBy | Bertrand Meyer ⓘ |
| originatedInContext | object-oriented programming ⓘ |
| relatedTo |
Hoare logic
ⓘ
assertion-based programming ⓘ formal methods ⓘ software specification ⓘ |
| requires |
explicit specification of invariants
ⓘ
explicit specification of postconditions ⓘ explicit specification of preconditions ⓘ |
| supports |
defensive programming
ⓘ
formal verification ⓘ modular reasoning ⓘ test case generation ⓘ |
| usesConcept |
assertions
ⓘ
class invariants ⓘ postconditions ⓘ preconditions ⓘ runtime checking ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Design by Contract Description of subject: Design by Contract is a software development methodology that treats software components as parties to a formal agreement, specifying precise obligations, benefits, and invariants to improve correctness and reliability.
Referenced by (14)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
Eiffel (programming language)
subject surface form:
Eiffel (programming language)
this entity surface form:
C# code contracts
this entity surface form:
DbC
subject surface form:
Object-Oriented Software Construction
Touch of Class: Learning to Program Well with Objects and Contracts
→
mainSubject
→
Design by Contract
ⓘ
Touch of Class: Learning to Program Well with Objects and Contracts
→
usesMethodology
→
Design by Contract
ⓘ