Non-editable Topic Diagrams for UML Model Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software development, UML class diagrams require manual updates when the underlying model changes, leading to inconsistencies and conflicts in team development environments due to the need to persist graphical notation elements, which can cause version control issues.

Innovation Solution

A computer method and system that generates a non-editable topic diagram based on a query, where only the query information is stored, allowing the diagram to regenerate itself from scratch, eliminating the need for persistent notation elements and reducing version control conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If diagram notation elements are persisted to maintain diagram consistency, then diagram reliability is improved, but version control conflicts increase

Engineering Contradiction:
Improvediagram consistencyVSAvoidversion control conflicts
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the diagram generation logic from the diagram file itself and places it in a separate model element. The diagram is no longer stored as persistent notation elements but is regenerated from the model element, separating the diagram representation from the source of truth.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of storing the original diagram notation elements, the system creates a copy of the diagram generation capability through a model element that can be serialized and stored. This model element contains the information needed to regenerate the diagram, serving as a template rather than a direct copy of the diagram itself.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If manual diagram updates are performed to maintain synchronization, then diagram accuracy is improved, but productivity decreases

Engineering Contradiction:
Improvediagram accuracyVSAvoiddevelopment efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system implements self-service by automatically regenerating the diagram from the model element whenever the model changes. The diagram generation process is automated and does not require manual intervention, allowing the diagram to update itself in response to model changes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes a feedback mechanism where changes to the model element automatically trigger regeneration of the diagram. This closed-loop system ensures that the diagram continuously reflects the current state of the model without requiring manual review or update.

Inventive Principle:
Principle #23Feedback

3Duration of action of stationary object

If diagram files are stored for version control, then diagram persistence is improved, but device complexity increases

Engineering Contradiction:
Improvediagram persistenceVSAvoidsystem complexity
Core Design Contradiction:
Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The patent extracts the diagram representation functionality from the diagram file and relocates it to a model element. This separation allows the diagram to be generated dynamically rather than stored statically, simplifying the system architecture by eliminating the need for complex diagram file management.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS7669137B2Computer method and apparatus for representing a topic in a software modeling system
Publication Date: 2010.02.23 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7669137B2 patent drawing
  • US7669137B2 patent drawing
  • US7669137B2 patent drawing

AI summary

A computer method and apparatus for visual modeling software programs represents a topic by providing a respective topic diagram. The topic diagram is non-editable and has non-persisting notation data. The topic diagram demonstrates a respective set of relationships between one or more given elements representative of the subject topic. The topic diagram is derived based on a query which saves search criteria and information that enables an editor to generate the diagram notation data. There are different topic providers for different queries. A topic service manages the topic providers and processes client calls (requests) regarding specific context and query. Queries are end-user customizable and are extensible per topic.