Metamodel Entity Morphing in BPMN Tools
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Business Process Management (BPM) tools lack the ability to rapidly adjust diagram elements based on a given metamodel definition, limiting their functionality in model-driven process development.
Innovation Solution
The implementation of an inheritance hierarchy within the metamodel allows for entity morphing in BPMN tools, enabling entities to be transformed from one non-abstract type to another, with the system receiving commands and determining the appropriate sub-types or siblings to morph into, thereby enhancing the modeling infrastructure's adaptability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a metamodel definition is provided in BPMN tools, then the structural framework for modeling is established, but the ability to rapidly adjust diagram elements based on the metamodel is missing
Solution Approach 1:
The system enables self-service by allowing the modeling infrastructure to automatically adjust diagram elements based on metamodel definitions without requiring manual intervention. The morphing functionality autonomously transforms entities according to inheritance hierarchies defined in the metamodel, making the system self-adapting to structural changes.
Solution Approach 2:
The patent introduces dynamic adjustment capabilities where diagram elements can be rapidly transformed between different entity types based on metamodel definitions. The inheritance hierarchy enables flexible morphing operations that allow entities to dynamically change their structure and properties according to the defined metamodel relationships.
2Productivity
If manual adjustment of diagram elements is performed without automated morphing functionality, then full control over entity transformation is maintained, but the process becomes time-consuming and inefficient
Solution Approach 1:
The patent introduces an intermediary morphing functionality that mediates between the user's modeling intentions and the actual diagram element transformations. This intermediary layer automatically handles the complex transformation logic based on inheritance hierarchies, simplifying the user interaction while maintaining full control over entity transformations.
Solution Approach 2:
The system performs preliminary action by pre-defining inheritance hierarchies and transformation rules in the metamodel. These pre-established relationships enable rapid entity transformation without requiring users to manually configure each transformation step, thus improving productivity while maintaining ease of operation.
3Adaptability or versatility
If inheritance hierarchy functionality is added to the modeling infrastructure, then rapid adjustment of diagram elements is enabled, but the system complexity increases
Solution Approach 1:
The patent implements universality by creating a general-purpose morphing functionality that works across all entity types in the metamodel. The inheritance hierarchy mechanism provides a universal framework for entity transformation that can be applied consistently throughout the modeling infrastructure, reducing the need for specialized transformation logic for each entity type.
Solution Approach 2:
The system manages complexity by focusing on parameter changes within the existing metamodel framework. The morphing functionality achieves flexibility through parameter transformations (changing entity types, properties, and relationships) rather than requiring fundamental changes to the modeling infrastructure architecture.
Data Source
AI summary
A system and method for morphing entities in metamodel-based business process model and notation (BPMN) tools is disclosed. A command is received for an entity to be morphed from a first non-abstract entity type to a second non-abstract entity type. A modeling infrastructure (MOIN) returns all non-abstract sub-types or siblings of the entity based on an inheritance hierarchy in a metamodel associated with the entity. The second non-abstract entity type is determined from the non-abstract sub-types or siblings of the entity, and the selected entity is morphed from the first non-abstract entity type to the second non-abstract entity type.