Sparx EA natively supports every major EA framework and modeling language. The question is not which frameworks work in EA: they all do. The question is which combination serves your practice, how well-governed your implementation is, and whether your MDG Technology definitions enforce the semantics that make AI integrations useful. A team using ArchiMate informally and a team with a governed MDG implementation are not operating the same practice: they share a tool and a notation, but not a capability level.
Key Takeaways
| Framework/Language | Primary Use | Best For | MDG Complexity |
|---|---|---|---|
| ArchiMate 3.0 | Enterprise architecture | Layered architecture models across business, application, and technology | Medium |
| TOGAF ADM | Architecture governance process | Organizations needing a structured architecture practice with governance | Low (process, not notation) |
| BPMN 2.0 | Business process modeling | Process design alongside EA: cross-org and cross-system processes | Low |
| SysML/MBSE | Systems engineering | Defense, aerospace, automotive, complex systems engineering | High |
| DoDAF/MODAF/NAF | Defense architecture | Government and defense organizations with mandated viewpoint compliance | High |
| UML | Software and component design | Technical architecture, software engineering, component behavior | Medium |
| DMN | Decision modeling | Business rules documentation alongside BPMN processes | Low |
The MDG Complexity column reflects the investment required to get your MDG Technology definition right: not whether the framework is hard to learn. High-complexity MDG implementations require careful planning of element types, tagged value schemas, relationship constraints, and profile inheritance. That investment pays off in governance consistency and AI query quality. Low-complexity frameworks can still be implemented poorly if the underlying repository structure is informal.
Most EA teams underestimate how much framework governance quality determines AI integration value. When you deploy EA GraphLink or connect Kernaro AI Hub or MCP-enabled tools to your Sparx EA repository, those tools query your data: elements, relationships, tagged values, and the semantic structure that MDG Technology definitions impose.
An ArchiMate model where elements are correctly typed, tagged values are populated consistently, and cross-layer relationships follow the ArchiMate specification gives AI tools rich, queryable data. A query like “which application components implement the Order Management capability?” returns a useful answer because the ArchiMate realization relationships are there, typed correctly. The same repository built informally: elements named generically, stereotypes applied inconsistently, relationships created ad hoc: returns noise, or nothing useful.
MDG Technology is the mechanism in Sparx EA that makes the difference. It enforces element typing, required tagged values, valid relationship types, and template inheritance. It is also the upstream prerequisite for EA GraphLink: EA GraphLink transforms the repository via the MDG definition, making your architecture data accessible to AI systems. Poor MDG quality means poor AI output, regardless of which AI tool you use.
Framework choice matters. Governance quality matters more.
The standard notation for enterprise architecture in Sparx EA. This guide covers the six ArchiMate layers from a practice maturity perspective, MDG Technology governance for ArchiMate semantics, common modeling mistakes that reduce both human and AI usability, the ArchiMate + BPMN integration pattern, and what well-governed ArchiMate enables for stakeholder intelligence queries. If your team has ArchiMate models but isn’t sure whether they’re well-governed, start here.
TOGAF provides the architecture process; Sparx EA provides the platform. This guide maps every ADM phase to the specific Sparx EA artifacts it should produce, covers Architecture Repository structure inside Sparx EA, explains the TOGAF + ArchiMate combined stack, and identifies the most common implementation failure: treating TOGAF as a documentation checklist rather than a governance framework. Includes AI readiness implications of TOGAF-governed repository structure.
BPMN 2.0 is natively supported in Sparx EA. This guide covers the elements enterprise architects actually use, the integration pattern that connects BPMN processes to ArchiMate application services, the decision criteria for BPMN versus UML Activity Diagrams, DMN for decision logic alongside BPMN, and how well-structured process models contribute to AI query quality. Relevant to both EAs who own process models and architects collaborating with business analysts.
Most enterprise practices don’t choose a single framework: they choose a stack. The most common stack in commercial enterprise architecture is TOGAF + ArchiMate + BPMN: TOGAF for process governance, ArchiMate for notation across business, application, and technology layers, and BPMN for process detail where ArchiMate’s business layer notation isn’t granular enough.
Defense and government organizations typically extend this with DoDAF, MODAF, or NAF viewpoints. Complex systems engineering programs add SysML. Organizations with significant business rules add DMN alongside BPMN.
The question your practice needs to answer is not just which frameworks to use, but how governed your implementation of each is. A Discover engagement with Sparx Services includes an MDG readiness assessment: evaluating whether your current framework implementation enforces the semantics your practice needs and whether your repository structure supports the AI integrations you’re planning.
Architect Development: Sparx Services works with EA teams to develop ArchiMate, TOGAF, and BPMN practice capability: governance models, MDG Technology customization, modeling standards, and architect enablement.
Discover ($25K–$75K): Includes an MDG readiness assessment: evaluating your current framework implementation, identifying gaps between your stated standards and actual repository practice, and establishing the baseline for AI integration planning.
Talk to a Sparx Services architect about where your organization is on the journey and what the next stage looks like.