PLC Class Diagram Visualization for Object-Oriented Relationships
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques for visualizing project structures in programmable logic controller (PLC) projects do not effectively display object-oriented components and relationships, as they are not compliant with the latest standards introduced by IEC 61131-3 Part 3.
Innovation Solution
A programming assisting program and device that acquires component and relationship information, generates a class diagram to represent the project structure, and updates the display format to distinguish the level of relationships between selected components, allowing for easier identification of object-oriented components and relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a tree diagram is used to display project structure, then the basic component relationships can be visualized, but object-oriented components and relationships cannot be properly identified
Solution Approach 1:
The patent changes the display parameters from a traditional tree diagram format to a class diagram format that supports object-oriented notation. This includes displaying inheritance relationships, interface implementations, and component compositions using standard UML class diagram symbols and conventions, thereby preserving and visualizing object-oriented relationship information that would be lost in a simple tree structure.
Solution Approach 2:
The patent adds a new dimensional aspect to the visualization by introducing multiple relationship types (inheritance, implementation, composition) that can be distinguished through different visual representations. This allows the system to display not just hierarchical structure but also the nature of relationships between components, enabling proper identification of object-oriented design patterns.
2Loss of information
If all relationship information is displayed in a class diagram, then complete project structure is visible, but the level of relationships between components becomes difficult to distinguish
Solution Approach 1:
The patent applies local quality by differentiating the visual representation of relationships based on their specific type and level. Different line styles, arrow types, or formatting conventions are used to indicate different relationship levels (e.g., inheritance vs. implementation vs. composition). This allows the display to remain comprehensive while making relationship levels easily distinguishable through localized visual variations.
Solution Approach 2:
The patent introduces dynamic interaction capabilities where users can select specific components or relationships to view in detail. The display format can be updated dynamically to highlight selected relationships or filter by relationship level, allowing users to navigate the complexity interactively rather than presenting all information statically at once.
3Ease of operation
If traditional project structure visualization is used, then simple hierarchy is displayed, but interaction for selecting and analyzing specific components is limited
Solution Approach 1:
The patent implements feedback mechanisms where user selections of components or relationships trigger updates to the class diagram display. When a user selects a component, the system provides feedback by highlighting related components, showing relationship details, or filtering the view to display only relevant relationships. This interactive feedback loop enables detailed analysis of specific components while maintaining the overall project structure context.
Data Source
AI summary
A programming assisting program causes a computer to function as a project information acquirer that acquires component information indicating a plurality of components included in a project including object-oriented components and relationships, and acquiring relationship information indicating relationships between the plurality of components, a generator that generates a class diagram indicating a structure of the project based on the acquired component information and the acquired relationship information, a display that displays the generated class diagram on a screen, and a display updater that receives a selection operation of selecting a component included in the class diagram displayed on the screen, and updates a display format of the class diagram such that a level of a relationship between the component selected in the selection operation and another component is distinguishable.