Sequence Diagram to Architecture Diagram Transformation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Sequence diagrams provide high detail but struggle to maintain an overall view of logic interactions in complex systems, making it difficult to combine them into architectural diagrams that show system structure and logic flows effectively.
Innovation Solution
A system and method that transform sequence diagrams into architectural diagrams by identifying participants and messages, creating nodes and edges, and merging these diagrams to generate a master architecture diagram, allowing for navigation and updating based on changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If sequence diagrams are used to document system requirements and design interactions, then detailed interaction logic is captured, but overall system architecture view is lost
Solution Approach 1:
The patent segments the detailed sequence diagram information into two views: a high-level architecture diagram showing overall system structure and component groupings, and detailed sequence diagrams for specific interaction logic. This segmentation allows users to navigate between overview and detail as needed, resolving the contradiction between capturing detailed interactions and maintaining overall architecture visibility.
Solution Approach 2:
The patent introduces a hierarchical dimension to the diagram representation, where sequence diagrams are transformed into architecture diagrams that add a spatial/structural dimension. This allows the same information to be viewed at different levels of abstraction, with the architecture diagram providing the missing overall view while preserving links to detailed sequence diagrams for interaction logic.
2Adaptability or versatility
If multiple sequence diagrams are created to cover different scenarios, then comprehensive interaction coverage is achieved, but difficulty in combining them into unified architecture view increases
Solution Approach 1:
The patent merges multiple sequence diagrams into a unified architecture diagram by extracting common participants and their relationships. The system automatically combines information from multiple sequence diagrams, grouping participants into architectural components and showing their interconnections, thereby achieving comprehensive scenario coverage while simplifying the overall view.
Solution Approach 2:
The patent creates a transformed copy of sequence diagram information in the architecture diagram format. Rather than manually combining multiple sequence diagrams, the system generates an architecture diagram that copies and reorganizes the essential structural information from multiple sequence diagrams, making it easy to maintain and update.
3Area of stationary object
If high-level architecture diagrams are created to show system structure, then overall view is maintained, but detailed interaction logic is lost
Solution Approach 1:
The patent introduces an intermediary linking mechanism between architecture diagrams and sequence diagrams. The architecture diagram serves as an intermediary view that shows overall structure while maintaining hyperlinks or navigational connections to detailed sequence diagrams, allowing users to drill down from high-level view to detailed interaction logic as needed.
Solution Approach 2:
The patent creates a dynamic navigation system where the architecture diagram can be interactively explored. Users can select specific components or interactions in the architecture diagram to reveal corresponding detailed sequence diagrams, making the level of detail dynamically adjustable based on user needs rather than statically fixed.
4Reliability
If sequence diagrams are updated to reflect design changes, then accuracy of interaction logic is improved, but maintenance effort increases due to multiple diagrams
Solution Approach 1:
The patent creates a multi-functional system where a single architecture diagram serves multiple purposes: it provides overall system view, automatically generates from multiple sequence diagrams, and maintains consistency across all diagrams. Updates to the underlying sequence diagram data automatically propagate to the architecture diagram, reducing maintenance effort while improving accuracy.
Solution Approach 2:
The patent implements automatic feedback mechanisms where changes in sequence diagram data are detected and automatically reflected in the architecture diagram. The system monitors updates to sequence diagrams and triggers automatic regeneration of the architecture diagram, ensuring consistency without requiring manual maintenance effort.
Data Source
AI summary
A system including a processor; and a memory having stored thereon computer program code that, when executed by the processor, controls the processor to: receive data indicative of a plurality of sequence diagrams; for each of the plurality of sequence diagrams, generate a corresponding architecture diagram by: identifying a plurality of participants within the sequence diagram, transforming each of the plurality of participants into a plurality of nodes, identifying a plurality of messages identifying at least one message participant, and transforming the identified plurality of messages by establishing a single edge between respective nodes of the plurality of nodes corresponding to message participants identified by one or more messages of the plurality of messages; and merge the corresponding architecture diagrams of each of the plurality of sequence diagrams to generate a master architecture diagram.