
Architecture Vision
The Architecture Vision domain focuses on an initial sketch of the overall outcome of the architecture work. To ensure success, relevant stakeholders are to be identified, and the context of both business and IT are to be gathered. It includes already formulated business and IT strategies, which are refined for the selected scope within the Strategy and Motivation domain. Finally, the statement of architectural work defines the scope and requirements of what to do in the project’s subsequent phases.
Strategy and Motivation
The Strategy and Motivation domain is the first part of Business Architecture, deriving objectives (value drivers) from company strategic priorities and long-term goals, which establish the company’s vision. This domain ensures that the enterprise architecture is aligned with the business strategy and motivates stakeholders by clearly communicating the benefits and rationale behind architectural decisions and transformations.
Business Architecture
The Business Architecture domain focuses on describing an organization with reference to all business aspects including capabilities, processes, data, and organizational structure. It facilitates business-led discussions with all stakeholders and decisions based on agreed business terms. It enables communication of business values and impact of architecture work to all stakeholders.
Solution Architecture
The Solution Architecture domain covers reference, base, target, and/or transition architectures, focusing on capabilities, processes, data, and organizational structure. The value of Solution Architecture lies in its ability to align technology solutions with business goals and requirements. Solution Architects serve as a bridge between the business side and the technical side of an organization, ensuring that technology solutions are designed and implemented to meet business needs.
Technology Architecture
The Technology Architecture domain documents how the target Solution Architecture building blocks are delivered via technology components (operating systems, virtualized environments, hardware, networks) and depicts the deployment of the organization’s IT systems in specific data center locations.
Road map and Transition
The Road map and Transition domain focuses on overcoming project growth opportunities and managing the transition of systems or processes. It involves pinpointing potential advantages, planning, migrating, and executing changes to efficiently achieve the project’s objectives.
Requirements and Governance
The Requirement and Governance domain is not linked to a particular phase of an architecture engagement. Still, it includes relevant governance artifacts like a risk catalog and architecture principles and captures important architecture decisions such as Architecture Decision Records (ADR). Requirements are not only collected when creating the statement of architecture in the architecture vision domain but can also be displayed with any architecture domain.