The different levels of an architecture within the TOGAF standard

TOGAF Architecture Development Method (ADM) - Deliverables Preliminary Objectives The objectives for the Preliminary phase are: Prepare the organization for successful architecture projects Establish the foundation for architecture capability, principles and framework Define the scope and constraints for architecture projects Deliverables Architecture Capability Assessment Architecture Capability Gap Analysis Organisational Model for Enterprise Architecture Architecture Framework - tailored for organisation and customisations of ADM Architecture Principles Architecture Governance Framework Architecture Request for Work (Scope) Phase A - Architecture Vision Objectives The objectives for the Architecture Vision phase are: ...

Overview The Architecture Development Framework(ADF) can be used to iteratively deliver and Enterprise Architecture Capability. Capability Topic ADM Level Enterprise Deliverables EA Capability Deliverables Enterprise & EA Content Phase B Partial Strategic - Goals, Objectives, Initiatives, Competitive and Tactics Analysis - Goals - Operating model (partners, supplier) - Explore what-if scenarios and scorecards Business Objectives Phase A Capability None - Provide initial goals and objectives - Select a reference EA Capability and Maturity Model - Candidate EA Capability - Candidate Operating Model - EA Capability Gap and Priority Roadmap Architecture Governance Phase B Partial Segment/Capability - Enterprise Risk Management Model - Risk Management Model - Governance Model - Governance Model - Extend Candidate Operating Model to include EA Governance - Initial Architecture Partition Model - Trace to EA Capability Goals Alignment with other Frameworks Phase B & Partial Phase C (Data) Partial Capability - Reference Models for key frameworks - Framework touch-points - Capability Assessment of Key Frameworks - Extend Candidate Operating Model to include other Frameworks - Extend EA Governance and EA Risk Management - Initial EA Content Framework aligned to other Frameworks and EA Governance - Candidate Architecture Partition Model - Trace to EA Capability Goals - EA Capability Customisation of Architecture Contents & Metamodel Phase C (Data) Capability None - EA Content Framework - EA Content Metamodel - Viewpoint Library - Architecture Repository Model - Trace to EA Capability Goals - Initial EA Content Framework and Architecture Repository Gap Analysis Organisation Model Phase B Capability None -EA Organisation Model -Select Reference EA Skills Framework -Initial alignment with Enterprise Job titles and roles -Initial Accountability Matrix for EA Content Framework -Initial Architecture Repository -Organisational Gap and Priority Roadmap Process Model Phase B, C (Application) and D Partial Capability - Process Model highlighting touch-points between EA Capability and Enterprise Processes - Process Model -Performance Matrix for Key Processes and Organisation - Architecture Repository Application Model - Accountability Matrix for EA Content Framework and Organisation - Matrix for EA Content Framework and Architecture Repository Application Architecture - Process and Architecture Repository Gap and Priority Roadmap Roadmap Phase E Capability Create a Roadmap highlighting development of the EA Capability by changes in: - Trace Roadmap to EA Capability Goals - Organisation Model - Process Model - EA Content Framework - Architecture Repository Establishing & Evolving Phase F & G Capability - Transition the EA Capability Roadmap to an Implementation & Migration Plan - Execute Implementation & Migration Plan

ADM Phase Key Artifacts Preliminary Phase - Architecture Principles - Tailored Architecture Framework - Architecture Capability Assessment - Initial Architecture Vision - Architecture Governance Framework Phase A: Architecture Vision - Statement of Architecture Work - Architecture Vision Document - Initial Architecture Definition Document - Initial Architecture Requirements Specification - Stakeholder Map Matrix - Value Chain Diagrams - Solution Concept Diagrams Phase B: Business Architecture - Organization Structure Diagrams - Business Service/Function Catalogs - Business Process Flows - Business Interaction Matrix - Actor/Role Matrix - Business Footprint Diagram - Business Use-Case Diagrams - Updated Architecture Definition Document Phase C: Information Systems Architecture (Data) - Data Entity/Data Component Catalog - Data Entity/Business Function Matrix - Application/Data Matrix - Conceptual Data Diagram - Logical Data Diagram - Data Dissemination Diagram - Data Security Diagram Phase C: Information Systems Architecture (Applications) - Application Portfolio Catalog - Interface Catalog - Application/Organization Matrix - Application/Function Matrix - Application Interaction Matrix - Application Communication Diagram - Application and User Location Diagram Phase D: Technology Architecture - Technology Standards Catalog - Technology Portfolio Catalog - Technology Matrix - Environments and Locations Diagram - Platform Decomposition Diagram - Network Computing/Hardware Diagram - Communications Engineering Diagram Phase E: Opportunities & Solutions - Project Context Diagram - Benefits Diagram - Consolidated Gaps, Solutions, and Dependencies Matrix - Implementation Factor Assessment and Deduction Matrix - Consolidated Roadmap - Architecture Definition Document (inlcuding Target and Transitions) Phase F: Migration Planning - Implementation and Migration Plan - Project Charter (for each project) - Capability Assessment - Architecture Contract - Implementation Governance Model Phase G: Implementation Governance - Architecture Compliance Assessments - Implementation Governance Artifacts - Architecture Contract Monitoring Reports - Change Request Impact Assessments Phase H: Architecture Change Management - Architecture Change Request Form - Architecture Compliance Reviews - Change Implementation Plan - Architecture Update Blueprint Requirements Management (Central) - Requirements Catalog - Requirements Impact Assessment - Requirements Traceability Matrix

