Non-graphical Model Dependencies in Graphical Modeling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional graphical modeling environments face challenges in managing execution dependencies between blocks, leading to confusion and inefficiency due to the need for explicit graphical representations, which clutter the model and hinder quick specification of model-wide execution behavior.
Innovation Solution
The introduction of non-graphical dependency information allows users to specify execution constraints without altering the visual representation of the model, enabling users to manage dependencies through additional criteria that influence model execution, such as sorting and relative dependencies, while preserving existing block orderings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If explicit lines or textual information are added to specify dependencies between blocks, then execution control is improved, but diagram readability deteriorates
Solution Approach 1:
The patent extracts the dependency specification from the graphical diagram and places it in a separate non-graphical form (textual information or metadata). This allows execution dependencies to be controlled without adding visual elements to the block diagram, thus maintaining diagram readability while improving execution control.
Solution Approach 2:
The patent introduces an intermediary layer (non-graphical dependency information) that mediates between the graphical block diagram and the execution engine. This intermediary allows dependency specification without directly modifying the visual representation, resolving the contradiction between execution control and diagram readability.
2Reliability
If block sorting priorities are used to specify execution dependencies, then execution order control is improved, but ease of operation deteriorates
Solution Approach 1:
The patent creates a universal dependency specification mechanism that works across the entire model-wide level, rather than requiring individual block-level sorting priorities. This multi-functional approach allows a single dependency specification to control execution order across multiple blocks, improving ease of operation while maintaining execution order control.
Solution Approach 2:
The patent changes the parameter representation from numerical sorting priorities to semantic dependency relationships. This parameter change makes the specification more intuitive and easier to operate with, while still achieving precise execution order control through the defined dependency relationships.
3Adaptability or versatility
If multiple valid sorts are allowed for model execution, then execution flexibility is improved, but analysis confusion increases
Solution Approach 1:
The patent applies preliminary action by establishing non-graphical dependency constraints before model execution. These pre-defined constraints guide the execution engine to produce consistent, predictable execution orders while still allowing flexibility for valid variations. This preliminary specification prevents analysis confusion by ensuring all executions follow the same dependency rules.
Data Source
AI summary
Graphical programming or modeling environments, such as a block diagram environment, are disclosed in which dependencies that influence how a model executes are defined without altering the visual representation of the model. In the graphical modeling or programming environment, users create a model that describes how the system is to execute. The users can then augment the model with non-graphical dependencies that provide general execution goals or specific dependencies between blocks. The user can augment the graphical model with dependency constraints specifying how the model should execute. The constraints are coupled to the model and can be optionally displayed on the model in a debugging/analysis mode to provide further insight into how the model executes.