Targetarchitecturen

Targetarchitecturen, or the target architecture, is the envisaged future state of a system, application landscape, or enterprise IT environment. It specifies the desired structure, components, interfaces, data flows, and non-functional requirements needed to achieve strategic business objectives.

It contrasts with the current (as-is) architecture and serves as a guiding reference for transformation programs, capital allocation, and technology choices. The target state provides a stable vision against which projects and investments can be evaluated.

Key elements typically include scope and boundaries, architectural principles, reference models, technology stack decisions, data and security architectures, integration patterns, and a transition roadmap describing how to reach the future state in phases.

Development often occurs within an architecture practice using frameworks such as TOGAF, Zachman, or other enterprise architecture methodologies. The process usually covers business understanding, baseline assessment, future-state design, gap analysis, migration planning, and governance to ensure alignment with strategy.

Artifacts associated with the target architecture include a target architecture document, capability maps, technology roadmaps, migration plans, and architecture principles. These documents guide solution design, procurement, and program management, and are typically reviewed by an architecture review board.

Typical use cases include cloud migration to a scalable, modular architecture; consolidation of legacy systems; and adoption of service-oriented, microservices, or event-driven patterns to improve agility and interoperability.

Risks include scope creep, misalignment with business goals, and excessive complexity. Successful use requires ongoing governance, stakeholder engagement, and regular updates to reflect evolving business strategies and technology options. See also enterprise architecture, TOGAF, architecture framework, as-is and to-be architecture.