Fundamentals 8 min read

ArchiMate Basic Views: Composition, Support, Collaboration, and Implementation Viewpoints

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.

Architects Research Society
Architects Research Society
Architects Research Society
ArchiMate Basic Views: Composition, Support, Collaboration, and Implementation Viewpoints

ArchiMate basic views consist of elements and three main layers—business, application, and technology. The article lists four categories of ArchiMate 3.1 viewpoints: composition, support, collaboration, and implementation, indicating their direction and scope.

Composition View defines internal composition and aggregation of elements.

Support View shows how elements are supported by others, typically moving upward across layers.

Collaboration View focuses on cooperative relationships between peer elements, often across different aspects.

Implementation View illustrates how elements implement other elements, usually moving downward across layers.

Composition View Table

Name

Perspective

Focus

Organization

Structure of the enterprise in terms of roles, departments, etc.

Identify capabilities, authority, and responsibility

Information Structure

Shows the structure of information used in the enterprise.

Structure, dependencies, consistency, and completeness of data and information

Technology

Infrastructure and platforms such as networks, devices, and system software.

Stability, security, dependencies, and cost of infrastructure

Layering

Provides an overview of the architecture.

Consistency, reduced complexity, impact of change, flexibility

Physical

Physical environment and its relation to IT infrastructure.

Relationships and dependencies of the physical environment with IT infrastructure

Support View Table

Name

Perspective

Focus

Product

Shows product content.

Product development and enterprise value delivery

Application Usage

Links applications to their usage in business processes.

Consistency, completeness, reduced complexity

Technology Usage

Shows how applications use technology.

Dependencies, performance, scalability

Collaboration View Table

Name

Perspective

Focus

Business Process Collaboration

Shows relationships between various business processes.

Business processes, consistency, completeness, responsibility dependencies

Application Collaboration

Shows application components and their interrelationships.

Application relationships and dependencies, service orchestration, consistency, reduced complexity

Implementation View Table

Name

Perspective

Focus

Service Implementation

Shows how services are realized through necessary behaviors.

Value addition of business processes, consistency, responsibility

Implementation and Deployment

Shows how applications map to underlying technology.

Structure of application platforms and their relationship to supporting technology

Information Structure View works like traditional information models used in system development, displaying the structure of information used in the enterprise and how business‑layer information is represented in the application layer and mapped to technology.

The view’s stakeholders are domain and information architects, focusing on data structure, dependencies, consistency, and completeness. Its purpose is design, covering multi‑layer or single‑aspect scopes and elements such as business objects, representations, data objects, and artifacts.

An example ArchiMate diagram (image) illustrates this viewpoint.

Service Realization View models how business services are implemented by underlying processes or application components.

Stakeholders include process and domain architects, product and operations managers. The view emphasizes added value of business processes, consistency, completeness, and responsibility. Elements span business participants, roles, collaborations, interfaces, processes, events, services, data objects, application components, and more.

An example ArchiMate diagram (image) demonstrates the service realization viewpoint.

The remainder of the source contains promotional links and community information unrelated to the technical content.

enterprise architectureArchiMateInformation StructureService RealizationViewpoints
Architects Research Society
Written by

Architects Research Society

A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.