How to implement the ADM Phases E, F, and G to implement an architecture, together with the applicable techniques

Marrick County is in Phase E of an architecture that links its social-services case system with three partner agencies. Today the agencies email spreadsheets to each other. The Target Architecture requires that case records sent by one agency are processed automatically by the receiving system using a shared data model, without staff re-keying them. Stakeholders disagree on how much integration is really needed.

How should the architect express and agree the interoperability needed for each exchange?

1. AUse the Interoperability Requirements technique to state the required degree of interoperability for each information exchange, such as seamless sharing of data, and record it in an interoperability matrix agreed with the stakeholders.The technique defines degrees of interoperability, from unstructured data exchange through structured exchange and seamless sharing of data to seamless sharing of information, so each exchange can be stated and agreed precisely.
2. BRun a Business Transformation Readiness Assessment for each agency and use the readiness scores as the interoperability requirements.A readiness assessment evaluates an organisation's ability to undergo change. It does not specify how systems must exchange data.
3. CAdd the partner agencies to the power/interest grid and let the agency with the highest power decide the integration level.Stakeholder mapping decides how to engage stakeholders. It is not a method for defining interoperability, and letting one stakeholder decide skips the requirements agreement.
4. DLeave the integration level for each implementation project to decide in Phase G and capture the decision in its Architecture Contract.Interoperability requirements are consolidated and reconciled in Phase E so that work packages and Transition Architectures can be planned. Deferring them to Phase G leaves the migration plan without a basis.

Langstone Retail's Head of Stores sponsors the store-systems architecture. Before funding implementation, she wants a formal agreement stating what the architecture will deliver to the stores business, the quality expected, and how the architecture function will ensure that delivered solutions remain fit for purpose. A separate agreement with the systems integrator is already in place.

What should the architect put in place for the Head of Stores?

1. AA Compliance Assessment signed by the Head of Stores.A Compliance Assessment records the result of a compliance review of a project. It is not an agreement on what the architecture will deliver.
2. BA Communications Plan describing how stores staff will be told about the new systems.A Communications Plan schedules stakeholder communication. It does not set out deliverables, quality or fitness for purpose.
3. CA dispensation that allows the stores business to fund implementation outside the normal governance process.A dispensation permits a project to deviate from the architecture. It is not a sponsor agreement.
4. DAn Architecture Contract between the architecting function and the business users.The TOGAF Standard describes Architecture Contracts between the architecting function and business users, alongside contracts with development partners.

Elstow Energy's architect is in Phase E with 35 gaps from Phases B to D. Several gaps could be closed by the same solution, some solutions depend on others, and the steering committee wants to see how gaps, potential solutions and dependencies relate before work packages are formed.

Which technique should the architect use?

1. AThe Consolidated Gaps, Solutions, and Dependencies Matrix.This matrix lists the gaps from the domain architectures with their potential solutions and dependencies, and is the basis for creating work packages.
2. BThe Architecture Definition Increments Table.This table lists the projects and their incremental deliverables across Transition Architectures. It is used after work packages and transitions are defined.
3. CA stakeholder map matrix.Stakeholder maps support engagement planning and do not relate gaps to solutions.
4. DThe Business Transformation Readiness Assessment.This assessment evaluates the organisation's readiness to undergo change. It does not consolidate gaps or solutions.

Dunmore Logistics is in Phase E. Phase B recorded that dispatchers must see live vehicle positions inside the order system, but Phase D recorded that the vehicle telematics platform can only export files every hour. The two requirements were captured by different teams and have never been compared.

What should the architect do?

1. AAccept the Phase D constraint and remove the Phase B requirement from the Architecture Requirements Specification without consulting stakeholders.Removing a business requirement unilaterally bypasses Requirements Management and stakeholder agreement.
2. BConsolidate and reconcile the interoperability requirements from Phases B to D, resolve the conflict with stakeholders, and reflect the agreed requirement in the work packages.Phase E includes a step to consolidate and reconcile interoperability requirements so that conflicts like this are resolved before migration planning.
3. CDefer the conflict to the Phase G compliance review of the telematics project.A compliance review checks a project against an agreed architecture. Here the architecture itself contains conflicting requirements.
4. DRaise a re-architecting Change Request in Phase H.The architecture has not been implemented, so Phase H change classification does not apply.