fpf.tools
Library / Systems Engineering Principles Framework
Jump to passage
In this reading
Source · lines 5532–5543

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:25:05 UTC

SYSE.11:11 - SoTA and Source Use

Source lineAdopted contributionLimit retained
SEBoK v2.14, Applying the Systems Approach, 18 May 2026, Application PrinciplesConcurrent, iterative, recursive application and successive evolutionary solutions.The source keeps older lifecycle and requirements framing and does not establish comparative SoTA.
DORA, Trunk-based development, Continuous integration, Continuous delivery and Streamlining change approval; Steven Thurgood, Example Error Budget Policy, SRE Workbook (2018); Zampetti et al., Continuous Integration and Delivery Practices for Cyber-Physical Systems: An Interview-Based Study, ACM TOSEM 32(3), article 73Frequent integration, automated and physical checks, feedback, and risk-sensitive review in bounded software/CPS settings.No universal cadence, pipeline, complete automation, or removal of independent assurance transfers.
Hernández, Moros and Nicolás, Requirements management in DevOps environments: a multivocal mapping study (2023); Norheim et al., Challenges in applying large language models to requirements engineering tasks (2024); Kosenkov et al., Systematic mapping study on requirements engineering for regulatory compliance of software systems (2025)Requirements, traceability, monitoring, models, and compliance Work continue during rapid change.Software/CPS-heavy evidence does not establish one requirements phase or Method.
Eichenwald et al., Production system ontology for continuous Capability-based Engineering, Procedia CIRP 128 (2024), 387–392; Ghanjaoui et al., Model-based assembly process planning for flexible aircraft cabin architectures (2024), §§1–3 and 5–6; Meixner et al., Variability Modeling of Products, Processes, and Resources in Cyber-Physical Production Systems Engineering (2024), §§2.1 and 5–7Product, process, resource, capability, and architecture evidence return during manufacturing and assembly planning.Small proposed methods and cases do not establish one cross-domain PPR ontology or toolchain.

This pattern develops the engineering move from completed parts to bounded integrated use. Current sources refine that move within their stated application settings. Reopen when comparative evidence changes the cross-domain integration boundary or an application profile needs a different specialized Method.