Application Model for Architectural Refactoring Complexity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing refactoring technologies focus on individual module complexity evaluation but lack support for architectural-level refactoring of large-scale applications, making it difficult to reduce overall complexity and quantify enhancement impacts effectively.

Innovation Solution

A method that generates an application model based on control flow and data dependency relations, evaluates architectural complexity using the Impact Scale, and identifies enhancement points to reduce complexity and quantify refactoring impacts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If refactoring is performed at the architecture level on an entire application, then the enhancement impact is highly effective and produces greater impact, but it is difficult to find locations for enhancement to achieve reduction in the complexity of the entire application

Engineering Contradiction:
Improveenhancement impactVSAvoidapplication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces manual architectural analysis with automated computer-based analysis. The system automatically generates application models from source code, evaluates complexity metrics, and identifies enhancement locations without requiring manual inspection of the entire application architecture.

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

Solution Approach 2:

The patent introduces an application model as an intermediary representation between the source code and the refactoring process. This model captures control flow and data dependency relations, serving as a bridge that enables systematic analysis and identification of enhancement points without directly manipulating the complex source code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If conventional technology evaluates complexity of individual modules, then modules of inferior quality can be identified, but no support is provided to the refactoring at the architecture level of an entire application

Engineering Contradiction:
Improvemodule complexity evaluationVSAvoidarchitectural-level refactoring support
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent merges individual module complexity evaluations into a unified application-level assessment. By combining control flow analysis and data dependency analysis across all modules, the system produces a comprehensive application model that enables architectural-level refactoring while retaining detailed module-level insights.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent adds the architectural dimension to module-level analysis. Instead of only evaluating modules in isolation, the system analyzes modules within the context of the entire application architecture, considering inter-module dependencies and control flows to identify enhancement opportunities at multiple levels simultaneously.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If locations for enhancement are found, then refactoring can be performed, but it is important that the enhancement impact be quantitatively evaluable in advance, which is also a difficult task

Engineering Contradiction:
Improveenhancement location identificationVSAvoidenhancement impact evaluation
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The patent performs preliminary evaluation of enhancement impact before actual refactoring is executed. The system calculates complexity metrics and identifies potential enhancement locations with their expected impact, allowing planners to assess and prioritize refactoring activities in advance without committing to specific changes yet.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8307326B2Method and apparatus for supporting application enhancement
Publication Date: 2012.11.06 FUJITSU LTD
  • US8307326B2 patent drawing
  • US8307326B2 patent drawing
  • US8307326B2 patent drawing

AI summary

A method includes generating an application model that represents a relation of connection based on a control flow relation and a data dependency relation between a module and data constituting an application, by analyzing a source code, evaluating complexity of the relation of connection that is represented by the application model generated in the generating, and outputting an enhancement point used in reducing the complexity evaluated in the evaluating.