SYSE.22:4.1.2 - Construct family alternatives with a feasible common basis
Develop alternatives around the disputed connection. Change the allocation of behaviour, the physical or computational means, the interface, or the operating arrangement when that could answer the revised question. An alternative can retain the incumbent, vary a current member, add a family branch, change the shared architecture, replace a previously assumed means, or stop pursuing this use. Creativity need not come from one assigned role: production, service and domain practitioners can expose a better candidate through their own constraints and available means.
For each promising alternative, recover what remains common and what must vary. State the retained
architectural commitments, permitted differences and dependencies between differences. Use SYSE.13:4.1
for variant, unit, configuration and effectivity identity. It supplies the distinctions and supported mappings;
the engineering work here determines which proposed combinations can meet this problem.
For example, local fallback, a different compressor, a larger processor and a network gateway are four design choices, not four independent switches. The new compressor may require a different output board; the fallback algorithm may fit only the larger processor; that board may lack an applicable test result. Build a candidate by carrying these dependencies together. Reject an incompatible combination, retain a conditional combination for inquiry, or propose the missing interface or realization change. Do not count the Cartesian product of independently feasible features as reachable family variants.
Retain more than one alternative when they answer materially different conditions or preserve a useful future choice. Ask which differences change admission, value, burden or later reuse; do not expand every possible parameter. The family boundary can also change. If an option requires different functioning, support and evidence assumptions from the shared architecture, compare a separate branch or family with extending the common basis. Forced commonality can move repeated adaptation and service burden into every member.
This produces candidate specifications with explicit variation and compatibility rules. It does not produce new actual Systems or establish that current installed units realize the specifications.