This article explains value streams in TOGAF 10, their four core elements, relationship with business capabilities and processes, a four-step identification method, and illustrates practical application through Huawei's IPD/LTC and SAP's five end-to-end business processes.
This article explains TOGAF 10's stakeholder concept using an HR system case study, detailing how to identify stakeholders by defining system boundaries, six key questions for discovery, mapping stakeholder concerns, and converting those concerns into architecture requirements through the Stakeholder→Concern→Architecture Requirement chain.
The article explains how TOGAF 10's flexible framework requires enterprises to identify their unique architectural style characteristics and adapt models, viewpoints, and tools accordingly, emphasizing that each organization should extend the standard metamodel to create its own architecture content framework.
This article outlines the TOGAF 10 Architecture Board's key responsibilities — ensuring sub-architecture consistency, component reuse, compliance, and cross-boundary decision escalation — and details how Huawei operationalizes these principles through a layered governance structure comprising the Enterprise Architecture Committee, Transformation Steering Committee, Project Office, and Requirements & Architecture Management Teams to align local changes with corporate strategy.
This article breaks down the 22 stakeholder types defined in the TOGAF 10 standard, organized into five major categories: Corporate Functions, End-user Organization, Project Organization, System Operations, and External Stakeholders, detailing the responsibilities of each role.
This article breaks down the four components of TOGAF 10 architecture principles—Name, Statement, Rationale, and Implications—and demonstrates their application through a detailed Business Continuity principle example covering resilience, redundancy, and risk management requirements.
This article outlines the seven key elements of business architecture as defined in the TOGAF 10 standard, including business capability mapping, information mapping, organization mapping, process modeling, structured analysis, use case analysis, and value stream mapping, noting that decomposition levels vary by enterprise context.
This article explains TOGAF 10 business scenarios as complete business problem descriptions, details the five-step creation process (identify problem, document environment, define SMART outcomes, identify human and computer actors), and walks through a SMART refinement example for a consistent user interface goal.
This article presents the 21 standard enterprise architecture principles defined in TOGAF 10, covering primacy of principles, enterprise benefit maximization, shared responsibility, business continuity, common applications, service orientation, legal compliance, IT accountability, intellectual property protection, data as an asset, data sharing, data accessibility, data stewardship, common vocabulary, data security, technology independence, usability, requirements-based change, responsive change management, technology diversity control, and interoperability.
This article details the eight phases of the TOGAF Architecture Development Method (ADM) from Architecture Vision to Architecture Change Management, and presents TOGAF 10's four official agile iteration cycles with accompanying Gantt chart examples for iterative enterprise architecture development.
This article defines the EA capability organizational model, outlines its five key elements, presents evaluation questions for existing EA capabilities, and details TOGAF 10's three recommended models: function-centered, IT-centered, and strategy-centered.
TOGAF 10 defines Enterprise Architecture as a description of an enterprise's future state to guide change, and EA capability as the ability to develop, use, and maintain architecture to manage change across four roles: supporting strategy, portfolio, projects, and solution delivery.
