Visual Domain Model Canvas with Annotated Stencils

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional domain model creation is cumbersome and time-consuming, requiring deep knowledge of the domain model framework and is difficult to integrate existing models into visual frameworks, necessitating imperative code that does not provide additional features.

Innovation Solution

The implementation of canvas technologies that allow for efficient integration of domain models into visual frameworks, providing real-time feedback and enabling developers to modify and develop source code without in-depth knowledge of specific software code, using annotated classes with definitions, properties, and rules to visually represent and modify stencil relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional visual representation tools are used to create domain models, then users can create diagrams to show relationships between elements, but the process is cumbersome and time-consuming requiring deep knowledge of the framework

Engineering Contradiction:
Improveease of domain model creationVSAvoidtime required for domain model creation
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system provides pre-defined stencils that represent common domain model elements and relationships. Users can drag and drop these pre-configured stencils onto the canvas instead of creating diagrams from scratch, significantly reducing the time and complexity required for domain model creation while maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If conventional tools require imperative code for integration, then existing models can be integrated into visual frameworks, but the code does not provide additional features and increases complexity

Engineering Contradiction:
Improveintegration capability of domain modelsVSAvoidcomplexity of integration code
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces a visual canvas as an intermediary between domain models and visual frameworks. Instead of requiring direct imperative code integration, the canvas serves as a mediation layer that handles the integration automatically through visual drag-and-drop operations, eliminating complex code while maintaining adaptability and versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical system of imperative code integration with a visual interaction system. Users interact with domain models through visual manipulation on the canvas rather than writing and executing code, substituting the mechanical coding process with a more intuitive visual mechanism that provides additional features without increasing complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If domain models are created without visual feedback, then development process is simpler, but developers cannot see real-time changes and violations

Engineering Contradiction:
Improvevalidation of domain model relationshipsVSAvoidcomplexity of visual feedback system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements real-time visual feedback by automatically detecting rule violations when users drag and drop stencils onto the canvas. The system provides immediate visual indication of violations through color changes or other visual cues, enhancing reliability of domain model relationships without adding significant complexity to the overall system.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10817268B2Framework for modeling with domain model capabilities
Publication Date: 2020.10.27 RED HAT INC
  • US10817268B2 patent drawing
  • US10817268B2 patent drawing
  • US10817268B2 patent drawing

AI summary

Methods, systems, and computing systems are provided for providing a visual representation of a domain model. An example method includes providing a class corresponding to a first stencil. The class is annotated to include a definition, a property, and a rule. A visual representation of the first stencil is provided in a graphical user interface, where the annotated definition and the annotated property modify the visual representation that is displayed. When the visual representation is moved, by a user, in relation to a second stencil, a determination is made, based on the location of the moved first stencil and the second stencil, that the first stencil violates the rule. The visual representation of the moved first stencil is modified to indicate the violation of the rule.