Application Design Plugin for Dependency Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software developers face inefficiencies in creating application designs within integrated development environments (IDEs) due to the time-consuming process of establishing dependencies between objects, often requiring modifications across multiple historical applications without clear awareness of interdependencies.

Innovation Solution

Implementing an application design plugin within the IDE that analyzes historical applications to identify and utilize existing dependencies, updating the user interface with design features and metadata to streamline the creation and validation of new or modified application designs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If developers manually establish dependencies between objects in historical applications, then application designs can be created, but the process is time-consuming and error-prone

Engineering Contradiction:
Improveapplication design creation speedVSAvoidtime for establishing dependencies
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of historical applications to extract dependency information before the developer needs to create a new application design. By pre-processing and storing dependency relationships from historical applications, the system enables rapid retrieval and reuse without requiring developers to manually re-establish these dependencies, thus resolving the time-consuming issue.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a virtual copy of dependency relationships from historical applications and presents them as reusable design features. Instead of manually recreating dependencies, developers can select and reuse pre-extracted dependency patterns, effectively copying successful dependency structures from the past to accelerate current development.

Inventive Principle:
Principle #26Copying

2Ease of manufacture

If developers modify historical applications without awareness of interdependencies, then modifications can be made, but errors in dependency management increase

Engineering Contradiction:
Improveease of modifying applicationsVSAvoiddependency management accuracy
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system provides feedback to developers about existing dependency relationships when they modify historical applications. By displaying dependency information and its impact on other components, the system enables developers to make informed modifications that maintain dependency integrity, preventing errors while preserving modification flexibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system introduces an intermediary layer that represents dependency relationships between applications. This intermediary dependency model acts as a mediator between developers and the complex inter-application relationships, allowing developers to modify applications while the intermediary layer ensures dependency constraints are maintained, thus preventing errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the IDE supports plugins for customizing the workspace, then functionality can be extended, but device complexity increases

Engineering Contradiction:
Improveworkspace customization capabilityVSAvoidIDE structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The dependency analysis plugin is designed as a universal component that can be integrated into the IDE without requiring changes to the core IDE structure. By implementing multi-functionality within the plugin (analyzing, extracting, presenting, and validating dependency information), the system extends functionality while keeping the overall device structure modular and manageable, thus resolving the complexity issue.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10157069B2Identifying and using dependencies in historical applications to generate application designs
Publication Date: 2018.12.18 ACCENTURE GLOBAL SOLUTIONS LTD
  • US10157069B2 patent drawing
  • US10157069B2 patent drawing
  • US10157069B2 patent drawing

AI summary

A device to execute an application design plugin associated with a user interface. The device may analyze, using the application design plugin, a set of historical applications to identify one or more dependencies included in the set of historical applications. The device may provide, to a storage device, historical application metadata relating to the one or more dependencies. The device may receive, via the user interface, a request to generate an application design. The device may update the user interface with design information that includes design feature metadata identifying the one or more dependencies. The device may determine that the application design is ready for validation. The device may validate the application design based on determining that the application design is ready for validation.