Preliminary Phase Artifact Description Architecture Principles Fundamental statements that guide architecture development, providing a foundation for decision-making throughout the ADM cycle. Tailored Architecture Framework The customized version of TOGAF that has been adapted to meet the specific needs and constraints of the organization. Architecture Capability Assessment Analysis of the organization’s readiness and capabilities to conduct architecture work, identifying strengths and gaps. Initial Architecture Vision Preliminary outline of the target architecture’s scope, stakeholders, and high-level objectives. Architecture Governance Framework Structure and processes that ensure architecture compliance, quality, and alignment with business goals. Phase A: Architecture Vision Artifact Description Statement of Architecture Work Formal document defining the scope, approach, and timeline for the architecture work, serving as a contract between the architecture team and sponsors. Architecture Vision Document High-level aspirational view of the target architecture, communicating the business value and key architecture requirements. Initial Architecture Definition Document Preliminary outline of the baseline and target architectures across all domains. Initial Architecture Requirements Specification Early documentation of the key stakeholder requirements that the architecture must address. Stakeholder Map Matrix Identification of key stakeholders, their concerns, and their influence on the architecture development. Value Chain Diagrams Visual representations of how the organization delivers value to customers through its business processes. Solution Concept Diagrams High-level conceptual illustrations of the proposed solution architecture. Phase B: Business Architecture Artifact Description Organization Structure Diagrams Representations of the organizational hierarchies, roles, and responsibilities. Business Service/Function Catalogs Inventories of business services and functions performed by the organization. Business Process Flows Step-by-step sequences of activities that constitute business processes. Business Interaction Matrix Mapping of interactions between business functions and organizational units. Actor/Role Matrix Relationships between actors (people or systems) and the roles they perform. Business Footprint Diagram Mapping of business goals to organizational units, processes, and functions. Business Use-Case Diagrams Visual representations of how actors interact with business processes to achieve specific objectives. Updated Architecture Definition Document Refined documentation of the business architecture, incorporating all business domain artifacts. Phase C: Information Systems Architecture (Data) Artifact Description Data Entity/Data Component Catalog Inventory of all data entities and their components used within the organization. Data Entity/Business Function Matrix Mapping of data entities to the business functions that create, read, update, or delete them. Application/Data Matrix Relationships between applications and the data entities they manage. Conceptual Data Diagram High-level representation of business data objects and their relationships. Logical Data Diagram Detailed model of data structures including entities, attributes, and relationships. Data Dissemination Diagram Illustration of how data flows through the organization and between systems. Data Security Diagram Representation of security classifications and access controls for data entities. Phase C: Information Systems Architecture (Applications) Artifact Description Application Portfolio Catalog Comprehensive inventory of all applications used within the organization. Interface Catalog Documentation of all interfaces between applications and external entities. Application/Organization Matrix Mapping of applications to the organizational units they support. Application/Function Matrix Relationships between applications and the business functions they enable. Application Interaction Matrix Documentation of how applications communicate and exchange information. Application Communication Diagram Visual representation of application connections and data flows. Application and User Location Diagram Geographic mapping of applications and their users across locations. Phase D: Technology Architecture Artifact Description Technology Standards Catalog List of approved technology standards and specifications for the organization. Technology Portfolio Catalog Inventory of all technology platforms, hardware, and software used. Technology Matrix Mapping of technologies to the applications and data they support. Environments and Locations Diagram Geographic representation of technology environments across locations. Platform Decomposition Diagram Breakdown of technology platforms into their component services. Network Computing/Hardware Diagram Visual representation of hardware components and their network connections. Communications Engineering Diagram Detailed diagram of communications infrastructure and protocols. Phase E: Opportunities & Solutions Artifact Description Project Context Diagram Visual representation showing how implementation projects relate to each other and to the business context. Benefits Diagram Illustration of how projects deliver business benefits and value. Consolidated Gaps, Solutions, and Dependencies Matrix Comprehensive view of architecture gaps, proposed solutions, and dependencies between them. Implementation Factor Assessment and Deduction Matrix Analysis of factors affecting implementation and resulting deductions for planning. Consolidated Roadmap Integrated timeline of all projects and milestones required to implement the target architecture. Transition Architecture Definition Documents Documentation of interim architecture states between baseline and target architectures. Phase F: Migration Planning Artifact Description Implementation and Migration Plan Detailed plan for moving from the baseline to the target architecture through transition states. Project Charter (for each project) Formal authorization documents for each implementation project. Capability Assessment Evaluation of the organization’s ability to implement and operate the changes required. Architecture Contract Agreement between development partners and sponsors on deliverables, quality, and fitness-for-purpose. Implementation Governance Model Framework for decision-making and oversight during the implementation phase. Phase G: Implementation Governance Artifact Description Architecture Compliance Assessments Evaluations of how well projects comply with the established architecture standards. Implementation Governance Artifacts Documentation supporting governance activities during implementation. Architecture Contract Monitoring Reports Regular updates on compliance with architecture contracts and any deviations. Change Request Impact Assessments Analysis of how proposed changes might affect the architecture and implementation. Phase H: Architecture Change Management Artifact Description Architecture Change Request Form Formal documentation of proposed changes to the established architecture. Architecture Compliance Reviews Assessments of implemented solutions against established architecture standards. Change Implementation Plan Detailed plan for implementing approved architecture changes. Architecture Update Blueprint Guidance for updating the architecture repository with changes and lessons learned. Requirements Management (Central) Artifact Description Requirements Catalog Comprehensive inventory of all architecture requirements across domains. Requirements Impact Assessment Analysis of how new or changed requirements impact the existing or planned architecture. Requirements Traceability Matrix Mapping showing how requirements are addressed through the architecture and implementation.

