Construct · 4 fields · 7 citations
One name. Different field. Different construct. One map.
● jingle · one word, four constructs Nearest construct by meaningcommunitycompare the meaningsEvery construct on the map is compared with every other by the meaning of its definitions, and the closest one is surfaced here. The nearest construct to modularity is community.
Hold this as a prompt, not a verdict. Two constructs sitting close in meaning is a reason to read them side by side and decide for yourself whether they are one idea under two names. It is not proof that they are. Compare the meanings in the Collider.
Spokes are fields; dashed arcs are shared lineage. Tap a field for its definition, unit, and measures.
Drag to watch the word get claimed. Each field appears at the publication date of the earliest source cited for it. Tap a year to see which.
The design of a product or system as a set of largely independent modules that connect through standardized interfaces, so that each module can be built, changed, or replaced with little effect on the others. Ulrich's 1995 The role of product architecture in the manufacturing firm tied this to how a product's functions are mapped onto its physical components, and Baldwin and Clark's 2000 Design rules: The power of modularity treated modular design as a source of strategic flexibility and industry structure. Here modularity is a property a designer builds into an artifact, judged by how cleanly the components separate, and it is different from a computed score on a network, a biologist's semi-independent body parts, or a philosopher's account of the mind.[1][2]
A single number that measures how well a network splits into communities, comparing the fraction of links that fall inside groups against what would be expected if the same links were placed at random. Newman and Girvan's 2004 Finding and evaluating community structure in networks introduced this quantity, and Newman's 2006 Modularity and community structure in networks showed how to find the grouping that makes it as large as possible. Here modularity is a computed quality of a particular partition, high when a grouping captures real structure, and it is not a design property of a product, a feature of an organism, or a claim about the architecture of the mind.[3][4]
The organization of an organism into units, whether developmental, genetic, or anatomical, whose parts are tightly connected within a unit and only loosely connected between units, so that each unit can vary and evolve somewhat on its own. Wagner and Altenberg's 1996 Perspective: Complex adaptations and the evolution of evolvability argued that such a modular map from genes to traits makes a lineage more able to adapt, and Wagner, Pavlicev, and Cheverud's 2007 The road to modularity reviewed the evidence for it. Here modularity describes how a living body is partitioned into quasi-independent parts, inferred from patterns of variation, and it is separate from a designed product, a network score, or a theory of the mind.[5][6]
The claim that the mind contains special-purpose systems, each dedicated to a narrow task such as recognizing faces or parsing speech, that work quickly and automatically and cannot be freely steered by the rest of what a person knows. Fodor's 1983 The modularity of mind set out these features, including domain specificity and what he called informational encapsulation, the way such a system is sealed off from general knowledge. Here modularity is a proposed feature of how the mind is built, argued from behavior and from brain injury, and it does not name a designed product, a network score, or the evolving parts of a body.[7]
Next
See how modularity sits against neighbouring constructs in the Collider, or export every reference on this page in one click.
Open in ColliderExport BibTeXReport this collisionCited on this page?
If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.
Claim your construct