Screaming Architecture
E679173
Screaming Architecture is a software design approach that emphasizes organizing code so that the system’s core business domain and use cases are immediately evident from its structure.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Architecture That Screams the Domain | 1 |
| Screaming Architecture canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7666614 — 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: Screaming Architecture Context triple: [Clean Architecture, influencedBy, Screaming Architecture]
-
A.
The Belly of an Architect
The Belly of an Architect is a 1987 art-house drama film directed by Peter Greenaway, centered on an American architect in Rome whose obsession with a historical figure mirrors his own physical and psychological decline.
-
B.
Architext
Architext was an early web search engine company that later became known as Excite, one of the prominent internet portals of the 1990s.
-
C.
My Architect
My Architect is a 2003 documentary film in which Nathaniel Kahn investigates the life, work, and complex personal legacy of his father, the renowned architect Louis Kahn.
-
D.
Vers une architecture
Vers une architecture is a seminal 1923 book by Le Corbusier that articulates his modernist vision for architecture, emphasizing functionalism, industrial aesthetics, and the concept of the house as a "machine for living in."
-
E.
Morphosis
Morphosis is an innovative American architecture firm known for its bold, fragmented forms and experimental, deconstructivist designs.
- 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: Screaming Architecture Target entity description: Screaming Architecture is a software design approach that emphasizes organizing code so that the system’s core business domain and use cases are immediately evident from its structure.
-
A.
The Belly of an Architect
The Belly of an Architect is a 1987 art-house drama film directed by Peter Greenaway, centered on an American architect in Rome whose obsession with a historical figure mirrors his own physical and psychological decline.
-
B.
Architext
Architext was an early web search engine company that later became known as Excite, one of the prominent internet portals of the 1990s.
-
C.
My Architect
My Architect is a 2003 documentary film in which Nathaniel Kahn investigates the life, work, and complex personal legacy of his father, the renowned architect Louis Kahn.
-
D.
Vers une architecture
Vers une architecture is a seminal 1923 book by Le Corbusier that articulates his modernist vision for architecture, emphasizing functionalism, industrial aesthetics, and the concept of the house as a "machine for living in."
-
E.
Morphosis
Morphosis is an innovative American architecture firm known for its bold, fragmented forms and experimental, deconstructivist designs.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf | software architecture style ⓘ |
| aimsToAvoid |
architecture that hides business intent
ⓘ
architecture that only reveals technical frameworks ⓘ |
| alsoKnownAs |
Architecture That Screams the Domain
ⓘ
linked to:
Screaming Architecture
|
| appliesTo |
backend applications
ⓘ
enterprise applications ⓘ microservices ⓘ |
| benefit |
better communication with non-technical stakeholders
ⓘ
clear mapping between business language and code ⓘ easier onboarding for developers ⓘ improved maintainability ⓘ reduced coupling to frameworks ⓘ |
| contrastsWith |
layered architecture organized by technical concerns
ⓘ
package-by-layer organization ⓘ package-by-technical-component organization ⓘ |
| corePrinciple |
architecture should tell you what the system does
ⓘ
domain concepts should be top-level structural elements ⓘ use cases should be first-class citizens in the codebase ⓘ |
| deemphasizes |
framework-specific layers
ⓘ
infrastructure details in top-level structure ⓘ |
| describedIn | blog posts by Robert C. Martin ⓘ |
| designConcern |
dependency direction
ⓘ
module boundaries ⓘ package structure ⓘ |
| discourages |
framework-driven package structure
ⓘ
grouping code primarily by technical layers ⓘ |
| emphasizes |
making the domain model prominent
ⓘ
organizing code by business domain ⓘ organizing code by use cases ⓘ |
| focusesOn |
business rules
ⓘ
use-case level behavior ⓘ |
| goal |
align code structure with business language
ⓘ
improve understandability of system purpose ⓘ make the system’s core business domain evident from its structure ⓘ |
| hasCreator | Robert C. Martin ⓘ |
| influencedBy |
Clean Architecture principles
ⓘ
Domain-Driven Design strategic design ⓘ |
| organizesBy |
application use cases
ⓘ
business capabilities ⓘ domain subdomains ⓘ |
| originatedIn | 2010s ⓘ |
| promotes |
separation of domain and infrastructure
ⓘ
ubiquitous language in code structure ⓘ |
| relatedTo |
Clean Architecture
ⓘ
Domain-Driven Design ⓘ hexagonal architecture ⓘ onion architecture ⓘ |
| typicalStructure |
modules representing use cases or application services
ⓘ
packages named after domain concepts ⓘ |
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: Screaming Architecture Description of subject: Screaming Architecture is a software design approach that emphasizes organizing code so that the system’s core business domain and use cases are immediately evident from its structure.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Screaming Architecture