Business scenarios are an important technique that may be used at various stages of the enterprise

architecture, principally the Architecture Vision and the Business Architecture, but in other architecture

domains as well, if required, to derive the characteristics of the architecture directly from the high-level

requirements of the business. They are used to help identify and understand business needs, and

thereby to derive the business requirements that the architecture development has to address.

Because business requirements are important throughout all phases of the ADM cycle, the business scenario technique has an important role to play in the TOGAF ADM, by ensuring that the business requirements themselves are complete and correct.

Business scenarios figure most prominently in the initial phase of the Architecture Development Method (ADM), Architecture Vision, when they are used to define relevant business requirements, and to build consensus with business management and other stakeholders.

The ADM has its own method (a \"method-within-a-method\") for identifying and articulating the business requirements implied in new business capability to address key business drivers, and the implied architecture requirements.

This process is known as \"business scenarios\", and is described in Part III, 26. Business Scenarios and Business Goals. The technique may be used iteratively, at different levels of detail in the hierarchical decomposition of the Business Architecture.

Phase H includes an objective to ensure that the Architecture Governance Framework is executed

TOGAF 9.1