System Testing Intermediate Value Determination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for computing intermediate and output values in system testing require all input values to be defined or assume default values, leading to complex and time-consuming processes that make it difficult to determine which system outputs are impacted by specific inputs and whether they are desired for operation.
Innovation Solution
A method and system that determine system intermediate values and output values unambiguously from defined system inputs, without assuming or using default values for undefined inputs, and provide coverage of functional characteristics based on these defined inputs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all input values are defined or default values are assumed for testing, then the system can execute testing scenarios, but the complexity and time required to determine impacted outputs increases significantly
Solution Approach 1:
The patent segments the system outputs into two distinct categories: impacted outputs (those affected by defined inputs) and unimpacted outputs (those affected only by undefined inputs or defaults). This segmentation allows testers to focus analysis only on impacted outputs, eliminating the need to review all system outputs and significantly reducing the time required to determine which outputs are affected by specific inputs.
Solution Approach 2:
The patent introduces an intermediary computational process that traces the dependency relationship between defined inputs and system outputs. This intermediary mechanism automatically identifies and flags only those outputs that are impacted by the defined inputs, serving as a mediator between the test inputs and the comprehensive output set, thereby reducing manual analysis time while maintaining testing reliability.
2Loss of information
If all system outputs are generated regardless of input definition status, then complete system behavior is captured, but it becomes difficult to determine which outputs are impacted by specific inputs
Solution Approach 1:
The patent segments the output analysis by distinguishing between impacted and unimpacted outputs. This segmentation maintains complete system behavior coverage by considering all outputs, but simplifies the testing complexity by clearly identifying which outputs are actually impacted by the defined inputs. Testers can see the full system behavior while focusing analysis only on relevant impacted outputs.
Solution Approach 2:
The patent extracts and isolates the subset of outputs that are impacted by defined inputs from the complete set of system outputs. This extraction process removes the complexity of analyzing all outputs by separating out only those that are relevant to the current test scenario, while still maintaining awareness of complete system behavior through the structured identification of impacted versus unimpacted outputs.
3Productivity
If default values are assumed for undefined inputs, then testing can proceed, but it is time-consuming to validate whether impacted outputs are desired
Solution Approach 1:
The patent implements a feedback mechanism that provides clear indication of which outputs are impacted by defined inputs versus those affected by default values. This feedback allows testers to quickly validate whether impacted outputs match expected behavior without having to manually trace through all outputs. The system automatically feeds back information about output impact status, reducing validation time while maintaining testing productivity.
Data Source
AI summary
In one example, a method includes receiving one or more test scenarios based on requirements for a system under test having one or more inputs, wherein a value for at least one input of the one or more inputs is undefined for at least one test scenario of the one or more test scenarios. The method further includes determining system intermediate values and system output values that are unambiguously derivable from defined system inputs for the one or more test scenarios. The defined system inputs are defined in the one or more test scenarios and not assumed or default input values. The method further includes determining coverage of one or more functional characteristics of each function of the system under test executed based on the defined system inputs. The method further includes validating the determined system output values that are unambiguously derivable from the defined system inputs.