SYSE.22:4.1.3 - Test the join between use, variant and means of realization
A correspondence becomes useful when an engineer can follow why the variant could answer the problem.
For each relied-on pair, connect the outside result to the proposed behaviour, the required configuration,
the means of obtaining it, and the evidence the receiving decision needs. Use the supported realization branch
from SYSE.3:4.2–4.4, a platform result from SYSE.12:4.1, and the applicable SYSE.10 evidence
assessment where these answer the question. Open only the first unsupported result that can change
the decision.
The conditions must hold together. A candidate that fits one board, a test that covers another firmware
realization, and a service procedure for a third installation do not combine into one supported family option.
Likewise, separate statements that two trials can each use the only rig this week do not make their simultaneous
commitment feasible. Compare compatible configurations, conditions and receiving decisions, and check shared
capacity where the portfolio relies on simultaneous Work. Use SYSE.20 when overlap or acceptance of a
partial result is the engineering question.
Keep two different conclusions visible. An option can deserve development attention while its operational admission remains unresolved. A bounded experiment can be feasible even when its subject variant is not yet admissible for ordinary use. State the scope of admission at the receiving decision; evidence sufficient to select a probe does not become evidence that permits deployment.
Use a failed join constructively. If a variant cannot be tested within the existing arrangement, the result
may be a precise builder investment question for SYSE.23. If the proposed behaviour cannot supply the
required outside effect, return to the use–concept pair. If every candidate fails a protected condition,
reject the set or seek an authorized reformulation; ranking failed options cannot supply a successful one.