Metraipolis › archive › dc_2e45d99ce422

Engineering as Code: Bringing Software Engineering Methodology to Engineering Design — arXiv:2609.04216

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.04216
License (as archived)
CC0-1.0
Archived
2026-10-16T23:01:22.993Z
SHA-256 of the archived text
fa14ea89cadd6995aeea5720d876fcd9fd2034651c3362a108adb8668f26c99e
Stable URL of this page
https://metraipolis.com/documento/dc_2e45d99ce422

How to cite

Engineering as Code: Bringing Software Engineering Methodology to Engineering Design — arXiv:2609.04216 — arXiv (en), https://arxiv.org/abs/2609.04216 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_2e45d99ce422 (Metraipolis archive dc_2e45d99ce422, sha256 fa14ea89cadd6995aeea5720d876fcd9fd2034651c3362a108adb8668f26c99e)
BibTeX
@misc{dc2e45d99ce422,
  title = {Engineering as Code: Bringing Software Engineering Methodology to Engineering Design — arXiv:2609.04216},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.04216},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_2e45d99ce422; sha256 fa14ea89cadd6995aeea5720d876fcd9fd2034651c3362a108adb8668f26c99e},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.04216. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Large language models have made significant progress in verifiable domains such as code generation and chip design, yet remain limited on engineering design tasks in fields like architecture, mechanical engineering, and HVAC. This paper argues the root cause is not model capability but the absence of a "Design as Code" computable foundation: design representations that can be consumed, verified, and versioned by machines. Existing CAD/BIM systems couple design logic with geometry, causing quality assurance to drift downstream; Automated Compliance Checking (ACC) suffers from geometric false positives and naming-dependent model reconstruction overhead. We propose the Engineering as Code (EaC) paradigm: expressing engineering design as text-native declarative language with automated rule engines, version control, and package management as quality gates. Core contributions: (1) the Information Representation Hypothesis, arguing the engineering AI bottleneck stems from missing computable design representations rather than model capability; (2) ADL (Assembly Definition Language) with Part as atom, organized into three orthogonal sub-languages -- PDL (Part Definition), PML (Part Mating), and PLL (Part Layout); (3) ESA (Engineering Static Analysis), shifting compliance checking from downstream review to design-time, operating on semantic categories (Family types, Mate relations) rather than geometry, eliminating false positives and naming dependencies. A prototype validates ADL expressiveness and ESA detection across three cross-domain samples (telecom rack expansion, modular datacenter, mechanical keyboard), checking 69 rules in under 200ms. A controlled violation injection experiment achieves 100% detection rate with zero false positives. The SD-HWE-Bench benchmark design is complete as an empirical testbed for the hypothesis.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-07 in cs.SE).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2609.04216 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-16T22:37:16.587Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-07?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).