Enterprise Architecture Functional Component

id EAID D3A0314D 41B1 411e 93ED 8F861134CC21
Figure 1. Enterprise Architecture Functional Component Model

Purpose

The Enterprise Architecture functional component manages Enterprise Architectures that will ensure a coherent and optimized portfolio of Digital Products that address enterprise business needs on a long-term basis.

The Enterprise Architecture functional component supports the value streams:

Functional Criteria

The Enterprise Architecture functional component:

  • Shall be the system of record (authoritative source) for all Architecture Roadmaps and Architecture Roadmap Items

  • Shall develop an Architecture Vision, based on business strategy, goals, and high-level Portfolio Backlog Items that define the capabilities and business value to be delivered

  • Shall develop or use existing baseline state Business, Information, Application, Technology, and Security architectural artifacts based on stakeholder assessments of the current state

  • Shall develop target state Business, Information, Application, Technology, and Security architectural artifacts based on strategies, principles, and policies

  • Shall identify gaps between Baseline and Target Architectures

  • Shall create an architecture definition document (or Architecture Blueprint)

  • Shall identify the migration strategy

  • May identify intermediate Architecture Roadmap Items that will deliver continuous business value, if an incremental approach is required

  • Shall identify reusable building blocks, which are a package of functionality designed to meet business needs across the organization

    The building blocks can either be Architecture Building Blocks (ABBs) or Solution Building Blocks (SBBs), where ABBs are realized through the application of the ADM and guide the creation of SBBs; see the TOGAF Standard.

  • Shall identify Digital Products (SBB) that realize the Target Architecture

  • Shall ensure that the architectural artifacts are compliant with all standards and policies, including security standards and policies

  • Shall ensure that the realized architecture meets the KPIs and SLAs

  • Shall ensure that each Architecture Blueprint addresses Portfolio Backlog Items and stakeholder concerns

  • Shall ensure that the output of the Enterprise Architecture functional component is used by the Product Portfolio functional component to define the Digital Products that need to be created

  • Shall ensure the compliance of created Digital Products to the Architecture Roadmap and Architecture Blueprint artifacts

  • Can receive Strategic Objective information which includes the objectives and some content based upon which the Enterprise Architecture is developed if a Strategy functional component exists

  • Can receive Portfolio Backlog Item information from the Portfolio Backlog functional component used to create the Architecture Roadmap and Architecture Blueprint if a Portfolio Backlog functional component exists