Production Software Validation With Selective Synthetic Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software validation techniques are time-intensive and computationally expensive, often requiring validation of all aspects of a software application, even when only a portion has changed, and they do not efficiently address regulatory compliance in production environments.
Innovation Solution
A production system is configured to perform workflow steps, identify synthetic execution indicators, and generate validation tests within the production environment, allowing focused validation on regulated aspects while avoiding unnecessary revalidation of unregulated parts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional validation techniques are used to validate all aspects of a software application, then regulatory compliance is achieved, but validation time and computational costs increase significantly
Solution Approach 1:
The patent segments the software application into regulated and unregulated components, and further divides validation into synthetic execution validation for regulated portions and standard execution for unregulated portions. This segmentation allows selective validation of only necessary components, reducing overall validation time while maintaining compliance for regulated functions.
Solution Approach 2:
The patent applies partial action by performing validation only on portions of the software that require it (regulated components), rather than validating the entire application. The synthetic execution mode performs validation actions selectively, avoiding excessive validation of unregulated portions while ensuring adequate validation of regulated portions.
2Measurement precision
If a testing environment is established to mirror the production environment, then accurate validation testing is enabled, but computational costs and setup complexity increase
Solution Approach 1:
The patent creates a synthetic copy of the production environment within the same system by implementing synthetic execution modes that simulate validation conditions without requiring a separate physical testing environment. This synthetic copying approach maintains validation accuracy while eliminating the computational overhead of maintaining a duplicate environment.
Solution Approach 2:
The production system is designed to perform multiple functions: it can execute software normally for unregulated portions and switch to synthetic execution mode for regulated portions. This multi-functionality eliminates the need for a separate testing environment, as the same system handles both production and validation tasks differently based on the software portion being validated.
3Reliability
If all aspects of a software application are revalidated after changes, then compliance is maintained, but productivity and development speed decrease
Solution Approach 1:
The patent segments changes into regulated and unregulated modifications, allowing revalidation to be applied only to regulated portions that require it. Unregulated changes can be implemented without triggering full revalidation sequences, thereby maintaining compliance where necessary while preserving development speed for non-critical updates.
Solution Approach 2:
The validation process is made dynamic by automatically determining which portions of the software require revalidation based on the nature of changes detected. The system adapts the validation scope in real-time, switching between synthetic execution and standard execution modes as needed, rather than applying a static full-revalidation approach to all changes.
Data Source
AI summary
A production system is configurable to obtain a set of computer-executable instructions that are operable to cause the production system to perform a set of workflow steps. The production system is also configurable to obtain implementation data associated with the set of workflow steps and identify a set of synthetic execution indicators associated with the set of workflow steps. The production system is configurable to (1) generate a validation test based on the implementation data, the set of synthetic execution indicators, and the set of workflow steps, and (2) perform the validation test by synthetically executing the one or more workflow steps on the production system using inputs generated from the implementation data, recording synthetic execution output in a synthetic execution data repository, and refraining from recording the synthetic execution output as production transaction output on a production transaction data repository.