Explanation
The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization. The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work. It covers both functional and non-functional requirements as well as constraints and assumptions.

Explanation
In the ADM documents which are under development and have not undergone any formal review and approval process are called "draft". This indicates that they are subject to change and refinement as the architecture development progresses. Reference: The TOGAF Standard | The Open Group Website, Section
4.2.5 Architecture Deliverables.

The objective of the ADM Implementation Governance Phase is to provide an architectural oversight of the implementation and to ensure conformance for the target architecture. This phase involves establishing procedures and processes to monitor and control the implementation projects and to verify that they comply with the defined architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.7 Phase G: Implementation Governance.

According to the TOGAF standard, the objectives of each ADM phase are as follows1:
*Phase E: Opportunities and Solutions
oDetermine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value oIdentify and group major work packages within the Architecture Roadmap oIdentify and group major implementation projects to realize the Architecture Roadmap oIdentify dependencies between increments and projects oEstimate cost, benefit, and risk at a high level for each increment and project oConduct initial prioritization and sequencing of the Architecture Roadmap and projects
*Phase F: Migration Planning
oGenerate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D oConfirm the Transition Architectures with relevant stakeholders oCreate the Implementation and Migration Plan, including Transition Architectures, work packages, projects, and other activities oConfirm and agree the Architecture Roadmap and Implementation and Migration Plan with relevant stakeholders
*Phase G: Implementation Governance
oFinalize the Architecture Roadmap and the supporting Implementation and Migration Plan oEnsure conformance with the Target Architecture by implementation projects oPerform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests oEnsure that the architecture lifecycle is maintained oEnsure that the Architecture Governance Framework is executed
*Phase H: Architecture Change Management
oEnsure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders oManage risks and issues related to the Architecture Roadmap and Implementation and Migration Plan oMonitor the implementation projects and Transition Architectures oManage changes to the architecture baseline oManage changes to the Architecture Capability Therefore, the correct matching of the objectives and the phases is:
*1G: Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
*2E: Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
*3F: Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
*4F: Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders References: 1: The TOGAF Architecture Development Method

Explanation
The Implementation Governance Model is a framework that defines the roles, responsibilities, processes, and standards for governing the implementation of the target architecture. It ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance, which is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. The Implementation Governance Model is part of the Implementation and Migration Plan, which is the output of Phase F: Migration Planning of the Architecture Development Method (ADM)12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50:
Architecture Governance