Modular Software Framework for Asynchronous Code Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software systems face challenges in processing large data sets and modifying complex code due to excessive system resource consumption and difficulty in identifying and modifying asynchronous execution structures, which leads to significant overhead in normalization processes.

Innovation Solution

A framework system that separates execution flow and data flow, converting software code into modular code with graphical representations, allowing users to modify modular code which automatically updates the associated software code, and enabling synchronous, asynchronous, or combined execution modes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software code is written in a single large file to handle complex query processing, then the system can process large data sets, but the code becomes difficult to modify and maintain

Engineering Contradiction:
Improvequery processing capabilityVSAvoidcode modification difficulty
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent divides the single large software file into multiple smaller modules, each handling specific query processing tasks. This segmentation allows the system to maintain query processing capability while making individual modules easier to modify and maintain without affecting the entire codebase.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a framework layer that acts as an intermediary between the user and the query processing system. This framework provides standardized interfaces and abstractions, allowing users to modify query logic through the framework's modular components rather than directly editing large monolithic code files.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If asynchronous execution structures are used to improve job processing efficiency, then concurrency is improved, but identifying and modifying these structures becomes problematic

Engineering Contradiction:
Improvejob processing efficiencyVSAvoidasynchronous structure identification
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The framework introduces intermediary components that wrap and manage asynchronous execution structures. These intermediaries provide standardized interfaces that make asynchronous operations visible and manageable, allowing developers to identify and modify asynchronous structures through the framework's consistent abstraction layer rather than dealing with scattered async code.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The framework implements feedback mechanisms that track and report on asynchronous job execution. This feedback system provides visibility into asynchronous structures through standardized events and interfaces, making it easier to identify, monitor, and modify asynchronous execution flows without losing the concurrency benefits.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If files are normalized for flow control programming to enable passage to different machines, then system compatibility is improved, but significant overhead is introduced especially when large numbers of files are passed

Engineering Contradiction:
Improvesystem compatibilityVSAvoidnormalization overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The framework performs normalization preparations in advance by establishing standardized data structures and protocols at the framework level. By pre-configuring compatibility layers and standard interfaces, the system reduces the need for repeated normalization operations when files are passed between machines, thereby reducing overhead while maintaining compatibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The framework implements universal, machine-agnostic data structures and communication protocols that work across different systems without requiring extensive normalization. This multi-functional approach allows the same standardized interfaces to handle file passage between various machines, reducing the overhead associated with repeated normalization processes.

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

Data Source

PatentUS8806433B2Method and framework for software development
Publication Date: 2014.08.12 REPUTATION COM
  • US8806433B2 patent drawing
  • US8806433B2 patent drawing
  • US8806433B2 patent drawing

AI summary

Presented are systems and methods of operation for a framework system. The framework system acquires software code and modularizes the software code to create an associated modular code, wherein the modular code is composed of a plurality of synchronous and asynchronous modular elements. The framework system modifies the modular code using a modular element, and automatically modifies the software code based on the modified modular code.