Automated Target Application Composition Engine
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of transitioning from a proposed application architecture to a target sample application is labor-intensive and error-prone, often failing to demonstrate business value, requiring manual adjustments and additional skills for the sales team to convince clients of the proposed solution's validity.
Innovation Solution
A computer-implemented process that receives a logical topology diagram, locates part type information, identifies application parts, determines integration dependencies, consolidates parts into an application structure, and builds a target application, reducing errors and time through automated composition and exclusion of unnecessary parts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If manual process is used to transition from proposed architecture to target application, then flexibility and customization are possible, but labor intensity and error rate increase
Solution Approach 1:
The system performs automatic composition of target applications using the composition engine that retrieves parts from repositories, determines integration dependencies, and assembles the target application structure without manual intervention, allowing the system to serve itself in creating demonstrations
Solution Approach 2:
The patent replaces manual mechanical processes with automated computer-implemented processes. The composition engine substitutes human analysts by automatically retrieving parts, determining dependencies, and assembling target applications through algorithmic processing rather than manual configuration
2Reliability
If manual process is used to transition from proposed architecture to target application, then complex configurations can be handled, but error rate increases
Solution Approach 1:
The system determines integration dependencies automatically by analyzing relationships between parts and their required configurations. The composition engine uses feedback loops to verify that selected parts meet integration requirements and adjusts the composition accordingly, ensuring reliability without manual verification
Solution Approach 2:
The composition engine acts as an intermediary between the proposed architecture and the target application. It mediates the complex transition process by automatically resolving dependencies, selecting appropriate parts from repositories, and assembling the final structure, thereby reducing errors while handling complexity
3Manufacturing precision
If correct products are selected for target application, then product accuracy is improved, but business value demonstration may still fail
Solution Approach 1:
The system dynamically adjusts the target application composition based on the proposed architecture and business value requirements. The composition engine continuously evaluates integration dependencies and part selections, adapting the configuration to ensure both product accuracy and business value demonstration rather than using static product lists
4Productivity
If automated composition is implemented, then time and errors are reduced, but system complexity increases
Solution Approach 1:
The composition system is segmented into distinct functional modules: a part repository storage component, a composition engine with dependency determination logic, and a target application assembly component. This segmentation manages system complexity by organizing functions into independent, manageable units that can operate autonomously
Data Source
AI summary
An illustrative embodiment of a computer-implemented process for target application creation receives a representation of a logical topology diagram for an application architecture to form a source input, locates part type information in a part type dictionary using the source input, locates application parts in an application parts repository for each located part type and composes a subset of identified parts. The computer-implemented process further determines whether integration dependencies are met and responsive to a determination that integration dependencies are met, consolidates parts into an application structure, determines whether to exclude parts and responsive to a determination to not exclude parts, builds a target application.


