Graphical Modeling Class Hierarchy for System Variant Inheritance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional graphical modeling environments require users to create separate models for each member of a family of related systems or include complex conditional logic, leading to duplication of effort and error-prone models that are difficult to maintain and create.

Innovation Solution

A graphical modeling environment that allows users to define a hierarchy of user-defined classes of graphical objects, enabling inheritance, modification, and polymorphism to simplify the creation and simulation of complex systems by capturing common features and variations in a single model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate models are created for each member of a family of related systems, then each system can be modeled independently, but considerable duplication of effort occurs

Engineering Contradiction:
Improvemodel accuracyVSAvoidmodel creation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a parent class model that can serve multiple child systems simultaneously. The parent class contains common elements, parameters, and behavior that are inherited by multiple child classes, allowing a single model to fulfill multiple functions for different system variants.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent creates a hierarchical structure where child class models are nested within the parent class framework. The parent class acts as a container that holds shared resources and definitions, while child classes extend or specialize specific aspects, creating a nested organizational structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Adaptability or versatility

If complex conditional logic is included in a model to account for variations in behavior among related systems, then system variations can be represented, but the model becomes complex and error-prone

Engineering Contradiction:
Improvesystem variation representationVSAvoidmodel complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the model into distinct hierarchical levels: a parent class containing common elements and child classes containing specific variations. This segmentation allows system variations to be represented through class structure rather than conditional logic within a single monolithic model.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to the model organization, moving from a single-level model with conditional logic to a multi-level class hierarchy. This dimensional change allows variations to be managed through inheritance relationships rather than temporal or spatial conditions.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of manufacture

If separate models are created for each system variant, then each model can be simple and maintainable, but duplication of effort increases and maintenance becomes difficult

Engineering Contradiction:
Improvemodel maintainabilityVSAvoidnumber of models
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent implements a copying mechanism where child classes automatically inherit elements from the parent class. This allows the parent model to serve as a template that is copied and specialized for each child system, reducing the need to manually recreate common elements for each variant.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The parent class model is designed to be universal, serving as the foundation for multiple child systems. By making the parent class multi-functional and highly configurable, the need to maintain separate models for each variant is reduced, as changes to common behavior can be made in a single location.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9038016B2User-defined hierarchies of user-defined classes of graphical objects in a graphical modeling environment
Publication Date: 2015.05.19 MATHWORKS INC
  • US9038016B2 patent drawing
  • US9038016B2 patent drawing
  • US9038016B2 patent drawing

AI summary

The present invention allows a user to graphically define a hierarchy of user-defined, executable classes of graphical objects that can be implemented in a graphical model. The present invention supports the features of inheritance, abstraction and polymorphism. Further, descendant classes of graphical objects can graphically extend the behavior and/or structure of ancestor classes of graphical objects.