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.
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 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 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.
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.
This article explains requirement analysis in software engineering, covering its purpose, key activities, business versus software requirements, and various techniques such as BPMN, ArchiMate, data flow diagrams, use cases, and user stories for capturing and modeling stakeholder needs.
This article introduces the growing discipline of business architecture, explains its role within enterprise architecture, outlines core domains and their relationships, and presents nine practical modeling techniques supported by BIZBOK and ArchiMate, while also noting available training resources.
The article explains how ArchiSurance maps new digital‑customer‑intimacy capabilities to existing business functions, distinguishes capabilities from functions, and shows how enterprise architecture visualizes and supports these capabilities with resources and strategic planning.
This article explains ArchiMate's basic views—including composition, support, collaboration, and implementation viewpoints—as well as detailed descriptions of the physical and layered views, their stakeholders, concerns, purposes, scope, and example diagrams.
The article explains organization and business process collaboration views in enterprise architecture, detailing their purpose, stakeholders, concerns, scope, and elements, and provides example diagrams, while also including promotional information for related communities and resources.
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 introduces the growing field of business architecture, its core domains, key modeling techniques, and how standards like BIZBOK® and ArchiMate 3.0 support strategic enterprise design and decision‑making.
This article explains what reference models are, outlines business, technical, and information reference models, and provides guidance on how to represent them consistently using the ArchiMate modeling language, including examples and best‑practice recommendations for aligning stakeholders and ensuring reuse across organizations.
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 explains what reference models are, why they are valuable, and how to consistently represent business, technical, and information reference models using the ArchiMate language, providing practical guidance for architects and stakeholders.
