SYSE.23:4.1.2 - Trace what has to change and why
Work one scenario through the current arrangement. Begin at the proposed change in functioning, configuration
or interface and ask what must be revised, reproduced, obtained, checked and supported for the result to become
usable. Follow the action-changing dependencies across target parts, descriptions, production means, tests,
release and service. Use the realization branch construction in SYSE.3:4.2–SYSE.3:4.4 rather than reconstructing
a complete builder hierarchy. A branch can stop at an adequate supplied result.
Explain each consequential propagation. A new protocol may require an adapter because its timing differs; an evidence result may need renewal because its configuration basis changed; a rig may require requalification because its emulator now represents a different physical response. Check timing, failure behaviour and support demands even when the interface name is unchanged.
Distinguish two mechanisms that often get mixed:
- Change propagation: modifying one description, interface or implementation requires compatible changes elsewhere before the new configuration can be used.
- Operational propagation: a disturbance or failure in one part affects another during use.
A boundary can reduce one propagation while worsening the other. An adapter may localize future firmware changes yet add response delay or another failure mode. A shared test service may reduce duplicated setup while making several projects depend on its availability. Retain both consequences where they matter.
For every apparent bottleneck, compare the required contribution with what the current arrangement supplies. A slow task can result from intrinsic technical work, repeatable setup, waiting for a shared resource, missing capability, unresolved authority or unavailable evidence. Each suggests a different intervention. The number of touched modules and elapsed time of one change are observations, not a causal decomposition. Use the five claim kinds in §4.1 to keep the supported constraint distinct from the suspected explanation.
The useful intermediate result is a small set of constraining relations and their effects on the chosen scenarios. It can be written directly on the existing architecture or realization account: what change demands what contribution, why, from which System or performer, under which condition, and with what support or gap. Do not model an entire organization when one interface and rig correspondence decides the question.