In which part of the ADM cycle do building block gaps become associated with work packages that will address the gaps?
In which part of the ADM cycle do building block gaps become associated with work packages that will address the gaps?
Phase F is the part of the ADM cycle where building block gaps become associated with work packages that will address the gaps. This phase focuses on implementation governance and the transition from architecture to implementation, which includes the final preparation of the work packages that will deliver the proposed solutions.
Phase E
12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D Consolidate and integrate the gap analysis results from the Business, Information Systems, and Technology Architectures (created in Phases B to D) and assess their implications with respect to potential solutions and inter-dependencies. This should be done by creating a Consolidated Gaps, Solutions, and Dependencies matrix, as shown in Part III, 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix , which will enable the identification of Solution Building Blocks (SBBs) that could potentially address one or more gaps and their associated ABBs. Review the Phase B, C, and D gap analysis results and consolidate them in a single list. The gaps should be consolidated along with potential solutions to the gaps and dependencies. A recommended technique for determining the dependencies is to use sets of views such as the Business Interaction matrix, the Data Entity/Business Function matrix, and the Application/Function matrix to completely relate elements from different architectural domains.