Metamodel

Intro

A metamodel defines the framework, rules, and constraints that underpin model creation. In EA, it specifies the allowed elements, relationships, and semantics.

Key points:

• Provides consistency across models and repositories.
• Enables validation, reuse, and analytics.
• Common use cases across EA/BPM/Data/App/Tech include tailoring architecture frameworks, defining BPMN extensions, and standardizing data models.
• Pitfall: overcomplicating the metamodel, making modeling hard.

Examples:

• EA metamodel linking capabilities, applications, and technologies.
• BPMN extension elements for organization-specific attributes.
• Data metamodel defining entities, attributes, and lineage links.

In practice:

Start with a minimal metamodel that meets core needs, then extend based on governance and reporting requirements.

Related terms: Model; Viewpoint; Architecture Framework

FAQs:

Q: Is a metamodel the same as a model?
A: No; it’s the model of the modeling language itself.

Q: Who owns the metamodel?
A: Architecture governance, with input from modeling communities.

‍