1 views collected around this technical thread.
The article explains what reference models are, outlines business, technical, and information reference model types, and provides guidance on how to represent these models consistently using the ArchiMate modeling language within enterprise architecture practice.
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.
The article explains how strategy development and execution are interdependent, outlines why executives often prioritize execution, and demonstrates how Archimate 3.1's motivation layer can model strategic intent, capabilities, and feedback loops to bridge strategy with actionable enterprise architecture practices.
This article explains ArchiMate's basic views—including composition, support, collaboration, and implementation perspectives—by describing each viewpoint's purpose, focus, and example tables for composition, support, collaboration, and implementation views, as well as physical and layered views.
This article explains ArchiMate's basic views—including composition, support, collaboration, and implementation perspectives—detailing their purpose, stakeholder concerns, and examples of information structure and service realization viewpoints within enterprise architecture modeling.
This article explains ArchiMate's basic views and the four categories of viewpoints—Composition, Support, Collaboration, and Implementation—detailing their focus areas, examples, and the specific technical and technology‑usage perspectives for enterprise architecture modeling.
This article explains ArchiMate basic views—including composition, support, collaboration, and implementation viewpoints—detailing their purpose, concerns, and the elements they address, and provides examples of application usage and implementation‑deployment views with stakeholder information.
The article explains the purpose, stakeholders, concerns, scope, and key elements of the Organization View and Business Process Collaboration View in ArchiMate, illustrating how these viewpoints model enterprise structures and business process dependencies for better design and decision‑making.
This guide introduces ArchiMate views, explains their role in modeling enterprise architecture, outlines the 23 official example viewpoints grouped into basic, motivation, strategy, and implementation & migration categories, and provides detailed descriptions of basic viewpoints such as composition, support, collaboration, and implementation.
The article explains how enterprise applications have evolved to web‑based distributed environments, describes the three‑tier architecture, and shows how UML/EAP and Archimate can be used to model and visualize the deployment of hardware and application components in a networked infrastructure.
The article explains how environment and location diagrams map applications to physical sites, defines key UML/BPMN EAP elements such as headquarters, site locations, servers, workstations, applications, interactive components, and class relationships, and illustrates these concepts with an Archimate diagram while also providing community links.
The article explains how to create data‑security diagrams that map which participants can access specific enterprise data, recommends breaking large diagrams into role‑based views, and illustrates the approach with UML/BPMN and ArchiMate models while addressing compliance and trust considerations.
The article explains the purpose and benefits of data publication diagrams for visualizing relationships among data entities, services, and application components, introduces UML/BPMN EAP profile components with illustrative images, and outlines Archimate modeling elements, highlighting how data is localized within repositories or entity application components.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented component layering, introduces the UML/BPMN EAP profile and Archimate concepts, and provides a detailed list of application component types for enterprise architecture modeling.
The article explains how organization decomposition diagrams illustrate the links between participants, roles, and locations, define responsibilities, show information flows, and map goals to stakeholders using UML/BPMN and Archimate models, providing a comprehensive view of enterprise structure and governance.
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 introduces the growing importance of business architecture, outlines its core domains and nine practical modeling techniques, and explains how BIZBOK and ArchiMate can be leveraged—often via tools like BiZZdesign Enterprise Studio—to bridge strategic business models with detailed enterprise design.
This article explains what reference models are, outlines business, technical, and information reference model types, and provides practical guidance on representing them consistently using ArchiMate concepts within enterprise architecture to facilitate reuse, communication, and impact analysis.
The article explains how strategy development and execution are interdependent, outlines a capability‑to‑technology roadmap approach, and shows how Archimate 3.1 can model motivation elements to provide traceability and feedback between strategic goals and operational actions.
This article explains ArchiMate's basic views—including composition, support, collaboration, and implementation—detailing their names, viewpoints, and concerns across business, application, and technology layers, and provides examples of information structure and service implementation views with stakeholder and purpose information.