GUI Flow Chart Mapping to System Diagrams
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current system diagrams and flow charts are often created separately, making it difficult to effectively convey the nature of interactions and relations within a system process due to spatial restrictions and complexity, which hinders the clear representation of interactions and their relation to system processes.
Innovation Solution
A method for mapping flow chart process descriptions to system diagram graphics through a graphical user interface (GUI) using a user interface controller, associator, combiner, and graphics processor, which integrates action/outcome text nodes with component name text nodes to generate semantically modified process description text branches, allowing for simultaneous display and interaction between flow chart and system diagram elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If system diagrams and flow charts are created separately, then each diagram can be detailed and comprehensive, but it becomes difficult to effectively convey the nature of interactions and relations within a system process
Solution Approach 1:
The patent combines system diagrams and flow charts into a single integrated diagram where system components are represented as graphical elements and process flows are shown through connected nodes. This merging allows both the system architecture and process interactions to be visualized simultaneously, eliminating the need to switch between separate diagrams and preserving all interaction information in one unified view.
Solution Approach 2:
The patent adds a process flow dimension to the traditional system diagram by incorporating directional connections and sequence indicators. This transforms the static system diagram into a dynamic representation that shows not only component relationships but also the temporal and logical sequence of operations, enabling comprehensive understanding of system processes without losing spatial organization.
2Area of stationary object
If spatial restrictions within the diagram are considered, then the diagram remains compact and manageable, but the nature of interactions and their relation to system processes cannot be easily conveyed
Solution Approach 1:
The patent segments the diagram into hierarchical levels where system components are divided into graphical elements with internal nodes representing sub-components. This segmentation allows complex interactions to be broken down into manageable sections while maintaining the overall system context, enabling detailed interaction representation without requiring excessive diagram space.
Solution Approach 2:
The patent implements nesting by placing process flow nodes within or adjacent to system component graphical elements. This allows multiple levels of detail to be contained within a compact structure, where clicking or expanding a component reveals its internal process interactions, effectively conveying interaction nature while maintaining diagram compactness through hierarchical organization.
3Loss of information
If the complexity of the system is fully represented, then the diagram provides comprehensive information, but it becomes difficult to convey the nature of interactions clearly
Solution Approach 1:
The patent applies local quality by differentiating the visual representation of different interaction types through varied connection styles, node shapes, and labeling conventions. Each interaction type (e.g., data flow, control signal, physical connection) has its own visual characteristics, allowing users to quickly understand interaction nature without overwhelming detail, while comprehensive information remains available through systematic visual coding.
Solution Approach 2:
The patent introduces intermediary elements such as labeled connection lines and annotation nodes that mediate between complex system components and user understanding. These intermediaries provide contextual information about interactions without requiring direct examination of complex component relationships, making the diagram easier to interpret while preserving complete interaction information through systematic labeling and annotation.
Data Source
AI summary
A method of graphically mapping actions to actors may include displaying a first UI element containing system diagram representative of a system diagram and a second UI element containing a list of contextually related actions through a user interface; operating branch creation logic, in response to receiving a first selection input through the user interface; operating branch merge logic, in response to receiving a subsequent selection input through the user interface; rendering a chart element from an action/outcome text node branch, in a third window of the user interface through operation of the graphics processor; and/or linking at least two chart elements in the third window based, in part, on hierarchical ranking of the associated ranked action/outcome text node branches through operation of the graphics processor.