This article demystifies the concept of architecture by tracing its origins, explaining the 4+1 and C4 modeling approaches, introducing TOGAF‑4A, and clarifying the role of enterprise architecture in aligning people, processes, technology, and data to manage complexity across large organizations.
This article provides a deep dive into the five major enterprise architecture methodologies—TOGAF, Zachman, OEA, ITSA, and DODAF—explaining their core principles, step‑by‑step implementation processes, a detailed omni‑channel order and marketing platform case study, and a comparative analysis to help architects choose the right framework for their projects.
Enterprise Architecture, essential for competitive advantage, is explored through TOGAF’s comprehensive framework and the 4A model, detailing business, application, technology, and data architectures, their purposes, design steps, and visualization techniques, offering practical guidance for building coherent, integrated enterprise blueprints.
The article presents a comprehensive case study of XinXuan Group’s data ecosystem, detailing its business background, data platform construction, governance framework, technical architecture, and practical analytics applications that support live‑commerce operations and strategic decision‑making.
This article explains the TOGAF framework and its 4A architecture model—Business, Technology, Application, and Data Architecture—detailing each domain's definition, purpose, value, and step‑by‑step guidance for creating enterprise architecture diagrams to align strategy, processes, and technology.
This article explains the 4A enterprise architecture model, compares it with TOGAF and Huawei’s “One Body Four Faces” framework, outlines the four architectural layers, and shows how Domain‑Driven Design can be mapped onto each layer with concrete examples and diagrams.
The article explains how to classify architecture descriptions along the TOGAF Enterprise Continuum—from foundational architectures to common, industry, and organization‑specific models—providing practical guidance for architects to select and adapt reference models for their enterprises.
This article explains the purpose and components of enterprise architecture, compares the two leading frameworks TOGAF and Zachman, outlines their respective processes and viewpoints, and offers guidance on selecting the most suitable approach for an organization.
This article explains the role of application architecture within enterprise architecture, describes its focus on application behavior and data exchange, outlines strategic alignment and common architectural patterns, and details the responsibilities and knowledge areas of an application architect.
The article explains the recently released TOGAF 10, highlighting its modular, topic‑centric structure, the various audiences and roles that can benefit from it, the core documents and series guides, and concrete examples of how different practitioners can apply the framework in their organizations.
The second part of the six‑part series analyzes Google Trends data and the Open Group's certification landscape, showing a decline in generic EA terms while specific topics like master data, micro‑services, cloud‑native computing and new TOGAF‑related certifications are gaining interest.
This article provides a concise, high‑level walkthrough of the TOGAF 9.2 framework, its five parts, the Architecture Development Method, key phases such as Requirements Management and the Preliminary Phase, and practical guidance for self‑studying toward the certification exam.
This article reflects on the often‑overlooked discipline of enterprise architecture, highlighting common mistakes such as treating EA as a purely technical function, short‑term focus, executive arrogance, and over‑reliance on outdated frameworks like TOGAF, and proposes using data‑driven, metacognitive tools to guide more valuable, lightweight, and automated architectural practices.
This article explains the core concepts of enterprise architecture, defines both enterprise and architecture, outlines major frameworks such as Zachman, TOGAF, DoDAF and FEA, distinguishes business and IT architecture, and details the components, models, and practical integration of business architecture with value streams, capabilities, information, organization, products, stakeholders, policies, and metrics.
The article systematically defines software architecture, distinguishes systems, subsystems, modules, and components, compares frameworks with architectures, explores TOGAF and RUP classifications, traces the evolution from monoliths to micro‑services, and presents concrete design principles and common pitfalls for building scalable, maintainable systems.
A Tencent architect explains that effective software architecture requires clear distinctions between systems, subsystems, modules and components, understanding frameworks versus structural design, applying TOGAF classifications, evolving from monoliths to microservices, and following fifteen practical principles while avoiding common misconceptions such as over‑design and technology‑driven choices.
The article examines the relationship between enterprise architecture and systems engineering, discussing overlapping frameworks such as TOGAF, DoDAF, UPDM, and model‑based approaches, and argues that while they share terminology and goals, EA focuses on business transformation and IT alignment, whereas SE emphasizes technical system development.
This article explains the purpose of data class diagrams in enterprise architecture, describing how they model high‑level business entities, their attributes and relationships, and how these conceptual models serve as the foundation for later persistence and service design.
The Goal/Objective/Service diagram defines how business services contribute to strategic goals, links services with drivers, objectives, and measures, and can be visualized alone or with a matrix to aid impact analysis and system evolution in enterprise architecture.
Solution concept diagrams are high‑level, pencil‑sketch representations that capture key goals, requirements, constraints and stakeholder involvement for an architecture initiative, highlighting areas needing detailed formal modeling and enabling rapid coordination of change plans across the enterprise.
The article explains TOGAF's concept of business services, compares them with SOA and ITIL services, provides insurance and banking examples, and outlines a top‑down process for identifying and modeling business services within an enterprise architecture framework.
This article explains the TOGAF enterprise architecture framework, its evolution to version 10 with a modular agile‑focused structure, the core and extended guidance it provides, the business benefits and certification paths, salary impact, and a list of certified tools for implementation.
The article examines the challenges of demonstrating ROI for enterprise architecture in companies that have replaced ERP with default EA, discusses common misconceptions and high costs, and proposes a 5W2H‑based approach to regain EA’s strategic impact while minimizing effort.
The article explains how Enterprise Architecture (EA), especially when guided by frameworks like TOGAF, bridges business strategy and technical execution through governance, capability and technical roadmaps, and a structured repository, while highlighting common misconceptions and proposing a collaborative, cross‑organizational role for EA to deliver real business value.
TOGAF 10 reorganizes and modularizes its content into six core documents and 23 guidebooks, updates key topics like data management, agility, resilience, and the glossary, and aims to address past criticisms by improving readability, relevance, and update frequency for enterprise architects.
The article summarizes Steve Nunn’s 2022 outlook for TOGAF, highlighting the Open Group’s recent milestones, the evolving relevance of the TOGAF framework, upcoming guide updates, and the strategic focus on digital standards and integration for enterprise architecture.
This article examines the declining relevance of enterprise architecture in 2021, analyzing Google Trends data, the aging of major frameworks like TOGAF and Zachman, and the scarcity of EA roles in modern tech firms, while hinting at a forthcoming rebuttal.
This article examines the concept of business architecture, its origins in TOGAF, and presents a detailed case study of Qunar’s activity capability layer design, highlighting pain points, architectural solutions, and a step-by-step methodology for building robust, reusable activity systems.
This article explains the essence of software architecture, its core principles, the distinction between development and architecture design, and presents a methodology based on TOGAF and the ADM cycle, covering business, data, application, and technology architecture domains.
The article examines the ongoing debate about whether Enterprise Architecture (EA) is a subset of Systems Engineering (SE), discusses major architecture frameworks such as TOGAF, DoDAF, and UPDM, and highlights the role of model‑based engineering and SysML in bridging EA and SE practices.
The article explains the purpose of data class diagrams in TOGAF, describing how they model key business entities, their attributes and relationships at a high-level conceptual stage to aid understanding of the underlying data model, and includes examples from the tourism discount domain.
System use case diagrams illustrate how participants and application services interact, enriching functional descriptions with technical details and supporting architecture design, while the article also explains UML/BPMN EAP profiles, Archimate representations, and provides community resources for further enterprise architecture discussion.
The article explains the concept of business services within the TOGAF framework, clarifies their definition and identification through examples from insurance and banking, and shows how they relate to SOA, ITIL, and enterprise architecture service models.
This article explains software architecture design by defining its essence, contrasting it with ordinary software development, outlining three core principles—appropriateness, simplicity, and evolution—and detailing the TOGAF/ADM methodology and its business, data, application, and technology domains for building robust, adaptable systems.
This article provides a comprehensive overview of TOGAF, covering its definition, development history, core concepts of enterprise architecture, the seven-part TOGAF structure, the Architecture Development Method (ADM) phases, guidelines, content framework, reference models, and the architecture capability framework.
The article provides a comprehensive overview of TOGAF’s architecture capability framework and governance model, detailing how enterprises can build, govern, and mature their architecture functions through organized processes, roles, resources, and compliance mechanisms across multiple architectural domains.
This comprehensive guide explains how TOGAF’s Architecture Capability Framework helps enterprises build and govern architecture capabilities, covering governance structures, capability components, the ADM phases, architecture committees, compliance processes, and practical governance guidelines for successful enterprise architecture implementation.
This article provides a comprehensive overview of TOGAF’s content framework, detailing how enterprise architecture development methods use structured inputs and outputs, describing the classification of architecture deliverables, artifacts, building blocks, and the various work products, catalogs, matrices, and diagrams that support effective architectural governance and communication.
This article explains how TOGAF’s Content Framework integrates with the Architecture Development Method to define, organize, and deliver enterprise architecture work products—such as deliverables, artifacts, and building blocks—enabling stakeholders to view and use architecture information effectively across the organization.
This article explains why architecture diagrams are essential for developers, outlines the main categories of diagrams, introduces the Zachman framework and its six-by-six matrix, and provides step‑by‑step examples for creating selection, microservice, and technical architecture diagrams.
The article explains how data security diagrams map which participants can access specific enterprise data, discusses best practices such as using focused participant‑centric or external‑access diagrams, presents example tables and UML/BPMN and Archimate visualizations, and highlights their role in compliance and trust management.
This article presents a thorough exploration of system design and architecture, covering core concepts, thinking models, analysis techniques, design processes, modeling methods, TOGAF framework, and practical tools to help architects transform complex business requirements into clear, implementable system solutions.
The Goal‑Objective‑Service diagram explains how business services link to drivers, goals, objectives and measures, providing a visual and matrix‑based view of service contributions to enterprise strategy and performance, while also describing alternative representations and related UML/BPMN and ArchiMate profiles.
The article explains business footprint diagrams, illustrating how business goals, organizational units, functions, and services map to technical components, providing traceability for C‑level stakeholders and highlighting their use in enterprise architecture modeling with UML/BPMN and ArchiMate references.
The article explains how TOGAF and ArchiMate define and differentiate “function” and “capability” within enterprise architecture, detailing abstract and concrete structures, behavior, and their mapping to organizational units, and compares various sources’ interpretations of these concepts.
The article explains the concept of business services within the TOGAF 9.1 metamodel, compares it to SOA and ArchiMate definitions, demonstrates how to identify services from business processes using real insurance and banking examples, and discusses how these services relate to IS, SOA, and ITIL service models.
This article explains the TOGAF® framework, its ADM phases, the challenges of applying it in modern IT environments, and how the LeanIX Enterprise Architecture suite supports each stage with agile practices, reporting, visualizations, and governance tools to streamline enterprise architecture initiatives.
This article explains how enterprise architecture descriptions range from foundational, generic models to highly specific, organization‑level designs, outlines the TOGAF terminology for artifacts, and offers practical advice on classifying and applying these architectures in real‑world projects.
This article provides a comprehensive overview of TOGAF, covering its history, core components, the Architecture Development Method, its three pillars, benefits, criticisms, and practical guidance for organizations seeking to adopt the framework for enterprise architecture.
This article provides a comprehensive overview of TOGAF, explaining its purpose, structure, the Architecture Development Method (ADM) phases, content framework, reference models, and the enterprise and solution continuums, while also detailing governance, deliverables, and the architecture repository for effective enterprise architecture practice.
This article outlines the development of enterprise business architecture—from early models like Zachman and TOGAF to modern frameworks such as FEA and DODAF—defines its purpose as a structured capability analysis that bridges business strategy and IT implementation, and explains its role in digital transformation and its interplay with various IT architecture layers.
This article traces the historical origins of architecture from Vitruvius’s ancient treatise to contemporary IT frameworks such as Zachman, TOGAF, and FEA, explains core definitions, compares various architect roles, and offers practical guidance on applying architectural frameworks to drive enterprise transformation and operational efficiency.
