TOGAF: Content Metamodel

From Glitchdata
Jump to navigation Jump to search
ACF Concepts

A content metamodel is used to formalize the definition of an enterprise architecture, structuring architectural information in an ordered way so that it can be processed to meet stakeholder's needs. The content metamodel aids in communication and understanding.

Content Metamodel Components

ADM Iteration Cycles

The metamodel can be thought of as having 3 layers. These are:

  1. Layer 1: Architecture Principles, Vision and Requirements
  2. Layer 2: The Architecture Domains
  3. Layer 3: Architecture Realization

Core Metamodel Concepts

A TOGAF architecture is based on defining ABBs within architecture catalogs, specifying the relationships between those building blocks in architecture matrices, and preseting communication diagrams that show in a precise way what the architecture is.


Core Metamodel Entities

ACF Metamodels

Entities within the content metamodel are:

  1. Actor
  2. Application Component
  3. Business Service
  4. Data Entity
  5. Function
  6. Organisation
  7. Platform Service
  8. Role
  9. Technology Component

The relationships between core metamodel entities are summarized as follows:

  • Process should normally be used to describe flow
  • Function describes units of business capability at all levels of granularity
  • Business services support organisational objectives and are defined as a level of granularity consistent with the level of governance needed.
  • Business services are deployed onto application components
  • Application components are deployed onto technology components

Content Metamodel presents TOGAF concepts using:

  • Building blocks
  • Catalogs
  • Matrices
  • Diagrams


Related ACF Topics