Delayed Evaluation of Condition-Based Trees for Software Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software package updates face challenges during the evaluation phase due to unpopulated or unreliable leaf parameters in condition-based trees, which can lead to incomplete or inaccurate evaluation and structural issues.

Innovation Solution

A two-phase evaluation method is introduced, where first, information capable of immediate evaluation is processed, and second, information requiring delayed evaluation is preserved in a human-readable format until all necessary parameters are received, allowing for a second evaluation phase to generate a final update result.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If condition based trees are evaluated immediately during the build phase, then the update process can proceed efficiently, but unpopulated or unreliable leaf parameters may lead to incomplete or inaccurate evaluation results

Engineering Contradiction:
Improveupdate evaluation efficiencyVSAvoidevaluation accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary evaluation of condition based trees during the build phase to the extent possible with available information. It identifies and separates evaluable conditions from those requiring delayed evaluation, preparing the update material in advance while marking portions that need later verification with populated parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The evaluation process is segmented into two distinct phases: an initial evaluation phase during build that processes available information, and a delayed evaluation phase that processes conditions requiring populated parameters. This segmentation allows the system to proceed with updates using partial evaluation results while maintaining the option to refine evaluations later.

Inventive Principle:
Principle #1Segmentation

2Reliability

If all evaluation is delayed until parameters are populated, then evaluation accuracy improves, but the update process time increases significantly

Engineering Contradiction:
Improveevaluation accuracyVSAvoidupdate process duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary evaluation of condition based trees during the build phase to the extent possible with available information. It identifies and separates evaluable conditions from those requiring delayed evaluation, preparing the update material in advance while marking portions that need later verification with populated parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The evaluation process continues across multiple phases rather than being interrupted. The initial evaluation during build phase provides preliminary results that can be used immediately, while the delayed evaluation phase completes the process when additional parameters become available, ensuring continuous progress without complete re-evaluation.

Inventive Principle:
Principle #20Continuity of useful action

3Productivity

If unpopulated parameters are left in the update material, then the update can be applied faster, but the tree structure may contain unreliable information that influences evaluation

Engineering Contradiction:
Improveupdate application speedVSAvoidinformation reliability
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system extracts and separates unpopulated or unreliable parameter information from the main evaluation flow. It identifies conditions that depend on these parameters and isolates them for delayed evaluation, allowing the rest of the update material to be processed and applied without being blocked by missing information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces an intermediary mechanism that handles unpopulated parameters by marking them for delayed evaluation rather than blocking the entire process. This intermediary layer allows the update system to proceed with available information while providing a structured way to incorporate additional parameters when they become available.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10127034B1System, method, and computer program for delayed evaluation of condition based trees
Publication Date: 2018.11.13 AMDOCS DEV LTD
  • US10127034B1 patent drawing
  • US10127034B1 patent drawing
  • US10127034B1 patent drawing

AI summary

A system, method, and computer program product are provided for delayed evaluation of condition based trees. In use, an update to perform on a software product is identified. Additionally, update material is generated to utilize for updating the software product. Further, first information associated with the update material that is able to be evaluated is evaluated in a first evaluation phase. In addition, second information associated with the update material that requires delayed evaluation is identified. The second information that requires delayed evaluation is preserved in a human readable format. Furthermore, parameters required for evaluating the second information that requires delayed evaluation are received. Still yet, the second information that requires delayed evaluation utilizing the received parameters is evaluated in a second evaluation phase. Moreover, a final evaluation result is generated utilizing a result of the first evaluation phase and the second evaluation phase for updating the software product.