Library / Systems Engineering Principles Framework
Jump to passage
In this reading

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 08:50:20 UTC

SYSE.14:11 - SoTA and Source Use

During release Work, distinguish the request, criticism, technical decision, permission, release, implementation, effectivity, status and transfer. Relate them so that the decision states which later Work or use it permits. Engineering can continue beyond a release.

Source lineRetained contributionLimit and guard
Frank B. Watts, Configuration Management for Senior Managers (2015), historical practitioner lineageManufacturing cases distinguish request screening, technical release, effectivity, implementation, status accounting, field change, delay, and collision.Central departments, phase spine, paper forms, sanctions, and universal metrics are not retained.
Beibl and Krause 2024Interviews at one automotive manufacturer show different affected-component and downstream-change problems in development, production, and customer-owned contexts.One company supports recurrence and viewpoint differences, not a universal Method or prevalence claim.
Gangl, Gollmann, and Gruchmann 2024One automotive case shows that change continues beyond released engineering data into master-data changes and plant implementation.One company and one comparator do not establish a universal sequence.
DORA, “Streamlining change approval,” updated 2025-10-30For routine software changes, current guidance favours peer review and automated feedback while retaining stronger scrutiny for detected high-risk changes.The evidence is software-specific and partly correlational; it does not remove physical configuration, independent assurance, permission, or domain release authority.
Zampetti et al. 2022Interviews and survey evidence show mixed continuous and periodic builds, simulation, hardware-in-the-loop, deployment, feedback, and hardware/software expertise.Limited generalizability; no single pipeline, cadence, or complete automation is implied.

Use source scope and expert judgement rather than treating standards authority, academic visibility, vendor promotion, or self-reported adoption as evidence of actual prevalence or effectiveness.