第10章エンタープライズアーキテクチャーとソリューションアーキテクチャーの管理

The TOGAF Content Framework contains vision, requirements, business architecture, information system architecture, technology, and architecture realization. You can learn more about it by exploring the Content Framework and Enterprise Metamodel (https://openstax.org/r/76OpenGroup) in The Open Group’s official guide. This framework provides an essential structure for managing and aligning IT strategies with business goals.

TOGAF’s foundation architecture sets forth the following:

• Architecture building blocks and standards

• Generic services and functions to build specific services

• Technical reference model

• Standards information base

TOGAF also provides an Enterprise Continuum that addresses the Architecture Continuum and the Solution Continuum, and an Architecture Governance with guidelines relating to the following:

• Management and control of architecture works at an enterprise level

• Repositories

• Process flow control

• Architecture board, including architecture compliance and contracts

• Process and content details (Table 10.3)

The business of evolving solutions to constantly adapt to change is akin to what people face in real life as they react to change when facing unforeseen situations. This happened recently because of the COVID-19 pandemic. It is not always possible to rely on the current state of a solution and its ability to evolve. Sometimes a leap forward must be made, and it is more important to manage the need to evolve rather than try to adapt an existing, and perhaps obsolete, solution. While it differs from traditional EA techniques, EAM provides a management practice that establishes, maintains, and uses a coherent set of guidelines, architecture principles, and governance regimes that provide direction and practical help in the design and development of an enterprise’s architecture to achieve its vision and strategy. As a result, EAM allows leaps forward to face unexpected changes such as having to innovate to remain competitive rather than simply focusing on being the best at providing a given service.

EA is typically used by companies to produce a blueprint of the future state and a road map for getting there.

Companies’ shift to lean and flexible operating models directly affects how their IT workforce architects design future business solutions, wherein it needs to enable the new operating model by advancing business capabilities through efficiently integrated and standardized business processes and corresponding solutions. EA ensures the alignment of business architectures with solution architectures by providing a holistic view that links all architecture domains through an enterprise reference architecture (ERA).

The result of this work, which is produced through an integrated planning process and methodology, aligns and sequences IT investments to optimally achieve the companies’ strategies. The assembly of the road map draws upon three distinct architectural domains:

• Business architecture

• Business solutions architecture

• IT solutions architecture

The adoption road map results from implementation planning, as illustrated in step 8 of Figure 10.27. Creating a road map requires a current state assessment, future state definition, and gap analysis.

Creating a future state model definition requires an understanding of future state needs and the definition of a target strategy based on various business and IT drivers, as illustrated in Figure 10.28.

Developing business drivers requires an evaluation of the dynamics of change that are necessary to keep sustaining the business. Businesses often use the five Porter forces illustrated in Figure 10.29 to analyze business dynamics. To ensure that a product competes in the market, you should study these factors: is there any barrier to entering the market? Are there any competitors competing with your product’s price? Is there any threat of substitute products? What is the buyer and supplier power?