Understanding Reference Models and Their Representation in ArchiMate

Reference models are standardized architectures that provide a reusable framework for a specific domain, industry, or field, and can be adapted to fit an organization’s needs.

They offer a clear, often visual, view of the area of interest and can be customized for discussion, reuse, and traceability across architectural domains.

Typical reference model types include Business Reference Models (BRM), Technical Reference Models (TRM), and Information Reference Models (IRM).

Reference models are frequently presented as PowerPoint slides, Visio diagrams, or Excel sheets, serving as communication tools that convey concepts quickly.

In enterprise architecture, reference models should not be used in isolation; they need to be linked to other architectural elements using standards such as ArchiMate, which provides concepts to represent the “blocks” of a reference model.

Choosing the appropriate ArchiMate concept for a reference model element often requires extensive discussion, but once agreed upon, consistent usage across the organization is essential.

Business Reference Model : Describes the business layer by decomposing high‑level areas into sub‑areas and further into detailed functions, effectively representing the organization’s roles and business functions.

Microsoft Industry Reference Architecture for Banking

Technical Reference Model : Focuses on the underlying infrastructure services and functions rather than detailed server or processor specifications, describing the technical layer from a functional perspective.

The Cloud Ecosystem Reference Model

Information Reference Model : Captures the passive structures—common information objects—available within an organization, often represented using Business Objects or Data Objects in ArchiMate.

The Information Framework (SID)

In conclusion, when using ArchiMate to model reference models, select appropriate ArchiMate concepts, maintain consistency across the organization, and share the results, ensuring that both technical and non‑technical stakeholders can understand and leverage the models effectively.