Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-22 19:46:44 UTC · snapshot created 2026-11-22 19:47:46 UTC · last check 2026-11-22 20:35:05 UTC

SYSE.23:4.1.3 - Construct mechanisms on both sides of the constraint

For each limiting relation, ask which premise an intervention could change. Keep the incumbent as the common basis and construct materially different responses. The following alternatives illustrate how to reason.

Limiting relationChange to considerWhy it could help and what it can worsen
A supplier difference propagates into several target partsStabilize a boundary and place the varying behaviour behind an adapterLocalizes some later changes; adds translation, interface qualification and possible run-time cost
Target differences are manageable, but every variant needs a new setupReconfigure or parameterize the production or test meansReuses setup and description-to-configuration relations; creates parameter validation and provider maintenance Work
A common asset forces unrelated members to change togetherSeparate a justified branch or accept bounded duplicationReduces coordinated change; increases maintenance, stock, evidence and eventual reconciliation burden
Configuration differences repeatedly invalidate evidenceChange the family rule and the evidence argument togetherCan make qualified reuse explicit; no identifier or automation by itself establishes that the earlier evidence applies
Suitable technical means exist but practitioners cannot obtain a usable resultChange access, service provision, Method, support or assignment under its proper authorityCan remove waiting or missing support; may move burden to another provider or demand capability development
The next change is singular and the retained architecture remains adequateMake a local adaptation, defer generalization, or retain the incumbentAvoids speculative investment; can leave later changes expensive or foreclose options if the commitment is irreversible

Derive an alternative through the complete scenario. A target-only change is insufficient when the unchanged rig cannot represent the new behaviour. A builder-only change may work by accepting wider test and maintenance Work. A mixed change can reduce that wider burden, but it adds migration and coordination. Demonstrate those differences; the label “mixed” gives no presumption of superiority.

A builder can itself need a new fixture, Method, service or qualified performer. Apply SYSE.3:4.4 to that specific unresolved branch. Recursion ends when a compatible supported means is available, an attainable next inquiry is selected, or the investment is rejected or narrowed. It does not require developing every builder anew.

When architecture and team responsibilities must change together, involve the affected practitioners in the same technical reasoning. Explain the constraint that supports or limits the proposal, the proposed boundary, which later decisions are fixed or open, and what evidence would overturn the proposal. Ask the production, test and service contributors to carry the scenario through their work and report any incompatibility they can substantiate. Organization redesign, assignments and authority need their own decisions and Methods. SYSE.6:4.1 supplies the architecture decision’s fixed/open constraints and receiving uses.