Which of the following does the TOGAF ADM recommend for use in developing an Architecture Vision document?
Which of the following does the TOGAF ADM recommend for use in developing an Architecture Vision document?
In the context of the TOGAF ADM, Business Scenarios are a recommended technique for developing an Architecture Vision document. They help in discovering and documenting business requirements and in articulating an Architecture Vision that responds to those requirements. Business Scenarios provide a structured approach for defining business problems and potential solutions in the context of the architecture development.
A - Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that responds to those requirements. Business scenarios may also be used at more detailed levels of the architecture work (e.g., in Phase B) and are described in the TOGAF® Series Guide: Business Scenarios.
A Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an architectural vision that responds to those requirements. Business scenarios are described in Part IV: Resource Base, Business Scenarios . Once an Architecture Vision is defined and documented in the Statement of Architecture Work, it is critical to use it to build a consensus, as described in Part IV: Resource Base, IT Governance . Without this consensus it is very unlikely that the final architecture will be accepted by the organization as a whole. The consensus is represented by the sponsoring organization signing the Statement of Architecture Work. Inputs
https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap06.html 6.3.8 Develop Architecture Vision Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that responds to those requirements. Business scenarios may also be used at more detailed levels of the architecture work (e.g., in Phase B) and are described in the TOGAF® Series Guide: Business Scenarios.
A Business Scenarios
A - Business Scenarios
It should be Business Scenario
https://pubs.opengroup.org/architecture/togaf92-doc/arch/chap06.html#tag_06_03_08 Based on the stakeholder concerns, business capability requirements, scope, constraints, and principles, create a high-level view of the Baseline and Target Architectures. The Architecture Vision typically covers the breadth of scope identified for the project, at a high level. Informal techniques are often employed. A common practice is to draw a simple solution concept diagram that illustrates concisely the major components of the solution and how the solution will result in benefit for the enterprise. Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that responds to those requirements. Business scenarios may also be used at more detailed levels of the architecture work (e.g., in Phase B) and are described in the TOGAF® Series Guide: Business Scenarios.
the Answer is A
Answer A. https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap06.html 6.3.8 Develop Architecture Vision Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that responds to those requirements. Business scenarios may also be used at more detailed levels of the architecture work (e.g., in Phase B) and are described in the TOGAF® Series Guide: Business Scenarios.