What Is MDG Technology in Enterprise Architect? Definition and Governance Guide

The short version: MDG Technology (Model Driven Generation) is Sparx EA’s metamodel extension mechanism. It defines the custom element types, stereotypes, tagged values, diagram types, and validation rules available inside the modeling environment. Every framework Sparx EA supports — ArchiMate, SysML, BPMN, DoDAF — is an MDG extension, either built in or custom-built for an organization’s own standards.

A well-designed custom MDG is the difference between a repository of loosely-typed diagrams and a governed, queryable architectural vocabulary. It is the foundation of model quality — and therefore of everything you can reliably do with the data downstream, from BI dashboards to AI-assisted querying.

What MDG Technology does

MDG Technology is what lets Sparx EA model in ArchiMate, SysML, BPMN, TOGAF content, and any custom notation an organization invents for its own governance.

The components of an MDG extension

An MDG Technology package contains four kinds of definition:

Stereotype profiles. Stereotypes extend base UML metaclasses (Class, Component, Node, Dependency) with additional metadata and semantic meaning. ArchiMate’s Business Process extends the UML Activity; a custom Managed Application extends Component with your specific attribute requirements.

Tagged value definitions. Each stereotype can define custom attributes — name, data type (text, integer, date, boolean, enumeration), allowed enumeration values, whether the value is mandatory, and any default. Enumerations matter most: they define the controlled vocabulary used when filtering, grouping, and reporting on the model.

Diagram types. Custom diagram types constrain which element and relationship types may appear. An ArchiMate Application Layer diagram allows Application Components and Services but not Business Process elements. This enforces modeling discipline.

Validation rules. Rules checked when the model is validated — mandatory relationships, attribute constraints, naming conventions, structural constraints. Running validation surfaces every element that violates a governance rule, without relying on each architect to self-enforce.

Built-in MDG extensions

Sparx EA ships MDG extensions for the major standards:

• ArchiMate 3.x — the Open Group’s EA notation. All layers, element types, relationships, and viewpoints. The primary MDG for most EA programs.
• BPMN 2.0 — flow elements (Tasks, Events, Gateways, Pools, Lanes) for process modeling.
• SysML 1.x — systems engineering: requirements, block definition diagrams, internal block diagrams.
• TOGAF Content Metamodel — Principles, Requirements, Gaps, Work Packages, Plateaus, used alongside ArchiMate.
• UML 2.5 — the base package: class, sequence, use case, and state machine diagrams.
• DoDAF / MODAF / NAF — defense architecture frameworks with their own viewpoint and stereotype sets.

Custom MDG extensions: the organizational standard

Beyond the built-in frameworks, organizations build custom MDG extensions to govern their own standards. A custom MDG typically includes:

• Organization-specific stereotypes — a Cloud Service stereotype with tagged values for provider and data classification; a Legacy System stereotype with migration priority and technical-debt scoring.
• Governance vocabulary — tagged-value enumerations defining lifecycle stages, investment bands, criticality ratings, and business-domain taxonomy.
• Validation rules — enforcing that new elements cannot be committed without mandatory governance data, the discipline that keeps the repository from filling with ownerless, statusless elements.
• Custom diagram types — tailored templates such as “Current State Application Landscape” or “Capability Heat Map.”
• A custom toolbox — surfacing your stereotypes prominently so architects reach for the right element types directly.

Why MDG is the model-quality foundation

The precision of your MDG directly determines the precision of everything you can do with the model downstream. An element typed only as a generic Class with a free-text note saying “this app is end of life” is not a structured, filterable fact. The same element typed as a SaaS Application with a governed Lifecycle Status = End-of-Life tagged value is a precise, queryable dimension.

That distinction compounds across reporting, portfolio analysis, and any AI or BI tool that reads the repository. Where a semantic layer exposes model data to those tools, it can only be as precise as the MDG underneath it. Every investment in MDG governance — more precise stereotypes, governed enumerations, enforced validation — improves the reliability of every output the repository feeds. MDG is not a technical detail; it is the foundation of intelligence quality.

Building vs consuming MDG extensions

Consuming built-in MDGs. Most teams start by activating built-in extensions (ArchiMate, BPMN) and using their element types. This is straightforward configuration.

Building custom MDG extensions. Custom development uses the MDG Technology editor — a profile-based approach where stereotypes are defined as UML profile packages with tagged-value definitions and constraint specifications, then packaged by the MDG wizard into a deployable .xml file importable into any Sparx EA installation. It is a specialist skill requiring fluency in both the UML metamodel and the Sparx EA MDG implementation.

For most organizations, 3–8 custom stereotypes covering the key element types is the right initial scope. Sparx Services delivers custom MDG design and implementation as a core part of Configure the Solution — building the governance framework that fits your modeling needs and transferring the knowledge so your team can maintain it.

Deploying and maintaining MDG extensions

Deployment. Custom MDGs deploy through Project/Model Options › MDG Technologies, or via Pro Cloud Server configuration so every connecting client receives the MDG automatically.

Version control. MDG extensions are XML files — version-control them in Git, with MDG version numbers for compatibility tracking.

Updates. When the MDG changes, redeploy to the repository and clients. Existing elements are not auto-re-validated; a model validation run surfaces elements that no longer meet updated rules.

Frequently asked questions

Build your MDG governance framework

Sparx Services’ Configure the Solution engagement delivers a custom MDG Technology extension designed for your modeling standards — stereotype design, tagged-value governance, validation rules, diagram templates, and deployment configuration. The MDG is what makes your enterprise architecture repository an intelligence asset rather than a diagram store. For how that foundation feeds an AI-ready practice, see AI Augmented Architecture.