Metamodel Transformation Engine for Cross-Platform Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application development tools are unable to utilize metamodels that conform to different meta-metamodels, as they do not expose the same modeling unit types, limiting their ability to support diverse business object models across various application platforms.
Innovation Solution
A metamodel transformation engine is employed to transform a first metamodel conforming to a first meta-metamodel into a second metamodel that conforms to a second meta-metamodel, using a mapping between the two meta-metamodels, allowing for the generation of a compatible metamodel that can be used by development tools with different native meta-metamodels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a development tool uses a native meta-metamodel with specific modeling unit types, then the tool can operate efficiently with its native metamodels, but it cannot utilize metamodels conforming to different meta-metamodels with different modeling unit types
Solution Approach 1:
The patent introduces a metamodel transformation engine as an intermediary component that converts metamodels from different meta-metamodels into a format compatible with the development tool's native meta-metamodel. This intermediary handles the complexity of mapping between different modeling unit types (e.g., UML classes to EMF EClasses) without requiring changes to the core development tool architecture, thus improving adaptability while containing complexity in an isolated transformation layer.
2Adaptability or versatility
If direct mapping between modeling unit types is used when meta-metamodels expose the same types, then the approach is simple and efficient, but it fails when meta-metamodels have different modeling unit types
Solution Approach 1:
The transformation engine dynamically changes parameters such as the target meta-metamodel type and specific mapping rules based on the source metamodel being transformed. When transforming from UML to EMF, it applies UML-specific mapping rules; when transforming from other meta-metamodels, it applies different mapping rules. This parameter-driven approach enables support for diverse meta-metamodels while maintaining relative ease of integration through configuration rather than hard-coded transformations.
3Adaptability or versatility
If a transformation engine is introduced to handle different meta-metamodels, then adaptability to diverse metamodels is improved, but the system complexity and transformation overhead increase
Solution Approach 1:
The transformation engine performs preliminary actions by pre-defining mapping rules and transformation templates for common meta-metamodels (such as UML to EMF, or other established meta-metamodels to the tool's native meta-metamodel). When a transformation is needed, the engine retrieves and applies these pre-configured rules, significantly reducing the actual transformation time. This preliminary preparation maintains high adaptability while minimizing the time loss during actual transformation operations.
Data Source
AI summary
Some aspects relate to systems and methods to receive a first metamodel conforming to a first meta-metamodel associated with first modeling unit types. A second metamodel conforming to a second meta-metamodel is generated based on the first metamodel and on a mapping between the first meta-metamodel and the second meta-metamodel, where the second meta-metamodel is associated with second modeling unit types, and where the first modeling unit types are different from the second modeling unit types.