Decision Code Module Testing Coverage Monitor
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex decision entities with numerous rules are often only partially tested due to the large number of permutations, making it difficult to determine the validation status of decision-making software projects.
Innovation Solution
A coverage monitor subsystem generates test status identifiers based on test status variables, transmitting this data to a reporting subsystem which displays a graphical representation of tested and untested decision code modules, aiding in visualization and prioritization of testing efforts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If comprehensive testing of all rules in a decision entity is performed, then validation completeness is improved, but testing time and complexity increase exponentially
Solution Approach 1:
The patent segments the decision entity into individual rules and groups them by decision code module. Instead of testing all rules uniformly, the system divides testing into manageable units and tracks coverage at the rule level within each module, allowing selective prioritization of testing efforts based on risk and importance.
Solution Approach 2:
The patent implements partial testing by allowing users to select specific decision code modules for testing rather than requiring comprehensive testing of all modules. The system provides visual indicators showing which modules have been tested and which remain untested, enabling staged validation approaches where critical modules are tested first.
2Reliability
If comprehensive testing of all rules in a decision entity is performed, then validation completeness is improved, but device complexity increases
Solution Approach 1:
The patent introduces a coverage monitor subsystem as an intermediary between the testing framework and the reporting subsystem. This intermediary automatically collects test status variables from decision code modules, processes the data, and generates visual reports, thereby simplifying the overall testing system architecture and reducing the complexity burden on users.
Solution Approach 2:
The system implements self-service through automatic tracking of test status variables within decision code modules. The coverage monitor subsystem automatically detects which rules have been tested and which remain untested, eliminating the need for manual tracking and reducing the complexity of test management.
3Measurement precision
If test status tracking is implemented at the rule level, then measurement precision is improved, but data processing complexity increases
Solution Approach 1:
The patent uses test status variables as digital copies or proxies for the actual testing state of rules. Instead of complex data structures to track testing status, the system uses simple boolean-like variables within each rule that indicate whether they have been tested, significantly simplifying data processing while maintaining precise tracking capability.
Data Source
AI summary
A coverage monitor subsystem receives an electronic message from a project data object over a communication network. The project data object includes decision code modules that have rules with a corresponding test status variable. The test status variable indicates whether the rule has been tested. The coverage monitor subsystem generates a test status identifier. The test status identifier indicates the decision code modules as tested decision code modules when all of the rules for the corresponding decision code modules have been tested. The coverage monitor subsystem transmits test status data to a reporting subsystem. The test status data includes a first identifier identifying the tested decision code modules and a second identifier identifying the decision code modules that are not tested. The reporting subsystem displays, at a computer display, a graphical representation based on the first identifier and the second identifier.