EAM.7:4 - Solution

Recover the required outside contribution, recipients, conditions and horizon from EAM.1 and EAM.2. Identify which feature of the incumbent arrangement is an assumption rather than a requirement.

Form materially different ways to supply the contribution. Depending on the problem, these can include changing an existing asset, acquiring a new one, redistributing capability, sharing a provider, leasing a service or changing demand. A renamed supplier offering with the same relevant behavior is not a distinct architectural alternative.

Describe how each option could work. Identify the asset or provider, integration with the present arrangement, interfaces, access, support and changes to operation. Use an applicable SYSE.5 result when functional organization and bearer allocation determine the option. Obtain subject-specific engineering where physics or other specialist constraints decide feasibility.

State the realization conditions and consequences at the same service basis. Include procurement and integration time, interruption, continuing cost, dependency, reversal and exit. Preserve what remains unknown; a proposed interface is not demonstrated compatibility.

Compare the set with the incumbent or a no-build response. Explain why withdrawal, demand change or another contribution is included or excluded in this case. If an option requires amending a service commitment, identify that separate decision rather than assuming the amendment.

Return enough alternatives for EAM.9 to make a genuine comparison. Stop adding options when further generation is unlikely to improve the requested answer at a worthwhile burden. Keep the precise unsupported dependency that prevents a promising option from being used.