# 3.5.6 Metamodel, ISO 42024

## Published contents

Contents1 Scope2 Normative references3 Terms and definitions4 Architecture concepts4.1 Overview4.2 Architecture and architecting4.3 Architecture design and solution design4.4 Architecture definition and communication4.5 Stakeholder concerns and architectural aspects4.6 Architecture viewpoints and architecture views4.7 Architecture frameworks and architecture description languages4.8 Architecture descriptions and architecture models4.9 Reference architectures and reference models4.10 Life cycle and life history4.11 Architecting precepts5 Architecting principles5.1 Introduction to the principles5.2 Principles about the purpose of an architecture5.3 Principles about the focus of an architecture5.4 Principles about architecting outcomesTerms
3.2 Architecting concepts
3.2.1 Architecture3.2.2 Architecture feature3.2.3 Architecting3.2.4 Architecting principle3.2.5 Architecture principle3.2.6 Architecture framework3.2.7 Reference architecture3.3 Entity related concepts
3.3.1 Entity of interest3.3.2 Solution entity3.3.3 Environment3.3.4 Context3.3.5 Enterprise3.3.6 System3.3.7 Aspect3.3.8 Dimension3.4 Architecture design concepts
3.4.1 Design (noun)3.4.2 Architecture design3.4.3 Architecture information package3.4.4 Engineering effort3.4.5 Solution design3.4.6 Solution information package3.4.7 Stakeholder3.4.8 Stakeholder perspective3.4.9 Concern3.5 Architecture description concepts
3.5.1 Architecture description3.5.2 Solution description3.5.3 Architecture view3.5.4 Architecture viewpoint3.5.5 Model3.5.6 Metamodel3.5.7 Reference model3.6 Entity life cycle concepts
3.6.1 Life cycle3.6.2 Life cycle phase3.6.3 Life cycle stage3.6.4 Life historyAnnexes
A.1 Architecture design and solution related entitiesA.2 Architecture expressed as a set of modelsA.3 Life cycle and life history conceptsA.4 Enterprise and system conceptsA.5 Duality of architectural decomposition and architectural synthesisB.1 BackgroundB.2 Aligning architecture in designB.3 Duality of architectureB.4 Pursuit of opportunities

Home / Glossary

Architecture description concepts · 3.5.6

# Metamodel

A model that sets out which elements and properties a model needs. It defines an abstract syntax, the concepts that will be modelled, their relationships and their attributes, and it is distinguished from the concrete syntax used to represent it.

  
- definition

  
- Term

  
- ISO/IEC/IEEE DIS 42024

  
- Last updated: 2026-10-21

## What this term settles

The metamodel decides what the tool can say. If a concept is not in the metamodel, it cannot appear in a conforming model, however important it is. That makes the metamodel a governance artefact, not a technical detail, and it explains why some architecture questions are unanswerable in a given tool.

## What to do in your practice

Keep the metamodel under configuration control with an owner. Write down the concepts the firm needs and test whether the metamodel supports them. Where it does not, record the extension or the workaround and the risk it carries.

## Who it binds

The role that owns the practice area the term governs. A definition binds nobody on its own; it binds the reader who adopts the term in a method, a description or a contract.

## Evidence an auditor or regulator asks for

- The metamodel version, owner and change record.
An auditor asks which rules the models were built under.

- A concepts to metamodel coverage map.
Shows which firm concepts can be expressed.

- A list of extensions and workarounds with their risk.
Shows the limits were managed, not hidden.

- The migration record when the metamodel changed.
Shows existing models were brought forward.

Ask your teamWhich concept the firm cares about cannot be expressed in this metamodel, and where is that worked around?

## Common gaps this page catches

- The metamodel is whatever the tool ships and no one owns it.

- Extensions are made locally and are invisible to other teams.

- A metamodel change orphans existing models with no migration record.

## What to prepare before publication

Write the concepts to metamodel coverage map for the main tool. The gaps are the questions the firm cannot answer from its models. Decide for each whether to extend, work around or accept.

## Common questions

What does Metamodel mean in ISO 42024?
A model that sets out which elements and properties a model needs. It defines an abstract syntax, the concepts that will be modelled, their relationships and their attributes, and it is distinguished from the concrete syntax used to represent it.
What evidence should we keep for 3.5.6?
The metamodel version, owner and change record. A concepts to metamodel coverage map. A list of extensions and workarounds with their risk.

## Related units

- 3.5.5

- 3.5.4

Source. ISO/IEC/IEEE DIS 42024, Clause 3.5.6, Terms and definitions. Open the official record. Retrieved 21 October 2026.
https://www.iso.org/obp/ui/en/#iso:std:iso-iec-ieee:42024:dis:ed-1:v1:en
ISO catalogue record 87510, the status, stage and page count.
Claim level: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text.

Last updated: 2026-10-21 · Markdown version · Check your practice

Source: https://iso-42024-revision-checker.theartofservice.com/glossary/metamodel/