Integrated Design¶
A design process jointly evaluates and revises coupled choices across specialties against shared whole-system goals.
Core Idea¶
Integrated design jointly resolves choices that different specialties make but that constrain one another. Shared goals, cross-specialty evidence and revision of linked decisions distinguish it from merely gathering specialists in a meeting. Whole-building design and embedded hardware/software co-design exhibit the same pattern with very different artifacts.[ref-cf5d4b190e5d][ref-c9aecb4e758a]
Scope of Application¶
In buildings, envelope, daylight, structure and mechanical systems affect one another; an early team can use simulations to compare combined choices. In embedded systems, hardware and software designers can allocate functions under shared performance constraints. The NIST abstract documents a feature–component/virtual-prototype method, not accessible numerical case outcomes. A charrette or shared model can help, but no one meeting format is required, and particular savings are not guaranteed.[ref-cf5d4b190e5d][ref-c9aecb4e758a][^ref-f94ae8c9841d]
Clarity¶
The LANL guide's printed p. 14 gives sample goals—not measured results—of 50% less energy use than an ASHRAE 90.1 baseline, daylighting that offsets electric lighting, and cost no more than 5% above conventional design. Its p. 16 warns that daylight causing work-surface glare fails indoor quality, so glazing, shading, lighting and mechanical choices must be checked together before commitment. Its p. 17 offers another illustrative mechanism: on-site stormwater infiltration can avoid a detention pond and sewers, releasing budget for other project features. No dollar saving is reported. In both examples the whole-project consequence, not the specialist's local optimum, governs the next design revision.[^ref-cf5d4b190e5d]
Manages Complexity¶
The method exposes cross-effects that local optimization can miss. Whole-system evaluation can restrain a local optimum but may sacrifice some of its benefit; broad coordination reveals hidden dependencies but consumes decision time. Early freezing offers procurement certainty yet can push unresolved conflict into expensive field changes. These are choices to calibrate, not universal claims of savings.[^ref-cf5d4b190e5d]
Abstract Reasoning¶
List system-level goals, the variables controlled by each specialty and the dependencies between them. Identify choices that materially change another specialty's feasible options. Evaluate combinations with shared evidence, revise before commitment, and document any interface deliberately chosen to reduce further coupling.[ref-cf5d4b190e5d][ref-c9aecb4e758a]
Knowledge Transfer¶
The reusable pattern is coupled choices, shared evaluation and revision before commitment. Its design identity depends on artifacts, constraints, specialist authority and a revision path; generic collaboration alone is insufficient. The live Design prime is the strict genus for this placement: integrated design is a specialized design process. A wider prime would need evidenced non-design transfer.
[^ref-cf5d4b190e5d]: Los Alamos National Laboratory Sustainable Design Guide, Chapter 2. [^ref-c9aecb4e758a]: NIST, original embedded hardware/software co-design paper. [^ref-f94ae8c9841d]: Abid et al., original hardware/software co-design methodology (1998).
Relationships to Other Abstractions¶
Current abstraction Integrated Design Domain-specific
Parents (1) — more general patterns this builds on
-
Integrated Design is a kind of Design Prime
Integrated design is a specialized design process with coupled cross-specialty revision.
Neighborhood in Abstraction Space¶
Integrated Design sits in a sparse region of the domain-specific corpus (97th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Software Evolution Laws & Code Smells (17 abstractions)
Nearest neighbors
- Performative Architecture — 0.78
- System of Systems Engineering — 0.76
- Capability Management in Business — 0.76
- Change impact analysis — 0.76
- Goal programming — 0.76
Computed from structural-signature embeddings · 2026-10-08