The states of an architecture

Overview This page describes the TOGAF content framework and its key components. Key Components This is the key categorisation for the Architecture Content that is produced. It structures the artifacts and work products to be developed and described in an Architecture. There is a relationship between the content framework and the ADM phases. There are multiple different frameworks for describing architecture content - TOGAF, Zachman, DoDAF and NAF, to name a few. ...

Overview The meta model defines the entities within an organisation and the relationships between them. TOGAF provides templates for documents but does not constrain the notation used for the models and artifacts. This could be defined as part of the preliminary phase of the architecture Examles are ArchiMate, Business Process Model and Notation (BPMN), and Unified Modeling Language (UML).

Enterprise Continuum Provides structure and categorisation of assets held within the Enterprise Repositories. Sets a broader context to the re-use of the artifacts Explains how generic solutions can be leveraged and specialised so that they can be re-used to support the architecture requirements of an individual organisation Comprises of 2 distinct continuums - Architecture and Solution Provides a view or perspective of the models, patterns, viewpoints, building blocks and other artifacts stored in the repository This includes Internal architecture and solution artifacts that have been delivered from previous work and are available for re-use. It may also extend to include external architecture and solution artifacts taken from industry reference models or patterns (e.g. AWS Reference Architecture and Well-Architected framework)

Architecture Scope Dimensions 4 dimensions define the limit and the scope of an architecture: Enterprise Detail Domain Period Breadth Depth BDAT Planning Horizon - What is the full extent of the enterprise? - What level of detail will the architecture cover? - What domains will the architecture cover? - What time period for the architecture vision? - How much will the architecture cover? - How much architecture is enough? - Business - Can we cover the period to a required level of detail? - Organisations - What is the boundary between solution and delivery? - Data - Do we have enough information? - Business Units - Application - Do we have enough resources to complete the architecture? - Departments - Technology - Processes