SYSE.5:11 - SoTA and Source Use
Functional and constructive organization can diverge. Compare function-to-bearer allocations, including many-to-many relations, together with interfaces, intended and unintended uses, integration and later revision. Current FPF distinctions govern the selected views, roles and allocation relations used in that comparison.
| Source line | Use here | Epistemic boundary |
|---|---|---|
| Eisenbart, Gericke, and Blessing 2017, Yildirim and Campean 2020, and She, Belanger, and Bartels 2024 | Supports heterogeneous function-model purposes and formalisms, iterative functional/structural reasoning, flow- and time-aware analysis, and functional decomposition as an exploratory move. | The reported ten-company exploration, mobility case, and preliminary metrics example support their bounded uses. Notation, sequence, broad effectiveness, and decomposition policy remain open questions. |
| Monetti, Lundström, and Maffei 2025 and Grønvald et al. 2026 | Brings assembly and modular-product consequences into early candidate development and requires explicit economic and data limits. | The sparse, bounded company evidence supports local assembly and modular-product consequences. Broader benefit, cost, substitutability, and Method-dominance claims remain open. |
| Haddad and Seibel 2025 | Supports AI-assisted generation and iterative refinement of candidate function structures. | The bounded course comparison reported 42% error-free and 72% fully connected outputs for its best configuration and left, for example, non-functional requirements, domain interdependencies, physical effects, and principal solutions outside. Use it as evidence for candidate generation under the reported conditions; project correctness, bearer feasibility, and architecture selection require project evidence. |
Current FPF A.6.F, A.6.M, A.22, C.30–C.32, C.31, representation, comparison, evidence, and assurance patterns | Used for the normative ontology and transdisciplinary candidate-synthesis machinery. | This DPF uses those kinds and the general palette, then adds the applied Systems Engineering Method and result needed for engineered functional contribution, bearer allocation, physical interfaces, realization, integration, wrong-use challenge, and decision use. |
Official modular-open-system or model-based guidance may contain current interface fields or candidate prompts. Treat enacted project prevalence, interoperability, effectiveness, and SoTA as separate claims grounded by direct industrial observations or qualified expert estimates when stronger evidence is unavailable. State their epistemic status. Reopen only the claims affected by a newer source that changes the allocation Method, interface test, AI-use boundary, modularity consequence, or application-profile restriction.