Organization looking into Enterprise Architecture and specifically TOGAF 9 may consider adopting a Business Analysis framework such as BABOK and integrate them in the Preliminary Phase.If both approaches exist in a company, this would be a great opportunity for optimizing the alignment between Business and IT, and to run an Enterprise Architecture program from a complete business perspective.Previously in a Pharmaceutical (Chemical) company, in charge of the worldwide Enterprise Architecture program and Governance, the IT Research & Innovation, following the reorganization of the IT Department, implementing Service Management based on ITIL Best Practices and deploying new processes: Change, Configuration, Release, and Capacity/Availability Management, responsible for the Disaster Recovery Plan and for the System Management team.
I'm not sure your diagram mapping TOGAF to BABOK makes sense.
If TOGAF is an enterprise-focussed implementation of the BABOK (as I posit above), then TOGAF A to H are all primarily related to three KAs: EA (most enterprise focus), SAV (straddles enterprise and project focus) and BAPM (more project focus, but with a strong enterprise view).
Enterprise Analysis is a knowledge area which describes the Business analysis activities that take place for an enterprise to identify business opportunities, build a Business Architecture, determine the optimum project investment path for that enterprise and finally, implement new business and technical solutions.
The question you may ask: Does this really differs from Enterprise Architecture, and if so, how?
The BABOK® Guide describes Business Analysis areas of knowledge, their associated activities and the tasks and skills necessary to be effective in their execution.
The BABOK® Guide is a reference for professional knowledge for Business Analysis and provides the basis for the Certified Business Analysis Professional™ (CBAP®) Certification.It describes business analysis areas of knowledge, their associated activities and tasks and the skills necessary to be effective in the execution: This describes the interview and research process-how to best extract needs from stakeholders (and even how to recognize needs they don't know they have).Elements such as metrics (tracking the amount of time spent eliciting requirements) and elicitation techniques (prototyping and brainstorming are just a couple) among the topics covered Phase A: Architecture Vision is the initial phase of an architecture development cycle.They are defined at a high level, and include goals, objectives, and needs are identified Business Requirements are collected from business people during the Architecture Vision’s phase using the technique called Business Scenario (as mentioned above).That document identifies what will be the business solutions in generic terms This outlines the crucial (and sometimes political) process of keeping everyone in the loop and on the same page regarding project's direction and progress.The BABOK specifies dependencies in tasks, where TOGAF specifies a sequence of tasks.