Graphical Modeling Environment for Automatic Component Interface Code Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current graphical modeling environments, such as MATLAB and Simulink, do not provide a model-based design approach for automatically generating component interfaces between electronic components of computational hardware devices with heterogeneous topologies, requiring manual implementation and re-implementation when hardware topology changes occur.

Innovation Solution

A graphical modeling environment that allows for partitioning of block diagram models to represent component interfaces, identifying interface boundaries, and configuring physical, communication, and control interfaces, enabling automatic code generation for implementing these interfaces across different computational hardware devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual implementation of component interfaces is used, then flexibility to handle different hardware topologies is achieved, but design time and productivity are reduced

Engineering Contradiction:

Improveflexibility to handle different hardware topologiesVSAvoiddesign time

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system enables self-service by automatically generating component interface code from block diagram models without requiring manual programming. The code generation process autonomously handles interface implementation across different hardware topologies, eliminating the need for manual re-implementation when hardware configurations change.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-defining interface specifications in the block diagram model before code generation. This allows the interface structure to be designed and validated in the graphical model, with the actual code being automatically generated later, ensuring adaptability is built-in from the design phase.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If manual re-implementation is performed when hardware topology changes, then interface correctness is maintained, but loss of time occurs

Engineering Contradiction:

Improveinterface correctnessVSAvoidre-implementation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system implements dynamics by enabling the block diagram model to adapt to different hardware topologies through configuration rather than structural changes. When hardware topology changes, the same block diagram model can be re-configured and re-targeted to new hardware without manual re-implementation, maintaining interface correctness while reducing time loss.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system uses copying by generating code from the block diagram model template. The interface specifications are copied from the graphical model representation into the actual implementation code automatically, ensuring consistency and correctness without manual re-programming when hardware changes.

Inventive Principle:

Principle #26Copying

3Productivity

If automatic code generation is implemented, then productivity is improved, but device complexity increases due to heterogeneous topologies

Engineering Contradiction:

Improvecode generation efficiencyVSAvoidheterogeneous topology complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the code generation process into distinct components: block diagram model parsing, interface specification extraction, and code generation. This modular approach handles heterogeneous topologies by treating each interface segment independently, managing complexity while maintaining high productivity through automated generation.

Inventive Principle:

Principle #1Segmentation

4Ease of operation

If model-based design approach is extended to component interfaces, then ease of operation is improved, but device complexity increases

Engineering Contradiction:

Improveinterface design simplicityVSAvoidinterface configuration complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system implements universality by creating a unified block diagram model representation that handles multiple interface types and hardware topologies through a single modeling paradigm. The same graphical modeling environment and code generation process works across diverse hardware configurations, simplifying operation while the underlying system manages the complexity of heterogeneous interfaces.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7523023B1Automatic generation of component interfaces for computational hardware implementations generated from a block diagram model

Publication Date: 2009.04.21 MATHWORKS INC

AI summary

Method and systems are provided for representing interfaces between electronic components of a computational hardware device in a graphical model and automatically generating code from the graphical model to implement one or more component interfaces in the computational hardware device. A graphical modeling environment provides for the definition of interface boundaries to represent component interfaces between electronic components associated with partitions of a graphical model design. A code building tool automatically generates code from the graphical model to build executable instructions to run the component interfaces on the electronic components of the computational hardware device.