SYSE.10:11 - SoTA and Source Use
When using research to make an engineering decision, distinguish the physical phenomenon, model, computation, hypothesis, experiment, observation, evidence, candidate and decision. Return what the investigation supports for that decision and state the conditions of reliance. Select a specialized research line when it can change the practitioner move under consideration.
| Source line | Retained contribution | Limit and guard |
|---|---|---|
Current FPF C.11:4.2.2–4.2.4 and Huan, Jagalur, and Marzouk 2024/2026 | An authorized Agent applies C.11 to choose on the current comparison basis and, when further inquiry is a live alternative, compare a feasible local probe using budget, cost and its value to the decision. The result can select a current option, reject the set, choose a probe, or reroute; current OED distinguishes the design of experiment sets and sequential policies through utility, design variables, model assumptions, computation, and robustness. | Assessment Work guided by SYSE.10 produces an engineering claim assessment; when further evidence is chosen, it uses a compatible C.11 or specialist experimental-design result. C.29 can govern a mathematical-lens use, but neither a lens nor this assessment is an experiment plan. |
| Riedmaier et al. 2021 and Schwarzburg et al. 2024 | Decision-specific model use requires verification, validation, uncertainty quantification, extrapolation attention and consideration of model history, competence, access and decision risk. | No one VV&UQ Method is universal; the 2024 practitioner sample is small and non-probability. Confidence is not truth, physical adequacy, decision correctness or complete reliability. |
| Papalambros et al. 2025, Yilmaz et al. 2015, and Koen 2003 | Heuristics can be context-dependent strategies for intentional variation and candidate generation; current field synthesis retains their engineering relevance. | Koen is historical and philosophical; the 2015 experiment is one short task; the 2025 source is a retrospective. No heuristic family becomes universal law or proof of effectiveness. |
| Lehner et al. 2025 | Digital-twin engineering uses heterogeneous model transformations, code generation and interpretation across design, implementation and operation. | The mapped literature is manufacturing- and transport-heavy with heterogeneous maturity; it establishes neither one twin ontology nor physical evidence by synchronization. |
| Hernández et al. 2023, Norheim et al. 2024, and Kosenkov et al. 2025 | Requirements and compliance Work persist under continuous software and cyber-physical development through collaboration, traceability, monitoring, models and changing descriptions. | The evidence is software-heavy and uses requirements in several senses. It neither restores a requirements phase nor shows that legal interpretation, independent assurance or physical evidence disappear. |
| Mohanani et al. 2022, Binamungu and Maro 2023, Fakhoury et al. 2024, and Wang et al. 2025 | BDD, test-driven interaction and requirements-driven testing can connect selected software intents, scenarios and executable checks; template fixation and incomplete automation remain material. | Software cases do not turn tests into obligations, outside-use effects, acceptance, compliance or complete assurance; industry evidence and full automation remain limited. |
| Krajcer et al. 2026 and Mirzaei et al. 2026 | Current evidence supports task-specific AI acceleration or widening alongside losses in engagement, confidence, opacity, bias and diversity; critical evaluation and integration remain necessary. | The experiment concerns novice UX students and one tool family; the review aggregates heterogeneous design-thinking studies. Neither establishes transfer across engineering profiles or holder replacement. |
| Becker et al. 2025 with the 2026 METR update, Agarwal et al. 2026, and Pradas Gomez et al. 2025 | AI already participates in bounded software and engineering-design Work, with task-, quality-, prior-use- and integration-dependent results. | The sources do not establish universal productivity, complete engineering autonomy, independent problem selection, authority transfer, or correctness of generated evidence. |
Treat “current SoTA” as claim- and use-specific. A newer paper does not automatically supersede a still-useful Method; it must change the relied-on claim, alternative, validity boundary or engineering move. Conversely, an old standard, famous framework or official procedure does not remain current merely because it is widely cited. Use expert judgment with an explicit epistemic status when direct comparative evidence is unavailable and the cost of obtaining it would exceed the decision value.