Graphical Model Structural Templatization Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional graphical modeling languages lack a mechanism for graphically performing structural templatization, which prevents the separation and propagation of interface information from model components, limiting flexibility, reusability, and efficiency in model design.
Innovation Solution
A graphical model design mechanism that instantiates an interface component and an implementation component, allowing their connection to merge internal port information with functional content, enabling separate management of interface and content information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional graphical modeling languages are used, then model components can be organized hierarchically and packaged into defined components, but interface information cannot be separated from and propagated to other instantiated model components
Solution Approach 1:
The model component is segmented into two distinct parts: an interface component that defines the interface information (ports, connections, data types) and an implementation component that contains the functional content. This segmentation allows interface information to be separated and reused independently across multiple instances without duplicating implementation details, thereby improving adaptability while managing complexity through clear separation of concerns.
Solution Approach 2:
An interface component acts as an intermediary between the implementation component and other model components. The interface component exposes ports and connection information that can be connected to other components, while the implementation component remains hidden behind this interface layer. This intermediary structure enables interface propagation and reusability without exposing implementation complexity.
2Productivity
If interface and content are managed separately, then flexibility and reusability increase, but additional mechanisms for managing interface components are required
Solution Approach 1:
The interface component and implementation component are merged into a unified model component structure that automatically manages their relationship. When an interface component is instantiated, the system automatically connects it to the implementation component and propagates the interface information to other connected components. This merging approach maintains flexibility and reusability while reducing the manual management burden through automated integration.
Solution Approach 2:
The interface component is designed to be self-sufficient, containing all necessary interface information (ports, data types, connections) that allows it to function independently. Once defined, the interface component automatically propagates its interface information to connected components without requiring additional manual configuration, thereby improving productivity while minimizing management complexity.
Data Source
AI summary
A mechanism for graphically performing structural templatization in a graphical model is discussed. A model component with a defined interface is designated as an “interface component” and includes at least one external interface port and one or more internal ports. An instance of the interface component is instantiated in a graphical model and exposes the external interface port. A user also instantiates in the graphical model an instance of a component that is designated as an “implementation component” that includes model functional content and which exposes an implementation port. The user connects the exposed interface port and implementation port and the internal port information from the interface component programmatically merges with the content of the implementation component. The model designer is thus able to concentrate on separately providing interface and content information during the design of the graphical model.