SOLID principles
E672060
SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
All labels observed (2)
| Label | Occurrences |
|---|---|
| SOLID principles canonical | 6 |
| SOLID design principles | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7540073 — 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: SOLID principles Context triple: [Robert C. Martin, isKnownFor, SOLID principles]
-
A.
Dependency Inversion Principle
The Dependency Inversion Principle is an object-oriented design guideline that promotes decoupling by having high-level and low-level modules depend on shared abstractions rather than concrete implementations.
-
B.
Single Responsibility Principle
The Single Responsibility Principle is a core object-oriented design guideline stating that a class or module should have only one reason to change, meaning it should be responsible for just a single, well-defined functionality.
-
C.
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.
-
D.
Open-Closed Principle
The Open-Closed Principle is a fundamental object-oriented design guideline stating that software entities should be open for extension but closed for modification, enabling systems to grow without altering existing, tested code.
-
E.
KISS principle
The KISS principle is a design and problem-solving guideline that advocates keeping systems and solutions as simple as possible to improve clarity, reliability, and maintainability.
- 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: SOLID principles Target entity description: SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
-
A.
Dependency Inversion Principle
The Dependency Inversion Principle is an object-oriented design guideline that promotes decoupling by having high-level and low-level modules depend on shared abstractions rather than concrete implementations.
-
B.
Single Responsibility Principle
The Single Responsibility Principle is a core object-oriented design guideline stating that a class or module should have only one reason to change, meaning it should be responsible for just a single, well-defined functionality.
-
C.
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.
-
D.
Open-Closed Principle
The Open-Closed Principle is a fundamental object-oriented design guideline stating that software entities should be open for extension but closed for modification, enabling systems to grow without altering existing, tested code.
-
E.
KISS principle
The KISS principle is a design and problem-solving guideline that advocates keeping systems and solutions as simple as possible to improve clarity, reliability, and maintainability.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
object-oriented design guideline set
ⓘ
software design principle set ⓘ |
| acronymFor | Single Responsibility Open–Closed Liskov substitution Interface segregation Dependency inversion ⓘ |
| aimsTo |
promote flexible software architectures
ⓘ
promote maintainable software architectures ⓘ promote scalable software architectures ⓘ |
| appliesTo |
API design
ⓘ
class design ⓘ component design ⓘ object-oriented architecture ⓘ |
| associatedWith | Robert C. Martin NERFINISHED ⓘ |
| category | best practices in software design ⓘ |
| consistsOf |
Dependency Inversion Principle
NERFINISHED
ⓘ
Interface Segregation Principle NERFINISHED ⓘ Liskov Substitution Principle NERFINISHED ⓘ Open–Closed Principle NERFINISHED ⓘ Single Responsibility Principle NERFINISHED ⓘ |
| describedIn | software engineering literature ⓘ |
| emphasizes |
abstraction
ⓘ
encapsulation ⓘ polymorphism ⓘ separation of concerns ⓘ |
| field |
object-oriented programming
ⓘ
software engineering ⓘ |
| goal |
facilitate change in software systems
ⓘ
improve software quality ⓘ reduce software complexity ⓘ |
| influencedBy | object-oriented programming paradigm ⓘ |
| popularizedBy | Robert C. Martin NERFINISHED ⓘ |
| promotes |
extensibility
ⓘ
high cohesion ⓘ low coupling ⓘ readability ⓘ reusability ⓘ testability ⓘ |
| relatedTo |
GRASP principles
ⓘ
clean code ⓘ design patterns ⓘ |
| timePeriod | early 2000s popularization ⓘ |
| typicalContext |
object-oriented languages such as C#
ⓘ
object-oriented languages such as C++ ⓘ object-oriented languages such as Java ⓘ object-oriented languages such as Python ⓘ |
| usedIn |
agile software development practices
ⓘ
clean architecture ⓘ domain-driven design ⓘ enterprise application development ⓘ |
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: SOLID principles Description of subject: SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
SOLID design principles
subject surface form:
Robert C. Martin